• Dear list,
    I am a happy user of NGGallery and NGG Custom Fields.

    However, NGG Custom fields has been broken ever since I changed my website’s URL. I mean, I just changed the doc root in my Apache installation from an hidden folder to the domain root: since then, the custom fields plugin is no longer working.

    I’ve turned debugging on and I keep getting error messages such as the following:

    [15-Jul-2013 12:37:41 UTC] PHP Notice: Undefined index: Date: in /home/vega/web/wordpress/wp-content/themes/bloomingstars/nggallery/gallery.php on line 73
    [15-Jul-2013 12:37:41 UTC] PHP Notice: Undefined index: Weather: in /home/vega/web/wordpress/wp-content/themes/bloomingstars/nggallery/gallery.php on line 77
    [15-Jul-2013 12:37:41 UTC] PHP Notice: Undefined index: SQM: in /home/vega/web/wordpress/wp-content/themes/bloomingstars/nggallery/gallery.php on line 81
    [15-Jul-2013 12:37:41 UTC] PHP Notice: Undefined index: Notes: in /home/vega/web/wordpress/wp-content/themes/bloomingstars/nggallery/gallery.php on line 85
    [15-Jul-2013 12:37:41 UTC] PHP Notice: Undefined index: 26 in /home/vega/web/wordpress/wp-content/plugins/nextgen-gallery-custom-fields/ngg-custom-fields.php on line 300
    [15-Jul-2013 12:37:41 UTC] PHP Notice: Undefined index: 30 in /home/vega/web/wordpress/wp-content/plugins/nextgen-gallery-custom-fields/ngg-custom-fields.php on line 300
    [15-Jul-2013 12:37:41 UTC] PHP Notice: Undefined index: 43 in /home/vega/web/wordpress/wp-content/plugins/nextgen-gallery-custom-fields/ngg-custom-fields.php on line 300

    I deleted all the old custom fields and all references to those fields from the individual images, but to no avail apparently.

    So my question is: is there a way to reset the whole thing in order to get it back to normal? Thanks in advance!

    alien123

    http://ww.wp.xz.cn/extend/plugins/nextgen-gallery-custom-fields/

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter alien123

    (@alien123)

    Update… I have:

    1) Disabled and re-enabled the plugin
    2) Reinstalled the plugin with the given URL as per the FAQs
    3) Redefined a new set of custom fields having exactly the same names and order as the previous ones

    Now the debug log is flooded with error messages like

    Trying to get property of non-object in /home/vega/web/wordpress/wp-content/plugins/nextgen-gallery-custom-fields/ngg-custom-fields.php on line 678

    Is there a way to do a clean reset of the plugin, possibly without removing the pictures?

    Thanks again in advance!

    Plugin Author shauno

    (@shauno)

    Hi alien123

    Unfortunately NGG Custom Fields wasn’t written with the error settings as strict as possible. This means that the plugin will throw lots of NOTICE errors. They are essentially harmless though, and the plugin will still function as it should.
    You just need to make sure WP_DEBUG is not turned on for your site, and the warnings should go away.

    How do I deactivate WP_DEBUG?

    Thread Starter alien123

    (@alien123)

    Hi shauno,
    thanks for your feedback.

    I understand NGG CF is not capable of managing all these warnings. But is it OK to be getting so many?

    I am using NGG CF to fill in picture captions for my lightbox. Before moving to the domain root, it was working like a charm, so there must be something wrong.

    Is there a way to completely reset NGG CF’s configuration? Just as if it were a first-time installation?

    Thanks,
    alien123

    I found it in the wp_config.php file. It is turned off and I still get the error messages whenever I activate the Custom Fields plugin.

    Plugin Author shauno

    (@shauno)

    @alien123: So when you moved the site, does it have it’s own wp-config.php file. I guess it does, and you have WP_DEBUG set to true for the new site. You just need to set it to false.
    I guess it was working fine before because that site had WP_DEBUG set to false.

    @cse7: If WP_DEBUG is set to false, you shouldn’t get any NOTICE warnings. Are you sure it’s set to false?

    Thread Starter alien123

    (@alien123)

    Ok, I set that flag to false. The warnings are now gone, but apparently NGGallery is no longer able to correctly retrieve the field values.

    I mean, $image->ngg_custom_fields[whatever] is empty even if I put some values in (I made sure they are in the wp_nggcf_field_values table)

    alien123

    Thread Starter alien123

    (@alien123)

    I mean, the gallery edit page shows and retrieves the attribute values correctly, but they do not show up in the actual gallery…

    Plugin Author shauno

    (@shauno)

    There’s no reason it shouldn’t work. Are you sure you aren’t doing something silly like adding the data to the wrong gallery?

    Thread Starter alien123

    (@alien123)

    I don’t think so. To be more precise, I am doing the following:

    1) I defined about ten image custom fields (i.e. they are meant to be attributes attached to each individual image)
    2) I edited a few of these fields for one image in the gallery edit page, then click “save changes”. Of course, in doing so, I *carefully* noted down the image ids
    3) Then these fields don’t get written in the gallery pop-up, although they are handled correctly in the gallery edit page.

    I am also 100% sure that when I changed my website URL I just changed the Apache doc root to point directly to my WP home, without physically making any alterations to the WP installation.

    Looks like there is kind of a “missing link” between the NGG gallery and the NGGCF fields in the backend. But I also checked out the tables in the DB and they apparently look fine.

    I’m at a loss here. Is there any additional info you need to help me nail down this problem?

    Thx, alien123

    Plugin Author shauno

    (@shauno)

    The fields won’t show in the popup automatically, you need to add them to the gallery template. Have you done that? I imagine you have if it was working before?

    Can you send me an email to shaunalberts AT gmail DOT com. If I can get some extra (non-public) info maybe we can solve this quicker.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Plugin broken after directory move’ is closed to new replies.