Strict declaration errors using 2.0.55 beta

  • frisco

    (@frisco)


    10 years, 2 months ago

    There are a number of strict declaration errors with the .55 beta. These also exist in the .40 release, and it would be great if you cleared them up. Here’s one example:

    Declaration of P_Photocrati_NextGen::define() should be compatible with that of C_Base_Product::define()
    Location: wp-content/plugins/nextgen-gallery/pope/lib/class.component_registry.php:870
    Call stack: C_Component_Registry::_load_module_internal()
    C_Component_Registry->_load_module_internal()
    C_Component_Registry->load_module()
    C_Component_Registry->load_all_modules()
    C_Component_Registry->load_all_products()
    C_NextGEN_Bootstrap->_load_pope()
    C_NextGEN_Bootstrap->__construct()

    You can see them for yourself if you use John Blackbourn’s excellent Query Monitor plugin: http://wordpress.org/plugins/query-monitor/

    Further, over in this thread, http://wordpress.org/support/topic/conflict-with-nextgen-gallery-7, John points out a few issues with NGG (e. g., the output buffering, the internal WP function calls). NGG is a big and popular plugin, so those things should be addressed (i. e., if they’re real, they should be fixed).

    Is there a Github repo where people can help improve the plugin? If not, there should be. Comments like those John made should become fixes rather than lingering complaints, and a Github repo would facilitate that. There are Github repos to escape NGG – how about one to improve it?

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

  • The topic ‘Strict declaration errors using 2.0.55 beta’ is closed to new replies.