Version v3.4.16 / Modals not working

Deleted after edition of opening post

Deleted after edition of opening post

Have contacted Developers to take a look.

The biggest risk in falling back is any transactions added to your database. Otherwise, simplest would be to ask Hosting to recover latest backup (if it was taken in past 24h). Otherwise, Developer should take a look today and will need to see the site in error state.

Hello, can you answer to some questions?
1) Do you mean that they worked before the upgrade?
2) How do you build them, with a plugin? If yes, did you also upgrade the plugin?
3) Did you try cleaning wp-supercache’s plugin and disabling the plugin itself?

Thank you.
about copying the old tc-scripts, well there have been improvements to it in the latest version, none of them, though, should cause your issue, and yes should be safe, but .. try what do you have to lose ? ??

p.s.
as you’re not in debug mode, you have to copy tc-scripts.min.js not tc-scripts.js
p.p.s.
you can always downgrade your customizr version to the previous one..

I just copied a piece of code from your src html to reproduce the issue, but it works fine here.
https://prntscr.com/9fn2fc

It might also be a conflicting plugin issue, but in this case shouldn’t depend on the theme update, as there have been no modal related changes to it.

Ok, found it, the problem is a conflicting plugin named
simplemodal-login
(or at least this is a plugin you have I found conflicting, not sure if you have other conflicting plugins)
Of course this has nothing to do with the theme upgrade.
It conflicts also with the previous theme release
(just tested with 3.4.15 – probably it conflicts with ALL theme release. The modal feature of this theme is performed with the bootstrap2 modal js code)
You should disable that plugin then.

Hope this helps.

Amazing support service! You saved my head.

I installed that plugin (simplemodal-plugin) few weeks ago but never used it, nor did it messed up my sites till last update. Once I disbaled the plugin (adding it to my black list) all came back to regular state.

The lesson here is that we must check what tools do plugin developers use before installing them.

Thanks, thanks, thanks!

My recommendation is to NEVER update on live (production) environment before testing it first on a separate identical test one.

I always fire up a test environment, which is a copy of the live one (production), and do all my updates/ new releases there first and check if everything works fine.

I also always backup everything in production before releasing new stuff or updating anything.
If something goes wrong you always need to have a way to rollback to the state is was before.

For versioning and compare purpose you may also want to keep all developments under a source control software or something like that.

That will be my recommendations, so no need to panic when things go sideways in production.