[MAGNOLIA-1394] New paragraph don't "see" new dialogs without reloading the dialogs Created: 21/Feb/07 Updated: 23/Jan/13 Resolved: 10/Dec/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Giancarlo Berner | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mac OS X, Tomcat 5, Firefox 2 |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| 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 |
|
| Comments |
| Comment by Magnolia International [ 21/Feb/07 ] |
|
so that's only the case when using the packager ? |
| Comment by Giancarlo Berner [ 21/Feb/07 ] |
|
In earlier Magnolia EE RC I used to experience the same issue. I though don't know how it is today. |
| Comment by Philipp Bracher [ 06/Mar/07 ] |
|
In case the dialogs node was existing during the startup, the newly defined dialogs should be reloaded. |
| Comment by Philipp Bracher [ 06/Mar/07 ] |
|
Make sure that the dialogs node is not part of your package |
| Comment by Simon Goodchild [ 06/Mar/07 ] |
|
I always get this behaviour when adding new dialogs, wherever I have defined them (including the main dialogs node that AdminCentral provides a shortcut link to), so the problem is not just limited to modules. I find that I always need to restart for them to become available which is a pain. Is it the case then that these new dialogs should be picked up by the system? If so then there's definitely a bug somewhere. If not then a (hopefully) quick workaround would be if there was an option to force a reload of all the template and dialog definitions, basically calling whatever routine is used at start-up. Then we can achieve the same effect as restarting the servlet engine without impacting any other applications running in it. |
| Comment by Giancarlo Berner [ 07/Mar/07 ] |
|
I noticed this issues only with packages. However, the packager is an important tool to move or backup development work. If I add a dialog node-by-node, the dialog is recognized. If I copy an existing dialog, I often can not even rename the folder name anymore. If I test without renaming, the dialog is not recognized. I agree with Simon, there must be something weird with dialogs. Please re-evaluate this entry. Thanks! |
| Comment by Simon Goodchild [ 07/Mar/07 ] |
|
I think Giancarlo may have narrowed down where the problem is, as I normally create new dialogs by copying an existing node and then changing the entries. So maybe creating new dialogs from scratch triggers the reload behaviour, but copying does not. Not sure if it's to do with node IDs being duplicated and making Magnolia think the dialogs are already loaded? |
| Comment by Philipp Bracher [ 08/Mar/07 ] |
|
needs to be checked |
| Comment by Karl Krukow [ 28/Mar/07 ] |
|
Two comments:
To reproduce bug: ( I am running Magnolia EE v. 3.0.2 on windows xp)
(/Example:
Now in my setup, if I create a web-page using this template and I click the Properties button, I get the same problem: info.magnolia.cms.beans.config.ConfigurationException: no dialog registered for name: myPageParagraph However, there is more: If I restart, it works, BUT supposing that I now change the dialogPath from myProject/myHelloWorldPageProperties to myProject/InvalidReference (or any other that is not defined) it still works: If I refresh the browser and click the button I get the dialog. So it seems that the changes are not "flushed". There is a workaround: if I 'Activate' the paragraph and the dialog, I (correctly) get the ConfigurationException. Regards,
|
| Comment by Magnolia International [ 17/May/07 ] |
|
We should check this from 3.1 |
| Comment by Magnolia International [ 22/Nov/07 ] |
|
Will try to check for rc2 ... |
| Comment by Magnolia International [ 10/Dec/07 ] |
|
Could indeed reproduce the issue, for dialogs that don't have the same name as their paragraphs. One could work around the issue by forcing a reload of the dialogs (i.e editing any dialog). Fixed for 3.5. |