PHP Fatal error when Expand shortcodes is enabled

No, having TablePress or not has nothing to do with this. Your Relevanssi installation is missing a file which defines the function. I would recommend reinstalling Relevanssi to make sure no files are missing.

Okay, thanks. This is not the missed file but the problem with the other plugin. The topic can be closed.

No, you are getting the error because you are missing the file that defines the relevanssi_enable_tablepress_shortcodes() function. Trust me, I wrote this code, I know. This function should always be defined, whether you use TablePress or not, it’s a Relevanssi function, not a TablePress function.

I have another plugin that tries to insert a post before your plugin initializes relevanssi_init() which includes tablepress and other classes.

Just an example that will cause the problem:

add_action( 'init', function () {
wp_insert_post(..);
}, 0);

Ok, that explains it: you’re acting too early. Move your function to a priority later than Relevanssi (Relevanssi runs on default 10). At the time your function runs, Relevanssi is active, but hasn’t loaded up everything yet. Move your function to priority 11 or later, and it shoud run just fine.

Up.

Hi, finally I would say this is the error because even this code leads to the fatal error:

add_action( 'init', function () {
wp_insert_post(..);
});

Quite normal case – creating posts inside the ‘init’ hook with the default priority. However even it throws the error message.

Thanks.

I’ll move Relevanssi initialization to priority 1 to avoid problems like this, but still, I’d seriously warn about creating posts on init on priority 10 – at that point, most plugins haven’t done their initialization yet, and you’re bound to run into problems. Acting on priority 11 will make sure all the plugins that init on priority 10 have got their stuff together.

@msaari I would hate to reopen this, but I’m getting the same error when I use the “Duplicate Post” plugin to create new posts.

I’m using version 2.6.1. Have you changed your plugin’s priority already?

Since this is another plugin’s code, I would rather not edit its code myself.

It’s fixed, but the fix hasn’t been released. Next release is coming in August, I guess, and will contain the fix.

To hotfix this now, change /lib/init.php

add_action( 'init', 'relevanssi_init' );

to

add_action( 'init', 'relevanssi_init', 1 );