Invalid Display Type – Version 2.0

oh right i’m using version
wordpress 3.6.1
nextgen-gallery 2.0.31
xili-language 2.9.1

Can anyone confirm that unticking “Modify home query” on the “https://www.xxxxx.xx/wp-admin/options-general.php?page=language_front_set” page fixes the issue

Ofloo,

glad to hear that you were able to fix it.

I don’t use xili-language on my site, so that fix won’t work for me. I therefore still believe that Nextgen is causing the problem.

Your fix probably will be helpful though – I might try installing xili-language just to fix the multisite issue ??

Have you contact xili-language author via the support form in 5th tabs of settings ? It might be a conflict in sub-query to sub select post in the home page ! Be patient…

M.

Yeh I’ve contacted them.

It will be very difficult to test in WP_debug mode (WP 3.6.1 – PHP Version 5.4.10)

The plugin generated 25514 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

To much notice messages (here a – very – little excerpt) :

Strict Standards: Declaration of Hook::call_parent() should be compatible with Mixin::call_parent($method) in /Applications/MAMP/htdocs/wp_svn36/wp-content/plugins/nextgen-gallery/pope/lib/class.extensibleobject.php on line 1377

Strict Standards: Declaration of C_Component_Factory::define() should be compatible with C_Component::define($context = false) in /Applications/MAMP/htdocs/wp_svn36/wp-content/plugins/nextgen-gallery/pope/lib/class.component_factory.php on line 7

Strict Standards: Declaration of C_Base_Module::define() should be compatible with C_Component::define($context = false) in /Applications/MAMP/htdocs/wp_svn36/wp-content/plugins/nextgen-gallery/pope/lib/class.base_module.php on line 13

Strict Standards: Declaration of C_Base_Product::define() should be compatible with C_Component::define($context = false) in /Applications/MAMP/htdocs/wp_svn36/wp-content/plugins/nextgen-gallery/pope/lib/class.base_product.php on line 14

Strict Standards: Declaration of P_Photocrati_NextGen::define() should be compatible with C_Component::define($context = false) in /Applications/MAMP/htdocs/wp_svn36/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/product.photocrati_nextgen.php on line 12

Strict Standards: Declaration of M_Fs::define() should be compatible with C_Component::define($context = false) in /Applications/MAMP/htdocs/wp_svn36/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/fs/module.fs.php on line 8

Strict Standards: Declaration of M_Validation::define() should be compatible with C_Component::define($context = false) in /Applications/MAMP/htdocs/wp_svn36/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/validation/module.validation.php on line 10

Strict Standards: Declaration of M_Router::define() should be compatible with C_Component::define($context = false) in /Applications/MAMP/htdocs/wp_svn36/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/router/module.router.php on line 9

Strict Standards: Declaration of M_WordPress_Routing::define() should be compatible with C_Component::define($context = false) in /Applications/MAMP/htdocs/wp_svn36/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/wordpress_routing/module.wordpress_routing.php on line 10

Strict Standards: Declaration of M_Security::define() should be compatible with C_Component::define($context = false) in /Applications/MAMP/htdocs/wp_svn36/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/security/module.security.php on line 10

The diagnosis was difficult due these numerous annoying errors messages (Strict Standards) but… we found that nextgen plugin don’t call properly WP_query for his custom post type like ‘display_type’… even in admin side, the is_home value is set to true !!!

Next version (2.9.2) of xili-language will detect that… be patient…

M.

Hi,

I don’t know whether anybody still cares about the original problem. I described it in post #6, and it was also described in post #1, #7 and some others.

After the recent WordPress-update to 3.8, I thought I could try updating NextGEN as well. So I updated NextGEN Gallery to version 2.0.40 (before that, it was running at 1.9.13 due to the multisite issue).

And: The problem is no more! The “Invalid Display Type” for multisites is fixed.

So, in my opinion, this thread can be marked as resolved, and you can try to update NextGEN tu 2.0.40. I don’t know whether you need WordPress 3.8, but it surely won’t hurt ??

Thanks for fixing and of course: Thanks photocrati for this wonderful plugin.

Yes, it′s resolved, thanks a lot

All – Thanks for the follow-ups and the update to say its working!

– Cais.