cappellania.uniroma3

Just to follow up on this, I was getting this double output while there was a notification of a more recent automatic save of the event post. After updating the event post, the more recent automatic save disappeared and there was no more double call to the “em_map_meta_cap” function. I believe the “more recent automatic save” is not being taken into account somewhere in the code…

I don’t see why I should open a new topic for the same exact error… The solution is, as proposed in the very first reply on this topic, to add the “static” keyword in front of the add_mrss_alternate_link() function:

photocrati (@photocrati) – 10 months, 1 week ago
As to the specifics of the notice you are seeing, you can try prepending the method definition with static at this line:

../wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ngglegacy/lib/media-rss.php:10

I am simply confirming that the problem is still present, and should be fixed as proposed.

I started getting the same error message recently, so I went and added the “static” keyword in front of the function add_mrss_alternate_link() and this fixed the issue.

Here are some lines from my error log for the website:

[Sun Mar 06 19:30:44.196961 2016] [fcgid:warn] [pid 17908] [client 37.187.213.136:44233] mod_fcgid: stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 1048576 bytes) in /var/www/vhosts/bibleget.io/httpdocs/wp-content/plugins/polylang/modules/wpml/wpml-compat.php on line 404
[Sun Mar 06 20:28:57.311429 2016] [fcgid:warn] [pid 17899] [client 37.187.213.136:59136] mod_fcgid: stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 1048576 bytes) in /var/www/vhosts/bibleget.io/httpdocs/wp-content/plugins/polylang/modules/wpml/wpml-compat.php on line 404
[Sun Mar 06 20:32:25.767396 2016] [fcgid:warn] [pid 17899] [client 37.187.213.136:59172] mod_fcgid: stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 1048576 bytes) in /var/www/vhosts/bibleget.io/httpdocs/wp-content/plugins/polylang/modules/wpml/wpml-compat.php on line 404
[Sun Mar 06 21:29:11.457410 2016] [fcgid:warn] [pid 15521] [client 37.187.213.136:60107] mod_fcgid: stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 1048576 bytes) in /var/www/vhosts/bibleget.io/httpdocs/wp-content/plugins/polylang/modules/wpml/wpml-compat.php on line 404
[Sun Mar 06 21:33:56.418895 2016] [fcgid:warn] [pid 15521] [client 37.187.213.136:60125] mod_fcgid: stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 1048576 bytes) in /var/www/vhosts/bibleget.io/httpdocs/wp-content/plugins/polylang/modules/wpml/wpml-compat.php on line 404
[Sun Mar 06 22:26:00.902764 2016] [fcgid:warn] [pid 20218] [client 37.187.213.136:33186] mod_fcgid: stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 1048576 bytes) in /var/www/vhosts/bibleget.io/httpdocs/wp-content/plugins/polylang/modules/wpml/wpml-compat.php on line 404
[Sun Mar 06 22:27:27.540703 2016] [fcgid:warn] [pid 20222] [client 37.187.213.136:33246] mod_fcgid: stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 1048576 bytes) in /var/www/vhosts/bibleget.io/httpdocs/wp-content/plugins/polylang/modules/wpml/wpml-compat.php on line 404
[

Sorry I haven’t gotten back to you yet, I’ve been traveling for the past week. I have just now attempted to activate the Lingotek plugin on my wordpress website, activation was not successful it produced the “504 Gateway Time-out | nginx” error.

I took care of this by adding this to my child theme’s functions.php:

add_action('init', 'my_custom_init');
function my_custom_init() {
    add_post_type_support( 'event', 'publicize' );
    add_post_type_support( 'event-recurring', 'publicize' );
}

However I don’t see why everyone should have to do this on their own, I think it should be enabled by default. Those that use Jetpack Publicize would expect it to be enabled; those that don’t use Jetpack Publicize won’t even notice the difference.

Sorry I just noticed that there is an option for this in the settings. I just disabled the automatic tax addition.

I have succeeded in pinpointing the problem, it was the “Avast Online Security” plugin for Chrome that was causing this. In this case I was using Chrome 31.0 on Windows XP, as soon as I disabled the Avast Online Security extension everything started working again just fine.