<blockquote>
<p>Shouldn't the post date be different for every website?</p>
</blockquote>
<p>The post date isn't translatable, so it's always the same in all sites an entry is propagated to. Changing the post date in one entry will change it for all sites. That's by design, though you can always create a discussion on GitHub if you don't agree with this design.</p>
<p>However, you're not forced to utilize the post date in your frontend. In this case it's only relevant internally, to sort entries by the time they were created (though the post date can still be changed manually).</p>
<blockquote>
<p>Is there a way to display recent articles by the post date for the specific website?</p>
</blockquote>
<p>If you need a publication date for entries that is different between the two sites, I would just use a custom field. For example, create a date field <code>publication_date</code> and set it to <em>Translate for each site</em>. Set the field to required so every entry has a publication date. Then you can sort by that field in your templates:</p>
<pre class="lang-twig prettyprint-override"><code>{% set recentArticles = craft.entries()
    .section('articles')
    .orderBy('publication_date DESC')
    .limit(5)
    .all()
%}
</code></pre>
<p>You could even use a hook on <code>Entry::EVENT_BEFORE_SAVE</code> to set the publication date to the current date and time when a new article entry is created.</p>

CC BY-SA 4.0
2023-09-27T12:34:47.510Z
I definitely think that the post date should be translatable.
Thank you Moritz.
Michal Bulla
CC BY-SA 4.0
2023-09-26T15:06:30.353Z
2023-09-26T15:06:30.353Z
MoritzLost
<p>we are using multi-site setup to run 2 websites in different languages. We share articles between both sites and display some of them on the home page as &quot;recent articles&quot;. Since the translation of every article take some time, the article is not enabled on both websites at the same date/time.</p>
<p>Shouldn't the post date be different for every website? Is there a way to display recent articles by the post date for the specific website?</p>
<p>Thanks</p>

<multi-site><postdate>
Entry's post date in multisite
# Entry's post date in multisite

(Asked by: username_0 on 2023-09-26)

we are using multi-site setup to run 2 websites in different languages. We share articles between both sites and display some of them on the home page as "recent articles". Since the translation of every article take some time, the article is not enabled on both websites at the same date/time.

Shouldn't the post date be different for every website? Is there a way to display recent articles by the post date for the specific website?

Thanks

**Tags:** multi-site, postdate

---

## 1 answers

### Answer by username_1 on 2023-09-26. Score: 1 | Accepted answer

Shouldn't the post date be different for every website?

The post date isn't translatable, so it's always the same in all sites an entry is propagated to. Changing the post date in one entry will change it for all sites. That's by design, though you can always create a discussion on GitHub if you don't agree with this design.
However, you're not forced to utilize the post date in your frontend. In this case it's only relevant internally, to sort entries by the time they were created (though the post date can still be changed manually).

Is there a way to display recent articles by the post date for the specific website?

If you need a publication date for entries that is different between the two sites, I would just use a custom field. For example, create a date field publication_date and set it to Translate for each site. Set the field to required so every entry has a publication date. Then you can sort by that field in your templates:
{% set recentArticles = craft.entries()
    .section('articles')
    .orderBy('publication_date DESC')
    .limit(5)
    .all()
%}

You could even use a hook on Entry::EVENT_BEFORE_SAVE to set the publication date to the current date and time when a new article entry is created.

> **Comments:**
> **username_0**: I definitely think that the post date should be translatable. Thank you Moritz.  

---

