Viewing 4 replies - 16 through 19 (of 19 total)
  • Thread Starter alexDx

    (@alexdx)

    How does this solve this issue exactly? The problem isn’t data syncing between the two environments. The problem is that the new version of Yoast SEO is not working on staging environments. The issue isn’t with syncing, it is with titles and metas not updating when saving in the post/page editor on staging sites across the board.

    That still doesn’t answer the question as to why this is happening with the new version of the plugin, when all prior versions did not have this issue.

    Something changed with the new plugin that doesn’t properly update the database.

    Thread Starter alexDx

    (@alexdx)

    How exactly does this solve the issue though? The issue is not syncing between the two environments. Implementing this will just mess up our staging sites. The issue is titles and metas not updating on staging sites with the latest version of the plugin.

    It also doesn’t answer the question as to why this issue just cropped up with the latest version of the plugin, and everything was working fine on prior versions. Something in the recent update is not updating the database correctly on staging environments.

    Thread Starter alexDx

    (@alexdx)

    We shouldn’t have to alter settings on our hosting environment or on each individual staging site on 300+ websites to solve this issue that is an issue with the new version of your plugin.

    Plugin Support Mushrit Shabnam

    (@611shabnam)

    Hi @alexdx

    In version 23.0, we fixed a bug that caused unnecessary data to be written in the Yoast indexable database on non-production sites (where the environment is not set as non-production) or when the Yoast\WP\SEO\should_index_indexables filter was used to disable the indexable. Please take a look at the PR here for your reference. This bug fix was to fully prevent the creation of indexable data on the staging site. Otherwise, when migrating the site from staging to live, the indexable must be reset manually, else the Yoast indexable database will contain the staging site URLs, and it may get outputted on the source code.

    Regarding the issue you pointed out, we followed the steps you mentioned on the staging site and noticed that the values you added to the Yoast metabox are saved in the database. However, the overview screen outputs the recently created SEO title and meta description values on the column for all the posts. So we created a new bug report for it here: #21460.

    We tried to replicate the other issue you pointed out i.e with the page source code not getting outputted with the SEO title and meta description you added to the metabox. Upon testing from our lab sites, we noticed that the SEO title and meta description with the values added to the Yoast metabox are outputting correctly on the source code without any actions.

    So, to narrow down the issue further, can you please check whether you have added any filters for the indexable or set the environment as staging other than the WP_ENVIRONMENT_TYPE?

    Also, please make sure to reset the indexable again on the staging site to check whether the issue continues with version 23.0. After resetting the indexable, can you please check the database to see whether the table yoast_indexable contains any values?

    We look forward to hearing from you and are happy to help you.

Viewing 4 replies - 16 through 19 (of 19 total)
  • You must be logged in to reply to this topic.