Jump to content

Featured Replies

Posted

Hello,

I just wanted to point out that an scheduled topic appears as unread for the user that schedules it. That shouldn't be so. I mean, if I schedule 10 new topics to be published tomorrow, why should the person that schedules it have it appeared as "unread"? I am the user who scheduled it, I already read it. I don't want to see it as unread, it makes no sense 😞

Thanks.
Alfonso

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

IMO its a nice indication of the functionality working.

Maybe there could be a switch to display the topic as read or not...

This is a Schrödinger's cat isn't it?

If it hasn't been published yet, how can it be viewed?

1 hour ago, My Sharona said:

This is a Schrödinger's cat isn't it?

If it hasn't been published yet, how can it be viewed?

Thinking Think GIF by Rodney Dangerfield

  • Author
22 hours ago, Richard Arch said:

IMO its a nice indication of the functionality working.

Maybe there could be a switch to display the topic as read or not...

Well, if I am the person writing the topic, then it means that I've ALREADY read it. Its status should be read for the user that schedules the topic. Unless the user can write without reading what he writes 🙂

Yes, I'm sure you will have read it and if like me more than once proof reading, tweaking here and there.

But its a good indication to see the topic appear in your active list that its been published and on the day you expected it to appear.  I'd be more upset to discover the topic did not get published than having to see it.

  • Author
1 hour ago, Richard Arch said:

But its a good indication to see the topic appear in your active list that its been published and on the day you expected it to appear.  I'd be more upset to discover the topic did not get published than having to see it.

I trust the software 🙂 There is no reason why it shouldn't be published 🙂

  • 3 weeks later...

This has now been resolved in our latest 4.7.6 release. Please upgrade to that release if you are seeing this issue. If you have the same problem after upgrading, please let us know.

Recently Browsing 0

  • No registered users viewing this page.