bvigorda

Never mind. Error message is gone and all is well. Must have been just one of those unexplainable things. Thank you.

O.K. In non-tech speak, I’m going to take that as a yes, my child theme is safe during theme updates. If not and I’m misunderstanding, please let me know. Thank you.

Hello,

So sorry it has taken so long to reply. I initially replied by email then finally found I can’t do that so here I am.

The information you gave me in How Child Themes Work gave me the clue to what was wrong. I didn’t realize only the child theme should be active. My Divi theme was the one that was active. So I reinstalled Twenty Fifteen, enabled it then enabled Divi child and that did it.

I don’t know how my child theme got deactivated. I know I had been using it since I installed your plugin. I could see it named a the active theme when I’d use my theme customizer. Maybe I deactivated it when I deactivated my old themes. Anyway it’s working now and thank you for the info!

I wonder if you could answer a dumb newbie question. I made changes to my Divi theme using CSS-Hero and Divi’s own Custom CSS field. As you know, they are both supposed to prevent problems with theme updates.

Still, I decided to create a child theme just in case. Is my child theme still protected from theme updates even if it was installed after the CSS code was used?

It makes sense to me that it would be, but it would give me peace of mind if you could confirm it.

Thank you,
Gai

Hello Again

I should mention that I installed Child Theme Configurator after making quite a few CSS changes using CSS-Hero and Divi theme’s Custom CSS box.

Is it too late for protection from losing customizations from theme updates if I installed a child theme after the CSS customizations? Mostly I think not, but I just want to be sure.

Thanks,
Gail

Thank you!

Thank you!! I appreciate your quick reply also!

Eric = thanks so much for your reply! I never thought I’d hear from you since your last post on this was a month ago. Your explanation helps a lot – can’t thank you enough! Gail

Hi Paul,

That’s wonderful about the file editing in lockdown. I did have it set, but didn’t understand it at the time I set it up. Just did what was recommended.

By protecting local/remote files – please understand I’m very new to FTP and I may not be using the right terminology. I read that using FTP is vulnerable if a computer is hacked or has a virus or malware. I do have MSE anti-virus and firewall, but I just want to feel extra safe with FTP. I know there are such things as FTPS and FTPES and I’d like to know more about them – like how to get them and use them/set them up. FTPES has been especially recommended. Unfortunately, the recommendations don’t come along with any instructions how how to get them in the article I read.

Thank you,
Gai

Eric,

I sure hope you see this since it’s a month since your post.

I wonder if you could please help a real newbie understand what you’re saying. By any chance did you mean if a site has eCommerce, only use SiteGround’s Varnish static and dynamic caching and also Memcached?

In other words, don’t use SG CachePress if a site has eCommerce?

Thanks

One other request. Is it possible to do a tuturial on how to protect local and remote FTP files? Or do you know of a tuturial – something a newbie to FTP could understand? Thank you.

Hello,

Could you please tell me how to locate and remove the CSS the plugin injects?

Unfortunately, reset isn’t doing it.

Thank you,
Gail

Hello,

I sent an email to your company last week and haven’t heard back yet. I’d like to know what the pricing is on this for a single user/one website. Thank you.

Thank you Eli. I’m always happy to donate to a nice plugin and I’ll definitely donate to yours one way or another. Is there some way to get the automatic definition updates without the BETA for Core Files Integrity Check? I’m not good at fixing problems at my website if I should run into any with BETA. Thank you.

Also – is the $29 a one-time payment or does it need to be paid annually? Thank you

That’s great – thank you!