[magnolia-dev] [JIRA] Commented: (MAGNOLIA-1959) Leopard (osx 10.5) issues
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=21118#action_21118
]
Christian Ringele commented on MAGNOLIA-1959:
-
With only one instance i didn't have the problem too.
But this is not 100%, because today i could start it several times with two
instances and it worked fine.
But one big difference was:
When you click refresh many times as fast as you can, i received a blank screen
which could not be reloaded.
This behavior i didn't have with just one instance.
Leopard (osx 10.5) issues
-
Key: MAGNOLIA-1959
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-1959
Project: Magnolia
Issue Type: Bug
Affects Versions: 3.5
Reporter: Gregory Joseph
Assignee: Gregory Joseph
h3. Leopard's application level firewall :
Leopard's firewall behaves significantly differently than the firewall
shipped with OSX 10.4. The symptoms are that Tomcat seems unreachable
(kCFErrorDomainCFNetwork:302), but unfortunately no log message *clearly*
identifies the issue.
It seems the behavior was different prior to OSX 10.5.3, but at least in
10.5.4 the following seems to work:
- allow incoming connections for the Magnolia and Tomcat scripts
({{magnolia_control.sh}}, {{startup.sh}}, {{shutdown.sh}}, {{catalina.sh}}),
as well as the Java binary (ie
{{/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/java}})
- it seems sometimes necessary to lock and unlock the firewall settings
pane, so as to force it to take the new settings into account.
- if Magnolia was started, you'll have to kill it (-HUP works and shuts it
down nicely) and restart.
h4. More comments and questions
- somehow, setting the firewall too allow all does not seem to help.
- {{sudo launchctl remove com.apple.alf}} should remove the application-level
firewall, but for some reason, this hasn't proved very useful. Will have to
try again.
h4. Log files to watch:
* {{/var/log/system.log}}
* {{/var/log/secure.log}}
* {{/var/log/appfirewall.log}}
h4. Some interesting links:
* http://securosis.com/2007/11/01/investigating-the-leopard-firewall/
* http://documentation.magnolia.info/administration.html#Knownissues which
links back to here but has a nice little screenshot of Leopard's firewall
configuration gui ;)
h3. Max.files opened
There might be some max.files opened issues, with settings which are
different from Tiger(10.4), although this hasn't been reported in a while.
There is unfortunately not much we can do about this issue at the moment, as
far as we know.
*Feel free to comment on your own experience below and contribute tips and
tricks !*
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-1959) Leopard (osx 10.5) issues
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=21119#action_21119
]
Christian Ringele commented on MAGNOLIA-1959:
-
With:
- tomcat 6.0.16
- JDK 1.6
- EE version with two instances
Same bad behavior.
Leopard (osx 10.5) issues
-
Key: MAGNOLIA-1959
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-1959
Project: Magnolia
Issue Type: Bug
Affects Versions: 3.5
Reporter: Gregory Joseph
Assignee: Gregory Joseph
h3. Leopard's application level firewall :
Leopard's firewall behaves significantly differently than the firewall
shipped with OSX 10.4. The symptoms are that Tomcat seems unreachable
(kCFErrorDomainCFNetwork:302), but unfortunately no log message *clearly*
identifies the issue.
It seems the behavior was different prior to OSX 10.5.3, but at least in
10.5.4 the following seems to work:
- allow incoming connections for the Magnolia and Tomcat scripts
({{magnolia_control.sh}}, {{startup.sh}}, {{shutdown.sh}}, {{catalina.sh}}),
as well as the Java binary (ie
{{/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/java}})
- it seems sometimes necessary to lock and unlock the firewall settings
pane, so as to force it to take the new settings into account.
- if Magnolia was started, you'll have to kill it (-HUP works and shuts it
down nicely) and restart.
h4. More comments and questions
- somehow, setting the firewall too allow all does not seem to help.
- {{sudo launchctl remove com.apple.alf}} should remove the application-level
firewall, but for some reason, this hasn't proved very useful. Will have to
try again.
h4. Log files to watch:
* {{/var/log/system.log}}
* {{/var/log/secure.log}}
* {{/var/log/appfirewall.log}}
h4. Some interesting links:
* http://securosis.com/2007/11/01/investigating-the-leopard-firewall/
* http://documentation.magnolia.info/administration.html#Knownissues which
links back to here but has a nice little screenshot of Leopard's firewall
configuration gui ;)
h3. Max.files opened
There might be some max.files opened issues, with settings which are
different from Tiger(10.4), although this hasn't been reported in a while.
There is unfortunately not much we can do about this issue at the moment, as
far as we know.
*Feel free to comment on your own experience below and contribute tips and
tricks !*
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-1959) Leopard (osx 10.5) issues
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=21125#action_21125
]
Christian Ringele commented on MAGNOLIA-1959:
-
The limit maxfiles 4096 unlimited value didn't help on my machine at all.
Leopard (osx 10.5) issues
-
Key: MAGNOLIA-1959
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-1959
Project: Magnolia
Issue Type: Bug
Affects Versions: 3.5
Reporter: Gregory Joseph
Assignee: Gregory Joseph
h3. Leopard's application level firewall :
Leopard's firewall behaves significantly differently than the firewall
shipped with OSX 10.4. The symptoms are that Tomcat seems unreachable
(kCFErrorDomainCFNetwork:302), but unfortunately no log message *clearly*
identifies the issue.
It seems the behavior was different prior to OSX 10.5.3, but at least in
10.5.4 the following seems to work:
- allow incoming connections for the Magnolia and Tomcat scripts
({{magnolia_control.sh}}, {{startup.sh}}, {{shutdown.sh}}, {{catalina.sh}}),
as well as the Java binary (ie
{{/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/java}})
- it seems sometimes necessary to lock and unlock the firewall settings
pane, so as to force it to take the new settings into account.
- if Magnolia was started, you'll have to kill it (-HUP works and shuts it
down nicely) and restart.
h4. More comments and questions
- somehow, setting the firewall too allow all does not seem to help.
- {{sudo launchctl remove com.apple.alf}} should remove the application-level
firewall, but for some reason, this hasn't proved very useful. Will have to
try again.
h4. Log files to watch:
* {{/var/log/system.log}}
* {{/var/log/secure.log}}
* {{/var/log/appfirewall.log}}
h4. Some interesting links:
* http://securosis.com/2007/11/01/investigating-the-leopard-firewall/
* http://documentation.magnolia.info/administration.html#Knownissues which
links back to here but has a nice little screenshot of Leopard's firewall
configuration gui ;)
h3. Max.files opened
There might be some max.files opened issues, with settings which are
different from Tiger(10.4), although this hasn't been reported in a while.
There is unfortunately not much we can do about this issue at the moment, as
far as we know.
*Feel free to comment on your own experience below and contribute tips and
tricks !*
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-1959) Leopard (osx 10.5) issues
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=21124#action_21124
]
Christian Ringele commented on MAGNOLIA-1959:
-
I tried within the server.xml of the tomcazt this values:
Connector port=8080 protocol=HTTP/1.1
connectionTimeout=2
redirectPort=8443
max_threads=30
max_spare_threads=20
min_spare_threads=5 /
This did not help. But I'm not sure whether the values were accepted. Because
if i add a parameter which does not exits (WURST) it doesn't complain
Leopard (osx 10.5) issues
-
Key: MAGNOLIA-1959
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-1959
Project: Magnolia
Issue Type: Bug
Affects Versions: 3.5
Reporter: Gregory Joseph
Assignee: Gregory Joseph
h3. Leopard's application level firewall :
Leopard's firewall behaves significantly differently than the firewall
shipped with OSX 10.4. The symptoms are that Tomcat seems unreachable
(kCFErrorDomainCFNetwork:302), but unfortunately no log message *clearly*
identifies the issue.
It seems the behavior was different prior to OSX 10.5.3, but at least in
10.5.4 the following seems to work:
- allow incoming connections for the Magnolia and Tomcat scripts
({{magnolia_control.sh}}, {{startup.sh}}, {{shutdown.sh}}, {{catalina.sh}}),
as well as the Java binary (ie
{{/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/java}})
- it seems sometimes necessary to lock and unlock the firewall settings
pane, so as to force it to take the new settings into account.
- if Magnolia was started, you'll have to kill it (-HUP works and shuts it
down nicely) and restart.
h4. More comments and questions
- somehow, setting the firewall too allow all does not seem to help.
- {{sudo launchctl remove com.apple.alf}} should remove the application-level
firewall, but for some reason, this hasn't proved very useful. Will have to
try again.
h4. Log files to watch:
* {{/var/log/system.log}}
* {{/var/log/secure.log}}
* {{/var/log/appfirewall.log}}
h4. Some interesting links:
* http://securosis.com/2007/11/01/investigating-the-leopard-firewall/
* http://documentation.magnolia.info/administration.html#Knownissues which
links back to here but has a nice little screenshot of Leopard's firewall
configuration gui ;)
h3. Max.files opened
There might be some max.files opened issues, with settings which are
different from Tiger(10.4), although this hasn't been reported in a while.
There is unfortunately not much we can do about this issue at the moment, as
far as we know.
*Feel free to comment on your own experience below and contribute tips and
tricks !*
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-2654) Safari 4.0 beta - No trees are rendered in Admin Interface
Safari 4.0 beta - No trees are rendered in Admin Interface -- Key: MAGNOLIA-2654 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2654 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.0 Reporter: Christian Ringele Assignee: Philipp Bracher In Safari 4.0 beta (Version 5528.16) no trees are rendered in the admin interface. This is on all tabs (Configuration, DMS etc). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-2673) update: error message should print the failing task's name and root cause
update: error message should print the failing task's name and root cause - Key: MAGNOLIA-2673 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2673 Project: Magnolia Issue Type: Improvement Components: updatemechanism Affects Versions: 4.0.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 4.0.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-2673) update: error message should print the failing task's name and root cause
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele resolved MAGNOLIA-2673. - Resolution: Fixed update: error message should print the failing task's name and root cause - Key: MAGNOLIA-2673 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2673 Project: Magnolia Issue Type: Improvement Components: updatemechanism Affects Versions: 4.0.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 4.0.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLDATA-58) Error in data module/commands if STK updated form 1.0 to 1.1
Error in data module/commands if STK updated form 1.0 to 1.1 Key: MGNLDATA-58 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-58 Project: Magnolia Data Module Issue Type: Bug Affects Versions: 1.3 Reporter: Christian Ringele Assignee: Jan Haderka Fix For: 1.3.1 After updating the STK from version 1.0 to 1.1 on start up of magnolia this error occurs: 2009-04-03 15:54:25,792 WARN info.magnolia.commands.CommandsManager : Was not able to register [/modules/data/commands] java.lang.ClassCastException: info.magnolia.module.data.commands.ImportCommand at info.magnolia.commands.CommandsManager.registerCatalog(CommandsManager.java:93) at info.magnolia.commands.CommandsManager.onRegister(CommandsManager.java:82) at info.magnolia.commands.CommandsManager.onRegister(CommandsManager.java:86) at info.magnolia.commands.CommandsManager.onRegister(CommandsManager.java:86) at info.magnolia.commands.CommandsManager.onRegister(CommandsManager.java:86) at info.magnolia.cms.beans.config.ObservedManager.register(ObservedManager.java:85) at info.magnolia.module.ModuleLifecycleContextImpl.initEntry(ModuleLifecycleContextImpl.java:93) at info.magnolia.module.ModuleLifecycleContextImpl.start(ModuleLifecycleContextImpl.java:85) at info.magnolia.module.ModuleManagerImpl.startModules(ModuleManagerImpl.java:349) at info.magnolia.module.ui.ModuleManagerWebUI$1.exec(ModuleManagerWebUI.java:104) at info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:377) at info.magnolia.module.ui.ModuleManagerWebUI.execute(ModuleManagerWebUI.java:101) at info.magnolia.cms.filters.InstallFilter.doFilter(InstallFilter.java:95) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:82) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:84) at info.magnolia.cms.filters.CompositeFilter.doFilter(CompositeFilter.java:64) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) at info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:96) at info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:199) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-2765) Copiright year on ligin form shows 2008 instead of 2009
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele resolved MAGNOLIA-2765. - Resolution: Fixed Done Copiright year on ligin form shows 2008 instead of 2009 --- Key: MAGNOLIA-2765 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2765 Project: Magnolia Issue Type: Improvement Components: admininterface Affects Versions: 4.1 RC4 Reporter: Christian Ringele Assignee: Christian Ringele Priority: Minor Fix For: 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLGA-1) Initial implementation of Google Analytics
Initial implementation of Google Analytics -- Key: MGNLGA-1 URL: http://jira.magnolia-cms.com/browse/MGNLGA-1 Project: Magnolia Google Analytics Issue Type: New Feature Reporter: Christian Ringele Assignee: Christian Ringele First implementation of the Google Analytics module as described in STK Jira task MGNLSTK-406. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLGA-1) Initial implementation of Google Analytics
[ http://jira.magnolia-cms.com/browse/MGNLGA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLGA-1: --- Description: First implementation of the Google Analytics module as described in STK Jira task MGNLSTK-406. Initial implementation showed, that Google Analytics is being implemented best as a module and not as additional functionality directly in STK. Future expansion are better to implement in a separate module like: - Customization/Updating of the used JS's - For later retrieving of data from GA was:First implementation of the Google Analytics module as described in STK Jira task MGNLSTK-406. Initial implementation of Google Analytics -- Key: MGNLGA-1 URL: http://jira.magnolia-cms.com/browse/MGNLGA-1 Project: Magnolia Google Analytics Issue Type: New Feature Reporter: Christian Ringele Assignee: Christian Ringele First implementation of the Google Analytics module as described in STK Jira task MGNLSTK-406. Initial implementation showed, that Google Analytics is being implemented best as a module and not as additional functionality directly in STK. Future expansion are better to implement in a separate module like: - Customization/Updating of the used JS's - For later retrieving of data from GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MGNLGA-1) Initial implementation of Google Analytics
[ http://jira.magnolia-cms.com/browse/MGNLGA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele resolved MGNLGA-1. Resolution: Fixed First implementation done. The module keeps its site configurations within it's config path, and not within the STK site configuration. For each STK site configuration a configuration within the module must be added, named the same as the STK site. The Module uses JQuery GA script which tracks the external/download/mailto links too. For start tracking a site only two values must be entered: - enabled=true - trackerID = your project/site Google Analytics trackerID provided by Google. Initial implementation of Google Analytics -- Key: MGNLGA-1 URL: http://jira.magnolia-cms.com/browse/MGNLGA-1 Project: Magnolia Google Analytics Issue Type: New Feature Reporter: Christian Ringele Assignee: Christian Ringele First implementation of the Google Analytics module as described in STK Jira task MGNLSTK-406. Initial implementation showed, that Google Analytics is being implemented best as a module and not as additional functionality directly in STK. Future expansion are better to implement in a separate module like: - Customization/Updating of the used JS's - For later retrieving of data from GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-2834) Login screen should show Magnolia License and Version of the System
Login screen should show Magnolia License and Version of the System --- Key: MAGNOLIA-2834 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2834 Project: Magnolia Issue Type: Improvement Components: admininterface Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 4.2 Attachments: Picture 1.png This is a request by Pascal: The login screen should show: - The used Magnolia license - The used Magnolia version Comparable to on how its shown within the adminCentral (see attachment). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLGA-2) Testing: Link tracking doesn't work as expected
Testing: Link tracking doesn't work as expected
---
Key: MGNLGA-2
URL: http://jira.magnolia-cms.com/browse/MGNLGA-2
Project: Magnolia Google Analytics
Issue Type: Bug
Reporter: Christian Ringele
Assignee: Christian Ringele
Priority: Blocker
Attachments: Picture 2.png
I am testing the GA module on the demo http://demo.magnolia-cms.com/demo
instance.
Generally the tracking of the pages themselves work as expected. All the pages
and page hits are tracked and show up in the GA.
The JS tracking script the module is using is a JQuery plugin (in module JS
'jquery.gatracker.js'). It is supposed to track all links too: external links,
download links and mailto links.
It adds if found, a prefix to the link URL: 'external' or 'downloads' or
'mailtos'.
Setup:
- First I tried a advanced tracker function call with more defined file
extensions (in module init.gatracker.js').
- Then I tried the original function call. So its the unchanged JS running as
provided by JQuery:
(function($){
$.gaTracker('${trackerID}');
})(jQuery);
This call activates the link tracking with the original options defined in the
original JS script 'jquery.gatracker.js'.
Results:
- External links are never tracked
- mailto links are never tracked
- download links are only very seldom tracked:
Only download links which point to a .jpg provided by the image
module/image-zoom generator. See attached file.
I think the problem is located within the js function 'function
decorateLink(u){'.
The regex expression within this function does not apply to the links analyzed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLRES-17) Resource Template Strings not i18nized
Resource Template Strings not i18nized -- Key: MGNLRES-17 URL: http://jira.magnolia-cms.com/browse/MGNLRES-17 Project: Magnolia Resources Module Issue Type: Improvement Affects Versions: 1.1.1 Reporter: Christian Ringele Assignee: Teresa Miyar Fix For: 1.1.2 In the resource module/templates the property title is not i18nized. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-2901) Moving nodes in adminCentral shows moved node content as parent node content
Moving nodes in adminCentral shows moved node content as parent node content Key: MAGNOLIA-2901 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2901 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.1.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Priority: Critical Fix For: 4.1.x When moving a node in admin central to a different parent node, the parent node shows the content of the moved node instead of all child nodes. Using this version: magnoliaVersion4.1.1/magnoliaVersion stkVersion1.1.2/stkVersion This is 'only' a displaying problem right after moving the node, after refresh the node was moved and shows up correctly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2901) Moving nodes in adminCentral shows moved node content as parent node content
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-2901: Attachment: Screen shot 2009-10-15 at 2.15.20 PM.png Environment: Browsers I tested on: Firefox Safari Description: When moving a node in admin central to a different parent node, the parent node shows the content of the moved node instead of all child nodes. Using this version: magnoliaVersion4.1.1/magnoliaVersion stkVersion1.1.2/stkVersion This is 'only' a displaying problem right after moving the node, after refresh the node was moved and shows up correctly. I have seen this behavior on: - local instance - demoauthor This behavior I tested in these work spaced: - Config - DMA - Website was: When moving a node in admin central to a different parent node, the parent node shows the content of the moved node instead of all child nodes. Using this version: magnoliaVersion4.1.1/magnoliaVersion stkVersion1.1.2/stkVersion This is 'only' a displaying problem right after moving the node, after refresh the node was moved and shows up correctly Moving nodes in adminCentral shows moved node content as parent node content Key: MAGNOLIA-2901 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2901 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.1.1 Environment: Browsers I tested on: Firefox Safari Reporter: Christian Ringele Assignee: Philipp Bärfuss Priority: Critical Fix For: 4.1.x Attachments: Screen shot 2009-10-15 at 2.15.20 PM.png When moving a node in admin central to a different parent node, the parent node shows the content of the moved node instead of all child nodes. Using this version: magnoliaVersion4.1.1/magnoliaVersion stkVersion1.1.2/stkVersion This is 'only' a displaying problem right after moving the node, after refresh the node was moved and shows up correctly. I have seen this behavior on: - local instance - demoauthor This behavior I tested in these work spaced: - Config - DMA - Website -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-2964) Nice Editor should resize accodingly to the dialog window
Nice Editor should resize accodingly to the dialog window - Key: MAGNOLIA-2964 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2964 Project: Magnolia Issue Type: Improvement Components: gui Affects Versions: 4.2.1 Reporter: Christian Ringele Assignee: Boris Kraft Priority: Minor Fix For: 4.2.x Attachments: Screen shot 2009-12-07 at 10.58.10 AM.png When resizing the dialog window (of a inplace templateing script), the nice editor does not re size. The editor should re size accordingly to the dialog window. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-2980) Nice Editor: Tabs should be spaces and not tab character
Nice Editor: Tabs should be spaces and not tab character Key: MAGNOLIA-2980 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2980 Project: Magnolia Issue Type: Improvement Components: gui Affects Versions: 4.2.2 Reporter: Christian Ringele Assignee: Boris Kraft Priority: Minor Fix For: 4.2.x When using the 'tab' key in the nice editor, tab characters are used. It would be better if space characters (4 spaces) would be used instead of the tab. Especially when pasting some code out of a resource file, the tabs must be replaced manually. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-555) Demo content: can't resolve image variation for #section #main .text-box-tabs .text-box-section
Demo content: can't resolve image variation for #section #main .text-box-tabs .text-box-section --- Key: MGNLSTK-555 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-555 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: themepop Affects Versions: 1.2.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Priority: Minor Fix For: 1.2.x When rendering pages containing a text-tab box in hte main area, this warning is logged: 2010-01-07 11:15:53,560 WARN agnolia.module.templatingkit.paragraphs.ImageModel: Couldn't resolve a image varion for css selector [#section #main .text-box-tabs .text-box-section] Looks like a image variation definition is missing in the imaging configuration of the theme. By the way, the log has a typo: '...image varion for css...' -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-557) Demo content: No dummy events for 2010
Demo content: No dummy events for 2010 -- Key: MGNLSTK-557 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.2.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.2.x All dummy events in the demo content are events of the year 2009. The events are located under: demo-project/service/dummy-events/ These events should be updated to 2010. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777
]
Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:30 AM:
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
}
was (Author: cringele):
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{/code}
Demo content: No dummy events for 2010
--
Key: MGNLSTK-557
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Fix For: 1.2.x
All dummy events in the demo content are events of the year 2009.
The events are located under: demo-project/service/dummy-events/
These events should be updated to 2010.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MGNLSTK-557) Demo content: No dummy events for 2010
[ http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777 ] Christian Ringele commented on MGNLSTK-557: --- I had to update all events for demo Pascal gave. So I i changed all events and added some new events, so that the span of dates is over the complete year. Additionally there is one mont of events in the old year, and one month in the coming year. Like this, when the new year (2011) comes, simply all 'year' numbers have to be changes to one year higher. The events configured right now are: - January 2009: 4 events - All months of 2010: 4 events each - January 2011: 4 events I add here the boostrap file of all dummy-events. Additionally I have removed wrong generated page header image-properties from all dummy event pages: code sv:property sv:name=image sv:type=String sv:valuedms/sv:value /sv:property sv:property sv:name=imageDmsUUID sv:type=String sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value /sv:property sv:property sv:name=imageLocation sv:type=String sv:valueabove/sv:value /sv:property /code Demo content: No dummy events for 2010 -- Key: MGNLSTK-557 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.2.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.2.x All dummy events in the demo content are events of the year 2009. The events are located under: demo-project/service/dummy-events/ These events should be updated to 2010. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[ http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777 ] Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:29 AM: I had to update all events for demo Pascal gave. So I i changed all events and added some new events, so that the span of dates is over the complete year. Additionally there is one mont of events in the old year, and one month in the coming year. Like this, when the new year (2011) comes, simply all 'year' numbers have to be changes to one year higher. The events configured right now are: - January 2009: 4 events - All months of 2010: 4 events each - January 2011: 4 events I add here the bootstrap file of all dummy-events. Additionally I have removed wrong generated page header image-properties from all dummy event pages: code sv:property sv:name=image sv:type=String sv:valuedms/sv:value /sv:property sv:property sv:name=imageDmsUUID sv:type=String sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value /sv:property sv:property sv:name=imageLocation sv:type=String sv:valueabove/sv:value /sv:property /code was (Author: cringele): I had to update all events for demo Pascal gave. So I i changed all events and added some new events, so that the span of dates is over the complete year. Additionally there is one mont of events in the old year, and one month in the coming year. Like this, when the new year (2011) comes, simply all 'year' numbers have to be changes to one year higher. The events configured right now are: - January 2009: 4 events - All months of 2010: 4 events each - January 2011: 4 events I add here the boostrap file of all dummy-events. Additionally I have removed wrong generated page header image-properties from all dummy event pages: code sv:property sv:name=image sv:type=String sv:valuedms/sv:value /sv:property sv:property sv:name=imageDmsUUID sv:type=String sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value /sv:property sv:property sv:name=imageLocation sv:type=String sv:valueabove/sv:value /sv:property /code Demo content: No dummy events for 2010 -- Key: MGNLSTK-557 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.2.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.2.x All dummy events in the demo content are events of the year 2009. The events are located under: demo-project/service/dummy-events/ These events should be updated to 2010. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[ http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777 ] Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:30 AM: I had to update all events for demo Pascal gave. So I i changed all events and added some new events, so that the span of dates is over the complete year. Additionally there is one mont of events in the old year, and one month in the coming year. Like this, when the new year (2011) comes, simply all 'year' numbers have to be changes to one year higher. The events configured right now are: - January 2009: 4 events - All months of 2010: 4 events each - January 2011: 4 events I add here the bootstrap file of all dummy-events. Additionally I have removed wrong generated page header image-properties from all dummy event pages: [code] sv:property sv:name=image sv:type=String sv:valuedms/sv:value /sv:property sv:property sv:name=imageDmsUUID sv:type=String sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value /sv:property sv:property sv:name=imageLocation sv:type=String sv:valueabove/sv:value /sv:property [/code] was (Author: cringele): I had to update all events for demo Pascal gave. So I i changed all events and added some new events, so that the span of dates is over the complete year. Additionally there is one mont of events in the old year, and one month in the coming year. Like this, when the new year (2011) comes, simply all 'year' numbers have to be changes to one year higher. The events configured right now are: - January 2009: 4 events - All months of 2010: 4 events each - January 2011: 4 events I add here the bootstrap file of all dummy-events. Additionally I have removed wrong generated page header image-properties from all dummy event pages: code sv:property sv:name=image sv:type=String sv:valuedms/sv:value /sv:property sv:property sv:name=imageDmsUUID sv:type=String sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value /sv:property sv:property sv:name=imageLocation sv:type=String sv:valueabove/sv:value /sv:property /code Demo content: No dummy events for 2010 -- Key: MGNLSTK-557 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.2.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.2.x All dummy events in the demo content are events of the year 2009. The events are located under: demo-project/service/dummy-events/ These events should be updated to 2010. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777
]
Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:30 AM:
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{code}
was (Author: cringele):
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
}
Demo content: No dummy events for 2010
--
Key: MGNLSTK-557
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Fix For: 1.2.x
All dummy events in the demo content are events of the year 2009.
The events are located under: demo-project/service/dummy-events/
These events should be updated to 2010.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777
]
Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:30 AM:
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{/code}
was (Author: cringele):
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
[code]
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
[/code]
Demo content: No dummy events for 2010
--
Key: MGNLSTK-557
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Fix For: 1.2.x
All dummy events in the demo content are events of the year 2009.
The events are located under: demo-project/service/dummy-events/
These events should be updated to 2010.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777
]
Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:31 AM:
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{code}
was (Author: cringele):
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{code}
Demo content: No dummy events for 2010
--
Key: MGNLSTK-557
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Fix For: 1.2.x
All dummy events in the demo content are events of the year 2009.
The events are located under: demo-project/service/dummy-events/
These events should be updated to 2010.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777
]
Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:31 AM:
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{code}
was (Author: cringele):
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{code}
Demo content: No dummy events for 2010
--
Key: MGNLSTK-557
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Fix For: 1.2.x
All dummy events in the demo content are events of the year 2009.
The events are located under: demo-project/service/dummy-events/
These events should be updated to 2010.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-557) Demo content: No dummy events for 2010
[ http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-557: -- Attachment: website.demo-project.service.dummy-events.xml Demo content: No dummy events for 2010 -- Key: MGNLSTK-557 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.2.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.2.x Attachments: website.demo-project.service.dummy-events.xml All dummy events in the demo content are events of the year 2009. The events are located under: demo-project/service/dummy-events/ These events should be updated to 2010. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-572) JS files should not contain 'dot' in names - option 'Bypass' on the resource can not work otherwise
[ http://jira.magnolia-cms.com/browse/MGNLSTK-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-572: -- Description: All installed JS's containing a 'dot' in their file name are installed with a 'minus' instead of the 'dot'. (Dot is not allowed in a content node name). Now when activating the option 'Bypass' on the resource, it is not working because is searches for the JS with the 'minus' instead of the 'dot'. This can only be solved by not having any JS's containing a 'dot' in the file name. was: All installed JS's containing a 'dot' in their file name are installed with a 'minus' instead of the 'dot'. (Dot is not allowed in a content node name). Now when activating the option 'Bypass' on the resource, it is not working because is searches for the JS with the 'minus' instead of the 'dot'. This can only be soved by not having any JS's containing a 'dot' in the file name. JS files should not contain 'dot' in names - option 'Bypass' on the resource can not work otherwise Key: MGNLSTK-572 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-572 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.1.2, 1.2.2, 1.3 M1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.1.3, 1.3, 1.2.x All installed JS's containing a 'dot' in their file name are installed with a 'minus' instead of the 'dot'. (Dot is not allowed in a content node name). Now when activating the option 'Bypass' on the resource, it is not working because is searches for the JS with the 'minus' instead of the 'dot'. This can only be solved by not having any JS's containing a 'dot' in the file name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-572) JS files should not contain 'dot' in names - option 'Bypass' on the resource can not work otherwise
JS files should not contain 'dot' in names - option 'Bypass' on the resource can not work otherwise Key: MGNLSTK-572 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-572 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.3 M1, 1.2.2, 1.1.2 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.1.3, 1.3, 1.2.x All installed JS's containing a 'dot' in their file name are installed with a 'minus' instead of the 'dot'. (Dot is not allowed in a content node name). Now when activating the option 'Bypass' on the resource, it is not working because is searches for the JS with the 'minus' instead of the 'dot'. This can only be soved by not having any JS's containing a 'dot' in the file name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MGNLGA-4) Remove redundant basic install tasks from extra install tasks in version handler
[ http://jira.magnolia-cms.com/browse/MGNLGA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele resolved MGNLGA-4. Fix Version/s: RC-6 Resolution: Fixed Done Remove redundant basic install tasks from extra install tasks in version handler Key: MGNLGA-4 URL: http://jira.magnolia-cms.com/browse/MGNLGA-4 Project: Magnolia Google Analytics Issue Type: Bug Reporter: Nils Breunese Assignee: Christian Ringele Priority: Minor Fix For: RC-6 The getExtraInstallTasks() method has the following call: installTasks.addAll(super.getBasicInstallTasks(ctx)); This is redundant and should be removed. Please see the thread at http://www.nabble.com/Version-handler-install-tasks-td26011961.html for Jan Haderka's comment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MGNLGA-3) Rename GoggleAnalyticsJSResourceModel.java to GoogleAnalyticsJSResourceModel.java
[ http://jira.magnolia-cms.com/browse/MGNLGA-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele resolved MGNLGA-3. Fix Version/s: RC-6 Resolution: Fixed Done Rename GoggleAnalyticsJSResourceModel.java to GoogleAnalyticsJSResourceModel.java - Key: MGNLGA-3 URL: http://jira.magnolia-cms.com/browse/MGNLGA-3 Project: Magnolia Google Analytics Issue Type: Bug Reporter: Nils Breunese Assignee: Christian Ringele Priority: Trivial Fix For: RC-6 Original Estimate: 0.01d Remaining Estimate: 0.01d Please refactor src/main/java/info/magnolia/module/googleanalytics/model/GoggleAnalyticsJSResourceModel.java to src/main/java/info/magnolia/module/googleanalytics/model/GoogleAnalyticsJSResourceModel.java. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in dissapearing propertiy
On Windows only: Changing property name of characters to lower/upper case results in dissapearing propertiy --- Key: MAGNOLIA-3108 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 3.6.3 Environment: Windows 2003 Server MySQL 5.1 Magnolia 3.6.3 JCR 1.4.5 core PM: jackrabbit-mysql-search.xml Reporter: Christian Ringele Assignee: Christian Ringele When changing characters of a property's name to lower/upper case, the property disappears: - Change property in JCR from 'test' to 'TEST' The property disappears and is not stored anymore in MySql. The same happens when adding a second propert with the same name, just having different character in lower/upper case: - add property 'test' - add property 'TEST' - 'test' remains and 'TEST' disappears -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in dissapearing propertiy
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele resolved MAGNOLIA-3108. - Resolution: Workaround exists First deleting the property and then adding it again with the new name works. Is a bit cumbersome, but worked to resolve the problem. On Windows only: Changing property name of characters to lower/upper case results in dissapearing propertiy --- Key: MAGNOLIA-3108 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 3.6.3 Environment: Windows 2003 Server MySQL 5.1 Magnolia 3.6.3 JCR 1.4.5 core PM: jackrabbit-mysql-search.xml Reporter: Christian Ringele Assignee: Christian Ringele When changing characters of a property's name to lower/upper case, the property disappears: - Change property in JCR from 'test' to 'TEST' The property disappears and is not stored anymore in MySql. The same happens when adding a second propert with the same name, just having different character in lower/upper case: - add property 'test' - add property 'TEST' - 'test' remains and 'TEST' disappears -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in disappearing property
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3108: Summary: On Windows only: Changing property name of characters to lower/upper case results in disappearing property (was: On Windows only: Changing property name of characters to lower/upper case results in disapearing property) On Windows only: Changing property name of characters to lower/upper case results in disappearing property -- Key: MAGNOLIA-3108 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 3.6.3 Environment: Windows 2003 Server MySQL 5.1 Magnolia 3.6.3 JCR 1.4.5 core PM: jackrabbit-mysql-search.xml Reporter: Christian Ringele Assignee: Christian Ringele When changing characters of a property's name to lower/upper case, the property disappears: - Change property in JCR from 'test' to 'TEST' The property disappears and is not stored anymore in MySql. The same happens when adding a second propert with the same name, just having different character in lower/upper case: - add property 'test' - add property 'TEST' - 'test' remains and 'TEST' disappears -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in dissapearing property
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3108: Summary: On Windows only: Changing property name of characters to lower/upper case results in dissapearing property (was: On Windows only: Changing property name of characters to lower/upper case results in dissapearing propertiy) On Windows only: Changing property name of characters to lower/upper case results in dissapearing property -- Key: MAGNOLIA-3108 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 3.6.3 Environment: Windows 2003 Server MySQL 5.1 Magnolia 3.6.3 JCR 1.4.5 core PM: jackrabbit-mysql-search.xml Reporter: Christian Ringele Assignee: Christian Ringele When changing characters of a property's name to lower/upper case, the property disappears: - Change property in JCR from 'test' to 'TEST' The property disappears and is not stored anymore in MySql. The same happens when adding a second propert with the same name, just having different character in lower/upper case: - add property 'test' - add property 'TEST' - 'test' remains and 'TEST' disappears -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in disapearing property
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3108: Summary: On Windows only: Changing property name of characters to lower/upper case results in disapearing property (was: On Windows only: Changing property name of characters to lower/upper case results in dissapearing property) On Windows only: Changing property name of characters to lower/upper case results in disapearing property - Key: MAGNOLIA-3108 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 3.6.3 Environment: Windows 2003 Server MySQL 5.1 Magnolia 3.6.3 JCR 1.4.5 core PM: jackrabbit-mysql-search.xml Reporter: Christian Ringele Assignee: Christian Ringele When changing characters of a property's name to lower/upper case, the property disappears: - Change property in JCR from 'test' to 'TEST' The property disappears and is not stored anymore in MySql. The same happens when adding a second propert with the same name, just having different character in lower/upper case: - add property 'test' - add property 'TEST' - 'test' remains and 'TEST' disappears -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in disappearing property
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele reopened MAGNOLIA-3108: - On Windows only: Changing property name of characters to lower/upper case results in disappearing property -- Key: MAGNOLIA-3108 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 3.6.3 Environment: Windows 2003 Server MySQL 5.1 Magnolia 3.6.3 JCR 1.4.5 core PM: jackrabbit-mysql-search.xml Reporter: Christian Ringele Assignee: Christian Ringele When changing characters of a property's name to lower/upper case, the property disappears: - Change property in JCR from 'test' to 'TEST' The property disappears and is not stored anymore in MySql. The same happens when adding a second propert with the same name, just having different character in lower/upper case: - add property 'test' - add property 'TEST' - 'test' remains and 'TEST' disappears -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-593) Freemarker Error with OnAir-DAM control when corresponding metadata-uuid is missing - STKUtil does not return 'null' to freemarker
Freemarker Error with OnAir-DAM control when corresponding metadata-uuid is
missing - STKUtil does not return 'null' to freemarker
---
Key: MGNLSTK-593
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-593
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Affects Versions: 1.3 M2, 1.2.3
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Attachments: FreemarkerError_OnAir_Image.txt
General info:
All available Assets from media browser have a corresponding meta-data node in
the data module.
They correspond by their UUID.
Error setup:
- Selecting a image with the OnAir DAM control
- Corresponding meta-data node is missing in data module
- feemarker error
Call from Freemarker template:
[#assign image = imageModel.image!]
Source of the problem:
- In class 'STKUtil.java '
- In method 'public static Asset getAsset(Content content, String nodeDataName,
String variationName)'
In case of the catched 'catch(DAMException e){' null is not returned to the
freemarker template.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-594) Page Header image: Leftright of the text is not properly designed (css)
Page Header image: Leftright of the text is not properly designed (css) Key: MGNLSTK-594 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-594 Project: Magnolia Standard Templating Kit Issue Type: Bug Affects Versions: 1.2.3 Reporter: Christian Ringele Assignee: Philipp Bärfuss Attachments: Screen shot 2010-03-10 at 2.02.31 PM.png, Screen shot 2010-03-10 at 2.03.21 PM.png, Screen shot 2010-03-10 at 2.03.40 PM.png When choosing in a page header in the option 'Image Location' 'left of the text' or 'right of the text', the text is not placed correctly. The text stays below the image. On news overview page the text flows, but drags the next paragraph with it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MGNLSTK-593) Freemarker Error with OnAir-DAM control when corresponding metadata-uuid is missing - STKUtil does not return 'null' to freemarker
[
http://jira.magnolia-cms.com/browse/MGNLSTK-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=27080#action_27080
]
Christian Ringele commented on MGNLSTK-593:
---
Same error occurs on pages where OnAir image is used, when OnAir DAM handler is
deactivated.
Freemarker Error with OnAir-DAM control when corresponding metadata-uuid is
missing - STKUtil does not return 'null' to freemarker
---
Key: MGNLSTK-593
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-593
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Affects Versions: 1.2.3, 1.3 M2
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Attachments: FreemarkerError_OnAir_Image.txt
General info:
All available Assets from media browser have a corresponding meta-data node
in the data module.
They correspond by their UUID.
Error setup:
- Selecting a image with the OnAir DAM control
- Corresponding meta-data node is missing in data module
- feemarker error
Call from Freemarker template:
[#assign image = imageModel.image!]
Source of the problem:
- In class 'STKUtil.java '
- In method 'public static Asset getAsset(Content content, String
nodeDataName, String variationName)'
In case of the catched 'catch(DAMException e){' null is not returned to the
freemarker template.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3166) Nice Editor couts line only to value=1500 and starts afterwards with 1 again
Nice Editor couts line only to value=1500 and starts afterwards with 1 again Key: MAGNOLIA-3166 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3166 Project: Magnolia Issue Type: Bug Components: gui Affects Versions: 4.3.1, 4.2.3, 4.1.4 Reporter: Christian Ringele Assignee: Boris Kraft Priority: Minor The problem shows up on stk's css. The css has more lines than 1500. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-635) stkLinkList: hast its sub-paragraphs hard coded in freemarker template
stkLinkList: hast its sub-paragraphs hard coded in freemarker template -- Key: MGNLSTK-635 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-635 Project: Magnolia Standard Templating Kit Issue Type: Improvement Affects Versions: 1.3 Reporter: Christian Ringele Assignee: Philipp Bärfuss Priority: Minor All other paragraphs except the stkLinkList paragraphs get the sub-paragraphs list dynamically over the 'def' object. The stkLinkList should receive it's sub.paragraphs by the def object too, because it is very likely that more link paragraphs are implemented in a project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLFORM-48) Form field 'selection': default value is not used - null is passed to the freemarker
Form field 'selection': default value is not used - null is passed to the freemarker - Key: MGNLFORM-48 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-48 Project: Magnolia Form Module Issue Type: Bug Affects Versions: 1.1.1 Reporter: Christian Ringele Assignee: Teresa Miyar When adding a 'selection' field, and defining a label:value, the value is passed to the template if the checkbox is checked. If not checked, the defined default value should be passed. But 'null' is passed to the freemaker instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-637) STKUtil does not return 'null' to freemarker when DAMException is caught
STKUtil does not return 'null' to freemarker when DAMException is caught Key: MGNLSTK-637 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-637 Project: Magnolia Standard Templating Kit Issue Type: Improvement Components: base system Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss STKUtil.java line 144 163: When a DAMException is caught, a RuntimeException is thrown, but null is not returned. When choosing from DMS (uuidLink Control) a folder instead an image, freemarker template does not get a 'null' as return. This makes this case much harder to handle in the template. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-638) Page Header Images: Page header images do not react correctly to option 'above/right/left'
Page Header Images: Page header images do not react correctly to option 'above/right/left' -- Key: MGNLSTK-638 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-638 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: themepop Reporter: Christian Ringele Assignee: Philipp Bärfuss On section pages only leftright works On content pages only above works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-639) Meta Navigation: Links are editable on any subpage
Meta Navigation: Links are editable on any subpage -- Key: MGNLSTK-639 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-639 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: templates Reporter: Christian Ringele Assignee: Philipp Bärfuss Priority: Minor Links of the meta navigation are editable on every subpage. This should not be, it should be only editable on the homepage itself (as in the footer). Or at least the inherited once should not be editable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-651) Navigation: openAll config property is ignored - bean variable is named differently
Navigation: openAll config property is ignored - bean variable is named differently Key: MGNLSTK-651 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-651 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: base system Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Attachments: Screen shot 2010-07-02 at 10.45.28 AM.png In the horizontal- and vertical-navigation is a configuration property 'openAll'. This value should achieve, that all sub pages get rendered in the navigation, not only the active one. So a JS could fetch all sub pages and provide these drop down menus. The property is ignored, because the according bean 'info.magnolia.module.templatingkit.templates.Navigation.java' is not populated: The variable for the property is named different: private Boolean allOpen; and its setters and getters. So the setter is never called and populated - always false. I tried to fid out when this error came in, but in all previous bootstrap files of the site config it was always openAll. In all previous versions of the bean it was always allOpen - looks like it never worked, what surprises me. I thought I've seen it working. Workaround: rename the property in the site configuration to according to the bean: allOpen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-653) Navigation - Meta Navigation: branding.ftl does not react on property 'enabled'
Navigation - Meta Navigation: branding.ftl does not react on property 'enabled' --- Key: MGNLSTK-653 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-653 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: templates Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Ondřej Chytil In the past, the meta navigation in the branding was implemented as an area. Before it was a static include of the template. When implementing it as a Area, it was forgotten to have the 'if enabled' around the include of the area template. It should be: [#if def.navigation.meta.enabled] [#include def.navigation.meta.template] [/#if] instead of [#include def.navigation.meta.template] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-654) BodyClassResolver.java : variable allowedBodyClasses should be protected and not private
BodyClassResolver.java : variable allowedBodyClasses should be protected and not private Key: MGNLSTK-654 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-654 Project: Magnolia Standard Templating Kit Issue Type: Improvement Components: themepop Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Ondřej Chytil Priority: Minor A common use case of extending/redefining the BodyClassResolver is that you want to allow another bodyClass situation/configuration. In my case right now: nav-col-subcol-subcol So actually only the variable allowedBodyClasses should be over-writable for this situation - protected instead of private Otherwise the complete class has to be copied for adapting this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-655) Contect Teaser: does not have inheritance control in dialog
Contect Teaser: does not have inheritance control in dialog --- Key: MGNLSTK-655 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-655 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: paragraphs Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-655) Contact Teaser: does not have inheritance control in dialog
[ http://jira.magnolia-cms.com/browse/MGNLSTK-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-655: -- Summary: Contact Teaser: does not have inheritance control in dialog (was: Contect Teaser: does not have inheritance control in dialog) Contact Teaser: does not have inheritance control in dialog --- Key: MGNLSTK-655 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-655 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: paragraphs Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-655) extrasContactTeaser: does not have inheritance control in dialog
[ http://jira.magnolia-cms.com/browse/MGNLSTK-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-655: -- Summary: extrasContactTeaser: does not have inheritance control in dialog (was: Contact Teaser: does not have inheritance control in dialog) extrasContactTeaser: does not have inheritance control in dialog Key: MGNLSTK-655 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-655 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: paragraphs Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-656) extrasContactTeaser: wrong checking of the website property in template
extrasContactTeaser: wrong checking of the website property in template
---
Key: MGNLSTK-656
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-656
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: paragraphs
Affects Versions: 1.3.1
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Is:
[#if model.website?has_content]
div
h3${i18n['contact.web.title']}/h3
dl class=url
dt${i18n['contact.web']}/dt
dd class=urla
href=${model.website?html}${model.contact.web?html}/a/dd
/dl
/div
[/#if]
Should be:
[#if model.contact.web?has_content]
div
h3${i18n['contact.web.title']}/h3
dl class=url
dt${i18n['contact.web']}/dt
dd class=urla
href=${model.website?html}${model.contact.web?html}/a/dd
/dl
/div
[/#if]
Or without a website defined in the contact, a freemarker error occurs:
freemarker.core.InvalidReferenceException: Expression model.contact.web is
undefined on line 104, column 63 in css-intranet/paragraphs/contact.ftl.
at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124)
Or the website method of the model should not return something if no web
property defined.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-656) extrasContactTeaser: wrong checking of the website property in template
[
http://jira.magnolia-cms.com/browse/MGNLSTK-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Ringele updated MGNLSTK-656:
--
Description:
Is:
[#if model.website?has_content]
div
h3${i18n['contact.web.title']}/h3
dl class=url
dt${i18n['contact.web']}/dt
dd class=urla
href=${model.website?html}${model.contact.web?html}/a/dd
/dl
/div
[/#if]
Should be:
[#if model.contact.web?has_content]
div
h3${i18n['contact.web.title']}/h3
dl class=url
dt${i18n['contact.web']}/dt
dd class=urla
href=${model.website?html}${model.contact.web?html}/a/dd
/dl
/div
[/#if]
Or without a website defined in the contact, a freemarker error occurs:
freemarker.core.InvalidReferenceException: Expression model.contact.web is
undefined on line 104, column 63 in ...
at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124)
Or the website method of the model should not return something if no web
property defined.
was:
Is:
[#if model.website?has_content]
div
h3${i18n['contact.web.title']}/h3
dl class=url
dt${i18n['contact.web']}/dt
dd class=urla
href=${model.website?html}${model.contact.web?html}/a/dd
/dl
/div
[/#if]
Should be:
[#if model.contact.web?has_content]
div
h3${i18n['contact.web.title']}/h3
dl class=url
dt${i18n['contact.web']}/dt
dd class=urla
href=${model.website?html}${model.contact.web?html}/a/dd
/dl
/div
[/#if]
Or without a website defined in the contact, a freemarker error occurs:
freemarker.core.InvalidReferenceException: Expression model.contact.web is
undefined on line 104, column 63 in css-intranet/paragraphs/contact.ftl.
at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124)
Or the website method of the model should not return something if no web
property defined.
extrasContactTeaser: wrong checking of the website property in template
---
Key: MGNLSTK-656
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-656
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: paragraphs
Affects Versions: 1.3.1
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Is:
[#if model.website?has_content]
div
h3${i18n['contact.web.title']}/h3
dl class=url
dt${i18n['contact.web']}/dt
dd class=urla
href=${model.website?html}${model.contact.web?html}/a/dd
/dl
/div
[/#if]
Should be:
[#if model.contact.web?has_content]
div
h3${i18n['contact.web.title']}/h3
dl class=url
dt${i18n['contact.web']}/dt
dd class=urla
href=${model.website?html}${model.contact.web?html}/a/dd
/dl
/div
[/#if]
Or without a website defined in the contact, a freemarker error occurs:
freemarker.core.InvalidReferenceException: Expression model.contact.web is
undefined on line 104, column 63 in ...
at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124)
Or the website method of the model should not return something if no web
property defined.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-657) header.ftl: Should reacht on 'def.header.branding.enabled'
header.ftl: Should reacht on 'def.header.branding.enabled' -- Key: MGNLSTK-657 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-657 Project: Magnolia Standard Templating Kit Issue Type: Improvement Components: templates Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Ondřej Chytil In the template header.ftl, the branding template is directly included without checking the enabled properts. It is: [#include def.header.branding.template] should be: [#if def.header.branding.enabled] [#include def.header.branding.template] [/#if] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-658) main.ftl: template should react on property 'def.header.enabled'
main.ftl: template should react on property 'def.header.enabled' Key: MGNLSTK-658 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-658 Project: Magnolia Standard Templating Kit Issue Type: Improvement Components: templates Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Ondřej Chytil the main.ftl includes directly the header template, instead of checking the enabled property first. It is: [#include def.header.template] It should be: [#if def.header.enabled] [#include def.header.template] [/#if] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLFORM-51) Selection element: Ignores the property 'Horizontal'
Selection element: Ignores the property 'Horizontal' Key: MGNLFORM-51 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-51 Project: Magnolia Form Module Issue Type: Bug Affects Versions: 1.1.1 Reporter: Christian Ringele Assignee: Ondřej Chytil Priority: Minor Attachments: Screen shot 2010-07-08 at 10.34.28 AM.png, Screen shot 2010-07-08 at 10.34.34 AM.png The selection elements always stay horizontal aligned, no matter of 'Horizontal' is checked or not. See printscreens -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-659) Paragraphs using the tocMacro.ftl are not usable as subparagraphs or from nested calls
Paragraphs using the tocMacro.ftl are not usable as subparagraphs or from nested calls -- Key: MGNLSTK-659 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-659 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: paragraphs Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Christian Ringele The paragraphs 'stkTextImage' and 'stkLinkList' include the macro tocMarkup.ftl: [#include /templating-kit/paragraphs/macros/tocMarkup.ftl/] The macro tries to read out the pages renderable definition, but does that wrong: [#assign intro = model.parent.def.mainArea.intro] this works as long the parent model of the paragraph is a page's model. But when the paragraph is a subparagraph, the call model.parent will return a renderable definition of a paragraph and not of a page. the correct solution is: [#macro tocMarkup model content] [#assign rootDef = model.root.def!false] [#if rootDef.mainArea?if_exists] [#assign showTOC = rootDef.mainArea.intro.showTOC!false] [#else] [#assign showTOC = false] [/#if] [#assign siblings=mgnl.siblings(content)] [#if showTOC] [#assign id='id=jump' + (siblings.index + 1) + ''] [#else] [#assign id=] [/#if] [/#macro] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MGNLSTK-659) Paragraphs using the tocMacro.ftl are not usable as subparagraphs or from nested calls
[ http://jira.magnolia-cms.com/browse/MGNLSTK-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele resolved MGNLSTK-659. --- Fix Version/s: 1.3.2 Resolution: Fixed Paragraphs using the tocMacro.ftl are not usable as subparagraphs or from nested calls -- Key: MGNLSTK-659 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-659 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: paragraphs Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Christian Ringele Fix For: 1.3.2 The paragraphs 'stkTextImage' and 'stkLinkList' include the macro tocMarkup.ftl: [#include /templating-kit/paragraphs/macros/tocMarkup.ftl/] The macro tries to read out the pages renderable definition, but does that wrong: [#assign intro = model.parent.def.mainArea.intro] this works as long the parent model of the paragraph is a page's model. But when the paragraph is a subparagraph, the call model.parent will return a renderable definition of a paragraph and not of a page. the correct solution is: [#macro tocMarkup model content] [#assign rootDef = model.root.def!false] [#if rootDef.mainArea?if_exists] [#assign showTOC = rootDef.mainArea.intro.showTOC!false] [#else] [#assign showTOC = false] [/#if] [#assign siblings=mgnl.siblings(content)] [#if showTOC] [#assign id='id=jump' + (siblings.index + 1) + ''] [#else] [#assign id=] [/#if] [/#macro] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-671) Singleton Template Definitiona (feature pages): Contain relative include of mainArea.ftl which doesn't work if using a custom main.ftl
Singleton Template Definitiona (feature pages): Contain relative include of mainArea.ftl which doesn't work if using a custom main.ftl -- Key: MGNLSTK-671 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-671 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: templates Affects Versions: 1.3.4 Reporter: Christian Ringele Assignee: Ondřej Chytil Attachments: Screen shot 2010-08-02 at 12.18.48 PM.png Relative includes of sub templates/sub snippets don't work, if you use a main.ftl located in a different location/module. The relative include is the executed on the new location. In cause of this we had the same problem with all Section templates and removed them from the Section templates. The the singleton paragraph templates these relative includes still remain, see print screen. Best would be to check all template definitions (ans all ftl's for inlclue of macros) if there are still any relative includes left. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-671) Singleton Template Definitiona (feature pages): Contain relative include of mainArea.ftl which doesn't work if using a custom main.ftl
[ http://jira.magnolia-cms.com/browse/MGNLSTK-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-671: -- Description: Relative includes of sub templates/sub snippets don't work, if you use a main.ftl located in a different location/module. The relative include is the executed on the new location. In cause of this we had the same problem with all Section templates and removed them from the Section templates. The the singleton paragraph templates these relative includes still remain, see print screen. Best would be to check all template definitions (ans all ftl's for include of macros) if there are still any relative includes left. All includes, no matter where, should be absolute paths. was: Relative includes of sub templates/sub snippets don't work, if you use a main.ftl located in a different location/module. The relative include is the executed on the new location. In cause of this we had the same problem with all Section templates and removed them from the Section templates. The the singleton paragraph templates these relative includes still remain, see print screen. Best would be to check all template definitions (ans all ftl's for inlclue of macros) if there are still any relative includes left. Singleton Template Definitiona (feature pages): Contain relative include of mainArea.ftl which doesn't work if using a custom main.ftl -- Key: MGNLSTK-671 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-671 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: templates Affects Versions: 1.3.4 Reporter: Christian Ringele Assignee: Ondřej Chytil Attachments: Screen shot 2010-08-02 at 12.18.48 PM.png Relative includes of sub templates/sub snippets don't work, if you use a main.ftl located in a different location/module. The relative include is the executed on the new location. In cause of this we had the same problem with all Section templates and removed them from the Section templates. The the singleton paragraph templates these relative includes still remain, see print screen. Best would be to check all template definitions (ans all ftl's for include of macros) if there are still any relative includes left. All includes, no matter where, should be absolute paths. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-638) Page Header Images: Page header images do not react correctly to option 'above/right/left'
[ http://jira.magnolia-cms.com/browse/MGNLSTK-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-638: -- Assignee: Ondřej Chytil (was: Philipp Bärfuss) Page Header Images: Page header images do not react correctly to option 'above/right/left' -- Key: MGNLSTK-638 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-638 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: themepop Reporter: Christian Ringele Assignee: Ondřej Chytil On section pages only leftright works On content pages only above works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-504) section page header renders wrong if header image alignment chosen is not above text
[ http://jira.magnolia-cms.com/browse/MGNLSTK-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-504: -- Assignee: Ondřej Chytil (was: Philipp Bärfuss) section page header renders wrong if header image alignment chosen is not above text -- Key: MGNLSTK-504 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-504 Project: Magnolia Standard Templating Kit Issue Type: Bug Reporter: Boris Kraft Assignee: Ondřej Chytil Attachments: Picture 1.png See http://localhost:8080/magnoliaAuthor/demo-project/about/subsection-articles.html Click on edit section header, select left of the text or right of the text as Image Location (who came up with that name btw? It should be Image Alignment) Now the result will render the following P in a half-column, see screenshot. I strongly assume the following P should render across the complete main area -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-594) Page Header image: Leftright of the text is not properly designed (css)
[ http://jira.magnolia-cms.com/browse/MGNLSTK-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-594: -- Assignee: Ondřej Chytil (was: Philipp Bärfuss) Page Header image: Leftright of the text is not properly designed (css) Key: MGNLSTK-594 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-594 Project: Magnolia Standard Templating Kit Issue Type: Bug Affects Versions: 1.2.3 Reporter: Christian Ringele Assignee: Ondřej Chytil Attachments: Screen shot 2010-03-10 at 2.02.31 PM.png, Screen shot 2010-03-10 at 2.03.21 PM.png, Screen shot 2010-03-10 at 2.03.40 PM.png When choosing in a page header in the option 'Image Location' 'left of the text' or 'right of the text', the text is not placed correctly. The text stays below the image. On news overview page the text flows, but drags the next paragraph with it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-502) Include paths in paragraph should be provides by pragraph 'def.'
[ http://jira.magnolia-cms.com/browse/MGNLSTK-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-502: -- Assignee: Ondřej Chytil (was: Philipp Bärfuss) Include paths in paragraph should be provides by pragraph 'def.' Key: MGNLSTK-502 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-502 Project: Magnolia Standard Templating Kit Issue Type: Improvement Components: paragraphs Affects Versions: 1.1.2 Reporter: Christian Ringele Assignee: Ondřej Chytil Paragraph templates contain includes to other freemarker templates. Fore example every template using the image macro template includes it hard coded. This has the result, that if the image macro needs to be adapted, all other paragraphs using it must be adapted too. Like this it's not possible, to use the standard stkTextImage, but only adapting the macro image. A more dynamic solution would be to define the include path of the macro on paragraph 'def' level. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-671) Singleton Template Definitiona (feature pages): Contain relative include of mainArea.ftl which doesn't work if using a custom main.ftl
[ http://jira.magnolia-cms.com/browse/MGNLSTK-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-671: -- Description: Relative includes of sub templates/sub snippets don't work, if you use a main.ftl located in a different location/module. The relative include is the executed on the new location (relative to the new main.ftl). We had the same problem with all Section templates and removed the relative pathes from the Section templates. The the singleton paragraph templates still contain these relative includes, see print screen. Best would be to check all template definitions (and all ftl's for include of macros) if there are still any relative includes left. All includes, no matter where, should be absolute paths. was: Relative includes of sub templates/sub snippets don't work, if you use a main.ftl located in a different location/module. The relative include is the executed on the new location. In cause of this we had the same problem with all Section templates and removed them from the Section templates. The the singleton paragraph templates these relative includes still remain, see print screen. Best would be to check all template definitions (ans all ftl's for include of macros) if there are still any relative includes left. All includes, no matter where, should be absolute paths. Singleton Template Definitiona (feature pages): Contain relative include of mainArea.ftl which doesn't work if using a custom main.ftl -- Key: MGNLSTK-671 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-671 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: templates Affects Versions: 1.3.4 Reporter: Christian Ringele Assignee: Ondřej Chytil Attachments: Screen shot 2010-08-02 at 12.18.48 PM.png Relative includes of sub templates/sub snippets don't work, if you use a main.ftl located in a different location/module. The relative include is the executed on the new location (relative to the new main.ftl). We had the same problem with all Section templates and removed the relative pathes from the Section templates. The the singleton paragraph templates still contain these relative includes, see print screen. Best would be to check all template definitions (and all ftl's for include of macros) if there are still any relative includes left. All includes, no matter where, should be absolute paths. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLFORUM-115) Nodetype defintion is not correct in file magnolia-forum-nodetypes.xml
[
http://jira.magnolia-cms.com/browse/MGNLFORUM-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Ringele updated MGNLFORUM-115:
Assignee: Ondřej Chytil (was: Grégory Joseph)
Nodetype defintion is not correct in file magnolia-forum-nodetypes.xml
--
Key: MGNLFORUM-115
URL: http://jira.magnolia-cms.com/browse/MGNLFORUM-115
Project: Magnolia Forum Module
Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Fix For: 1.2.2
When updating the forum module from 1.1 to 1.2.1 it expects two new values in
the file custom_nodetype.xml:
{code}
propertyDefinition autoCreated=false mandatory=false
multiple=false name=mgnl:ordering_info onParentVersion=COPY
protected=false requiredType=String /
{code}
and
{code}
childNodeDefinition autoCreated=true
defaultPrimaryType=mgnl:metaData mandatory=true name=MetaData
onParentVersion=COPY protected=false sameNameSiblings=false
requiredPrimaryTypes
requiredPrimaryTypemgnl:metaData/requiredPrimaryType
/requiredPrimaryTypes
/childNodeDefinition
{code}
But when installing the forum module directly with version 1.2.1, these
definitions are not added, because they are missing in the file:
http://svn.magnolia-cms.com/svn/community/modules/forum/tags/magnolia-module-forum-1.2.1/src/main/resources/mgnl-nodetypes/magnolia-forum-nodetypes.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLFORUM-115) Nodetype defintion is not correct in file magnolia-forum-nodetypes.xml
[
http://jira.magnolia-cms.com/browse/MGNLFORUM-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Ringele updated MGNLFORUM-115:
Summary: Nodetype defintion is not correct in file
magnolia-forum-nodetypes.xml (was: Nodetype defintiion is not correct for
version 1.2.1)
Description:
When updating the forum module from 1.1 to 1.2.1 it expects two new values in
the file custom_nodetype.xml:
{code}
propertyDefinition autoCreated=false mandatory=false
multiple=false name=mgnl:ordering_info onParentVersion=COPY
protected=false requiredType=String /
{code}
and
{code}
childNodeDefinition autoCreated=true
defaultPrimaryType=mgnl:metaData mandatory=true name=MetaData
onParentVersion=COPY protected=false sameNameSiblings=false
requiredPrimaryTypes
requiredPrimaryTypemgnl:metaData/requiredPrimaryType
/requiredPrimaryTypes
/childNodeDefinition
{code}
But when installing the forum module directly with version 1.2.1, these
definitions are not added, because they are missing in the file:
http://svn.magnolia-cms.com/svn/community/modules/forum/tags/magnolia-module-forum-1.2.1/src/main/resources/mgnl-nodetypes/magnolia-forum-nodetypes.xml
was:
When updating the forum module from 1.1 to 1.2.1 it expects two new values on
the custom_nodetype.xml:
{code}
propertyDefinition autoCreated=false mandatory=false
multiple=false name=mgnl:ordering_info
onParentVersion=COPY
protected=false requiredType=String /
{code}
and
{code}
childNodeDefinition autoCreated=true
defaultPrimaryType=mgnl:metaData mandatory=true
name=MetaData
onParentVersion=COPY protected=false
sameNameSiblings=false
requiredPrimaryTypes
requiredPrimaryTypemgnl:metaData/requiredPrimaryType
/requiredPrimaryTypes
/childNodeDefinition
{code}
But when installing the forum module directly with version 1.2.1, these
definitions are not added, because they are missing in the file:
http://svn.magnolia-cms.com/svn/community/modules/forum/tags/magnolia-module-forum-1.2.1/src/main/resources/mgnl-nodetypes/magnolia-forum-nodetypes.xml
Nodetype defintion is not correct in file magnolia-forum-nodetypes.xml
--
Key: MGNLFORUM-115
URL: http://jira.magnolia-cms.com/browse/MGNLFORUM-115
Project: Magnolia Forum Module
Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Grégory Joseph
Fix For: 1.2.2
When updating the forum module from 1.1 to 1.2.1 it expects two new values in
the file custom_nodetype.xml:
{code}
propertyDefinition autoCreated=false mandatory=false
multiple=false name=mgnl:ordering_info onParentVersion=COPY
protected=false requiredType=String /
{code}
and
{code}
childNodeDefinition autoCreated=true
defaultPrimaryType=mgnl:metaData mandatory=true name=MetaData
onParentVersion=COPY protected=false sameNameSiblings=false
requiredPrimaryTypes
requiredPrimaryTypemgnl:metaData/requiredPrimaryType
/requiredPrimaryTypes
/childNodeDefinition
{code}
But when installing the forum module directly with version 1.2.1, these
definitions are not added, because they are missing in the file:
http://svn.magnolia-cms.com/svn/community/modules/forum/tags/magnolia-module-forum-1.2.1/src/main/resources/mgnl-nodetypes/magnolia-forum-nodetypes.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-694) ETKRootVirtualURIMapping should only be bootstrappes on Author instance.
ETKRootVirtualURIMapping should only be bootstrappes on Author instance.
Key: MGNLSTK-694
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-694
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: base system
Affects Versions: 1.3.5
Reporter: Christian Ringele
Assignee: Ondřej Chytil
The ETKRootVirtualURIMapping is used in
'/modules/adminInterface/virtualURIMapping/default' and set to this property by
the ETKModuleVersionHandler:
{code}
private CheckAndModifyPropertyValueTask setDefaultVirtualURIMapping = new
CheckAndModifyPropertyValueTask(ETK default virtual uri mapping, ,
config, /modules/adminInterface/virtualURIMapping/default, class,
DefaultVirtualURIMapping.class.getName(),
ETKRootVirtualURIMapping.class.getName());
{code}
But the ETKRootVirtualURIMapping makes only sense on a author system, and not
on a public.
Therefore it should only be set to the property by the VersionHandler on a
author system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3349) Allow subfolders/nodes in the observed 'virtualURIMapping' module nodes - adaption of the VirtualURIManager class
Allow subfolders/nodes in the observed 'virtualURIMapping' module nodes - adaption of the VirtualURIManager class - Key: MAGNOLIA-3349 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3349 Project: Magnolia Issue Type: Improvement Components: modulemechanism Affects Versions: 4.3.8 Reporter: Christian Ringele Assignee: Ondřej Chytil Priority: Minor Attachments: magnolia-core.patch, Screen shot 2010-10-29 at 12.13.53 PM.png When having a lot of virtualURIMappings registered in a module, it can be quite hard to keep the overview. Being able to sort them in folders/nodes would improve that a lot (as in paragraphs/dialogs already possible). I added a patch of this class, which does that. Code should be checked for core quality, was implemented very quickly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3353) Extends feature brakes various things (templates/dialogsparagraphs) if wrong configured
Extends feature brakes various things (templates/dialogsparagraphs) if wrong configured --- Key: MAGNOLIA-3353 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3353 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.2 Reporter: Christian Ringele Assignee: Ondřej Chytil The behavior is very different on tempates/dialogs and paragraphs, so I'll open for these three situations a sub issue with a detailed description. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3354) Extends: Registered teamplates get lost below wrong configuration
Extends: Registered teamplates get lost below wrong configuration - Key: MAGNOLIA-3354 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3354 Project: Magnolia Issue Type: Sub-task Components: core Affects Versions: 4.3.8, 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.2 Reporter: Christian Ringele Assignee: Ondřej Chytil Attachments: Screen shot 2010-11-02 at 10.49.55 AM.png, Screen shot 2010-11-02 at 10.51.44 AM.png, Screen shot 2010-11-02 at 10.52.11 AM.png Base setup: Adding a template definition, which extends another template definition (see print screen). Problem: If the value of the extends property is set wrong, all template definitions registered below the wrong node are invalid. So if placed for example below the stkSection (see print screen), all template below are not found anymore (print screen). Behavior on correct reconfiguration: When correcting the wrong extends value, all templates are registered correct again. What should be changed: Following template definitions of a wrong definition should be still registered. and usable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3354) Extends Templates: Registered teamplates get lost below wrong configuration
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3354: Summary: Extends Templates: Registered teamplates get lost below wrong configuration (was: Extends: Registered teamplates get lost below wrong configuration) Extends Templates: Registered teamplates get lost below wrong configuration --- Key: MAGNOLIA-3354 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3354 Project: Magnolia Issue Type: Sub-task Components: core Affects Versions: 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7, 4.3.8 Reporter: Christian Ringele Assignee: Ondřej Chytil Attachments: Screen shot 2010-11-02 at 10.49.55 AM.png, Screen shot 2010-11-02 at 10.51.44 AM.png, Screen shot 2010-11-02 at 10.52.11 AM.png Base setup: Adding a template definition, which extends another template definition (see print screen). Problem: If the value of the extends property is set wrong, all template definitions registered below the wrong node are invalid. So if placed for example below the stkSection (see print screen), all template below are not found anymore (print screen). Behavior on correct reconfiguration: When correcting the wrong extends value, all templates are registered correct again. What should be changed: Following template definitions of a wrong definition should be still registered. and usable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3355) Extends Dialogs: All registered dialogs get lost after correcting a wrong configuration
Extends Dialogs: All registered dialogs get lost after correcting a wrong configuration --- Key: MAGNOLIA-3355 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3355 Project: Magnolia Issue Type: Sub-task Components: core Affects Versions: 4.3.8, 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.2 Reporter: Christian Ringele Assignee: Philipp Bärfuss Attachments: Screen shot 2010-11-02 at 10.59.22 AM.png, Screen shot 2010-11-02 at 11.11.04 AM.png Base setup: Adding a dialog, which extends an existing one (see print screen) Problem 1 - Dialog is below all others: Step1: Adding a wrong value to the extends property makes the dialog unusable (that is correct yet). All other dialogs are still usable as they should. Step2: Changing the wrong value back to the correct value used before - all registered dialogs are lost! No dialog is available anymore provided by this module. Behavior on correct reconfiguration: All dialogs of the module are lost, no matter on which location the dialog was registered. Only a restart of the server registers the dialogs again. Problem 2 - Dialog is places in between: Step1: Adding a wrong value to the extends property makes the dialog unusable (that is correct yet). All dialogs placed below this wrong dialog are not registered anymore (same as on templates). What should be changed: That all dialogs are always registered and usable, except the one which has a wrong configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3355) Extends Dialogs: All registered dialogs get lost after correcting a wrong configuration
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3355: Assignee: Ondřej Chytil (was: Philipp Bärfuss) Extends Dialogs: All registered dialogs get lost after correcting a wrong configuration --- Key: MAGNOLIA-3355 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3355 Project: Magnolia Issue Type: Sub-task Components: core Affects Versions: 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7, 4.3.8 Reporter: Christian Ringele Assignee: Ondřej Chytil Attachments: Screen shot 2010-11-02 at 10.59.22 AM.png, Screen shot 2010-11-02 at 11.11.04 AM.png Base setup: Adding a dialog, which extends an existing one (see print screen) Problem 1 - Dialog is below all others: Step1: Adding a wrong value to the extends property makes the dialog unusable (that is correct yet). All other dialogs are still usable as they should. Step2: Changing the wrong value back to the correct value used before - all registered dialogs are lost! No dialog is available anymore provided by this module. Behavior on correct reconfiguration: All dialogs of the module are lost, no matter on which location the dialog was registered. Only a restart of the server registers the dialogs again. Problem 2 - Dialog is places in between: Step1: Adding a wrong value to the extends property makes the dialog unusable (that is correct yet). All dialogs placed below this wrong dialog are not registered anymore (same as on templates). What should be changed: That all dialogs are always registered and usable, except the one which has a wrong configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3353) Extends feature brakes templatesdialog definitions
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3353: Summary: Extends feature brakes templatesdialog definitions (was: Extends feature brakes various things (templates/dialogsparagraphs) if wrong configured) Description: The behavior is very different on templatesdialogs, so I'll open for these two situations a sub issue with a detailed description. If doing the same as described in the sub-tasks with paragraph definitions, it works fine. Only the wrong configured paragraph definition is invalid, but all other paragraph definitions stay always registered and available. was:The behavior is very different on tempates/dialogs and paragraphs, so I'll open for these three situations a sub issue with a detailed description. Extends feature brakes templatesdialog definitions --- Key: MAGNOLIA-3353 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3353 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7, 4.3.8 Reporter: Christian Ringele Assignee: Ondřej Chytil The behavior is very different on templatesdialogs, so I'll open for these two situations a sub issue with a detailed description. If doing the same as described in the sub-tasks with paragraph definitions, it works fine. Only the wrong configured paragraph definition is invalid, but all other paragraph definitions stay always registered and available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3359) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value
NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value - Key: MAGNOLIA-3359 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3359 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 4.3.x, 4.4.x Attachments: magnolia-core.patch, Screen shot 2010-11-03 at 4.15.43 PM.png The value of the renamed node is not the value of the old node, but the path to the passed NodeData object (see print screen). Ive written a test case which verifies that and attached it to the ticket. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3359) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3359: Attachment: magnolia-core.patch NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value - Key: MAGNOLIA-3359 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3359 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 4.3.x, 4.4.x Attachments: magnolia-core.patch, Screen shot 2010-11-03 at 4.15.43 PM.png The value of the renamed node is not the value of the old node, but the path to the passed NodeData object (see print screen). Ive written a test case which verifies that and attached it to the ticket. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3359) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3359: Attachment: (was: magnolia-core.patch) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value - Key: MAGNOLIA-3359 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3359 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 4.3.x, 4.4.x Attachments: magnolia-core.patch, Screen shot 2010-11-03 at 4.15.43 PM.png The value of the renamed node is not the value of the old node, but the path to the passed NodeData object (see print screen). Ive written a test case which verifies that and attached it to the ticket. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3359) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3359: Attachment: (was: magnolia-core.patch) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value - Key: MAGNOLIA-3359 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3359 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 4.3.x, 4.4.x Attachments: magnolia-core.patch, Screen shot 2010-11-03 at 4.15.43 PM.png The value of the renamed node is not the value of the old node, but the path to the passed NodeData object (see print screen). Ive written a test case which verifies that and attached it to the ticket. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3359) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3359: Attachment: magnolia-core.patch NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value - Key: MAGNOLIA-3359 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3359 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 4.3.x, 4.4.x Attachments: magnolia-core.patch, Screen shot 2010-11-03 at 4.15.43 PM.png The value of the renamed node is not the value of the old node, but the path to the passed NodeData object (see print screen). Ive written a test case which verifies that and attached it to the ticket. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3359) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3359: Attachment: (was: magnolia-core.patch) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value - Key: MAGNOLIA-3359 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3359 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 4.3.x, 4.4.x Attachments: Screen shot 2010-11-03 at 4.15.43 PM.png The value of the renamed node is not the value of the old node, but the path to the passed NodeData object (see print screen). Ive written a test case which verifies that and attached it to the ticket. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3359) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3359: Patch included: [Yes] Attachment: magnolia-core.patch Description: The value of the renamed node is not the value of the old node, but the path to the passed NodeData object (see print screen). I've written test cases and a solution in the Ops class and attached it as a patch. was: The value of the renamed node is not the value of the old node, but the path to the passed NodeData object (see print screen). Ive written a test case which verifies that and attached it to the ticket. NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value - Key: MAGNOLIA-3359 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3359 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 4.3.x, 4.4.x Attachments: magnolia-core.patch, Screen shot 2010-11-03 at 4.15.43 PM.png The value of the renamed node is not the value of the old node, but the path to the passed NodeData object (see print screen). I've written test cases and a solution in the Ops class and attached it as a patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3359) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3359: Fix Version/s: 5.0 Affects Version/s: 5.0 NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value - Key: MAGNOLIA-3359 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3359 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x, 5.0 Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 4.3.x, 4.4.x, 5.0 Attachments: magnolia-core.patch, Screen shot 2010-11-03 at 4.15.43 PM.png The value of the renamed node is not the value of the old node, but the path to the passed NodeData object (see print screen). I've written test cases and a solution in the Ops class and attached it as a patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLRES-28) Counts for all modules: getRepository() in module class should be static for use in update tasks.
Counts for all modules: getRepository() in module class should be static for use in update tasks. - Key: MGNLRES-28 URL: http://jira.magnolia-cms.com/browse/MGNLRES-28 Project: Magnolia Resources Module Issue Type: Improvement Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Teresa Miyar Priority: Minor On state of update, the module classes are not instantiated yet. So ModuleClass.getInstance().getRepository() can't be called. Should be possible to use the repo name dynamically in the update tasks too, and not hard coded: ModuleClass.getRepository() This counts for many modules, which provide the name of their repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLRES-28) Counts for all modules: getRepository() in module class should be static for use in update tasks.
[ http://jira.magnolia-cms.com/browse/MGNLRES-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLRES-28: - Assignee: Ondřej Chytil (was: Teresa Miyar) Counts for all modules: getRepository() in module class should be static for use in update tasks. - Key: MGNLRES-28 URL: http://jira.magnolia-cms.com/browse/MGNLRES-28 Project: Magnolia Resources Module Issue Type: Improvement Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Ondřej Chytil Priority: Minor On state of update, the module classes are not instantiated yet. So ModuleClass.getInstance().getRepository() can't be called. Should be possible to use the repo name dynamically in the update tasks too, and not hard coded: ModuleClass.getRepository() This counts for many modules, which provide the name of their repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3366) CreateNodePathTask: ItemType should be defineable
CreateNodePathTask: ItemType should be defineable -- Key: MAGNOLIA-3366 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3366 Project: Magnolia Issue Type: Improvement Components: updatemechanism Affects Versions: 4.4.x Reporter: Christian Ringele Assignee: Boris Kraft Priority: Minor Fix For: 4.4.x, 5.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3366) CreateNodePathTask: ItemType should be defineable
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3366: Assignee: Christian Ringele (was: Boris Kraft) Fix Version/s: 4.3.x Affects Version/s: 4.3.8 5.0 CreateNodePathTask: ItemType should be defineable -- Key: MAGNOLIA-3366 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3366 Project: Magnolia Issue Type: Improvement Components: updatemechanism Affects Versions: 4.3.8, 4.4.x, 5.0 Reporter: Christian Ringele Assignee: Christian Ringele Priority: Minor Fix For: 4.3.x, 4.4.x, 5.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3375) VirtualURIFilter: permanent redirect adds always the port to the url - port 80 is displayed on safari
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3375: Attachment: magnolia-core.patch VirtualURIFilter: permanent redirect adds always the port to the url - port 80 is displayed on safari -- Key: MAGNOLIA-3375 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3375 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x, 5.0 Reporter: Christian Ringele Assignee: Christian Ringele Fix For: 4.3.x, 4.4.x, 5.0 Attachments: magnolia-core.patch, Screen shot 2010-11-09 at 10.22.24 AM.png, Screen shot 2010-11-09 at 10.22.31 AM.png, Screen shot 2010-11-09 at 10.22.38 AM.png The permanent redirect adds always the port to the response if its port 80 (standard http port), firefox and IE hides the port in the URL. On Safari it shows up - port 80 appears after a permanent redirect (printscreen '/homee/' is removed by perms-redirect). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3375) VirtualURIFilter: permanent redirect adds always the port to the url - port 80 is displayed on safari
VirtualURIFilter: permanent redirect adds always the port to the url - port 80 is displayed on safari -- Key: MAGNOLIA-3375 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3375 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x, 5.0 Reporter: Christian Ringele Assignee: Christian Ringele Fix For: 4.3.x, 4.4.x, 5.0 Attachments: magnolia-core.patch, Screen shot 2010-11-09 at 10.22.24 AM.png, Screen shot 2010-11-09 at 10.22.31 AM.png, Screen shot 2010-11-09 at 10.22.38 AM.png The permanent redirect adds always the port to the response if its port 80 (standard http port), firefox and IE hides the port in the URL. On Safari it shows up - port 80 appears after a permanent redirect (printscreen '/homee/' is removed by perms-redirect). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3375) VirtualURIFilter: permanent redirect adds always the port to the url - port 80 is displayed on safari
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3375: Description: The permanent redirect adds always the port to the response if its port 80 (standard http port), firefox and IE hides the port in the URL. On Safari it shows up - port 80 appears after a permanent redirect (printscreen '/home/' is removed by perms-redirect). was: The permanent redirect adds always the port to the response if its port 80 (standard http port), firefox and IE hides the port in the URL. On Safari it shows up - port 80 appears after a permanent redirect (printscreen '/homee/' is removed by perms-redirect). VirtualURIFilter: permanent redirect adds always the port to the url - port 80 is displayed on safari -- Key: MAGNOLIA-3375 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3375 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x, 5.0 Reporter: Christian Ringele Assignee: Christian Ringele Fix For: 4.3.x, 4.4.x, 5.0 Attachments: magnolia-core.patch, Screen shot 2010-11-09 at 10.22.24 AM.png, Screen shot 2010-11-09 at 10.22.31 AM.png, Screen shot 2010-11-09 at 10.22.38 AM.png The permanent redirect adds always the port to the response if its port 80 (standard http port), firefox and IE hides the port in the URL. On Safari it shows up - port 80 appears after a permanent redirect (printscreen '/home/' is removed by perms-redirect). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3375) VirtualURIFilter: permanent redirect adds always the port to the url - port 80 is displayed on safari
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3375: Attachment: (was: magnolia-core.patch) VirtualURIFilter: permanent redirect adds always the port to the url - port 80 is displayed on safari -- Key: MAGNOLIA-3375 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3375 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x, 5.0 Reporter: Christian Ringele Assignee: Christian Ringele Fix For: 4.3.x, 4.4.x, 5.0 Attachments: magnolia-core.patch, Screen shot 2010-11-09 at 10.22.24 AM.png, Screen shot 2010-11-09 at 10.22.31 AM.png, Screen shot 2010-11-09 at 10.22.38 AM.png The permanent redirect adds always the port to the response if its port 80 (standard http port), firefox and IE hides the port in the URL. On Safari it shows up - port 80 appears after a permanent redirect (printscreen '/home/' is removed by perms-redirect). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3375) VirtualURIFilter: permanent redirect adds always the port to the url - port 80 is displayed on safari
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3375: Attachment: magnolia-core.patch Better patch, on port 80 443 is the schema checked too. VirtualURIFilter: permanent redirect adds always the port to the url - port 80 is displayed on safari -- Key: MAGNOLIA-3375 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3375 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.4.x, 5.0 Reporter: Christian Ringele Assignee: Christian Ringele Fix For: 4.3.x, 4.4.x, 5.0 Attachments: magnolia-core.patch, Screen shot 2010-11-09 at 10.22.24 AM.png, Screen shot 2010-11-09 at 10.22.31 AM.png, Screen shot 2010-11-09 at 10.22.38 AM.png The permanent redirect adds always the port to the response if its port 80 (standard http port), firefox and IE hides the port in the URL. On Safari it shows up - port 80 appears after a permanent redirect (printscreen '/home/' is removed by perms-redirect). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLRES-29) ResourceBackupTask: Task for backup a resource
ResourceBackupTask: Task for backup a resource -- Key: MGNLRES-29 URL: http://jira.magnolia-cms.com/browse/MGNLRES-29 Project: Magnolia Resources Module Issue Type: New Feature Affects Versions: 1.3.1 Reporter: Christian Ringele Assignee: Teresa Miyar Fix For: 1.x Will mainly be used for STK resource updates. Without possibility of backing up a resource updating JSs is 'dangerous', could overwrite customers resources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-709) Update and install mechanism for javascrips for 1.4 (refactoring of old components)
Update and install mechanism for javascrips for 1.4 (refactoring of old components) --- Key: MGNLSTK-709 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-709 Project: Magnolia Standard Templating Kit Issue Type: Improvement Affects Versions: 1.4 Reporter: Christian Ringele Assignee: Christian Ringele Fix For: 1.4 In the past the class InstallJavascriptsTask was used for installing all JS. In 1.2 it was 'miss'used to update them too. The drawback of this was, that possible changes within the JSs would just be overwritten. On the other hand subclassing this class for all new STK version lead to impossibility to see the deltas in between versions. New mechanism: JavascriptsVersionsMap - hold now all the scripts-versions (not InstallJavascriptsTask anymore) for all version ever. InstallJavascriptsTask - only used for installs and not delta updates. UpdateJavascriptsTask - used for updating all JSs in between two versions. (backups and removes old scripts) UpdateSingleJavascriptTask - used for updating a single JS or installing a new one for delta update tasks. (backups and removes old script) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-715) Glossary: Glossary letter pages do not show all terms anymore
Glossary: Glossary letter pages do not show all terms anymore - Key: MGNLSTK-715 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-715 Project: Magnolia Standard Templating Kit Issue Type: Bug Affects Versions: 1.3.5 Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 1.3.x, 1.4 Attachments: Screen shot 2010-11-29 at 3.54.14 PM.png When having more them 5 (or configured value) terms per letter in the glossary, the glossary letter page should show all terms. Right now it shows the 'read all terms of letter 'd'' on the letter page too, instead of showing all. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3429) DialogFile should eb repository aware: Using LinkUtil (makes DataFileControl obsolete)
DialogFile should eb repository aware: Using LinkUtil (makes DataFileControl obsolete) -- Key: MAGNOLIA-3429 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3429 Project: Magnolia Issue Type: Improvement Components: gui Affects Versions: 4.3.8 Reporter: Christian Ringele Assignee: Boris Kraft Fix For: 4.3.x, 4.4 Attachments: magnolia-module-data.patch The control file can be used in a context of data module itself or the DAM control again in the data module. Because the control does not resolve the link by the repository it is stored in, the preview is not working when using within the data repo and not within website. There fore the DataFileControl was created. using the LinkUtil for creating the link makes that obsolete, the repo is taken into account (see patch) Code has to be checked for production quality, exceptions are not handled yet (TODO's in the code). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
