Versioning: back-end displays wrong current vs working ver.

More
11 years 8 months ago #34286 by jackdaniels
Hi,

When using advance version control (ie disabling auto approval), the Current version, Working version and the version list don't work correctly: they all displays the last version id even if, on the front-end, the last approved version is correctly displayed (see attachment).
Attachments:

Please Log in or Create an account to join the conversation.

More
11 years 8 months ago #34289 by micker
Hello which version of FLEXIcontent ?

FLEXIcontent is Free but involves a very big effort on our part.
Like the our support? (for a bug-free FC, despite being huge extension) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing reviews. Thanks![/size]

Please Log in or Create an account to join the conversation.

More
11 years 8 months ago #34292 by ggppdk
Hello,

these were fixed in v2.0.0 final (r1468) Do you still have this issue in r1468 ?

The current version reported by r1468 is the real current version


-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...

Please Log in or Create an account to join the conversation.

More
11 years 8 months ago #34329 by jackdaniels
yes, it is for version 2.0.0 (r1648). I just update it from the previous unofficial 2.5 version. Something I forgot to mention earlier is that you can see in the NOTICE message the correct current and working version. However, it is wrong in the "statistic" box and in the versions history.

Please Log in or Create an account to join the conversation.

More
11 years 8 months ago #34351 by ggppdk
OK if you update it in r1648, then this message is correct meaning :

-- current version is not last, just click save on this item, to make last version current.

--- In short this message is not a bug it is what it says !
-- for some reason a document version was save WITHOUT becoming current e.g. the editor that saved it does not have permission to publish the item AKA he/she does not have permission to publish new document versions either OR a user that can publish the item choose to save the item without approving the new document version, you may want to Set Auto-Approve on (Global Config), and not allow users to save items without approving the new document versions

-- if you click save but still get this message then it would be a bug


-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...

Please Log in or Create an account to join the conversation.

More
11 years 8 months ago #34372 by jackdaniels
Hi,

I think we misunderstand each other a little bit. Note that I'm still a rookie with Joomla and Flexicontent, so maybe I'm the one trying things that shouldn't be done that way. I'll try to explain what I expect and what I get instead.

Case: I want to use the Approval field to allow users to work on a new article's version without actually publishing it (base on what i read there: www.flexicontent.org/documentation/faq/i...ment-versioning.html ).

Editing is done from the back-end by a Super User:

1) Create an article, state = Published and Approve = Yes
Upon saving, Current version = #1, Working version = #1

2) Edit the previous article, state = Published and Approve = Yes
Upon saving, Current version = #2, Working version = #2

3) Edit again the previous article but I do not want these modifications yet displaying in the front-end, state = Published and Approve = NO
Upon saving, a notice is displayed, which is expected and correct:

NOTICE: your new version of the document was not approved, so it is not yet current and thus visible to the viewers
NOTICE: loaded an unapproved document version, which is different than the CURRENT version that is visible to the viewers :: Loaded document version --3-- . Current document version: --2--

However, in the right section, we have a wrong current version, it should be #2 and not #3:

Current Version(Frontend Active) #3
Working Version(Loaded in Form) #3

and in the Version history too, current label is set to #3 and should be at #2:
Code:
Versions history #1 12/Mar 09:46 Super User Comment ViewLoad version #2 12/Mar 09:47 Super User Comment ViewLoad version #3 12/Mar 09:47 Super User Comment current

Note that it is working in the Front-end, I correctly see only the version #2.

Please Log in or Create an account to join the conversation.

Moderators: vistamediajoomlacornerggppdk
Time to create page: 0.435 seconds
Save
Cookies user preferences
We use cookies to ensure you to get the best experience on our website. If you decline the use of cookies, this website may not function as expected.
Accept all
Decline all
Essential
These cookies are needed to make the website work correctly. You can not disable them.
Display
Accept
Analytics
Tools used to analyze the data to measure the effectiveness of a website and to understand how it works.
Google Analytics
Accept
Decline