The current update to 8.x-2.0-beta6 completely destroys the data integrity, the patch # 2983348 → is responsible for this.
How I found out by chance: I updated the module and rolled it out on 23.11 to the productive environment. 2 days later, the monitoring showed that the Google Bot was extremely rampant on the website. At first I couldn't make sense of it. I went into the Google Search Console and was shocked to discover that over 15,000 nodes were kicked out of the index from 23.11 onwards.
At first I couldn't explain it at all, until I got the hint from some users that the Solr search was giving strange dates and times for many articles. On closer inspection, I found that over 32,000 nodes have the same published date.
It explains of course why Google kicked the pages out of the index, old articles suddenly & en masse get more recent dates. So the data does not fit with Google's matching, ergo these nodes fly out of the index.
I have a database of over 40,000 nodes from 12 years, a year ago I migrated from another system to Drupal. So the module was installed from the beginning and all migrated nodes got a published_at data. So I didn't have any fields at all that may have been empty.
However, due to the update hook from the last update, over 32,000 were given a new timestamp. I don't know why this date of all dates, but it was 1639841486, GMT: Saturday, 18 December 2021 15:31:26.
Fortunately I had a DB backup and was able to restore most of the data, even if the published_at is not correct for some current nodes, because I had to use the create date. Especially with nodes that have been published via the scheduler, the date does not match, but this can be avoided with about >300 nodes.
Enclosed are my SQL queries with which I was able to fix the problem. Actually, it is extremely annoying that a patch was applied here that so blatantly violates the data integrity.
The only thing left to hope for now is that Google will compare the nodes with its own database and include them in the index again and not perceive it as a SPAM/cloacking attempt. This way, many large news portals could lose their ranking after the update.
a rollback release should be issued and the patch removed for the time being. until an exact check and reroll of the patch can take place.
Postponed: needs info
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
No activities found.