[magnolia-dev] [JIRA] Created: (MAGNOLIA-3719) Provide advanced editing possibilities for paragraphs in the edit view
Provide advanced editing possibilities for paragraphs in the edit view -- Key: MAGNOLIA-3719 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3719 Project: Magnolia Issue Type: New Feature Components: gui Affects Versions: 4.4.4 Reporter: Maximilian Störzer Currently a user can add new paragraphs only at the end of a container. The only options for existing paragraphs are edit, move or delete. It would be nice if our authous had the possibility to 1) add a new paragraph anywhere in the page 2) copy paragraphs within a page 3) move paragraphs to any matching container (not only within a given container) These features can speed up page creation considerably. -- 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-3720) Tree Views close when changing workspace / save tree state / provide 'bookmarks'
Tree Views close when changing workspace / save tree state / provide 'bookmarks' Key: MAGNOLIA-3720 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3720 Project: Magnolia Issue Type: New Feature Components: admininterface Reporter: Maximilian Störzer Assignee: Philipp Bärfuss Currently in admin central expanded trees close each time the workspace is changes. This is tedious when working with dms and website in parallel. We suggest that a) trees save their last state and / or b) admin central provides a way to 'bookmark' certain folders in the tree view which are quickly accessible and open the tree at the respective position when used. -- 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: (MGNLRSSAGG-40) Support for RSS enclosures
[ http://jira.magnolia-cms.com/browse/MGNLRSSAGG-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lutz Hühnken updated MGNLRSSAGG-40: --- Affects Version/s: 1.2.1 1.2 1.1.3 1.1.2 Updated the affected versions to reflect the fact that this still applies to the current version of rss aggregator. Support for RSS enclosures -- Key: MGNLRSSAGG-40 URL: http://jira.magnolia-cms.com/browse/MGNLRSSAGG-40 Project: Magnolia RSS Aggregator Module Issue Type: Improvement Affects Versions: 1.1.1, 1.1.2, 1.1.3, 1.2, 1.2.1 Reporter: Lutz Hühnken Assignee: Jan Haderka Priority: Major Fix For: 1.x Attachments: enclosures.patch RSS enclosures are a way of attaching multimedia content to RSS feeds by providing the URL of a file associated with an entry, such as an MP3 file to a music recommendation or a photo to a diary entry. (See http://en.wikipedia.org/wiki/RSS_enclosure;). The mapping from SyndEntry to content node seems to be done in info.magnolia.module.rssaggregator.importhandler.RSSFeedImportHandler.createFeedChannelEntryNode(SyndEntry, String, Content) The method does not store any enclosures in the node. I suggest to extend it to store enclosures as well. -- 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: (MGNLFORM-88) Summary template to display submitted fields
[ http://jira.magnolia-cms.com/browse/MGNLFORM-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teresa Miyar updated MGNLFORM-88: - Description: We will provide a new paragraph that will present a list of the parameters sent in the form, the paragraph is a new additional form step. Summary template to display submitted fields Key: MGNLFORM-88 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-88 Project: Magnolia Form Module Issue Type: Improvement Affects Versions: 1.2.2 Reporter: Teresa Miyar Assignee: Teresa Miyar Fix For: 1.3 We will provide a new paragraph that will present a list of the parameters sent in the form, the paragraph is a new additional form step. -- 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: (DOCU-160) Paragraph properties
Paragraph properties Key: DOCU-160 URL: http://jira.magnolia-cms.com/browse/DOCU-160 Project: Documentation Issue Type: Task Security Level: Public Components: content Reporter: Antti Hietala Assignee: Ruth Stocks Document common paragraph properties in the [Paragraph reference|http://documentation.magnolia-cms.com/reference/paragraph.html]. Take content from the [Paragraphs wiki page|http://wiki.magnolia-cms.com/display/DOCU/Paragraphs] and make a table similar to how we have [common dialog properties|http://documentation.magnolia-cms.com/reference/dialogs.html]. Check the table and make sure all common properties are there and are correct. Then delete the wiki page with a note that official docs are 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-3721) Dialog multiselect does not escape single quotes
Dialog multiselect does not escape single quotes
Key: MAGNOLIA-3721
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3721
Project: Magnolia
Issue Type: Bug
Components: gui
Affects Versions: 4.4.3
Reporter: Vincent Gombert
Using dialog multiselect to manage a list of labels (no choose button) will
fail if a label contains a single quote (') as it is not escaped in JSON string.
Fixing this bug seems simple : just escape single quotes in method getJSON() of
class DialogMultiSelect
Line 199: value = value.replaceAll(\\', \\');
--
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-3715) Magnolia Author: The generic icon 'general.gif' is currently missing
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph updated MAGNOLIA-3715: - Component/s: admininterface Magnolia Author: The generic icon 'general.gif' is currently missing Key: MAGNOLIA-3715 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3715 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.4.4 Reporter: Rory Gibson Priority: Major Fix For: 4.4.x Magnolia Author: The generic icon 'general.gif' is currently missing - this icon should be displayed when an unknown document file type is uploaded into the 'Documents' section. An example of this is .dwg file. -- 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-3721) Dialog multiselect does not escape single quotes
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Gombert updated MAGNOLIA-3721:
--
Description:
Using dialog multiselect to manage a list of labels (no choose button) will
fail if a label contains a single quote (') as it is not escaped in JSON string.
Fixing this bug seems simple : just escape single quotes in method getJSON() of
class DialogMultiSelect
Line 199: {value = value.replaceAll(\\', \\');}
was:
Using dialog multiselect to manage a list of labels (no choose button) will
fail if a label contains a single quote (') as it is not escaped in JSON string.
Fixing this bug seems simple : just escape single quotes in method getJSON() of
class DialogMultiSelect
Line 199: value = value.replaceAll(\\', \\');
Dialog multiselect does not escape single quotes
Key: MAGNOLIA-3721
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3721
Project: Magnolia
Issue Type: Bug
Components: gui
Affects Versions: 4.4.3
Reporter: Vincent Gombert
Using dialog multiselect to manage a list of labels (no choose button) will
fail if a label contains a single quote (') as it is not escaped in JSON
string.
Fixing this bug seems simple : just escape single quotes in method getJSON()
of class DialogMultiSelect
Line 199: {value = value.replaceAll(\\', \\');}
--
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-3721) Dialog multiselect does not escape single quotes
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Gombert updated MAGNOLIA-3721:
--
Description:
Using dialog multiselect to manage a list of labels (no choose button) will
fail if a label contains a single quote (') as it is not escaped in JSON string.
Fixing this bug seems simple : just escape single quotes in method getJSON() of
class DialogMultiSelect
Line 199: {noformat}value = value.replaceAll(\\', \\');{noformat}
was:
Using dialog multiselect to manage a list of labels (no choose button) will
fail if a label contains a single quote (') as it is not escaped in JSON string.
Fixing this bug seems simple : just escape single quotes in method getJSON() of
class DialogMultiSelect
Line 199: {value = value.replaceAll(\\', \\');}
Dialog multiselect does not escape single quotes
Key: MAGNOLIA-3721
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3721
Project: Magnolia
Issue Type: Bug
Components: gui
Affects Versions: 4.4.3
Reporter: Vincent Gombert
Using dialog multiselect to manage a list of labels (no choose button) will
fail if a label contains a single quote (') as it is not escaped in JSON
string.
Fixing this bug seems simple : just escape single quotes in method getJSON()
of class DialogMultiSelect
Line 199: {noformat}value = value.replaceAll(\\', \\');{noformat}
--
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-120) Support nested messages
[ http://jira.magnolia-cms.com/browse/MGNLFORUM-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph updated MGNLFORUM-120: - Fix Version/s: (was: 1.2.2) Support nested messages --- Key: MGNLFORUM-120 URL: http://jira.magnolia-cms.com/browse/MGNLFORUM-120 Project: Magnolia Forum Module Issue Type: New Feature Reporter: Grégory Joseph Assignee: Grégory Joseph Priority: Major Fix For: 1.3, 2.0 While I have never been (and still am not) convinced that threaded discussion work for *forum* based discussions, it seems a little more relevant for commenting. We could have this as an optional behavior per-forum. -- 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-120) Support nested messages
[ http://jira.magnolia-cms.com/browse/MGNLFORUM-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph updated MGNLFORUM-120: - Description: Having threaded/nested messages can in some cases be desired. This could be an optional per-forum behavior. It should not impact the way messages are rendered - but info.magnolia.module.forum.ForumManager#getMessages or the rendering model might need to be adapted to get an appropriate sorting. The default behavior does not change: messages are retrieved sorted by date. If messages need to be *rendered* in a threaded fashion, then templates will need to be adapted to reflect that, for example by looking at the message's depth. (see MGNLCMNT-44 for example) was:While I have never been (and still am not) convinced that threaded discussion work for *forum* based discussions, it seems a little more relevant for commenting. We could have this as an optional behavior per-forum. Support nested messages --- Key: MGNLFORUM-120 URL: http://jira.magnolia-cms.com/browse/MGNLFORUM-120 Project: Magnolia Forum Module Issue Type: New Feature Reporter: Grégory Joseph Assignee: Grégory Joseph Priority: Major Fix For: 1.3, 2.0 Having threaded/nested messages can in some cases be desired. This could be an optional per-forum behavior. It should not impact the way messages are rendered - but info.magnolia.module.forum.ForumManager#getMessages or the rendering model might need to be adapted to get an appropriate sorting. The default behavior does not change: messages are retrieved sorted by date. If messages need to be *rendered* in a threaded fashion, then templates will need to be adapted to reflect that, for example by looking at the message's depth. (see MGNLCMNT-44 for example) -- 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: (MGNLFORUM-101) Posts shouldn't have a title
[ http://jira.magnolia-cms.com/browse/MGNLFORUM-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph reopened MGNLFORUM-101: -- Assignee: Grégory Joseph (was: Fabrizio Giustina) Actually we shouldn't remove it. It's probably more relevant for commenting, which the forum module can also be used for. We could make it optional, or simple template-dependent. Posts shouldn't have a title Key: MGNLFORUM-101 URL: http://jira.magnolia-cms.com/browse/MGNLFORUM-101 Project: Magnolia Forum Module Issue Type: Improvement Reporter: Fabrizio Giustina Assignee: Grégory Joseph Priority: Major Fix For: 2.0 In every forum software I ever tried posts doesn't have a title, only thread/topics have one. Having a title is pretty confusing, we should remove from the new post paragraph (it's already not-mandatory) -- 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: (MGNLFORUM-152) Forum page templates should use the forum/thread title in page title, breadcrumbs and other meta page info
Forum page templates should use the forum/thread title in page title,
breadcrumbs and other meta page info
Key: MGNLFORUM-152
URL: http://jira.magnolia-cms.com/browse/MGNLFORUM-152
Project: Magnolia Forum Module
Issue Type: Improvement
Security Level: Public
Components: templates
Reporter: Grégory Joseph
Assignee: Grégory Joseph
Fix For: 2.0
We currently use a single page to display threads or forums; they are dynamic.
Since all the logic is contained in a paragraph, the page currently can't
have relevant breadcrumbs. Example: current breadcrumbs are
{{Magnolia Community Forums Thread list Thread}}, and the page title is
something along the lines of {{Magnolia Community Forums - Thread}}, which is
really not that useful. It should be something along the lines of
{{Magnolia Community Forums Help How to do this or that}} and {{Magnolia
Community Forums - How to do this or that}}, respectively. *
Other dynamic pages such as events have the same problem.
One way of doing this would be:
# customize the *page* template to override the breadcrumbs and page title etc.
Breadcrumbs should be a breeze, since they're a well extracted include in the
stk templates. Page title might involve more copy and paste.
# and/or : all such page-level meta information should be provided via the
page model. This would allow simply overriding the page model to provide the
forum-specifics for these page (i.e override {{getBreadCrumbsProvider()}} and
{{getPageTitle()}} methods, for instance)
As far as the forum is concerned, this shouldn't cause much of a performance
overhead, since we retrieve the content by uuid, and we assume the repository
provided will keep that node warmly in its cache. It might not be that simple
for other use cases, so I'm not sure how much this can be generalized. Option
#2 is still probably a valid approach to be moved to STK anyway.
\* (and yes, those breadcrumbs are there on forum.magnolia-cms.com, only
because we've hacked them in the *paragraph* 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-3722) Tomcat bundle, setenv.sh: [ -a file ] should be replaced by (equivalent and more portable) [ -e file ]
Tomcat bundle, setenv.sh: [ -a file ] should be replaced by (equivalent and more portable) [ -e file ] -- Key: MAGNOLIA-3722 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3722 Project: Magnolia Issue Type: Bug Affects Versions: 4.4.4 Reporter: Felix Rabe Attachments: setenv-patch.txt The [ -a file ] version breaks e.g. on Ubuntu, where '#!/bin/sh' scripts are executed by Dash which doesn't know [ -a file ]. -- 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: (MGNLDMS-211) MimeMappings config should include mappings for .m4a, .m4v, and .srt to aid with serving audio and video assets
MimeMappings config should include mappings for .m4a, .m4v, and .srt to aid
with serving audio and video assets
---
Key: MGNLDMS-211
URL: http://jira.magnolia-cms.com/browse/MGNLDMS-211
Project: Magnolia DMS Module
Issue Type: Bug
Affects Versions: 1.5.2
Reporter: Matt Dertinger
Assignee: Philipp Bärfuss
Attachments:
config.modules.dms.config.contentDisposition.contentType.rejected.xml,
config.server.MIMEMapping.m4a.xml, config.server.MIMEMapping.m4v.xml,
config.server.MIMEMapping.srt.xml
Hi,
Currently there are no mime mappings for .m4a, m4v, and .srt files. Config
files for these are attached. Additionally, the {{Content-Distribution}}
response header may cause issues with some video streaming providers, such as
pseudostreaming. I've attached a xml export of the {{rejected}} content node
that adds video/mp4 to the list of files not to apply the
{{Content-Distribution}} header to.
Please let me know if you have any questions.
Thanks,
Matt
--
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: (MGNLDMS-211) MimeMappings config should include mappings for .m4a, .m4v, and .srt to aid with serving audio and video assets
[
http://jira.magnolia-cms.com/browse/MGNLDMS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Dertinger updated MGNLDMS-211:
---
Attachment: config.server.MIMEMapping.srt.xml
MimeMappings config should include mappings for .m4a, .m4v, and .srt to aid
with serving audio and video assets
---
Key: MGNLDMS-211
URL: http://jira.magnolia-cms.com/browse/MGNLDMS-211
Project: Magnolia DMS Module
Issue Type: Bug
Affects Versions: 1.5.2
Reporter: Matt Dertinger
Assignee: Philipp Bärfuss
Attachments:
config.modules.dms.config.contentDisposition.contentType.rejected.xml,
config.server.MIMEMapping.m4a.xml, config.server.MIMEMapping.m4v.xml,
config.server.MIMEMapping.srt.xml
Hi,
Currently there are no mime mappings for .m4a, m4v, and .srt files. Config
files for these are attached. Additionally, the {{Content-Distribution}}
response header may cause issues with some video streaming providers, such as
pseudostreaming. I've attached a xml export of the {{rejected}} content node
that adds video/mp4 to the list of files not to apply the
{{Content-Distribution}} header to.
Please let me know if you have any questions.
Thanks,
Matt
--
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
