Hello,
I installed your latest update that was sent on 8/9/2018 PST and it broke my home page:
Before my home page looked like this: https://www.screencast.com/t/uHsfCkoyys
Now it looks like this: https://www.screencast.com/t/sUupCBGOmvb
I had to roll back my restore to get it to work. Why would the update interfere with the home page design? How can I prevent this from happening in the future?
Thanks!
I would like to add that “Edit with TD Composer” is no longer an option under page edits.
Has that feature been moved elsewhere?
The update also broke my homepage in the same way and I had to recreate it again.
@epickenyan – is the TD Composer working for you? I don’t see it in my staging environemnt after the update…
@tszabolcs – all plugins are updated…
It did not work when I opened it with the broken page after the update. Sent an error like this – Error at rows: 7(models) : 4(dom). The model does not match the content-. But when I recreated the page afresh (deleted shortcodes), it worked. But if you are talking about not seeing it in the plugins section, then I do not have that problem.
@epickenyan – I found the problem, I looked into the plugin section in the Newspaper managed section and saw the following:
Updating Plugin: tagDiv Composer
The plugin does not have a valid header.
Download failed. cURL error 60: SSL certificate problem: unable to get local issuer certificate
Return to tagDiv plugins panel
I was able to get the issue fixed by my Cloudways engineer. It was an issue with the http/https and how the plugin was seeing it in the header.
Hopefully it will not be an issue again during the next update.
Can you tell me how you fixed this? I am also with Cloudways and have this same problem.
When I did the update, I didn’t update the TD Composer, cause I believe the main theme update disables it, and then when I enabled it, everything worked again.
If you’re trying to update theme in staging, you’re going to need to work with your CW engineer and have them add something to your .htaccess file to account for https so the update can successfully install. If you explain the issue to them, they should understand.
Hope that helps!
