WordPress.org

Ready to get started?Download WordPress

Forums

NextGEN Gallery
Lost custom fields and can't add back after upgrade from 1.9.3 to 1.9.12 (3 posts)

  1. Jane
    Member
    Posted 1 year ago #

    I upgraded our site from WP 3.3.2 -> WP 3.5.1 and upgraded the NextGen Gallery from 1.9.3 -> 1.0.12.

    After the upgrade, I go to a page (in the WordPress backend) that used to have 3 custom fields and now there is only 1 custom field. When I try to add the custom fields back in I get the message "Please provide a custom field value." even though I have entered a value in the field.

    The custom fields and their values are:
    dynamic_sidebar Sidebar - Janitorial
    page_menu_image_thumbnail_id 862
    page_menu_page_image_thumbnail_id 1166

    The page in the upgraded site is:
    http://www.jswebsitedesign.com/services/janitorial-services/

    And the page on the old site is:
    http://www.flagshipinc.com/services/janitorial-services/

    If you have any idea about what is going on or how I can troubleshoot this I'd appreciate it.

    http://wordpress.org/extend/plugins/nextgen-gallery/

  2. Jane
    Member
    Posted 1 year ago #

    I ended up rolling back to NextGen 1.9.3 and the gallery / custom field information was restored and I was able to view all the text and galleries on the pages.

    If anyone knows what the issue is with NextGen 1.9.12 I would still like to know as I'd like to use the latest version if possible.

  3. photocrati
    Member
    Plugin Author

    Posted 1 year ago #

    @Jane - Could you confirm with v1.9.12 activated on your site, if when you follow the below instructions, if it helps or is still broken?

    1) Deactivate all plugins (including v1.9.12 of NextGEN Gallery)
    2) Temporarily switch to WordPress default theme
    3) Reactivate NextGEN Gallery v1.9.12 only
    4) Clear your browser cache (test this in Chrome Browser), and reload your site

    Please let us know if that helps resolve the issue. If it does resolve that issue, could you let us know which plugin you found to cause the issue or if you found the Theme when activated, causes the issue?

    Thanks!
    --Becky

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic