[magnolia-dev] [JIRA] (TASKMGMT-19) TasksManager API improvements
Title: Message Title Aleksandr Pchelintcev updated an issue Task Management / TASKMGMT-19 TasksManager API improvements Change By: Aleksandr Pchelintcev Fix Version/s: 1.1 Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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] (MGNLUI-3383) Add Scheduled tasks to pulse
Title: Message Title Sang Ngo Huu updated an issue Magnolia UI / MGNLUI-3383 Add Scheduled tasks to pulse Change By: Sang Ngo Huu Original Estimate: 0.75d Remaining Estimate: 0.75d Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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] Re: Build tutorial project failed due to not able to fetch magnolia-setproperty-maven-plugin
Try to add following towards end of your pom file. It seems like maven doesn't see magnolia repo. [code] magnolia.public https://nexus.magnolia-cms.com/content/groups/public true [/code] -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=499a6b13-c968-48cd-a610-6df6e3da7831 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] (MGNLUI-3410) Create new icon font with one additional icon
Title: Message Title Andreas Weder updated an issue Magnolia UI / MGNLUI-3410 Create new icon font with one additional icon Change By: Andreas Weder Assignee: Mikaël Geljic Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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] (MGNLUI-3410) Create new icon font with one additional icon
Title: Message Title Andreas Weder created an issue Magnolia UI / MGNLUI-3410 Create new icon font with one additional icon Issue Type: Task Assignee: Unassigned Attachments: MAG_Icons_Version13_150506.zip Components: design Created: 06/May/15 5:07 PM Labels: visual-design Priority: Major Reporter: Andreas Weder Security Level: Public Please create a new version of the icon web font using the archive attached to this issue. We're actively using our icon web font for building the new company website. For this site, we've designed and added one additional icon. Icon #181 is used to illustrate and highlight a link to another page or element.
[magnolia-dev] [JIRA] (MGNLDEMO-20) Improve search by using autoGenerated content (searchResult component) and by making search result page configurable
Title: Message Title Philip Mundt updated an issue Magnolia Demo Projects / MGNLDEMO-20 Improve search by using autoGenerated content (searchResult component) and by making search result page configurable Change By: Philip Mundt Reporter: Federico Grilli Philip Mundt Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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] (MGNLDEMO-26) Template definition "main" should be called "home"
Title: Message Title Philip Mundt created an issue Magnolia Demo Projects / MGNLDEMO-26 Template definition "main" should be called "home" Issue Type: Bug Assignee: Unassigned Components: magnolia-travels Created: 06/May/15 3:30 PM Fix Versions: 1.0 Priority: Neutral Reporter: Philip Mundt Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814)
[magnolia-dev] [JIRA] (MGNLDEMO-25) htmlHeader should be an area to simplify the code of main.ftl
Title: Message Title
Philip Mundt updated an issue
Magnolia Demo Projects / MGNLDEMO-25
htmlHeader should be an area to simplify the code of main.ftl
Change By:
Philip Mundt
Make sure to use {{createAreaNode=false}} and {{type=noComponent}} .
Add Comment
This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814)
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] (MGNLDEMO-25) htmlHeader should be an area to simplify the code of main.ftl
Title: Message Title Philip Mundt created an issue Magnolia Demo Projects / MGNLDEMO-25 htmlHeader should be an area to simplify the code of main.ftl Issue Type: Bug Assignee: Unassigned Components: magnolia-travels Created: 06/May/15 2:52 PM Priority: Neutral Reporter: Philip Mundt Make sure to use createAreaNode=false. Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814)
[magnolia-dev] [JIRA] (MGNLDEMO-24) content area in site definitintion should no be of type=noComponent
Title: Message Title
Philip Mundt updated an issue
Magnolia Demo Projects / MGNLDEMO-24
content area in site definitintion should no be of type=noComponent
Change By:
Philip Mundt
This is confusion. We should rather use {{type=list}} in order to not have to override it in any sub-template .
Add Comment
This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814)
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] (MGNLDEMO-24) content area in site definitintion should no be of type=noComponent
Title: Message Title Philip Mundt updated an issue Magnolia Demo Projects / MGNLDEMO-24 content area in site definitintion should no be of type=noComponent Change By: Philip Mundt Summary: Content content area in site definitintion should no be of type=noComponent Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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] (MGNLDEMO-24) Content in site definitintion should no be of type=noComponent
Title: Message Title Philip Mundt created an issue Magnolia Demo Projects / MGNLDEMO-24 Content in site definitintion should no be of type=noComponent Issue Type: Bug Assignee: Unassigned Components: magnolia-travels Created: 06/May/15 2:24 PM Fix Versions: 1.0 Priority: Neutral Reporter: Philip Mundt This is confusion. We should rather use type=list. Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-23) Dialogs: Don't use extends for no reson (or some might possible future easons)
Title: Message Title Philip Mundt deleted an issue Magnolia Demo Projects / MGNLDEMO-23 Dialogs: Don't use extends for no reson (or some might possible future easons) This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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-300) Overview with scheduled workflow items
Title: Message Title Espen Jervidalo updated an issue Magnolia Workflow Module / MGNLWORKFLOW-300 Overview with scheduled workflow items Change By: Espen Jervidalo Attachment: Screen Shot 2015-05-06 at 14.00.30.png Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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] (PAGES-19) Inconsistent behavior for selecting delete and publish deletion actions
Title: Message Title Trang Truong updated an issue Magnolia pages module / PAGES-19 Inconsistent behavior for selecting delete and publish deletion actions Change By: Trang Truong Fix Version/s: 5.4 Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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] (PAGES-19) Inconsistent behavior for selecting delete and publish deletion actions
Title: Message Title Trang Truong created an issue Magnolia pages module / PAGES-19 Inconsistent behavior for selecting delete and publish deletion actions Issue Type: Bug Assignee: Trang Truong Created: 06/May/15 1:48 PM Labels: pages Priority: Neutral Reporter: Trang Truong Regarding to issue MGNLUI-3307 , we provide ability to publish deletion of multiple selected items. Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-23) Dialogs: Don't use extends for no reson (or some might possible future easons)
Title: Message Title Christian Ringele created an issue Magnolia Demo Projects / MGNLDEMO-23 Dialogs: Don't use extends for no reson (or some might possible future easons) Issue Type: Bug Affects Versions: 1.0 Assignee: Philip Mundt Attachments: Demo_TextImage_DialogExtends.png Components: magnolia-travels Created: 06/May/15 12:13 PM Priority: Major Reporter: Christian Ringele Something that killed STK is the way to complex referencing of configurations via extends. Extends is a really cool feature, if there is a good reason to use it (real need of variations). But until there is a real need of it, using if for future possible extensions is contradicting this: the goal should be that it is straight forward and by this easy to understand for beginners
[magnolia-dev] [JIRA] (MGNLDEMO-22) Freemarker Scripts: Should be simplified and best practices should be used
Title: Message Title
Christian Ringele created an issue
Magnolia Demo Projects / MGNLDEMO-22
Freemarker Scripts: Should be simplified and best practices should be used
Issue Type:
Improvement
Assignee:
Philip Mundt
Components:
magnolia-travels
Created:
06/May/15 11:50 AM
Fix Versions:
1.0
Priority:
Major
Reporter:
Christian Ringele
I see in many scripts parts which are either too complicated or do not use scripting best practices. This should be changes to make the readability and understandability much better.
One example (textImage.ftl): Original
[#assign headingLevel = "h2"]
[#if content.headingLevel?has_content]
[#assign headingLevel = content.headingLevel]
[/#if]
[#if content.headline?has_content]
<${headingLevel}>${content.headline!}
[/#if]
Replacing with (using properly "!"):
[#assign headingLevel = content.headingLevel!"h2"]
[#if content.headline?has_content]
<${headingLevel}>${content.he
[magnolia-dev] [JIRA] (MGNLWORKFLOW-301) Publisher don't get error messages
Title: Message Title Diana Racho created an issue Magnolia Workflow Module / MGNLWORKFLOW-301 Publisher don't get error messages Issue Type: Improvement Affects Versions: 5.4.5, 5.4.3 Assignee: Unassigned Created: 06/May/15 11:37 AM Priority: Neutral Reporter: Diana Racho If activation fails only the superuser gets detailed error message. Publisher only could see in the task that the activation fails, but not what happened (for example: parent node is not activated). Add Comment
[magnolia-dev] [JIRA] (MTE-24) Get rid of area template list.ftl – it is unnecessary as it implements the defaults
Title: Message Title Philip Mundt created an issue Magnolia Templating Essentials / MTE-24 Get rid of area template list.ftl – it is unnecessary as it implements the defaults Issue Type: Bug Assignee: Unassigned Components: ftl-templates, models Created: 06/May/15 11:00 AM Fix Versions: 1.0 Priority: Neutral Reporter: Philip Mundt Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814)
[magnolia-dev] [JIRA] (MTE-20) Don't store html elements in website workspace, use named/speaking headlineLevels instead
Title: Message Title Christian Ringele updated an issue Magnolia Templating Essentials / MTE-20 Don't store html elements in website workspace, use named/speaking headlineLevels instead Change By: Christian Ringele Summary: Don't store html elements in website workspace, use named /speaking headlineLevels instead Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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] (MTE-20) Don't store html elements in website workspace, use named headlineLevels instead
Title: Message Title Christian Ringele updated an issue Magnolia Templating Essentials / MTE-20 Don't store html elements in website workspace, use named headlineLevels instead Change By: Christian Ringele Attachment: Demo_TxtImage_CurrentImpl_HeadinLevels.png Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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:
