Currently whenever the current issue in epublish is requested it returns the most recent one. However, it does so regardless of whether an issue is marked as published. This makes it impossible to work on an issue privately before publication, which is why I am filing this as a bug. I found that simple changes to the SQL queries in function epublish_current_edition() fixes the problem. I have attached a modified version of the function, which I have named epublish_current_published_edition() .

CommentFileSizeAuthor
epublish_current_published_edition.txt647 bytespr1001

Comments

Attitudee’s picture

Attitudee commented

If you will make it published then only it will show else not.

If you will make it current and not published then it will not show you the edition and keep old current as current.

I dont see any need of the patch here.

This is not an bug.

Thanks.

kuldip zala’s picture

kuldip zala commented

according to Attitudee

I think no need of the patch here.
This is not a bug.

Thanks.

kuldip zala’s picture

kuldip zala commented
Status: Needs review » Fixed

according to Attitudee

I think no need of the patch here.
This is not a bug.

Thanks.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.