Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Lukas Juhas

    (@lukasneptun)

    Hi there,

    Thank you! I’ll look in to this and release fix shortly.

    Sorry about trouble!

    Lukas

    Plugin Author Lukas Juhas

    (@lukasneptun)

    Hey there,

    You seem to be the only one so far getting this error so I’m suspicious that it has something to do with your template / other plugins.

    I implemented a bit of code that might prevent some errors showing but I’m not sure if the plugin is gonna be working for you.

    please update to 2.0.1

    Lukas

    Hi, I got the same error message after the 2.0 update. The advanced toggle button also would not work and I was unable to scroll the content of the page (the content was cut off at the bottom of the page similar to when you have a fixed/absolute positioned div with overflow hidden). I haven’t updated to the 2.0.1 update yet. Anyway, just wanted to confirm the error messages. Otherwise a great plugin.

    Hello Lukas,

    I was having the same error as the original poster, after reading your reply I updated the plugin and that removed the error message from the top of the administration area, however if you go to the plugin settings page, scroll down and open the advanced settings the error is different from the first one and reads.

    New error
    Warning: Invalid argument supplied for foreach() in /XYZ/XYZ/public_html/XYZ.com/wp-content/plugins/lj-maintenance-mode/lj-maintenance-mode.php on line 245

    Original error
    Warning: Invalid argument supplied for foreach() in /XYZ/XYZ/public_html/XYZ.com/wp-content/plugins/lj-maintenance-mode/lj-maintenance-mode.php on line 333

    Thank you for your help.

    Plugin Author Lukas Juhas

    (@lukasneptun)

    Hi guys,

    Hmmm that’s weird.. what theme and other plugins are you using? I cannot get the same error whatsoever.

    Also what version of WP etc. ?

    Thanks

    Plugin Author Lukas Juhas

    (@lukasneptun)

    Hi guys,

    Fixed in 2.0.2 !

    There was a problem with sites that had different table prefix than the default one (wp_) so with the latest fix it should be all fine!

    Sorry for the trouble, I hope everything will work well now.

    Lukas

    Hello Lukas,

    Thank you for the update it fixed the back end error messages. And so you know, in my particular case I do have a different table prefix as you mentioned, I never thought about mentioning that but I’ll keep a mental note in the future in case something similar happens again.

    Thanks again and have a great day!!

    Thread Starter tekgirlymama

    (@tekgirlymama)

    Thank you! Great support. Yeah, I have your plugin on many sites and different themes. I use as part of security different table prefixes…

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘update damages things!’ is closed to new replies.