-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author picker doesn't default to current author #5072
Comments
I can see a potential for people accidentally saving a post as someone else. and given the politics of some organisations, that could be a big content issue. Certainly should default to the person who is editing |
I'm not able to reproduce this issue personally, I think it's probably related to the fact that this website has more than 100 authors which is the limit of the current API. Is this the case here? In which case the solution should be to work on a paginated selector somehow. Maybe scrolling could fetch other pages or something? In addition to fetching the current author initially. |
I can reproduce this on any site. Even with 2 users, it only shows the first user selected alphabetically. The issue is about defaults, it should default to show the existing user no matter how many authors. |
I didn't reproduce in my testings but I'll take another look. |
I believe I can reproduce this problem. In my development environment two requests are sent to the server. The second is the meta box request
This request contains the original value for the post_author. ( post_author=2 in my example ) Both requests update the post, but the second one trumps the first. Below are traces of the SQL update statements.
Meta box update
The result is that the Author isn't updated. Proposed solution - pass the latest value for the Author field as post_author. |
Good exploration @bobbingwide we had a similar issue with other fields (comment and ping status), we should probably update the additional fields here when saving the meta boxes https://github.com/WordPress/gutenberg/blob/master/edit-post/store/effects.js#L64-L67 |
While you're there check the spelling of overriden. L62 :-) |
I wasn't testing with metaboxes. |
I'll have to raise a separate issue then. With regards to your problem. |
Perhaps I don't understand the problem. When logged in as |
It should be fixed with #5438. I wasn't able to reproduce the issue anymore. Can you confirm? |
In latest version author name is cut. 1/3 of admin author name (bottom) is cut, outside dropdown select box.
|
Can you share a screenshot? Ideally, with developers console enabled so we could see what styles get applied? I couldn't reproduce locally. I asked @jasmussen about the same and he also didn't see the issue. |
Difficult to make screenshots with much of inspector visible. Even when positioned right, whole height.
So, previous version OK, last version not OK. I will test it now with Plugin organizer. Disable all plugins in backend. Edit: Disabled all plugins in backend, except Gutenberg. Still cut out. Tested with one of the default themes too. |
Possibly the same: #6326 |
Thanks for the screenshot, and yeah that other ticket is definitely the same. I know what it is and will fix monday. Thanks! |
Hi @jasmussen. Notice Title of Article. I did not touch it. Is there any smart way to prevent look like this ? Does not look very professional. |
Hmm yeah I'll take a look at that too. |
Thank you. Error console is clear, no errors. |
Thanks, I moved your comments to #6326 to make it easier to track since this issue is closed 👍 |
I can reproduce, occasionally, when typing a very long title and slowly resizing the screen. It seems like a bug in the autosizing textarea component we use, one that's exclusive to edge. If you find out more what makes this appear, I'd appreciate you open a ticket with as much info as you can provide. Thanks @StaggerLeee |
Difficult for me. As CSS only solutions are mostly bad hacks. |
The dropdown shows like this:
Whilst it doesn't save to a different author until you save it, not showing the author that is writing seems a little odd as an experience. Could this default to the logged in user? I know this may come from core but it feels like an awesome enhancement and visual indicator of who is writing.
The text was updated successfully, but these errors were encountered: