Co-Authors-Plus
Co-Authors-Plus copied to clipboard
Automattic
Selecting an author does not populate the form field
Hi, I am unable to repro this, despite lots of attempts to mimic the exact browser, OS, wp user, etc. See video. Any ideas?
I did a screenshare with the client and did not observe any console errors or network errors. He is located in India and is working in a large law firm office, so I can imagine there may be some unusual network factors. I'm stumped.
https://vimeo.com/416414068#t=30s
I'm having the same issue on a live site. I've had the co-authors plugin installed on this site for years and it always worked. I started having this issue a while back, at least 6 months. It's not consistently a problem and I haven't figured out when it is and when it isn't. Sometimes it works as expected. Sometimes, it works as in the video above. Sometimes I can still change or add an author when I choose quick edit, sometimes the only the I can do is disable co-authors plus plugin if I want to simply change the author. The problem is both with posts and CPTs. I ran into it again today. Not for the first time, I disabled all plugins (except for CAP), switched to TwentyTwenty, cleared the cache, did a hard refresh, nothing helped. I too saw nothing unusual in the console. I'm using WP 5.4.1, but have had this with the last few versions of WP. And the weird thing is that in the development version of the site (which is on a different server though) and on a local version of the site, I cannot reproduce the problem either. I switched to a different browser (Firefox to Chrome) and switched to a different admin account in WP, the problem persists. I'm a bit at a loss for where else to look.
My work around, that works consistently, is doing it in IE11 or in the Samsung browser on my phone. I cannot get it to work in any Chrome-based browser or in Firefox. Although, as I said, on the staging site and on the local site it works as expected (the author actually gets assigned when clicked) in all Chrome-based browsers and Firefox. I'm lost.
Other workarounds: Keyboard navigation probably works.
I also hacked a wordpress core file to extend the time before an input blurs:
https://core.trac.wordpress.org/browser/trunk/src/wp-includes/js/jquery/suggest.js?rev=36287#L37
That line is definitely a factor but ultimate I don't know if it's helping my client since he no longer responds to me as he's sick of this issue.
Oh! Thank you! Yes, that definitely works and I love keyboard navigation so that makes life easier. Interesting about input blurs... EDIT: the keyboard navigation works only sometimes, not consistently. Also, once I get it to work normally in IE11 or something, if I then test it in FF or Chrome it will work there too, until I save the post/cpt and then it stops working again.
I'm unable to reproduce this problem using WordPress 5.7, Co-Authors Plus 3.4.5, macOS 11.2.1 and the following browsers:
- Brave 1.22.71
- Chrome 89.0.4389.114
- Firefox 87.0
- Opera 75.0.3969.149
- Safari 14.0.3
In my case, it also works consistently both with keyboard and mouse.
Maybe someone who's able to reproduce this problem consistently can post the specifications for a test case here.
For the last several months I've had no issues using keyboard navigation. I'm wondering now if the edit in my last comment was just me doing something wrong (using tab instead of enter or vice versa, etc). Mouse still doesn't work on the live site and still works on the staging site with the same plugins and the same theme, and I haven't been able to reproduce it on any other site either. I'm using all the same browsers and Edge 89.0.774.68 and Vivaldi 3.7.2218.52. WordPress 5.7, Co-Authors Plus 3.4.5. Windows 10 Home 20H2. Would it be helpful to look at server specifications? And if so, anything in particular?
Hi niels, this issue is still repro-able in any modern browser I have tried. The key is to keep the mouse button pressed down for a bit longer than you ordinarily might (some people happen to just be slow-clickers). This is why in my comment above from May 29, extending that time limit before the input blurs, resolves the issue for most users. Really it's an issue with that js file. Makes no sense to blur an input based on a user clicking on it for x milliseconds.
Thanks for your replies, @Blindeman and @scofennell. As this problem seems to appear on Windows, someone with access to a Windows machine will have to work on this issue. As I'm using Mac, I'm afraid, I'm unable to address this problem as it does not appear on my end.
Hi Niels, this problem is repro-able for a wide variety of mac users, myself included. Did you try clicking slowly on the ajax author result? As in, keeping the mouse button down for a second or two? That's really the issue.
I do see the problem now, @scofennell. It indeed appears when clicking and holding the mouse for at least 2s.
Thanks very much for taking another look. To be clear though, I am seeing a failure much faster than 2s. I am seeing a failure after whatever time value is provided here (default core is 200ms):
https://core.trac.wordpress.org/browser/trunk/src/wp-includes/js/jquery/suggest.js?rev=36287#L37
Which makes this whole thing much harder to approach, since that's a very old core include.