-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add checkbox to disable Largo's SEO-related output #1437
Comments
Trying to post something similar saw that is already here. I want to use a seo plugin with Largo but apparently in the <title> meta tag, my site title appears twice. Outputted by the plugin and by the theme. Is it something I can override to fix this? |
@cartonic What you describe is this issue: #1470 The temporary fix for this is copying Largo's |
benlk Thank you for the help. I'll do that for now. |
Would we want to remove the SEO functionality in |
A checkbox would be awesome since some people could rely on this only. Since I use YOAST that already has the functionality I would delete that content for now.
On Friday, September 15, 2017 9:46 PM, Ben Keith <notifications@github.com> wrote:
Would we want to remove the SEO functionality in inc/opengraph.php entirely, or continue to include it by default but have a checkbox/toggle that lets people disable it if they don't want it?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I would still argue that having a sane set of defaults that don't necessarily rely on a plugin is a good idea, particularly for very small sites. The option to modify the defaults, filter the output of various functions, etc. would definitely be preferred though to avoid potential collisions like the one described here. |
Yes, exactly. If possible a toggle in the admin panel would be the best solution. Who wants to use a dedicated plugin to disable that feature.
On Saturday, September 16, 2017 12:28 AM, Adam Schweigert <notifications@github.com> wrote:
I would still argue that having a sane set of defaults that don't necessarily rely on a plugin is a good idea, particularly for very small sites. The option to modify the defaults, filter the output of various functions, etc. would definitely be preferred though to avoid potential collisions like the one described here.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
a good start would be to detect Yoast and automatically hide those settings if it's activated. |
Full fix in Largo:
A quick fix for this issue in child themes is to define the function |
#1589 removes Largo's largo_opengraph if Yoast is active, but that kicks the can down the line a while. |
The "if yoast is active" check should just be a option in the theme options:
|
Get the theme out of the way to other plugins can take over SEO functionality
The text was updated successfully, but these errors were encountered: