[MAGNOLIA-221] After creating new pages whole subtree not available in preview Created: 28/Nov/04 Updated: 23/Jan/13 Resolved: 29/Nov/04 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 2.0 Final |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Bernfried Howe | Assignee: | Boris Kraft |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows Standard Installation under XP SP2 |
||
| 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 |
|
After I have inserted some pages in a new subtree of my project the preview did not work at all anymore. The log file shows the following exception. Restart did not help. Even deleting the pages and creating them again did not work. Before I added the pages my new main.jsp and all include custom jsp's did work fine. info.magnolia.cms.Dispatcher 28.11.2004 14:23:36 – INFO – Forward to - /templates/jsp/webertise/templateThreeColumns/main.jsp |
| Comments |
| Comment by Boris Kraft [ 29/Nov/04 ] |
|
Please state exactly how we can reproduce this behavior, elswise we have to close this issues with status "works for me". Thanks. |
| Comment by Bernfried Howe [ 29/Nov/04 ] |
|
Preconditions: After this test I did following steps: If this does not help, I can provide you with my complete author directory, if you like. |
| Comment by Boris Kraft [ 29/Nov/04 ] |
|
Since these actions work fine on the default templates I must assume that you have a problem in your navigation jsp. In this case, I suggest you upload the template to jira and continue discussion on the user-list, not the dev-list. |