Skip to content

Just changed some code for the diacritics support in /js/wp-seo-metabox.js#2

Closed
gbili wants to merge 7 commits intoYoast:masterfrom
gbili:master
Closed

Just changed some code for the diacritics support in /js/wp-seo-metabox.js#2
gbili wants to merge 7 commits intoYoast:masterfrom
gbili:master

Conversation

@gbili
Copy link
Copy Markdown

@gbili gbili commented Dec 27, 2012

It is more clear now whether the matched keyword is the real keyword or the diacritical counterpart.
It says 52 files changed, but really I only would like you to merge the wp-seo-metabox.js if that is ok with you thanks.

gbili added 7 commits December 8, 2012 22:32
…repo was on GitHub to merge from jdevalk version is from 1 month ago)
or not. The update makes wp-seo match all occurences of the keyword
inside the content. It then informs the user what type of matches
it found.
Case scenario : keyword has no diacritics, but the content
(anywhere in the content: url, title, text, etc.) does have 2
keywrods with diacritics and 3 without. The new update outputs this
to the user:
<span title="it you see D.E. it means Diacritics Equivalent (Intl chars)" class="good">
Yes (3), D.E (2)
</span>
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moved ptest() function below removeLowerCaseDiacritics()

@barrykooij
Copy link
Copy Markdown
Contributor

@jdevalk What's your say on this PR? It's over a year old so there probably quite some merge conflicts and as you stated in #16 it's pretty messy (52 files changed).

barrykooij added a commit that referenced this pull request Jan 29, 2014
@barrykooij
Copy link
Copy Markdown
Contributor

This PR has been open for a very long time and our codebase has changed a lot since this PR was made, this PR is very messy and it appears that half of this PR is already added to current master. For these reasons it has become almost impossible to merge this PR into master.

@xanghyr xanghyr mentioned this pull request Apr 5, 2022
3 tasks
@leonidasmi leonidasmi mentioned this pull request Apr 14, 2022
8 tasks
hansjovis pushed a commit that referenced this pull request Nov 21, 2022
Moved docusaurus outside website directory
hansjovis pushed a commit that referenced this pull request Nov 21, 2022
Updated woocommerce schema
nickdavis added a commit to nickdavis/wordpress-seo that referenced this pull request Apr 1, 2023
Fixes Yoast\WP\Lib\Dependency_Injection\Container_Registry::register(): Argument Yoast#2 ($container) must be of type YoastSEO_Vendor\Symfony\Component\DependencyInjection\ContainerInterface, null given, called in /wp-content/plugins/wordpress-seo/lib/abstract-main.php on line 34

Discussed with Yoast Support via email and referencing issue number IM-296. As requested, this is a PR which solves this issue which I'm consistently seeing when installing WordPress SEO Premium and Yoast SEO Local via composer (with WordPress SEO standard, installed as a dependency) for a long time, across multiple versions.

Full error message / call stack at the following link:
https://share.cleanshot.com/3TNnjlHH
@nickdavis nickdavis mentioned this pull request Apr 1, 2023
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants