Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #56390
    netingenuity
    Participant

    I found an error message above the header on the site https://sculpturezone.com.

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the responsive-lightbox domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/evelynfloret/public_html/wp-includes/functions.php on line 6114

    And I could not, for hours, log into the WordPress admin. The login page was blank.

    I called the host. They told me the only solution was to restore from a backup. That did not help. I was stumped. But now, instead of getting a blank page for the WordPress login, I got an error message that the database was not found. I panicked for a while, not knowing how to restore your site. I suspect the cause was upgrading some plugins created a conflict, but I’ve never had one that disabled the WordPress admin like this.

    I contacted a fellow programmer who figured out how to reset the PW for the database user and we were able to re-access the WordPress admin. From there, I could deactivate the single plugin that was causing the text error to appear. The message went away. But visitors are no longer able to click on am image to make it open in a lightbox.

    I reported the problem as I deactivated the plugin. How can I find out when this problem is fixed in an update?

    #56443
    Toby TMEA
    Participant

    Hi netingenui,

    I’m having a similar problem with that error, but that error is in fact just a warning. Nothing is breaking and the plugin actually works fine. I’m using it quite happily on my site. It’s an issue that DFactory needs to address, but it’s not a critical one.

    The issue you have is that those warnings are displaying on your website which they absolutely should NOT be doing. This is a configuration issue on your website. You have your wordpress installation configured to show all errors on the pages themselves rather than just added to a log file. – this should only be done in the development environment, not the live production environmennt.

    Check with your developer friend about WP_DEBUG and set it correctly in your wp-config.php file and you should be able to use the plugin without any issues.

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