Yoast Seo meta box not available in Event Manager 5.5

hmm, this works for me – https://yoast.com/wordpress/seo/#utm_source=wpadmin&utm_medium=plugin&utm_campaign=wpseoplugin

@angelo_nwl, unfortunately, the SEO fields are not shown on events pages in admin. The situation is related to EM 5.5 update. My current solution is to downgrade the plugin.

Hiya,

I’ve just tried this and the SEO box is appearing fine when adding events for me.

Are you sure it isn’t deselected under Screen Options?

Thanks,
Phil

Hi, thank you for your feedback. I reinstalled the version 5.5 in order to check other posibilities. I discovered other anomalies:
– cannot change the slug of permalink
– pop-up is opened in the same main window when I try to set recommended image (by click the standard link)
– expanding/collapsing DIVs not working (including SEO form which is not opened)

So, I think there is a problem with jquery libraries or other js incuded in new EM 5.5.

Thanks,
John

Looking again on EM’s changelog, I found that everything is working just fine on https://. So, the right js library is loaded with no problem on SSL. I have no settings like FORCE_SSL_ADMIN or FORCE_SSL_LOGIN.

The errors remain on NON-SSL administration

I’m wondering if one or more of your plugins is forcing an SSL or non-SSL loaded library.

If you add a FORCE_SSL_ADMIN constant to your wp-config file does that fix the issue?

@caimin_nwl, on SSL it’s ok, but I need it to work on non-SSL. The admin is just fine when I restore the older version of plugin.

Can you explain the difference (js files, paths) between EM working on SSL and EM on non-SSL, hoping to discover the same resources in other plugins?

The only active plugin setting FORCE_SSL_ADMIN might be BuddyPress (Ver 1.8.1). But the conflict appears just on EM 5.5. I verified also with BuddyPress deactivated and the error persists.

It might be worth trying to fix it from the other direction by specifying:

define('FORCE_SSL_ADMIN', false);

AFAIK, the difference between SSL and non-SSL urls should be https / http.

I’ll make sure Marcus sees this thread, hopefully he’ll have a suggestion or two.

all shows in mine, so definitely not a 5.5 issue in itself

the same situation with define(‘FORCE_SSL_ADMIN’, false);
For the moment all editors will use ADMIN on SSL, but the error remains.

There is a javascript conflict started with 5.5 update in relation with GD Custom Posts And Taxonomies Tools PRO ver. 4.2

I created custom taxonomies for Event and Location with GD CPT Tools