We subscribe to the new events for changed title/description and update
the form fields so the changed value is stored.

We use the new event that is emitted by the Analyser to update the
keyword and seoScore values.

This is used to display the URL of the page in the snippet.

The pressing of the AJAX button within the form to submit to our Drupal
rendering endpoint also causes a formUpdated event to be fired. This can
cause a loop.

A simple if statement ensures this loop is broken in time.

We isolate the events from the React components and ensure they don't
trigger other events on the enclosing form that we're listening to.

RTSEO.js 3.0.0 has been rewritten to use React and Redux. It uses React
to display the UI instead of the YoastSEO built in presenter so that we
have a more fine-grained control over how our form interfaces with
YoastSEO. This change also enables the translation of feedback messages.

We alter some of the form, template and analyse logic to properly
interact with the changes that have been made in the javascript. This
should help the Real-Time SEO widget work if multiple instances
(multiple forms) are displayed on the same page.

Mario Vercellotti authored Oct 01, 2018 and Alexander Varwijk committed Oct 01, 2018

Issue #2980480 by vermario: Validation errors in forms are not really cleared when analysis is performed

Léon CROS authored Oct 01, 2018 and Alexander Varwijk committed Oct 01, 2018

Issue #2984590 by chipway, alonaoneill: Apply new {project}:{module} format for dependencies in info.yml

Alexander Varwijk authored Jun 03, 2018 and Alexander Varwijk committed Jun 03, 2018

Issue #2974301 by Kingdutch, emclaughlin: Yoast SEO Field Ajax Race Condition With Nested Paragraphs

Ruslan Piskarov authored Jun 03, 2018 and Alexander Varwijk committed Jun 03, 2018

Issue #2974202 by RuslanP, Ronak.addweb: Add a point to the end of the configuration menu item description

Instead of manually reading a YML file we now use the Drupal config
system to store the SEO scores. This makes it configurable and
easier to maintain.

This configuration is now also used by the javascript.

This commit removes some code that was used in earlier versions
that attempted to perform the new entity form submission. This is
now tackled by Form Handlers and solved in a better way.

Alexander Varwijk authored Apr 07, 2018 and Alexander Varwijk committed Apr 07, 2018

Issue #2941283 by Kingdutch, edurenye: Support context specific Metatags such as [current-page:title]

The new yoast_seo_metatags_alter searches for a yoast_seo field and
uses its value, if present, to alter the metatags of a page.
Because the field widget settings can not reliably be obbtained
(a widget without those settings may produce the same value) we
instead only check if the value is set. In the widget we then ensure
that no value is present if editing of title or description is
disabled.

This leads to a situtation where a custom title cna be lost if the
field widget setting is disabled and the entity is re-saved,
however, it ensures that the saved value is always equivalent to
the one displayed in the entity create/edit form.

Christian Fritsch authored Feb 03, 2018 and Alexander Varwijk committed Feb 03, 2018

The config form in the module replicated a lot of functionality
that is actually owned by the Field UI module. Therefor it makes
sense to simply remove the config form and make use of that
functionality instead.

Alexander Varwijk authored Jan 20, 2018 and Alexander Varwijk committed Jan 20, 2018

Issue #2934515 by Kingdutch, millionleaves: CKEditor openDialog error if Yoast module is enabled with multiple text fields

The class name was already changed and EntityAnalyser is more
descriptive.

This commit implements an alternative analysis method where an
entire entity is rendered. This makes the module agnostic of field
types for its analysis purposes. By hooking into the entity form
process different entity types can be supported and no entity
specific handlers will need to be written.

This also fixes #2917280

The added test tests the administration screen of the Real-Time
SEO module. It ensures that the module can be succesfully enabled
for simple nodes.

To achieve a passing test some of the classes have been refactored

slightly.

We now check whether the user can use the Real Time SEO module and
whether the user has at least view rights for the module. This way
we aren't able to leak data to the entire world.

The keyword highlighter still tried to highlight the keyword if it
didn't exist in the snippet title, leading to a malformed display.

We decided not to change existing views anymore but instead create
our own overview of all analysed entities. The added update hook
should remove our field for existing installations.

We don't touch any already set-up analysis as that'll correctly
get picked up in the configuration page.