Yeah, it's a cache issue. I did some experimentation and I found this:

- Create an entry
- See it on blog page
- Change entry to a draft
- It still appears on blog page
- Switch to a different web browser (but do not login to Roller) and see
that entry does not appear on blog page
- Login with different web browser and see that entry does appear on blog
page

Seems like a cache invalidation problem for logged in users, but I do not
see the problem in the code. I'm glad the draft entry gets removed from the
search index tho, and thanks for testing search functionality Greg
because it did change recently.

I'm +1 on this release despite this glitch.

Dave



On Sat, Jul 29, 2023 at 4:33 PM Michael Bien <mbie...@gmail.com> wrote:

> Hi Greg,
>
> I could reproduce it, this seems to be a cache invalidation issue.
>
> the entry will disappear if you clear the cache via the Maintenance UI.
> Roller has also various cache settings which can be set in roller
> properties, e.g age based eviction which would further mitigate this.
>
> This is probably a bug but not a show stopper IMHO - updating entries
> works fine for example,
>
> best regards,
> michael
>
>
> On 24.07.23 10:55, Greg Huber wrote:
> > If I have a published entry, and then change the status to draft it
> > does not update the front page/weblog and the entry still shows.
> >
> > If I publish another entry, the draft entry now does not so.
> >
> > Also how do I get it to show other weblog entries on the front page now?
> >
> > On 23/07/2023 21:10, Dave wrote:
> >> This release of Roller includes dependency updates, minor fixes and some
> >> input validation fixes. This new RC removes an unnecessary Solr
> >> dependency,
> >> makes some small docs fixes and removes an unnecessary error message.
> >> Thanks for the reviews!
> >>
> >> You can find the convenience binaries and the source code of the release
> >> here: https://dist.apache.org/repos/dist/dev/roller/roller-6.1/v6.1.2/
> >>
> >> Please take it for a spin and vote:
> >> +1 to release
> >> -1 not to release (with reasons)
> >>
> >> Thanks,
> >> Dave
> >>
>
>

Reply via email to