Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • Nothing in the debug log which might be useful, just these two lines after adding a new post and seeing the same strange behavior afterwards:

    [12-Nov-2018 09:23:54 UTC] PHP Notice:  Accessing static property WPOCore_Settings::$options_page_hook as non static in /homepages/37/d520648177/htdocs/whentotrade/wordpress/wp-content/plugins/wpovernight-sidekick/includes/wpo-core-settings.php on line 262
    [12-Nov-2018 09:23:54 UTC] PHP Notice:  Accessing static property WPOCore_Settings::$options_page_hook as non static in /homepages/37/d520648177/htdocs/whentotrade/wordpress/wp-content/plugins/wpovernight-sidekick/wpovernight-sidekick.php on line 7

    And after updating the pages to look correct, I see one additional line in the debug.log:

    [12-Nov-2018 09:29:18 UTC] PHP Notice: Undefined offset: 0 in /homepages/37/d520648177/htdocs/whentotrade/wordpress/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/codeblock.php on line 250

    What to check next?

    • This reply was modified 6 years, 1 month ago by datapool99.

    no idea. Really strange. I need to turn down bbpress plugin before updating a page/post. Not good. No idea. I will check the debug logs next and post here…

    Dear Günter,
    thanks for your detailed investigations. I did the painfull route to deactivate each plugin one by one and check…
    The surprising result is that the effect/error is back when the bbpress plugin is activated again. I would have never looked in that direction. I have now kept the bbpress disabled, but as our page has a long form discussion panel, it is no real option to keep it off.
    I dont know what caused the trouble with bbpress activated – we have the latest version of the plugin.
    Do you have any idea why this is caused by bbpress plugin once activated?
    Thanks & Regards,
    Lars

    This reply has been marked as private.

    We have updated to latest version 4.5
    The core problem is: After we manually solve the problem by the workaround (debug/autorepair), and now we update a page (doesnt matter which page) and press the “update” button after the edit. The error is back on ALL pages again. So we again see the “This element was disabled in your theme settings. You can activate it here:Performance Settings” on all pages. We have to manually process each single page now again with the workaround to repair.

    It comes again after each and every page update. This is not usable anymore.

    Any idea?

    Thanks & Regards,
    Lars

    What should I delete via FTP? The complete theme folder? I have also a child theme. Only the main theme? Not sure – so before I start to “delete” via FTP please give some detailed info as this is a very critical operation on the backend…
    Thank you.

    in reply to: Adding Loader/Spinner during WooCommerce Checkout #783148

    looks good. thank you!

    in reply to: Adding Loader/Spinner during WooCommerce Checkout #782018

    I would second the initial request. Once the woocommerce checkout has clicked. The page just overlays a fading grey window. Which sits there until the payment is processed. This may take 2-5 seconds and there is no real user information like “Please wait. We are processing your payment…” – therefore a short message or a waiting spinner instead of just “fading to grey” would really be helpful. Otherwise the user might “click” somewhere after 3-4 seconds without any information.

    Would that be possible somewhere in the CSS or in the php?

    Thanks & Regards,
    Lars

Viewing 8 posts - 1 through 8 (of 8 total)