zerokarma
Forum Replies Created
-
TypeError: Cannot read property ‘SnippetEditor’ of undefined
at block-editor-1611.js:1
at zj (react-dom.min.js:13)
at Th (react-dom.min.js:10)
at tj (react-dom.min.js:10)
at Te (react-dom.min.js:10)
at react-dom.min.js:7
at unstable_runWithPriority (react.min.js:2)
at Da (react-dom.min.js:7)
at Pg (react-dom.min.js:7)
at ha (react-dom.min.js:7)I have this same problem, YOAST plugin is causing the error when activated. When I deactivate it works fine.
TypeError: Cannot read property 'SnippetEditor' of undefined at block-editor-1611.js:1 at zj (react-dom.min.js:13) at Th (react-dom.min.js:10) at tj (react-dom.min.js:10) at Te (react-dom.min.js:10) at react-dom.min.js:7 at unstable_runWithPriority (react.min.js:2) at Da (react-dom.min.js:7) at Pg (react-dom.min.js:7) at ha (react-dom.min.js:7)Forum: Plugins
In reply to: [W3 Total Cache] JS broken in IE11 when cachedI disabled the HTTP/2 Push but this problem is still happening in IE11 with JS minify enabled.
If I disable the JS portion of minify it will work with IE11.
Forum: Plugins
In reply to: [W3 Total Cache] JS broken in IE11 when cachedIf I disable the JS Minify it works in IE11 but once I re-enable it then it breaks again.
The settings I have for JS Minify are:
< / head > Default (blocking)
< body > Default (blocking)
Combine only
HTTP/2 Push – EnabledForum: Plugins
In reply to: [W3 Total Cache] JS broken in IE11 when cachedw3 Total Cache is currently enabled.
I am not sure when this issue started but sometime within the last 2-3 months.
If you visit the site – spartonre.com with IE11 you will see that it is throwing all kinds of JS errors in the console.
This is only happening with IE11, in all other browsers it is working fine.
I have also encountered this error with the latest update for ACF pro version.
Is there an ETA on when Simple History will be updated to fix this?
Forum: Plugins
In reply to: [Redirection] unserialize(): Error at offsetMarking as fixed
Forum: Plugins
In reply to: [Redirection] unserialize(): Error at offsetOk I have an update.
I managed to track down the broken redirects.
I am not sure how this happened but it appears there were two old redirects that did not appear to have any URL setup to forward to.
Those two redirects without any forwarding url is what was causing the PHP notice error.
Once I deleted them the warnings went away.
Forum: Plugins
In reply to: [Redirection] unserialize(): Error at offsetIs there any way to trackdown which redirect might be causing it?
I have hundreds of redirects? I would be very difficult to test each one.
Forum: Plugins
In reply to: [WooCommerce PDF & Print] Is this plugin Abandoned?I also emailed the Developer and never got a response so at this point I think it is safe to say it is Abandoned.
As for an alternative, I found this plugin the other day:
https://codecanyon.net/item/woocommerce-print-products-pdf/14890964
I have not tried it yet or know if it is any good but maybe it might be a solution to replace this plugin. I am going to give it a try out later when I have some more free time.
Forum: Plugins
In reply to: [WP Go Maps - Most Popular Map Plugin] mkdir(): No such file or directoryThe problem wasn’t that the plugin wasn’t working, it always worked but it was generating that error notice that I identified above.
It generated that error even when the folders existed and the plugin was writing to it.
The only way I fixed the error was to switch the setting to store the Map data in the database instead of a folder/file.
Forum: Plugins
In reply to: [WP Go Maps - Most Popular Map Plugin] mkdir(): No such file or directoryUnder the settings for the plugin it is set to:
{uploads_dir}/wp-google-maps/
This folder does exist so the plugin must have created it, the 1markers.xml file is also inside the folder and written to as recently as today.
Forum: Plugins
In reply to: [Redirection] PHP7 giving HTTP Error 500This is with the latest version of Redirection 2.6.1.
Forum: Plugins
In reply to: [Ultimate FAQ Accordion Plugin] Toggle Symbol showing as “a” instead of “+”It is working now but I am not sure what I did to fix it or what happened to resolve it…
I thought that maybe it was a cache issue but trying it on another location produced the same lettering problem however now it appears to be working.
So to anyone else having this problem I am not sure what to suggest, it fixed itself somehow lol
Forum: Plugins
In reply to: [Ultimate FAQ Accordion Plugin] UFAQ permalinksAny update on this?