Support » Plugin: NextGEN Gallery - WordPress Gallery Plugin » Invalid Display Type – Version 2.0

  • Resolved benhartwich



    after upgrading to 2.0, no gallery is longer displayed at frontend. I´ve got the error at header and at the articles: array(1) { [“display_type”]=> array(1) { [0]=> string(20) “Invalid display type” } } and invalid display type.

    At Backend the slider option dialogs aren´t shown right, the titles are missing. I think it belongs to my multisite installation (subdomains), because at a single wordpress installation all is fine. And I use https on login.

    I think I do a rollback to .93 or have you got an idea?

Viewing 15 replies - 1 through 15 (of 39 total)
  • aaaahh same here… PAIN!

    I rolled back to previous version, this resovled it. Am going to investigate what is causing this in 2.0

    Same problem for me. I usually update NextGen with total confidence, but this time it ruined all my websites and galleries, displaying garbage code and breaking templates. I understand the concept of “checking for incompatibility” with other plugins, but up to now there was NO problem, so why should users now have to spend time digging in their install, juste for the sake of NGG? That’s not cool.

    I reverted to previous version, and things are back.

    This version 2 is obviously not ready, and way too dangerous to install if you have many galleries.

    I hope this version will be fixed soon. I used to be a huge fan of NGG, but I’m now wondering..

    I tested NGG 2 on a clean (with not many plug-ins) WordPress, and it’s OK. But if there is no knowledge provided by the developers of the precise plug-ins that cause problems in addition with NGG, i’s going to be a big burden for users to find out. And what if it means not using a very precious OTHER plug-in?
    Will share any new thoughts on the subject.

    Same problem here.

    I tried to network-deactivate all plugins, and then activated only NextGen, but that didn’t solve the problem.

    Therefore this really seems to be a multi-site problem.

    So here’s the bug report again:

    WordPress 3.5.2, Multi-Site, runs on my own little server.
    I display my galleries using the command [nggallery id=##]


    If there is a gallery to be displayed, the following error shows at the beginning of the post:
    array(1) { ["display_type"]=> array(1) { [0]=> string(20) "Invalid display type" } }
    If there are several galleries in one post (or on a site), this message is shown several times at the beginning of the post.

    At the position there the gallery (or galleries) should be, the following error shows:
    Invalid Displayed Gallery

    Menu Gallery -> Gallery Settings: Everything is empty. I can see some dropdown boxes, but most of them are empty. There are no descriptions, no pre-selected values in the dropdown boxes. This really is empty.

    Well, the backend part isn’t the annoying part. The frontend is the stuff that bothers me 🙂

    I have the same issue on 2 of my sites, but am not running multisite.

    For each post that contains an image, this appears. And in posts with multiple images, it appears multiple times:
    array(3) { ["entity_types"]=> array(1) { [0]=> string(30) "entity_types should be present" } ["name"]=> array(1) { [0]=> string(22) "name should be present" } ["title"]=> array(1) { [0]=> string(23) "title should be present" } }

    Would like to add that when I go to Gallery > Gallery Settings, I get the following error 14 times and nothing in the drop-downs:
    Warning: in_array() expects parameter 2 to be array, null given in /home/[xxx] /public_html/[xxx]/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_gallery_display/class.display_type_mapper.php on line 71

    It’s incredible!! A so used plugin, once so great, and now it’s more that a week that NOTHING is working and no patch is available!!

    I am having the same problem. Some galleries are not shown at all, others are only showing the first page of images and then when you hit the button to go to next page it just doesn’t find it, throwing a 404 error.
    WP 3.6, Flagallery 2.0

    Plugin Author photocrati


    Hey All,

    Please accept our deepest and sincerest apologies. Note that we did do a beta testing round and several rounds of internal testing before we released v2.0. Unfortunately we just couldn’t anticipate all the several various setups that our many thousands of users would be on. Please note, this was a significant update and we made note of this before we released it to the public.

    But, what I’d like to point out is that it’s actually working well for a large percentage of users. We know this from feedback and from the fact that a lot of people are upgrading to Pro, which they can’t do if 2.0 isn’t working well for them. However, as you have seen from experience, there are issues for some users.

    Keep in mind that NextGEN is active on 550,000 websites. So if a small percentage have problems, that’s still a big number. And the ones we hear from the fastest are precisely those with the issues. For those users, like yourself, the best thing we can do is rapidly troubleshoot and push out the next release. We’ll be introducing a couple dozen fixes in the next couple days, all within a week of launch.

    What we’ve done here with v2.0 is rare. NextGEN is a very old plugin. Because it’s been around a while, it’s deeply integrated into the WP ecosystem. Many people have customized it. Many plugins integrate with it.

    We’ve basically given NextGEN it’s first full revamp/rework since it was originally launched nearly 6 years ago. Most updates that Alex did, and that we’ve done since we took over last year have been minor. This last one was massive – a total overhaul.

    Because NextGEN touches so many things, that kind of massive overhaul is just bound to cause some issues.

    We did a ton of internal testing, and also pushed out a public beta for a full month. We had over 1000 people download the beta and we got a lot of feedback. So we tested thoroughly.

    But there are just bound to be issues, and now it’s just our job to resolve those as quickly as possible.

    If you have found and confirmed a bug or incompatibility issue with v2.0 on your site, please send as much detail (login credentials would be incredibly useful for our developers) to Or, you’re welcome to try our latest beta here: or rollback until we release our next update:

    Again, we’re very sorry for the inconvenience these errors have caused, we’ll do our very best to produce a solution as quickly as we can.


    the solution was simple but ell hidden and would be described s part of the upgrade process! Just go to Gallery->Other options->Reset & Uninstall and click “Reset all options to a default settings”
    No choice: you have to reprogram all your options, since 2.0 opts seems to be NOT compatible to 1.9
    Good luck!

    Plugin Author photocrati


    Hi all – just following up on this. If anyone is still having this in version 2.0.7, can you please consider submitting a bug report with login credentials so we can troubleshoot? Or provide additional links so we can see an example. We’re not able to duplicate and it’s hard to solve without seeing it.


    If you are going to roll back, please follow:

    As previously reported, I solved the problem, so I have no longer a sample to submit. I can just note the the solution was “Reset all options to a default settings” and that a symptom is that “Gallery settings” menu page shows no headers.

    Hi @photocreati,
    I understand the frustration, however for people to provide you with access they need to be assured they’re not jeopardising security. By saying “provide login credentials” we need to know where to send them, who is going to access these credentials and at what time.
    In other words an extremely safe way of doing it and for us to be online at the time.

    I’ve just sent my credentials via your web form. Hope all works out ….

    Plugin Author photocrati


    Hey all – I just wanted to follow up on this thread.

    First, we’ve release another informal release with some fixes for the “invalid display” error. If you are comfortable with FTP and manually updating your plugins, you can get it at the link below. Otherwise it will be in the next official update probably around Monday next week:

    If you are still having this issue, please do submit a bug report with login credentials and we’ll look into and try to resolve it for you:

    Finally, I know some of you expressed frustration at this release, and I totally understand. I’d be frustrated to if I was having some of the issues we’ve seen in the forums. I’ve written a bit about what we think happened and what we’re doing about it here, in case you’d like to get my thoughts on it.

    We are solving things very quickly right now, and we’ll keep up a pretty rapid pace in the coming weeks.

Viewing 15 replies - 1 through 15 (of 39 total)
  • The topic ‘Invalid Display Type – Version 2.0’ is closed to new replies.