It's in issue in the cache system. If someone is viewing the domain filter sort for a domain when the new post is created, it caches an old version of the template with the new post info filled in and pushes the cache fragment to the main page...
It's already been fixed in the new front end roll out which is almost done.
It's in issue in the cache system. If someone is viewing the domain filter sort for a domain when the new post is created, it caches an old version of the template with the new post info filled in and pushes the cache fragment to the main page...
It's already been fixed in the new front end roll out which is almost done.
It's in issue in the cache system. If someone is viewing the domain filter sort for a domain when the new post is created, it caches an old version of the template with the new post info filled in and pushes the cache fragment to the main page...
It's already been fixed in the new front end roll out which is almost done.