Forum replies created

    Evgeny
    Keymaster
    Posts: 988
    August 24, 2020 at 3:29 pm #45221

    Did you clear your cache? CTRL+F5 on the PC or Command+Shift+R on a Mac.

    Evgeny
    Keymaster
    Posts: 988
    August 24, 2020 at 3:05 pm #45219

    Hello. I’m not sure I understand the situation exactly, but in any case – what you need to do is to update to 2.9.9.8 + Component Shortcodes 1.0.2 + Widget Box + Demo Awesome (if you want). Only then you will be able to solve the incompatibility issues. The problem with the layout after the upgrade is inevitable because after 2.8.3 we completely changed the technology behind the theme. Although we have a mechanism in place, that transfers Customizer settings, it is no perfect, and with every new version we roll out, it is less efficient. You need to upgrade as I’ve described above, deactivate t4p-core and delete it – it causes conflicts now and isn’t being used nor updated for years. The layout you will have to rebuild in the new theme, everything that needs to be corrected. There is no other way. And do not forget at the end of the process to clear your browser’s cache.

    Evgeny
    Keymaster
    Posts: 988
    August 23, 2020 at 10:52 pm #45216

    Hi. Thank you for bringing this up. In some other thread we’ve discussed it already – in the next update we will correct those files. But still, thank you for taking the time to help out other forum members.

    Evgeny
    Keymaster
    Posts: 988
    August 23, 2020 at 10:49 pm #45215

    No problem, happy to help.

    Evgeny
    Keymaster
    Posts: 988
    August 23, 2020 at 9:02 pm #45213

    That’s not entirely correct. The problem now is your Team Member’s Pro plugin. If you disable it, everything works as expected. This plugin is incompatible with WordPress 5.5, creates an error, and interferes with our scripts. Look: https://prnt.sc/u4k8i5
    You should talk to their support, update it, or replace it. We cannot fix these errors, unfortunately – it’s their turf.

    Evgeny
    Keymaster
    Posts: 988
    August 23, 2020 at 9:58 am #45210

    Yes, this is how it is supposed to work. Customizer settings are different for every theme, including child themes. If you are not planning to change the functionality and/or design beyond what it in Customizer or Additional CSS, then there is no need for a child theme. But in any case, we will figure out why the child theme creates these bugs and we will solve them.

    Evgeny
    Keymaster
    Posts: 988
    August 23, 2020 at 12:16 am #45208

    This time we actually can get in. Interesting – once you activate Evolve Plus, the issues are gone. When you go back to the Child Theme, the issues are back. We will take a deeper look, but in the meanwhile the child theme is active.

    Evgeny
    Keymaster
    Posts: 988
    August 21, 2020 at 4:08 pm #45204

    Hi. Sorry – I thought my colleague answered you. No, the password doesn’t work.

    Evgeny
    Keymaster
    Posts: 988
    August 21, 2020 at 8:36 am #45201

    Yes, but that still doesn’t mean that speaking Elementor’s support would be illogical. You can theoretically find numerous other themes that generate precisely the same conflict as with Evolve, so it doesn’t mean anything. Usually, plugins solve conflicts with themes, not the other way around. They can also pinpoint the issue much easier and faster because they are used to the process. Anyway, if you wish to disable everything related to sliders in Evolve Plus, you go to Customize and make sure that Bootstrap Slider, Parallax Slider, and Posts Slider are deactivated. Theme4press slider should not have any slides as well. We can also take a look, but for this, we would require access to your admin area and FTP.

    Evgeny
    Keymaster
    Posts: 988
    August 20, 2020 at 10:45 pm #45199

    Hi. Hard to give an answer just like that ) It sounds like a question to Elementor support, because this is clearly not our functionality that doesn’t function correctly here. Did you try that?