• Resolved michel173

    (@michel173)


    Hello again,

    for two years the same problem was posted from another guy in your support-board. In the communication you say you fix this problem. https://www.ads-software.com/support/topic/modified-date-before-publishing-date/ We use YOAST premium version and also for little websites the free version from Yoast. The bug is in both plugins always there. We have test it on two different portals. Here is the result:

    “headline”: “Zwischen Kunst und Aktivismus – G?tz Sophie Schramm stellt in Erfurt aus”,
    “datePublished”: “2023-01-06T09:15:23+00:00”,
    “dateModified”: “2023-01-06T09:09:13+00:00”,

    The datemodified is younger than the datepublished for articles they were planing. Either you do a fix in your plugin or we use a hock there. Our solution for planed articles is datePublished = dateModified for the first publishing from the article.

    Or what did you think? Many thanks

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @michel173

    Thanks for reaching out. I understand that there’s a discrepancy in datePublished and dateModified for your posts. Do you schedule your posts ahead or publish them immediately after you’re done writing?

    We look forward to hearing from you.

    Thread Starter michel173

    (@michel173)

    Hello again, if we publish immediately everything is ok. But if we schedule the post, then dateModified is younger than datepublished. We would like for schedule posts detaPublish = dateModified. There gives a lot of hooks and workarrounds in the wordpress-Community. But at first we would like to ask you about the problem/bugfixing in YOAST. It can also be correct for you or your offical YOAST SEO Plugin. Thanks

    Plugin Support Maybellyne

    (@maybellyne)

    Hello @michel173

    Thank you for bringing this issue to our attention! I’m sorry that our plugin caused a problem on your site where the dateModified is earlier than datePublished for scheduled posts. A bug report has been created internally and is under review by our product team.

    Workaround
    A user in the community provided this workaround, but we have not tested it. So, please test it on a staging environment first.

    What’s next?
    Our product team will assess the severity of the issue and assign a priority level to the report. Our developers work on the highest priority issues first. We cannot give you an estimate of when they’ll start working on the issue.

    If you have any further information that may affect the prioritization or help our development team solve this bug, please feel invited to reply to this forum topic, and we’ll share the information with our product team.

    Thread Starter michel173

    (@michel173)

    			],
    			'headline'         => $this->helpers->schema->html->smart_strip_tags( $this->helpers->post->get_post_title_with_fallback( $this->context->id ) ),
    			'datePublished'    => $this->helpers->date->format( $this->context->post->post_date_gmt ),
    			'dateModified'     => $this->helpers->date->format( $this->context->post->post_modified_gmt < $this->context->post->post_date_gmt  ? $this->context->post->post_date_gmt :  $this->context->post->post_modified_gmt),
    			'mainEntityOfPage' => [ '@id' => $this->context->main_schema_id ],
    			'wordCount'        => $this->word_count( $this->context->post->post_content, $this->context->post->post_title ),
    		];

    Hey there, we adapt this little bugfix in your YOAST Plugin. wordpress-seo/src/generators/schema/article.php on line 57. Could you fix this in the new YOAST SEO Version of your plugin. Because it is now a customized fix by us and after update the problem/bug is back again. Thanks

    • This reply was modified 2 years, 1 month ago by michel173.

    Hey @michel173,

    As Mabel mentioned, the bug report is filed and under our radar. Whether this will be fixed or looked at for our next version is up to the product and development team. Our product team will assess the severity of the issue and assign a priority level to the report. Our developers work on the highest priority issues first. We cannot give you an estimate of when they’ll start working on the issue.

    Hope you understand.

    Thread Starter michel173

    (@michel173)

    No problem. Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘dateModified younger than datepublish for planed articles’ is closed to new replies.