Legenda update fatal error - by lulufactory

This topic has 6 replies, 2 voices, and was last updated 8 years, 6 months ago ago by Jack Richardson

  • Avatar: lulufactory
    lulufactory
    Participant
    October 20, 2015 at 09:12

    Hello,
    I updated Legenda to version 2.9.2 and got this message in my Home Page : Fatal error: Call to undefined function et_translateColumnsCountToSpanClass() in /web/abcdjoannes/lulu/wp-content/themes/legenda/framework/theme-functions.php on line 2148

    VC has also been updated to version 4.7.4 as requested by your security notice.

    Could you please help me fix it ?

    Thanks in advance.

    Please, contact administrator
    for this information.
    5 Answers
    Avatar: Jack Richardson
    Jack Richardson
    Support staff
    October 20, 2015 at 09:28

    Hello,

    Please specify what folder your files are located in and provide WP Dashboard credentials.

    Thank you.
    Best regards,
    Jack Richardson.

    Avatar: lulufactory
    lulufactory
    Participant
    October 20, 2015 at 10:35

    Sorry, I am not an expert, but I guess files are under /web/abcdjoannes/lulu.
    Please find WP Dashboard Credentials on private.

    Many thanks for your help.

    Please, contact administrator
    for this information.
    Avatar: Jack Richardson
    Jack Richardson
    Support staff
    October 20, 2015 at 11:18

    Hello,

    You were using outdated version of Post Grid element in Visual Composer editor. I’ve recreated it using updated Post Grid element in the home page.

    Please check the site now.

    Best regards,
    Jack Richardson.

    Avatar: lulufactory
    lulufactory
    Participant
    October 20, 2015 at 11:29

    Hello,

    Many thanks. It seems to work perfectly.

    Best regards !

    Avatar: Jack Richardson
    Jack Richardson
    Support staff
    October 20, 2015 at 12:10

    Hello,

    You’re welcome.

    Best regards,
    Jack Richardson.

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

The issue related to '‘Legenda update fatal error’' 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.