[MAGNOLIA-450] activated content is not visible until restarting of the container Created: 14/Jun/05  Updated: 17/Mar/09  Resolved: 26/Jul/05

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 2.1 Final
Fix Version/s: 2.1 Final

Type: Bug Priority: Critical
Reporter: Philipp Bärfuss Assignee: Sameer Charles
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

activated nodes don't appear in the tree. Aftert restarting tomcat they are visible.

test scenario:

  • contentnode1
  • subcontentnode2
  • nodedata: test2
  • nodedata: test1
  • activate contentnode1 (without subnodes)
  • the changes are visible in the tree (public)
  • activet contentnode1 with subnodes
  • the changes are not visible in the tree (public)
  • restart tomcat (public)
  • the changes are visible

The big question is: is the content not visible in the gui or is it also not visible to the core. If it is not visible to the core this issue is very critical.



 Comments   
Comment by Philipp Bracher [ 15/Jun/05 ]

The problem is session depending. opening a new browser helps!

The corrupted session produces an exception. This is a bug, but since the activated content will be showed to the other users it is not realy a blocker.

Comment by Philipp Bracher [ 22/Jul/05 ]

It seams that the session is not always updated after an activation.

  • Open a browser
  • Open a author and a public tab
  • activate a new page
  • change it
  • reactivate
  • the change is not visible in the public tab (still the same session)
  • close the browser(new session) -> the changes are visible

This is not critical in the sense of the application, but the user will not trust this. As you can see in the user list they think that one must restart the tomcat then -> very bad.

Comment by Sameer Charles [ 22/Jul/05 ]

Philipp, which browser you are using? I tested with firefox and safari everything seems to work fine, I could see new content
on public side without instantiating new browser session.

perhaps this is simply a problem on client side cache which could be solved by using http meta tags in templates?

All open sessions are valid after activation, we cannot invalidate these sessions otherwise it will never work for applications
like e-shop.

Comment by Philipp Bracher [ 25/Jul/05 ]

> Philipp, which browser you are using? I tested with firefox and safari everything seems to work fine, I could see new content
> on public side without instantiating new browser session.

I use MacOSX and Firefox (my common configuration)

> perhaps this is simply a problem on client side cache which could be solved by using http meta tags in templates?

I cleared the cash. The false information is also visible in the tree where no cashing is used.

There were other users having this problem. I will try it again.

Comment by Philipp Bracher [ 25/Jul/05 ]

I tested the same scenario again with the current trunk:

I was not able to reproduce it. Unless nobody reopens the bug we take it as fixed.

Comment by Boris Kraft [ 26/Jul/05 ]

reassigned to RC3

Generated at Mon Feb 12 03:17:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.