pattaya_web

Showing errors when I run a compatibility checker ??

And lots of stuff like this, also

There has been an error with the API:
INVALID_DOCUMENT – “text” was “” should be not (null or an empty string) (keyPath components->1->components->17->text)
INVALID_DOCUMENT – “text” was “” should be not (null or an empty string) (keyPath components->1->components->19->text)
INVALID_DOCUMENT – “text” was “” should be not (null or an empty string) (keyPath components->1->components->22->text)

And I just went through and reset the API, and secret key and still nothing.

Looks like the same error we have. Every article we publish has multiple [& nbsp ;] in it. Which explains why we’ve had nothing published for three months and about to lose our account.

We get this every time we publish also. We’re a news site and publish 10-15 news stories a day. Just got an alert from Apple that nothing has been published on our Apple News page for three months.

• This reply was modified 5 years, 2 months ago by pattaya_web.

I’ve had the same problem for four days and I can assure you I have never had a premium WPSSO core product on my site.

And it it won’t update with all of the other non-essential plugins on the site deactivated in troubleshooting mode either. Deactivating and reactivating the plugin is also ineffective.

Hi Pierre,

I’ve spent more time on this today and went through the live site and disabled almost all of plugins.

As soon as I activate AMP i get this error in the consol and cannot create a new gallery. Turn off AMP and the error message goes away and the create Gallery button re-appears.

Thank you

JQMIGRATE: Migrate is installed, version 1.4.1
load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,admin-bar,suggest,wp-ajax-response,jquery-color,wp-lists,jquery-ui-mouse,jquery-ui-sortable,postbox,jquery-ui&load[chunk_1]=-position,jquery-ui-menu,wp-dom-ready,wp-a11y,jquery-ui-autocomplete,tags-suggest,tags-box,word-count,wp-sanitize,post,editor-ex&load[chunk_2]=pand,thickbox,shortcode,backbone,wp-util,wp-backbone,media-models,wp-plupload&ver=5.3:414 Uncaught TypeError: Cannot convert undefined or null to object
    at g.cleanup (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,admin-bar,suggest,wp-ajax-response,jquery-color,wp-lists,jquery-ui-mouse,jquery-ui-sortable,postbox,jquery-ui&load[chunk_1]=-position,jquery-ui-menu,wp-dom-ready,wp-a11y,jquery-ui-autocomplete,tags-suggest,tags-box,word-count,wp-sanitize,post,editor-ex&load[chunk_2]=pand,thickbox,shortcode,backbone,wp-util,wp-backbone,media-models,wp-plupload&ver=5.3:414)
    at g.off (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,admin-bar,suggest,wp-ajax-response,jquery-color,wp-lists,jquery-ui-mouse,jquery-ui-sortable,postbox,jquery-ui&load[chunk_1]=-position,jquery-ui-menu,wp-dom-ready,wp-a11y,jquery-ui-autocomplete,tags-suggest,tags-box,word-count,wp-sanitize,post,editor-ex&load[chunk_2]=pand,thickbox,shortcode,backbone,wp-util,wp-backbone,media-models,wp-plupload&ver=5.3:414)
    at r (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,admin-bar,suggest,wp-ajax-response,jquery-color,wp-lists,jquery-ui-mouse,jquery-ui-sortable,postbox,jquery-ui&load[chunk_1]=-position,jquery-ui-menu,wp-dom-ready,wp-a11y,jquery-ui-autocomplete,tags-suggest,tags-box,word-count,wp-sanitize,post,editor-ex&load[chunk_2]=pand,thickbox,shortcode,backbone,wp-util,wp-backbone,media-models,wp-plupload&ver=5.3:414)
    at l (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,admin-bar,suggest,wp-ajax-response,jquery-color,wp-lists,jquery-ui-mouse,jquery-ui-sortable,postbox,jquery-ui&load[chunk_1]=-position,jquery-ui-menu,wp-dom-ready,wp-a11y,jquery-ui-autocomplete,tags-suggest,tags-box,word-count,wp-sanitize,post,editor-ex&load[chunk_2]=pand,thickbox,shortcode,backbone,wp-util,wp-backbone,media-models,wp-plupload&ver=5.3:414)
    at h.Collection.n.off (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,admin-bar,suggest,wp-ajax-response,jquery-color,wp-lists,jquery-ui-mouse,jquery-ui-sortable,postbox,jquery-ui&load[chunk_1]=-position,jquery-ui-menu,wp-dom-ready,wp-a11y,jquery-ui-autocomplete,tags-suggest,tags-box,word-count,wp-sanitize,post,editor-ex&load[chunk_2]=pand,thickbox,shortcode,backbone,wp-util,wp-backbone,media-models,wp-plupload&ver=5.3:414)
    at i.c.<computed> [as off] (media-views.min.js:1)
    at i.dispose (media-views.min.js:1)
    at i.dispose (media-views.min.js:3)
    at i.remove (media-views.min.js:1)
    at underscore.min.js:1

Saw this in my dashboard this morning. Have applied the fix and will see. Thanks ZAAAX (@zaaax)

I don’t know if this is applicable for your problem, but we were having massive problems with the image gallery after the WP 5.3 update.

Eg: Create new gallery button would not appear. Trying to select images for embedding in posts required two clicks and often opening and closing the media gallery several times. The preview function for posts required a save to preview.

Four hours of fault testing suggests that disabling AMP, Yoast SEO, & Glue for #Yoast SEO & AMP plugins will fix these problems. If you have these try disabling them.

Same problem. Lots of issues with images and the gallery after 5.3 update and no doubt someone will be along soon and say change your theme and turn off all of your plugins. It’s a WordPress problem, no doubt related to Gutenberg.

Thank you.

John

Okay. So what happens to that post? Posting to Apple news is set to occur automatically. Does it not post, or post without the video. Thank you.

Thank you,

I’ll work through all of those. The web server error log last had an entry on Oct 1 and there are no jQuery errors. I’ll keep working on it. Thank you JS!!

Hello JS,
After several weeks of testing the problem still exists. It only occurs when updating WPSSO plugin. On the latest update it didn’t clear properly and left a maintenance file behind for manual removal and did not reactivate.

I don’t know why, but its only with WPSSO.

Thanks,
John

Hello and thank you for the quick reply. My apologies for my tardiness. I was waiting until the latest weekly update.

We’ve been doing some work on the site and it looks like it might be related to cdn use. I’ll see what happens next week. Thank you so much.