Support » Plugin: WordPress Gallery Plugin - NextGEN Gallery » NGG Plugin Removes Styling From Post Pages

  • Resolved jonb1987

    (@jonb1987)


    Hi Guys,

    My client has just updated all of her plugins on her WP site florschutz.com, and noticed that her blog post pages aren’t showing their background, the content has shifted to one side, and at the bottom of the each post is the error message:

    “There has been a critical error on your website.

    Learn more about debugging in WordPress.”

    I have been through all of the plugins one by one and found that NGG is the source of the problem, any idea how to remedy it?

    Thanks,

    Jon

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support gabyimagely

    (@gabyimagely)

    Hello @jonb1987,

    So sorry, I tried to check the link but is giving me a 404 message.
    One thing you can try is, of course, activate the WordPress Debug Mode https://wordpress.org/support/article/debugging-in-wordpress/, which will provide more information.

    On the other hand, you can also try to re-install the plugin, just in case the files got corrupted during the update.

    Please, keep us posted, we are happy to help!

    Hi Gaby!

    Thanks for your response, I backed up and updated php yesterday which through out all of the pagination temporarily.

    If you’d still like to check and see now the problem persists.

    Is it possible to backup all of the galleries created in NGG so that we can restore them if we reinstall the plugin?

    Thanks,

    Jon

    Plugin Support mihai-imagely

    (@mihaiimagely)

    Hi @jonb1987,

    Are you getting the “There has been a critical error on your website.” only with NextGen Gallery enabled or it persists even with NextGen plugin deactivated?

    Usually, this sort of error is a critical one and it would stop the page’s code execution at the line where it fails so I am not wondering that the page’s styling breaks ( due to its styling resources not being entirely loaded ).

    Important note: We can’t test ourselves to try to replicate the problem as it is a premium theme and we aren’t being allowed to ask you for site’s access as this is insecure being the thing that this is a public forum thread.

    Please enable the WP Debug from by editing the site’s wp-config.php file and replacing:

    define( 'WP_DEBUG', false );

    with:

    define( 'WP_DEBUG', true );

    Once done, you should get a more detailed error report line. Please provide us with that error code.

    Thanks

    Hi Mihai,

    I’ve now disabled the NGG plug in And as you can see the error is gone.

    I shall attempt to debug when I get a chance. I’ll let you know the error code.

    Many thanks.

    Hi Guys,

    With debug on, this is the error given. Oddly, it refers to the theme, though the problem only exists with NGG enabled. Any thoughts?

    Warning: require(/home/florschu/public_html/wp-content/themes/rttheme15/comments.php): failed to open stream: Permission denied in /home/florschu/public_html/wp-includes/comment-template.php on line 1508

    Fatal error: require(): Failed opening required ‘/home/florschu/public_html/wp-content/themes/rttheme15/comments.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php:/usr/local/php56/lib/php’) in /home/florschu/public_html/wp-includes/comment-template.php on line 1508

    Thanks

    The below notices are also given, some of which do appear to refer to NGG;

    Notice: The called constructor method for WP_Widget in Twitter_Widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in /home/florschu/public_html/wp-includes/functions.php on line 4718

    Notice: The called constructor method for WP_Widget in Flickr_Widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in /home/florschu/public_html/wp-includes/functions.php on line 4718

    Notice: The called constructor method for WP_Widget in Latest_Posts is deprecated since version 4.3.0! Use
    __construct()
    instead. in /home/florschu/public_html/wp-includes/functions.php on line 4718

    Notice: The called constructor method for WP_Widget in Latest_Posts_2 is deprecated since version 4.3.0! Use
    __construct()
    instead. in /home/florschu/public_html/wp-includes/functions.php on line 4718

    Notice: The called constructor method for WP_Widget in Popular_Posts is deprecated since version 4.3.0! Use
    __construct()
    instead. in /home/florschu/public_html/wp-includes/functions.php on line 4718

    Notice: The called constructor method for WP_Widget in Contact_Info is deprecated since version 4.3.0! Use
    __construct()
    instead. in /home/florschu/public_html/wp-includes/functions.php on line 4718

    Notice: The called constructor method for WP_Widget in Testimonials is deprecated since version 4.3.0! Use
    __construct()
    instead. in /home/florschu/public_html/wp-includes/functions.php on line 4718

    Notice: The called constructor method for WP_Widget in Recent_Posts_Gallery is deprecated since version 4.3.0! Use
    __construct()
    instead. in /home/florschu/public_html/wp-includes/functions.php on line 4718

    Notice: add_custom_background is deprecated since version 3.4.0! Use add_theme_support( ‘custom-background’, $args ) instead. in /home/florschu/public_html/wp-includes/functions.php on line 4648

    Plugin Support mihai-imagely

    (@mihaiimagely)

    @jonb1987

    Can you please provide us with the line of code from your theme’s “rttheme15/comments.php” file that contains the require function?

    MIHAI!

    Oddly enough that file was set with zero permissions, giving read perms has fixed everything.

    Thanks for your help!

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Side note:

    Important note: We can’t test ourselves to try to replicate the problem as it is a premium theme and we aren’t being allowed to ask you for site’s access as this is insecure being the thing that this is a public forum thread.

    @mihaiimagely Really?

    That’s not correct. You cannot ask for back end access period, either public or privately as it’s not safe. It has nothing to do with public and this isn’t hard to understand.

    Plugin Support mihai-imagely

    (@mihaiimagely)

    Understood, Jan.

    I should have been more explicit and specified that he can’t provide them both here or privately, sorry about that … Just was trying to prevent any self initiative from the @jonb1987 to provide us with his site’s details as a reply to our impossibility to directly inspect the problem ( as that had to do with his premium theme ).

    Thanks for the note

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.