[magnolia-dev] [JIRA] (DOCU-454) Updates to Magnolia 4.5.10 release notes
Gavan Stockdale updated DOCU-454 Updates to Magnolia 4.5.10 release notes Change By: Gavan Stockdale (06/Aug/13 7:47 AM) Summary: Updates to Magnolia 4.5.10 release notes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5226) Observation Module 1.3.1: Update Content Node do automatic activate
Robert Deckel created MAGNOLIA-5226 Observation Module 1.3.1: Update Content Node do automatic activate Issue Type: Bug Assignee: Unassigned Attachments: activate-Daily-Reports.png Created: 06/Aug/13 12:15 AM Description: Within the DMS, we have a file that will be update on a daily basis, we would like to use the Observation module to automatically activate the file when it changes. Is this possible? I have attached a screen shot of our configured listener. As you can see, we do not have an "eventType" configured, so all eventTypes should trigger this listener to fire. Steps to reproduce: 1) Add new file to DMS, file is automatically activated to public instance. 2) "Edit document", remove file, add new file, save 3) We want the new file to be automatically activated to public. Thanks for any help you can provide. Bob Environment: Ubuntu 12.04 Project: Magnolia Priority: Neutral Reporter: Robert Deckel Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-3545) Enable usage of Maven's scope:import for our webapps and bundles
Grégory Joseph updated MAGNOLIA-3545 Enable usage of Maven's scope:import for our webapps and bundles Change By: Grégory Joseph (05/Aug/13 8:09 PM) Release notes required: Yes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-3979) Add explicit dependency to Tika for full text parsers
Grégory Joseph updated MAGNOLIA-3979 Add explicit dependency to Tika for full text parsers Change By: Grégory Joseph (05/Aug/13 8:07 PM) Summary: Add explicit dependency to Tika for full text parsers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5207) Enable usage of Maven's scope:import for magnolia-project
Grégory Joseph updated MAGNOLIA-5207 Enable usage of Maven's scope:import for magnolia-project Change By: Grégory Joseph (05/Aug/13 8:09 PM) Release notes required: Yes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5212) Upgrade Tika parsers libraries to 1.4
Grégory Joseph updated MAGNOLIA-5212 Upgrade Tika parsers libraries to 1.4 Change By: Grégory Joseph (05/Aug/13 7:38 PM) Summary: Upgrade Tika parsers libraries to 1.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5212) Upgrade Tika parsers libraries
Grégory Joseph
updated MAGNOLIA-5212
Upgrade Tika parsers libraries
Change By:
Grégory Joseph
(05/Aug/13 6:52 PM)
Description:
With MAGNOLIA-3979, we added an explicit dependency to {{tika-parsers}} since they're not shipped with Jackrabbit (dependency is set to scope:test, despite [JCR-2885|https://issues.apache.org/jira/browse/JCR-2885]). With MAGNOLIA-3975, MAGNOLIA-4846, MAGNOLIA-5034 and MAGNOLIA-568, we upgraded to JackRabbit 2.6.2 progressively, but we never updated the dependency to Tika, which is now at 1.3With MAGNOLIA-3545, we starting enabling the use of {{scope:import}} and with MAGNOLIA-5207 we're also
making sure one can use {{
scope:import
}} on {{
magnolia-project
it
}}
in the webapps. This means we should be able to remove the Tika dependency version specification from the webapps and import that from the main project.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5225) Allow setting Vaadin production mode via magnolia.properties
Grégory Joseph created MAGNOLIA-5225 Allow setting Vaadin production mode via magnolia.properties Issue Type: Improvement Assignee: Unassigned Created: 05/Aug/13 6:23 PM Description: We should be able to switch the productionMode flag of Vaadin based on the value of our magnolia.develop property rather than have the two independent mechanism (web.xml for Vaadin, magnolia.properties for everything else) It looks like this should be doable by override com.vaadin.server.VaadinServlet#createDeploymentConfiguration in AdmincentralVaadinServlet and perhaps have it use another implementation of com.vaadin.server.DeploymentConfiguration. This sounds easy - but of course needs to be tested. Ideally, this could be implemented using IoC if MAGNOLIA-4396 was fixed. Fix Versions: 5.1 Project: Magnolia Priority: Neutral Reporter: Grégory Joseph This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5224) Add support for queries using joins with selectors and use of RowIterators
Jan Haderka created MAGNOLIA-5224 Add support for queries using joins with selectors and use of RowIterators Issue Type: Bug Affects Versions: 4.5 Assignee: Unassigned Attachments: NodeUtil.patch Components: core Created: 05/Aug/13 5:18 PM Description: Currently NodeUtils do not provide any support for queries returning rows rather then nodes and conversion of their search results to more widely used node iterators. Attached patch adds support for iterating over row iterators and their on the fly wrapping into node iterators. Fix Versions: 4.5.11, 5.0.2 Project: Magnolia Priority: Neutral Reporter: Jan Haderka Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5223) Provide domain name based voter out of the box
Jan Haderka updated MAGNOLIA-5223 Provide domain name based voter out of the box And add previously forgotten attachment. Change By: Jan Haderka (05/Aug/13 5:19 PM) Attachment: DomainNameRegexVoter.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5223) Provide domain name based voter out of the box
Jan Haderka created MAGNOLIA-5223 Provide domain name based voter out of the box Issue Type: Bug Assignee: Unassigned Created: 05/Aug/13 5:09 PM Description: In many cases filters need to behave differently or be excluded based on domain (and therefore site) used to access the repo. Attached voter reacting based on configured domain names (regex based). Fix Versions: 4.5.11, 5.0.2 Project: Magnolia Priority: Neutral Reporter: Jan Haderka Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (DOCU-454) Magnolia 4.5.10 release notes
Gavan Stockdale reopened DOCU-454 Magnolia 4.5.10 release notes Change By: Gavan Stockdale (05/Aug/13 4:30 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (DOCU-454) Mistakes in Magnolia 4.5.10 release notes
Nils Breunese updated DOCU-454 Mistakes in Magnolia 4.5.10 release notes Change By: Nils Breunese (05/Aug/13 4:22 PM) Summary: Mistakes in Magnolia 4.5.10 release notes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (DOCU-454) Magnolia 4.5.10 release notes
Gavan Stockdale updated DOCU-454 Magnolia 4.5.10 release notes Change By: Gavan Stockdale (05/Aug/13 4:27 PM) Summary: Mistakes in Magnolia 4.5.10 release notes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLFORUM-182) Mismatch in name of property between bootsrapped and updated configuration
Robert Šiška
updated MGNLFORUM-182
Mismatch in name of property between bootsrapped and updated configuration
Change By:
Robert Šiška
(05/Aug/13 3:58 PM)
Description:
The control {{checkboxSwitch}} of forumEdit dialog is bootstrapped with property {{
select
selected
}} while update task names the property {{checked}}.Should be {{
select
selected
}}.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (DOCU-454) Magnolia 4.5.10 release notes
Jan Haderka updated DOCU-454 Magnolia 4.5.10 release notes Change By: Jan Haderka (05/Aug/13 3:54 PM) Priority: Neutral Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLFORUM-182) Mismatch in name of property between bootsrapped and updated configuration
Robert Šiška updated MGNLFORUM-182 Mismatch in name of property between bootsrapped and updated configuration Change By: Robert Šiška (05/Aug/13 3:58 PM) Assignee: Grégory Joseph Robert Šiška Fix Version/s: 1.3.4 Fix Version/s: 3.0.1 Affects Version/s: 1.3.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (DOCU-454) Magnolia 4.5.10 release notes
Jan Haderka updated DOCU-454 Magnolia 4.5.10 release notes Change By: Jan Haderka (05/Aug/13 3:54 PM) Assignee: Antti Hietala Gavan Stockdale This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLFORUM-182) Mismatch in name of property between bootsrapped and updated configuration
Robert Šiška created MGNLFORUM-182 Mismatch in name of property between bootsrapped and updated configuration Issue Type: Bug Assignee: Grégory Joseph Created: 05/Aug/13 3:49 PM Description: The control checkboxSwitch of forumEdit dialog is bootstrapped with property select while update task names the property checked. Should be select. Project: Magnolia Forum Module Priority: Neutral Reporter: Robert Šiška Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5222) Dialogs are not rendered correctly on screens with high resolution
Jaroslav Simak created MAGNOLIA-5222 Dialogs are not rendered correctly on screens with high resolution Issue Type: Bug Affects Versions: 4.5 Assignee: Unassigned Attachments: dialog.png Created: 05/Aug/13 3:49 PM Description: See screenshot - resolution 2560x1440 Tabs are not actually hidden by display:none .. they are "moved away" from the screen by rule left:-2000px Fix Versions: 4.5.11 Project: Magnolia Priority: Neutral Reporter: Jaroslav Simak Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (DOCU-454) Magnolia 4.5.10 release notes
Nils Breunese created DOCU-454 Magnolia 4.5.10 release notes Issue Type: Bug Assignee: Antti Hietala Created: 05/Aug/13 3:50 PM Description: According to http://wiki.magnolia-cms.com/display/DOCS45/Release+notes+for+Magnolia+4.5.10 Pacakager 4.0.9 was released. This version does not seem to be available in Nexus. The list of new modules also contains two versions of the Form module (1.4.7 and 1.4.8), two versions of the Groovy module (1.2.6 twice), two versions of the Diff module (1.1.5 and 1.2) and two versions of the LDAP module (1.6.1 and 1.6.2). And then below there is another section called 'Updated modules' which contains no modules. This is all a bit confusing. Project: Documentation Priority: Neutral Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5221) App layout: fix appearance of apps
Espen Jervidalo created MAGNOLIA-5221 App layout: fix appearance of apps Issue Type: Bug Affects Versions: 5.0.2, 5.1 Assignee: Unassigned Created: 05/Aug/13 3:29 PM Description: Due to some change the apps are not in correct order anymore. see pages, contacts and asset Fix Versions: 5.0.2, 5.1 Project: Magnolia Priority: Critical Reporter: Espen Jervidalo Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5220) magnolia is not accessible without default site definition
Tomáš Gregovský created MAGNOLIA-5220 magnolia is not accessible without default site definition Issue Type: Bug Affects Versions: 4.5.9 Assignee: Unassigned Created: 05/Aug/13 2:57 PM Description: on 4.5.9 when you move node from /modules/extended-templating-kit/config/sites/default to somewhere else, instance is not accessible any more... log: java.lang.NullPointerException info.magnolia.module.extendedtemplatingkit.filters.MultiSiteFilter.cleanURI(MultiSiteFilter.java:151) info.magnolia.module.extendedtemplatingkit.filters.MultiSiteFilter.doFilter(MultiSiteFilter.java:88) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) info.magnolia.cms.filters.MultiChannelFilter.doFilter(MultiChannelFilter.java:83) info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:61) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) info.magnolia.module.cache.filter.GZipFilter.doFilter(GZipFilter.java:75) info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:61) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:85) info.magnolia.cms.security.auth.login.LoginFilter.doFilter(LoginFilter.java:93) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) info.magnolia.enterprise.registration.RegistrationFilter.doFilter(RegistrationFilter.java:52) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:85) info.magnolia.cms.filters.CosMultipartRequestFilter.doFilter(CosMultipartRequestFilter.java:91) info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:61) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) info.magnolia.module.devicedetection.filter.DeviceDetectionFilter.doFilter(DeviceDetectionFilter.java:73) info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:61) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) info.magnolia.cms.filters.ContentTypeFilter.doFilter(ContentTypeFilter.java:102) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) info.magnolia.cms.filters.ContextFilter.doFilter(ContextFilter.java:131) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) info.magnolia.cms.filters.CompositeFilter.doFilter(CompositeFilter.java:67) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) info.magnolia.cms.filters.SafeDestroyMgnlFilterWrapper.doFilter(SafeDestroyMgnlFilterWrapper.java:108) info.magnolia.cms.filters.MgnlFilterDispatcher.doDispatch(MgnlFilterDispatcher.java:67) info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:108) info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:94) Fix Versions: 4.5.11 Project: Magnolia Priority: Neutral Reporter: Tomáš Gregovský Security Level: Public
[magnolia-dev] [JIRA] (MAGNOLIA-5219) Add support for inclusion/exclusion in VersionRange
Grégory Joseph created MAGNOLIA-5219 Add support for inclusion/exclusion in VersionRange Issue Type: New Feature Assignee: Unassigned Created: 05/Aug/13 2:38 PM Description: The VersionRange class (used among other for module dependencies) currently supports a very simple syntax: * - includes all versions 1.2 - matches only 1.2 exactly 1.2/* - matches all versions including and above 1.2 1.2/1.2.9 - matches all versions including and between 1.2 and 1.2.9 It'd be beneficial to be able to exclude versions in a range - currently, if you want to specify a dependency as "1.* but not 2.0", you can only use 1/1.999, which isn't elegant.. nor safe. We could support the following syntaxes - "math"-style, and Maven style: [1.2,1.2.9] - inward square brackets mean inclusion/exclusion [1.2,1.2.9[ - outward square brackets mean exclusion [1.2,1.2.9) - parenthesis mean exclusion Maven style is described here: http://maven.apache.org/enforcer/enforcer-rules/versionRanges.html http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges I currently don't see a use for supporting multiple sets, although it could be useful to avoid a specific, known-buggy, version. Fix Versions: 5.0.2, 5.1 Project: Magnolia Priority: Neutral Reporter: Grégory Joseph Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5168) MailAttachment uri may be set incorrectly
Zdenek Skodik updated MAGNOLIA-5168 MailAttachment uri may be set incorrectly Change By: Zdenek Skodik (05/Aug/13 2:26 PM) Fix Version/s: 4.5.11 Fix Version/s: 5.0.2 Fix Version/s: 4.4.x Fix Version/s: 4.5.x Fix Version/s: 5.0.x This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLRSSAGG-93) Components feedListParagraph and combinedFeedsParagraph were accidentally removed
Robert Šiška
updated MGNLRSSAGG-93
Components feedListParagraph and combinedFeedsParagraph were accidentally removed
Change By:
Robert Šiška
(05/Aug/13 2:05 PM)
Fix Version/s:
2.0.2
Description:
The bootstrap files of these components were removed in MGNLRSSAGG-74 and then added again to the wrong location.They need to be in mgnl-bootstrap folder to get bootstrapped.(i) Note: bear in mind, that path of the ftl templates changed from {{/info/magnolia/module/rssaggregator/}} to {{/rssaggregator/}}. Update task needs to
be
reflect this change.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5218) Channel detection applies on edit mode making not possible to modify channels anymore if you excluded desktop
Teresa Miyar created MAGNOLIA-5218 Channel detection applies on edit mode making not possible to modify channels anymore if you excluded desktop Issue Type: Bug Affects Versions: 5.0.1 Assignee: Unassigned Components: core Created: 05/Aug/13 12:44 PM Description: Was on page properties dialog, excluded desktop. And my current page is now a 404 error page. Cannot edit page properties anymore. Had to remove the property on jcr browser tool. Project: Magnolia Priority: Major Reporter: Teresa Miyar Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-5217) OptionGroupField saves the data but does not show the saved value when reoppening the dialog
Teresa Miyar created MAGNOLIA-5217 OptionGroupField saves the data but does not show the saved value when reoppening the dialog Issue Type: Bug Affects Versions: 5.0.1 Assignee: Unassigned Components: gui Created: 05/Aug/13 12:07 PM Description: To reproduce, you can use the channels functionality. Open the page properties, select a channel, save. Reopen dialog and the option selected is not displayed. When you look on the jcr browser the values are there, so it seems is able to save but not to read the value Project: Magnolia Priority: Critical Reporter: Teresa Miyar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLWORKFLOW-72) Prevent module from running in ce instance (license check)
Philip Mundt updated MGNLWORKFLOW-72 Prevent module from running in ce instance (license check) Change By: Philip Mundt (05/Aug/13 10:14 AM) Description: Module should require *enterprise* edition. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLWORKFLOW-101) Create WorkItemHandlers where appropriate
Espen Jervidalo updated MGNLWORKFLOW-101 Create WorkItemHandlers where appropriate Change By: Espen Jervidalo (05/Aug/13 9:36 AM) Summary: WorkflowScriptUtil: get rid of it Create WorkItemHandlers where appropriate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLWORKFLOW-70) Add tests for JbpmWorkflowManager
Daniel Lipp updated MGNLWORKFLOW-70 Add tests for JbpmWorkflowManager Change By: Daniel Lipp (05/Aug/13 9:23 AM) Summary: Add missing Unit and Integration tests (including UI) for JbpmWorkflowManager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
