totalgeeks

Oh that’s brilliant, thank you!

I’m afraid it’s currently in development on localhost…
But I’ve pinpointed it to the ajax script loading backup text and not the custom text.

That’s great!

Sorry but this is probably a bit dense… how would I use that to change the schema type? Do I need to use it in a function somehow?

Okay, it wasn’t Yoast SEO (it was a separate plugin called WP No Tag Base) which I used to remove the ‘/tag/’ part of the tag permalinks… and after getting rid of the plugin and flushing the rewrite rules, it looks as though it’s fixed!

I’ll keep checking it just to make sure, but several posts have gone through without problem at this stage, so it’s looking good.

By random fluke, I seem to have gotten somewhere in finding out what’s causing this.

Earlier today, I accidentally forgot to include tags on my post. And when I published the piece, it all worked as it should – no error. I added the tags and updated the article – still no error. The trouble is, I’ve tried replicating it and while it publishes fine every single time, sometimes adding the tags breaks my site structure, causing a 404 error for the article which is being updated.

So… it’s still not a fix. But it seems to be a conflict between Events Manager and the Tags of my site. Extra info – I’ve removed the ‘tags’ base in Yoast SEO so that tags don’t have the ‘/tag/’ bit in the url.

Okay, I tried the shortcode in the widget and it still throws out the error.

Sorry, I missed the latest responses – will try the shortcode and let you know.
(For the record, I’m not using Jetpack at all with my install)

Tried adjusting the sidebar widget in a attempt to fix this.
I tried removing event images, changing from eventlinks to eventname… but it still causes the error, no matter what the setup. Anyone got any ideas about this? I’d love to continue using the plugin, but I can’t risk Google News scraping the error message for much longer.

Okay, I’ve given this a try and it ‘s not exactly the result I hoped.

As I said, when I remove the sidebar widget, I don’t get the error on publishing posts.
With the widget back in place, the error happens every time I publish a post. Changing the events permalinks (or just saving them) does get rid of the error when it’s already present as it essentially flushes the permalinks. But as soon as I publish another post, the error returns, and flushing permalinks (or flushing the rewrite rules) is the only way to get rid of the error.

Hi guys, this is very helpful indeed.

I did have a widget appearing on all posts which showed upcoming events. When I removed the widget, the error seems to disappear. But that’s not a practical solution for me, as the widget is a big feature of what I’m doing with the plugin!

@codescout89 That info is hugely helpful – I will try fiddling with the permalinks and get back to you both to see if this resolves it!

No, it doesn’t seem to have helped – still kicking out the error whenever I publish a post.

I’ve just updated to the latest Dev version so will make a few posts and report back if it works! And yes, the error only appears on Post pages, not Events pages. And only when posting Posts, not when posting Events.

Hi there,

The error isn’t on every page when it happens – it only appears on Posts.
I didn’t have archives enabled but just tried enabling them to see if it makes a difference – still seems to cause the error.

And apologies, I thought I had the latest version? I can’t update it within wordpress itself so I assume it’s the latest version?

Hi there,

I’m using WordPress 4.9.1 and EM 5.8.1.1.
PHP version: 5.6.30 and the info under ‘Database Server in PHPMyAdmin is as follows:

Server: Localhost via UNIX socket
Server type: Percona Server
Server version: 5.6.36-82.1-log – Percona Server (GPL), Release 82.1, Revision 1a00d79
Protocol version: 10

Still having problems with this.

have tried everything from purging my htaccess to addressing file permissions.
Absolutely nothing seems to be helping. Essentially seems to be a problem with the permalinks (I think) in some way. Any help would be HUGELY appreciated. Have had to deactivate the plugin for now, but it would be great to get it back in working order!