chiefbrody2001
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Checking Browser Message before accessingThank you Steven.
The site went down after I tried switching the theme. It should be live again now.
I will try your other suggestions and have reached out to my host which is investigating.
- This reply was modified 1 year, 3 months ago by chiefbrody2001.
Forum: Plugins
In reply to: [Meta Box] New Plugin Update Causing Fatal ErrorMany thanks. Working again fine now.
Forum: Plugins
In reply to: [Meta Box] Error messageHad same issue as drakking mentions above.
Thank you. I also had the same issue and found that the latest Relevanssi update was causing the problem.
Do these errors when editing a WordPress post help (if my theme is causing the issue of YoastSEO and Classic Editor not working properly):
Uncaught TypeError: URL is not a constructor
at analysis-1262.min.js?ver=12.6.2:21
at e.default (analysis-1262.min.js?ver=12.6.2:21)
at t.createAnalysisWorker (wp-seo-post-scraper-1262.min.js?ver=12.6.2:5)
at HTMLDocument.<anonymous> (wp-seo-post-scraper-1262.min.js?ver=12.6.2:5)
at i (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils&ver=5.3:2)
at Object.fireWith [as resolveWith] (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils&ver=5.3:2)
at Function.ready (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils&ver=5.3:2)
at HTMLDocument.J (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils&ver=5.3:2)
wp-tinymce.js?ver=4960-20190918:1 Deprecated TinyMCE API call: <target>.onNodeChange.add(..)
analysis-1262.min.js?ver=12.6.2:21 Uncaught TypeError: Cannot set property ‘innerHTML’ of null
at d.renderIndividualRatings (analysis-1262.min.js?ver=12.6.2:21)
at _._renderAnalysisResults (analysis-1262.min.js?ver=12.6.2:21)
at _.runAnalyzer (analysis-1262.min.js?ver=12.6.2:21)
at _._pureRefresh (analysis-1262.min.js?ver=12.6.2:21)
at z (analysis-1262.min.js?ver=12.6.2:1)
at analysis-1262.min.js?ver=12.6.2:1
at _.y [as _pureRefresh] (analysis-1262.min.js?ver=12.6.2:1)
at _.refresh (analysis-1262.min.js?ver=12.6.2:21)
at _.pluginsLoaded (analysis-1262.min.js?ver=12.6.2:21)
at s._pollLoadingPlugins (analysis-1262.min.js?ver=12.6.2:14)- This reply was modified 6 years, 6 months ago by chiefbrody2001.
Using the troubleshooting procedures it would appear the problem is replicated only when using my current theme. So it appears to be caused by the THEME rather than YoastSEO or Classic Editor 1.5. Is that fixable – it’s the first time in years that this issue has arisen.
I’ve updated all but the issue is persisting.
On another of my sites running Classic Editor 1.5 and YoastSEO 12.4, the problem doesn’t exist.
The only workaround at the moment (without removing Yoast) is to deactivate the plugin while working/editing posts, then reactivating immediately afterwards so its functionality is only temporarily “off”. Not ideal.
I’m surprised, given how frequently Yoast is updated, that nothing has been done to correct this.
I’m also surprised no representative of Yoast has addressed the issue, particularly as paying Premium customers have the same problem.
I have the same problem and reported it 4 days ago but still no update/fix has been implemented by Yoast.
Another site of mine has the previous version of Yoast active and works fine. So it is the 12.6.2 version that is causing the problems.
Running another site which hasn’t had Yoast updated to version 12.6.2 and works fine so it is definitely Yoast that needs correcting. But sadly, no update to fix the problem has been implemented yet…
Still no update from Yoast or the Classic Editor plugin developers?
Given my site is a slave to Yoast, it has been turned back on to fix a number of other issues that were causing me headaches. Can Yoast update the plugin to fix the bug causing text editor (with Classic Editor plugin switched on) to stop working properly?
I’ve decided to switch off Yoast indefinitely instead of Classic Editor as it was a case of which one is most important to me at the moment. 🙁
That does enable Classic Editor to work correctly. 🙂
But it meant going into the header.php file to sort out the browser details as Yoast was handling that. I used this code to get that working correctly:
<?php bloginfo('name'); ?> | <?php is_front_page() ? bloginfo('description') : wp_title(); ?>It could be a clash between the Classic Editor plugin and Yoast. Turning off Classic Editor appears to get Yoast working correctly again.
Deleted plugin, re-installed – same problem. In fact, the site was broken and had to manually deactivate via ftp. Poor.