Bug #2909
closedyoast install on luna theme
0%
Description
Hi Dom,
This may be no big deal -- but I want to check with you before I do anything disastrous to the Fellowship site. After installing the Yoast plugin on the site, it gave me this error message: "Your theme contains a meta description, which blocks WordPress SEO from working properly, please delete the following line, or press fix it" (See attached image).
Should I go ahead and fix it, or will this break the site?
Thanks!
Erin
Files
Updated by Dominic Giglio over 10 years ago
- Category name set to WordPress (misc)
- Target version set to 1.5.11
Erin,
I just took a look at the live site and error message. I don't believe you will break the site if you click the "fix it" button. However, I'm not sure if that button will actually work. I'm concerned that you will receive another error message telling you that you do not have access to alter the template from the admin section. It might work and it might not.
The correct fix is for me to remove that description <meta> tag from the header.php template file in the child theme's directory. I'm going to do that right now so that it will be fixed after the next release on 12/11.
My question for you (and Matt) is this: do we need to fix this now and have Boone push out a 1.5.10.1 emergency release, or can you wait to finish setting up WordPress SEO on the 12th?
Updated by Dominic Giglio over 10 years ago
- Status changed from New to Resolved
Erin,
I've removed the description <meta> tag from the header.php templates in both the fellowships and chasefrobinson Luna child themes (incase you want to enable WordPress SEO on the Provost's site in the future as well). I believe you can continue to use the WordPress SEO plugin features and the error will disappear on the 11th when Boone releases version 1.5.11 of the Commons.
Commit: https://github.com/castiron/cac/commit/7afd15317f3ae593354ffc9b46b3df711787344e
Updated by Dominic Giglio over 10 years ago
Just double checked the plugins on Chasefrobinson dashboard and it looks like Erin disabled the plugin. I don't want to re-enable it if she's not ready to set it up. If she could re-enable when she has time, the error message should be gone.