Customizr update with a child theme and Polylang

We’re now on 3.1.22. You could wait until it comes through automatically.

It’s painful, but the best way to learn is to suffer and practice recovery. When it’s happened a few times, you’ll learn not to panic and to stay in control without having to revert to Hosting each time. But I’ve needed help from my Host today so it never goes away.

I suggest you bite the bullet and try it. There’s not a lot we can do to help until there’s a problem to diagnose.

Good luck!

A key thing is to have FTP access. That way, if something happens then behind the scenes you can put it right yourself (by editing your child theme files with FTP and not having to rely on the WordPress dashboard).

See if you can find out the password for FTP access to your site and install something like FileZilla.

Thank you to both of you. I’s not only painful but really scary because I couldn’t access the dashboard anymore and really don’t know what to do in this case. We’ll see…

I have FileZila, I used it in the first place to install the Polylang bridge code. I have to learn if I want to access my site this way!!!
But it’s great to know that I can. At least I can do some research and try.

At the beginning, you know just enough to get yourself into trouble, but not enough to get yourself out of it again ?? The trick is to go beyond that point.

If things go wrong with your child theme, then you simply rename your child theme folder with FTP. If things go wrong with Customizr, you simply rename your Customizr folder. (You can find these in the wp-content\themes folder.) In each case, WordPress will no longer find the theme it expects and will switch you to twentyfourteen. From there, you can put things back together again.