Forum replies created
They are all obsolete, after backing up, turn all those plugins off (all you’ve mentioned) and remove the old theme. 2.8.3 is not that old, it is right before the change – but if you used the T4P builder heavily, there might be a problem because many of the shortcodes aren’t supported. Unfortunately, we do not know that much about the old theme – the old team is not here anymore, and we (the new team) are simply not familiar with it. Sorry.
The newest version is 2.8.8.8. Could you please update it first? If nothing positive happens, we will gladly have a look )
Hello. This really shouldn’t happen, this code wasn’t touched. But we will be happy to help. Please upgrade to the latest version and if the problem persists, send us a link to your website. We will let you know if we need FTP and admin access. Thanks.
Hello. The process of moving from older versions to the new version (based on Kirki) is fairly simple – after backing everything up, you need to remove the old one and upload the new one. Activate it and install all required plugins. That being said, some of the clients have a version that is too old and relies heavily on the Theme4press builder. There is no migration tool for that, Component Shortcodes will not support all the old shortcodes and you will have to rebuild. But first, try the regular migration please, see if it works for you.
Hello. What you are describing is totally normal for a child theme, that wasn’t installed from the very beginning. The child theme inherits the abilities of the main theme, but not the settings you’ve changes and CSS codes you’ve added. You will have to transfer them manually or with the help of an import/export plugin of your choice, that can transfer Customizer settings.
Hello everybody, the update pushed right now fixed the problems you’ve mentioned. Just use the latest version.
It would be best to use API. Then you don’t have to deal with the file manager. As for the scarce information you’ve provided – it is not very helpful. Since the zip file is fine, this might be some kind of file manager issue. Check it with your hosting provider, please. Thank you.
Hi. If you’re using the front page builder, you can only add content boxes, as you’ve already done. You need a developer to do what you want to do. If you’re building the homepage with shortcodes, then you can embed anything you want using content boxes. In any other case, you need a developer.
I was able to recreate this issue. It is an incompatibility problem between SVG and IE, most probably. We will address it in one of the coming updates. In any case, there is nothing to worry about – IE is anything BUT a common browser. Is it being used by 1.57% of internet users, and the number is declining every month.
We’re on it, will let you know once we’ve figured out what’s wrong.