Hannah West Design

Thanks so much! I figured it was you but with all the security issues this year I just had to make sure. Have a fabulous day!

Oops, it also shows changes in this file: wp-fastest-cache/templates/update_error.php
You?

And sorry, the above files were not modified 19 hours ago, but more like 45 minutes ago.

Thanks!

LIttle Happy Dance!! It worked! I had to resave my custom menu after activating, but my custom styles and category exclusions are all intact! I will quickly disable my Edit CSS custom styles to make sure it stays this way…Squeak!! Everything looks good! Thanks for helping me help myself, Andrew. It was the error log I needed, and your suggestion spurred me to dig harder for it since I couldn’t find it in the hosting account. Looks like I’m good to go now.

Nope, that didn’t work. Again a new 500 internal server error:
20150629T112721: https://www.kimnovakartist.com/wp-admin/themes.php
PHP Fatal error: Cannot redeclare exclude_category_home() (previously declared in /hermes/bosnaweb04a/b761/ipw.kimnovakartistcom/public_html/wp-content/themes/twentyfourteen-child/functions.php:10) in /hermes/bosnaweb04a/b761/ipw.kimnovakartistcom/public_html/wp-content/themes/twentyfourteen/functions.php on line 527

It looks to me like this is due to the fact that I had previously added the exclude categories code to the main Twenty Fourteen functions.php. Let’s see if removing it before activating the child theme works.

Activating the child theme resulted in a new error appearing 3 times in the log:

20150629T110239: https://www.kimnovakartist.com/index.php
PHP Fatal error: Cannot redeclare theme_enqueue_styles() (previously declared in …/public_html/wp-content/themes/twentyfourteen-child/functions.php:5) in /hermes/bosnaweb04a/b761/ipw.kimnovakartistcom/public_html/wp-content/themes/twentyfourteen-child/functions.php on line 18

Looking at the code, I do see that the line
add_action( 'wp_enqueue_scripts', 'theme_enqueue_styles' ); appears at the beginning AND the end of the enqueue code. In my file, that’s line 3 and line 18. This is the way it was presented in the Codex…but could that be in error? I do see a note that this only works if you have one stylesheet, which is all we have in this case. And looking again I see another note: “Your child theme’s stylesheet will usually be loaded automatically. If it is not, you will need to enqueue it as well. Setting ‘parent-style’ as a dependency will ensure that the child theme stylesheet loads after it.” So maybe I don’t even need that second block of code. I’ll try removing it and activate again…

Thanks for your help.

OK, I think I see now that the opening line php declaration in the Codex is written in brackets that should not be included in the file. I’m going to try removed the parens and see if activating the child theme works after that. I’ll let everyone know if this worked. I’m a newb when it comes to PHP code but learning bits and pieces here and there…

This server error appeared several times in the sever error log, apparently for each time I tried to activate the child theme and instead got a 500 internal server error:

20150628T135127: https://www.kimnovakartist.com/wp-admin/admin-ajax.php
PHP Parse error: syntax error, unexpected ‘)’ in …/public_html/wp-content/themes/twentyfourteen-child/functions.php on line 1

This appears to reference the opening of the functions.php file, which I created according to the instructions on this page of the WordPress Codex: https://codex.www.ads-software.com/Child_Themes as follows:

(<?php)

What should I do?

Hi, I’ve used SEO for WordPress by Yoast with Divi and noticed these issues too, but only in pages/posts created using Divi’s Page Builder. I’ve concluded that this is because Yoast cannot program the plugin to recognize and access all the different types of custom page builders that developers include in their premium themes (How time-consuming would that be with all the theme developers out there who create proprietary page/post editors! Not cost efficient on his part I’m sure), so it’s just looking at the default WordPress Editor to find the content to be analyzed. In some cases (usually only in WooCommerce product editing pages) I can get around this by entering the same content into the default editor (which I then have to delete after analyzing so there isn’t duplicate content on the page), but this can’t be done on regular pages/posts since you’ll lose all the content you created in the Page Builder whenswitching over to the default editor. Really, I know the plugin works, so I just take the page builder limitation into account when reading the SEO plugin’s guidance, knowing that if it could read the headings and text and detect the images there, the page would receive a higher score. I know this doesn’t actually help you, but I hope it’s reassuring.

I will definitely press the host to account for that. Even with all plugins but Jetpack and BPS deactivated, the 404 reversion occurs. Never seen anything like it and I do have other clients with this host.

I removed all custom code except the redirects, brute force and bot enumeration code. Mail is still not working, so I’ll have to press the host about that too.

OK, I regained access to admin and the site is back up. I have no idea why the htacess file would continually revert to 404 as it has been, but it looks like it’s sticking for now. I will leave the site with the default WP rewrite rules for now and see what I can do when I get back. Thanks for the additional advice on how to proceed. The invalid code in the Custom Code might have been the WP rewrite rules, which I added because W3TC was continually notifying me that rewrite rules could not be detected.

OK, I have tried to restore the htaccess file, and the site comes up for a few seconds then goes back down. Admin not accessible. Now I really confused and not sure how to leave this site operational before I step out.

Nope, the moment I activate it, the site goes down and admin in not accessible. Guess I’ll have to put default wp rewrite rules and redirects back in htaccess and leave it that way until I get back. Thanks so much for the time you’ve put into helping me. Hope we can getthis worked out!!

Oh, this is so weird. Just went to look at the root htaccess and it was blank again, though this time with 644 permissions. I just removed all the W3TC stuff from BPS custom code and created a new root htaccess file, activating now…

Sorry, I renamed the Wordfence and W3TC plugin folders, but not the enclosing plugin folder. Can I leave it that way and reactivate BPS for now?

Saw your previous message about file permissions…their WordPress support guy said he didn’t know why it was set to 404 and thought that was part of the problem, so I don’t think it’s required by the host.

I went back and the root htaccess file had reverted so all the W3TC stuff was there again and the permission had again reverted to 404, so I changed it and replaced the default WP rewrite rules. I had deleted the admin htaccess, and now the site and admin are back up. Now I’m super-short of time but don’t want to leave for the afternoon with the site unprotected at all. I just made sure W3TC won’t reactivate by renaming the plugin folder. Should I go ahead and re-create root/admin htaccess files and activate them?