error

(@cappellaniauniroma3)

I see these errors have not been fixed for over two years now, I am still seeing them. They were already reported here:

https://wordpress.org/support/topic/plugin-nextgen-gallery-bad-coding-issues?replies=1#post-2844125

I am still seeing these errors continuously:

E_STRICT content.js 3
Redefining already defined constructor for class nggPostThumbnail - /var/www/vhosts/cappellaniauniroma3.org/httpdocs/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ngglegacy/lib/post-thumbnail.php:26

and

E_WARNING content.js 3
include_once(): Failed opening '/var/www/vhosts/cappellaniauniroma3.org/httpdocs/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_xmlrpc/package.module.nextgen_xmlrpc.php' for inclusion (include_path='.:') - /var/www/vhosts/cappellaniauniroma3.org/httpdocs/wp-content/plugins/nextgen-gallery/pope/lib/class.base_module.php:66

E_STRICT call_user_func_array() expects parameter 1 to be a valid callback, non-static method nggMediaRss::add_mrss_alternate_link() should not be called statically -

https://wordpress.org/plugins/nextgen-gallery/

Viewing 1 replies (of 1 total)

Plugin Contributor photocrati
(@photocrati)

11 years, 3 months ago

@cappellania.uniroma3 – The topic you linked to is a significantly older version of NextGEN Gallery and not representative of the current version of NextGEN Gallery.

Also, in most cases Strict Standards messages such as these should not be appearing on production servers unless their error reporting settings are set very high. In these cases we suggest as noted in the 2.0.40 changelog, “Added NGG_HIDE_STRICT_ERRORS constant. Define and set to TRUE to hide strict errors”

See if that helps with these error messages on your site.

Thanks!

– Cais.

Viewing 1 replies (of 1 total)

The topic ‘error’ is closed to new replies.

Tags