• Hi
    Can you please let me know if there has been any wordpress updates that would have caused these errors
    How do i fix these errors
    they also appear in the backend, and also on the woocommerce page

    home page on dashboard
    Notice: Trying to access array offset on value of type bool in /home/customer/www/marketdirect.com.au/public_html/wp-content/plugins/quick-interest-slider/quick-interest-slider.php on line 47

    and these all at the bottom of my woocommerce backend

    st_route was called incorrectly. The REST API route definition for bb-logic/v1/wordpress/posts is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /home/customer/www/marketdirect.com.au/public_html/wp-includes/functions.php on line 5831

    • This topic was modified 3 years, 9 months ago by Jan Dembowski. Reason: Moved to Fixing WordPress, this is not an Everything else WordPress topic

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator threadi

    (@threadi)

    Both errors have nothing to do with the WordPress core itself. They refer to the code of 2 plugins you use.

    The first error is “Loan Repayment Calculator and Application Form”. You would need to contact their support here: https://wordpress.org/support/plugin/quick-interest-slider/

    The second error is, I assume, “Extra Conditional Logic for Beaver Builder”. Their support can be found here: https://wordpress.org/support/plugin/bb-extra-conditional-logic/

    Both would have to look at and evaluate the one in question.

    Thread Starter janettec

    (@janettec)

    thankyou for the quick reply
    is there a reason why all these have now come up all of a sudden

    as the ones on our website are pushengage and our theme corporate pro

    Notice: Undefined index: site_id in /home/customer/www/marketdirect.com.au/public_html/wp-content/plugins/pushengage/core_class.php on line 1106

    eprecated: implode(): Passing glue string after array is deprecated. Swap the parameters in /home/customer/www/marketdirect.com.au/public_html/wp-content/themes/corporate-pro/includes/helpers.php on line 317

    Moderator threadi

    (@threadi)

    Why this suddenly happens I can’t judge because I don’t know your project. Possible causes are changes to the hosting settings or an update of server components (such as a newer PHP version).

    Since you seem to see the error messages directly, you probably have debugging enabled in WordPress – which is not usual for a live project. Maybe the errors have been there for a while, you just see them now that debugging is enabled directly in the browser.

    The last mentioned error comes from your theme which is a commercial product. If you have questions about it, you should contact their support here: https://www.premiumwp.com/theme/corporate-pro-wordpress-theme/ – because questions about commercial products are not allowed in the forum here.

    And the plugin support for the latter plugin is here: https://wordpress.org/support/plugin/pushengage/

    Thread Starter janettec

    (@janettec)

    Hi
    thankyou and understand
    i have turned off debugging display on website, and they have no gone
    what if i do not do anything, will this cause issues if i can see everything is still working normally?

    thanks

    Moderator threadi

    (@threadi)

    Such error messages are never a good sign. If the plugin developer himself doesn’t correct them (he can’t if he doesn’t know about it) then you might also risk a site failure at some point. “Eventually” could be, for example, if your hoster updates a server component like PHP and then the plugins are not compatible with it at all.

    Therefore, I had already written above that you best write to the respective plugin support. If there is no reaction from the plugin developers, you would have to decide to continue using the plugin and take a risk with it or to look for and use another, functionally similar plugin. In the best case the developers react to something like this and adapt their code with an update.

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

The topic ‘Errors appearing in webpage and dashboard’ is closed to new replies.