Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • March 28, 2019 at 4:28 pm #1084164
    sdesign-web

    hello,

    since ! have made the update to enfold 4.5.5 i have the following problems :

    1 – i can not edit no more english version of my pages ( see in private the error mentionned )
    2 – on only one of the page, the footer is not displayed correctly ??? ( see url and screenshot )

    Please find in pc the admin access

    Thank you very much for your help

    Stan

    • This topic was modified 5 years, 7 months ago by sdesign-web.
    March 31, 2019 at 1:16 pm #1085055
    Nikko

    Hey Stan,

    I tried to access, with the login details you gave but it doesn’t work, please check.
    Can you try to restore your backup first? so you can have your live site working.
    Then create a staging site (basically a duplicate of your live site placed on your subdomain) and do the update there, so we can try to test it out.
    It might just be some conflict with some plugins that’s causing the issue.
    Here is a tutorial on how to create a staging site: https://themeisle.com/blog/wordpress-staging-site/

    Best regards,
    Nikko

    April 1, 2019 at 11:46 am #1085438
    sdesign-web

    Hey Nikko,

    first i have discovered another big new issue : i can not restore any backups i did with updraft :-/

    I really need help of kriesi support as never before as my site is partly broken.

    Please find attached the admin access of the staging site i have create.

    Thank you very much in advance for your help !!!

    Best regards,

    Stan

    April 2, 2019 at 8:57 am #1085938
    Nikko

    Hi Stan,

    For the Salon page (link in private content), I have added a 1/1 column after the fullwidth easy slider which seems to mess up the footer.
    I have checked the same setup on my end but I couldn’t replicate the same issue.

    As for the english page, It seems to work properly on my end (2nd link in private content). In THE ESTATE section I put Added text… after the paragraph and it was successful.

    Best regards,
    Nikko

    April 2, 2019 at 1:43 pm #1086071
    sdesign-web

    hi Nikko,

    thank you very much for your time and your help.

    In the end the problem with editing english page has been resolve after cleaning all the cache and cookies of Chrome.

    There is just 2 problems that still remains :

    1 – i can not find the way to have 2 differents traductions of the widget in the footer with wpml, if i change it in english, it change also in french. Some other kriesi person told me last time that this bug will be resolved with the next release ( 4.5.5 ) but it seems not.

    2 – I don,t know why but the texture of the footer ( wood-dark ) is not displaying in english version

    thank you
    Best regards
    Stan

    April 4, 2019 at 8:11 am #1086840
    Nikko

    Hi Stan,

    1. What do you mean by 2 different traductions? is it translations? can you provide the link for the thread you mentioned?
    The workaround I can think of is to create 2 widgets one for each translation then:
    – use widget logic plugin or something like that to set conditions where it shows
    – use css to hide/show widget depending on the translation.

    2. In Enfold > Performance > disabled: CSS file fusion and compression, and it works fine.

    Best regards,
    Nikko

    April 4, 2019 at 10:56 am #1086968
    sdesign-web

    Hi Nikko,

    thank you so much for your help !!

    1- you are right, i put both french widget and english widget translation in a footer column and then i choose for each the language where it must display and it work fine !!!!

    2 – right again ! disableling CSS file fusion and compression make it works fine.

    have a nice day !

    best regards

    Stan

    April 4, 2019 at 11:21 am #1086984
    Nikko

    Hi Stan,

    You’re always welcome, we’re just glad that we could help you :)
    Thanks for using Enfold and have a great day!

    Best regards,
    Nikko

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • The topic ‘issue with upgrade to 4.5.5’ is closed to new replies.