I can no longer select text or lines of code without the mouse scrolling all the way up or down the moment I try selecting anything.
It never used to do this. Within the editor is the only place on my website or computer where I have this problem.
This problem is very annoying and has made it impossible to select text by dragging over it.
I find that the problem will sometimes go away after I close the section I’m working on and go back in. Refreshing, saving, or initially entering the page causes it to happen again.
Hi, thanks for reaching out.
I don’t think we’ve come across an issue like this before. There are a few ways you might troubleshoot this, here are a few options:
* Does the issue persist in another browser?
* Does the issue persist if you temporarily deactivate all plugins not authored by SiteOrigin?
* Does the issue persist if you temporarily switch to the Twenty Twenty theme and deactivate all non-SiteOrigin plugins?
Let us know how the above goes and we’ll take it from there.
I was asking if you might have seen the issue before and might have known what it could have been. I guess you haven’t so I’m going to try troubleshooting it my own way.
It’s happened a few times now and it isn’t my only issue with the editor. Most of the time the visual editor refuses to load, and it removes images I had just inserted into the page, after saving.
I have the feeling it has to do with a script not loading when it should. Refreshing the page usually fixes things. So disabling plugins and switching themes and browsers won’t help to show the error if there is one.
I get for the average user that is the easiest troubleshooting method. But it’s also a costly only, that’s not very friendly to the live site.
I probably shouldn’t have bothered asking here.
I haven’t come across an issue where the mouse scrolls uncontrollably when selecting text.
The first part of a plugin conflict takes a minute or two, you’re just checking for a working baseline in the first part of the test. You can use a maintenance mode plugin and keep it active during the test. If a working baseline isn’t found then the test is over.
Not all errors create warnings or errors in the JavaScript console or PHP error log so there are times where it’s necessary to check for a working baseline, if a working baseline can be found you can work from that point until the issue reoccurs to find the source.
If the SiteOrigin Editor or other widgets aren’t loading normally there might be a JavaScript error on the page, there might also be PHP errors.
Possible JS errors:
To investigate JavaScript errors on the page, edit the page in question, recreate the issue (if possible) and then open the browser console, here is how https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis.
Possible PHP errors:
You can also enable
WP_DEBUG
andWP_DEBUG_LOG
in your wp-config.php file. If you set WP_DEBUG_DISPLAY to false errors won’t be logged on the site front end. WithWP_DEBUG_LOG
set to true the debug.log will be written to the wp-content folder. You can check the log file for any issues. https://wordpress.org/support/article/debugging-in-wordpress/.There are no javascript errors
.
I have one repeating php error that I can’t trace. I can’t seem to find what specifically is causing it because the function isn’t the source of the error.
PHP Notice: Trying to get property ‘post_type’ of non-object in /home/hlfadmin/public_html/wp-includes/class-wp-query.php on line 4171
I doubt this is the forum for errors like these though.
Yeah, that’s tough to diagnose. You’d need to try to look at which plugins might be using post_type and work from there. If you have a custom theme or plugin and have used post_type, that’s a logical place to begin the search.
Ref: https://stackoverflow.com/questions/14930499/wordpress-notice-trying-to-get-property-of-non-object
For the Editor and mouse issues, it’s up to you how to approach troubleshooting the problem. For the mouse issue, I’d try other browsers, perhaps another computer to see if the issue is local to a browser or a computer. For the Editor issue, I’d seek out a baseline by temporarily switching to Twenty Twenty theme and temporarily deactivating all non-SiteOrigin plugins, check if the issue resolves. This is how I’d approach the issue.