Strict Standards: Non-static method WPBakeryShortCode

This topic has 6 replies, 2 voices, and was last updated 10 years, 11 months ago ago by Eva Kemp

  • Avatar: basera@pukka.ch
    basera
    Participant
    December 18, 2014 at 18:26

    This error appears on home page and all pages where we used Visual Composer for layout.
    Strict Standards: Non-static method WPBakeryShortCode::getExtraClass() should not be called statically in …./wp-content/themes/legenda/framework/vc.php on line 963

    It showed up after support of WPML asked me to change to default theme and I changed back to Legenda.

    Please, contact administrator
    for this information.
    5 Answers
    Avatar: Eva
    Eva Kemp
    Participant
    December 18, 2014 at 19:06

    Hello,

    Please provide us with wp-admin panel and FTP credentials in Private Content.

    Thank you.
    Regards,
    Eva Kemp.

    Avatar: basera@pukka.ch
    basera
    Participant
    December 19, 2014 at 15:29

    here it is

    Please, contact administrator
    for this information.
    Avatar: Eva
    Eva Kemp
    Participant
    December 19, 2014 at 16:40

    Hello,

    I’ve updated Visual Composer plugin and the errors have gone.
    Please check now and clear browser cache before.

    Thank you.
    Regards,
    Eva Kemp.

    Avatar: basera@pukka.ch
    basera
    Participant
    December 19, 2014 at 17:05

    Oh nooooo, now I have this 404 again when I click on a product in the shop.
    That was the issue I was working on with WPML since 2 weeks.

    Avatar: Eva
    Eva Kemp
    Participant
    December 19, 2014 at 17:34

    Hello,

    There is a problem with your permalinks settings. Please check them.
    Also ask your host to increase memory limit as there is an error:
    Fatal error: Out of memory (allocated 20971520) (tried to allocate 2048 bytes)

    Thank you.
    Regards,
    Eva Kemp.

  • Viewing 6 results - 1 through 6 (of 6 total)

The issue related to '‘Strict Standards: Non-static method WPBakeryShortCode’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.