akiai
Forum Replies Created
-
Thanks for the response.
localStorage.clear()didn’t do the job. Same problem persists in both Chrome and Firefox.It’s not a major problem as I just remove the
display: nonestyling if I ever need to see the errors. Stylesheet being referenced is indeed from Query Monitor and not anywhere else. I’ve also disabled all other plugins and tested.Very strange!
To add some further information:
I have just switched my local version to a vanilla TwentyTwenty theme, disabled all plugins and placed the following code:
if ($test) { return; }The 1 php error shows but again the field is blank.
On running a ctrl + f for an “undefined index” error, I’m able to find that the error does indeed exist.
But for some reason the CSS is set to:
#query-monitor-main .qm-hide, #query-monitor-main .qm-hide-scripts-dependencies, #query-monitor-main .qm-hide-styles-dependencies, #query-monitor-main .qm-hide-scripts-dependents, #query-monitor-main .qm-hide-styles-dependents, #query-monitor-main .qm-hide-scripts-host, #query-monitor-main .qm-hide-styles-host, #query-monitor-main .qm-hide-user, #query-monitor-main .qm-hide-result, #query-monitor-main .qm-hide-name, #query-monitor-main .qm-hide-type, #query-monitor-main .qm-hide-caller, #query-monitor-main .qm-hide-component { display: none !important; }Which is hiding all the errors. I have no idea how or why this CSS is in place.
Is there any way for me to remove the offending CSS? Is there a setting I’ve mistakenly hit?
- This reply was modified 5 years, 10 months ago by akiai.
Forum: Plugins
In reply to: [Limit Modified Date] checked as default?+1
Tried to look at submitting a PR but never used React or the React WordPress hooks.
Forum: Plugins
In reply to: [Limit Modified Date] Works on Custom Post Type ?You’ll need to edit the filter if you want multiple post types
add_filter( 'limit_modified_date_post_types', function( $post_types ) { $post_types[] = 'page'; $post_types[] = 'movie'; return $post_types; });Add to functions.php yes.
I’ve just had the same error after upgrading and not bothered to investigate what conflict is happening.
Instead have reverted to Yoast SEO 12.6. Download the ZIP under “assets” here:
https://github.com/Yoast/wordpress-seo/releases/tag/12.6
And upload.
All fixed. Will upgrade again once stable.