You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by bu...@apache.org on 2008/01/28 17:35:30 UTC
DO NOT REPLY [Bug 44313] New: - Saving in authoring causes updates to live
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44313>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44313
Summary: Saving in authoring causes updates to live
Product: Lenya
Version: 2.0
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Repository Integration
AssignedTo: dev@lenya.apache.org
ReportedBy: rfrovarp@apache.org
If a published document is saved (or updated), an update in the live area is
tripped as well. A new document and .meta file is generated with an old revision
be shot. The .rcml file is also updated. Content doesn't change, but these
updates aren't necessary. I have seen cases where the document is checked out in
the .rcml file under the live area, and then is not checked back in. This
prevents any action from occurring to the document. To fix, the .rcml file under
live must be edited and the application server restarted.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
DO NOT REPLY [Bug 44313] - Saving in authoring causes updates to live
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44313>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44313
------- Additional Comments From andreas@apache.org 2008-01-28 08:59 -------
(In reply to comment #3)
> I'm confused as to what meta data is being talked about.
The current workflow state is stored in the meta data.
> Shouldn't the meta data only be updated in live after a publish?
All area versions have the same workflow state - after publishing, the authoring
has the state "live", and the live version has the state "live". When you edit
the document again, both authoring and live version are set to the state
"authoring".
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
DO NOT REPLY [Bug 44313] - Saving in authoring causes updates to live
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44313>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44313
------- Additional Comments From andreas@apache.org 2008-01-28 08:43 -------
IIRC the reason for this behaviour is that all area versions of a document share
a common workflow. When the authoring document's workflow meta data change, the
live version's workflow meta data are updated as well.
A possible solution would be to introduce area-independent meta data, but this
would be a bit difficult to implement and hacky, because the repository layer
(which handles meta data) doesn't know about the concept of areas.
The cleanest solution would IMO be to abandon the area concept. This would
require a comprehensive analysis of possible workflow scenarios.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
DO NOT REPLY [Bug 44313] - Saving in authoring causes updates to live
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44313>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44313
------- Additional Comments From rfrovarp@apache.org 2008-01-28 08:53 -------
I'm confused as to what meta data is being talked about. Shouldn't the meta data
only be updated in live after a publish?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
DO NOT REPLY [Bug 44313] - Saving in authoring causes updates to live
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44313>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44313
------- Additional Comments From andreas@apache.org 2008-01-28 08:45 -------
Random thought: Another option would be a fallback hierarchy. If an area version
doesn't contain a value for a particular meta data element, it is fetched from
the authoring/trash/archive version.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
DO NOT REPLY [Bug 44313] - Saving in authoring causes updates to live
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44313>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44313
------- Additional Comments From nettings@apache.org 2008-01-28 09:53 -------
(In reply to comment #4)
> (In reply to comment #3)
> > I'm confused as to what meta data is being talked about.
>
> The current workflow state is stored in the meta data.
>
> > Shouldn't the meta data only be updated in live after a publish?
>
> All area versions have the same workflow state - after publishing, the authoring
> has the state "live", and the live version has the state "live". When you edit
> the document again, both authoring and live version are set to the state
> "authoring".
why should a live document have workflow meta data at all? doesn't make sense to
me. and btw, +1 to get rid of areas and -1 to any quick fixes that introduce yet
another area dependency.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
DO NOT REPLY [Bug 44313] - Saving in authoring causes updates to live
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44313>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44313
------- Additional Comments From rfrovarp@apache.org 2008-01-28 09:52 -------
Okay, I see that now. Of course the follow up question is, why? What difference
does that information make to the live area?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org