|
KIROS
|
April 7, 2016 at 11:09 am
We recently installed the wp-user plugin, then deleted it, however we are getting this error on our pages:
An error has occurred:
The [ESPRESSO_MY_EVENTS] shortcode has not been properly registered or the corresponding addon/module is not active for some reason. Either fix/remove the shortcode from the post, or activate the addon/module the shortcode is associated with.
The plugin is deactivated, so why is the error coming up? Thanks?
|
|
Josh
|
April 7, 2016 at 12:26 pm
The error comes up because the plugin is deactivated. You can remove the error by removing the [ESPRESSO_MY_EVENTS] short code from you website’s pages.
|
|
KIROS
|
April 7, 2016 at 2:06 pm
That’s the thing though, the shortcode is no longer on the pages, and this error also shows up on category pages which I no for a fact we have never placed the shortcode in.
|
|
Josh
|
April 7, 2016 at 2:12 pm
Can you try checking through WordPress posts for the short code?
|
|
KIROS
|
April 11, 2016 at 9:18 am
Hi there. I have checked, and the shortcode is not on those posts. Furthermore, the error is showing up on category pages, which would be taxonomy pages. We didn’t touch the code for those. Why would it be showing up on those pages?
|
|
Josh
|
April 11, 2016 at 2:44 pm
It can show up on a category archive when there’s a post in that category that has the short code in its content.
If you’d like, someone from Event Espresso support staff can run some code to find which post has the short code if you can send FTP log in details via the form on this page.
Or, if you have or can install the debug bar console plugin, you can execute the following code in the console:
print_r( EE_Registry::instance()->CFG->core->post_shortcodes );
This will print an array of posts that have shortcodes registered to them.
|
|
KIROS
|
April 14, 2016 at 9:22 am
Hi Josh, yes I’ve gone through all the posts and the shortcode doesnt seem to be anywhere but the error still shows. Let me get clearance to give FTP access, that might be the best route.
|
|
Josh
|
April 15, 2016 at 1:35 pm
Okay got it removed, there shouldn’t be any errors anymore.
|
