[magnolia-dev] [JIRA] (MGNLUI-3516) DialogMigrationTask does not properly migrate tabs with extends property and some override items

[on behalf of Roman Kovařík]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3516 
 
 
 
  DialogMigrationTask does not properly migrate tabs with extends property and some override items  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 In QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3570) Investigation for MGNLUI-2397 (defaultValues)

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3570 
 
 
 
  Investigation for MGNLUI-2397 (defaultValues)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 5.4.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3542) Temp files are not deleted after use of upload field

[JIRA (on behalf of Milan Divilek)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Milan Divilek reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3542 
 
 
 
  Temp files are not deleted after use of upload field  
 
 
 
 
 
 
 
 
 

Change By:
 
 Milan Divilek 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 In QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3590) Get rid of TODO: Let the customer decide who can archive tasks and don't hardcode it ('superuser' role)!

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3590 
 
 
 
  Get rid of TODO: Let the customer decide who can archive tasks and don't hardcode it ('superuser' role)!  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.2, 5.3.10 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 pulse 
 
 
 

Created:
 

 16/Sep/15 1:11 PM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Tasks which are resolved can only be achieved by users with 'superuser' role. But this does not fit reality in projects... The customer needs to be able to decide, who can archive successful pulse tasks. It is a 'no go' to give somebody complete superuser rights just to be able to archive pulse tasks. 
   

[magnolia-dev] [JIRA] (MGNLUI-3524) IE11: upon manual cropping of an image, its size gets dropped severely

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3524 
 
 
 
  IE11: upon manual cropping of an image, its size gets dropped severely  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 7 End result.png 
 
 
 

Attachment:
 
 1 Image to crop.png 
 
 
 

Attachment:
 
 2 Click on crop.png 
 
 
 

Attachment:
 
 6 Saved edit.png 
 
 
 

Attachment:
 
 4 Choosing excerpt.png 
 
 
 

Attachment:
 
 3 After zoom to fit.png 
 
 
 

Attachment:
 
 5 Cropped image.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLDEMO-101) Images in Demo should be sized to fit the layout

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-101 
 
 
 
  Images in Demo should be sized to fit the layout  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Summary:
 
 Images in  TextImage component  Demo  should be sized  properly  to fit the layout 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-102) Ad-hoc Images in demo should be loaded efficiently

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-102 
 
 
 
  Ad-hoc Images in demo should be loaded efficiently  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 0.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 16/Sep/15 2:01 PM 
 
 
 

Fix Versions:
 

 0.8 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 
By "Ad-hoc" images - I mean images that a user can add anywhere (not those "managed" in specific tour components). When a user places a textimage or teaser - in this responsive layout - ideally the site should not always load the same variation of an image. It should load an image with roughly the size that the element takes on the page. 
This can be achieved using the srcSet attribute of the image tag - as is done for the tour images (see related ticket) But this is configuration intensive - and better suited to situations where we know the actual likely sizes.  
For the ad-hoc images I recommend a lighter approach based on the "lazySizes" _javascript_ library. The key benefit is that no-one has to configure which size of image should be used based on browser-width as one must do with the srcSet attribute. The library uses the actual size of the element on the page - you must only specify the URL's of the images to use at different sizes of 

[magnolia-dev] [JIRA] (MGNLDEMO-101) Images in Demo should be sized to fit the layout

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-101 
 
 
 
  Images in Demo should be sized to fit the layout  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 Currently if you add an image to a "Text and Image" component, or to a teaser component the original image  file  is included , and it totally breaks the layout .A. A rendition should be included rather than the original.B. The image should not expand wider than its container - it should be resized.Notes - CSS: CSS classes should be added so that the images behave as if they have the bootstrap css class "img-responsive". Basically they should have a full width.A way to implement this for the teasers and text-image would be something like the following rules:{code}/* IMAGES-- */.teaser img{max-width:100%;}.text-image-section img{max-width:100%;}.content-image-wrapper{position: relative;}{code}Notes - VariationI recommend adding an image variation to the theme called "large" or "layout-width" with a width of 940px. This would then fill the full width of the bootstrap layout. The textImage & teaser components both use the ImageModel class which will pickup the value of a parameter named "imageVariation" in the template definition.Therefore, a possible path is to create new templateDefintions for the teasers and textImage components in the travel-demo module (which reference the mte script and dialog) and add this parameter to them - and of course update the content bootstraps to use these. :( 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLDEMO-101) Images in Demo should be sized to fit the layout

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-101 
 
 
 
  Images in Demo should be sized to fit the layout  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 Currently if you add an image to a "Text and Image" component,  or to a teaser component  the original image is included.A. A rendition should be included rather than the original.B. The image should not expand wider than its container - it should be resized. Notes - CSS: CSS classes should be added so that the images behave as if they have the bootstrap css class "img-responsive". Basically they should have a full width.A way to implement this for the teasers and text-image would be something like the following rules:{code:css}/* IMAGES-- */.teaser img{max-width:100%;}.text-image-section img{max-width:100%;}.content-image-wrapper{position: relative;}{code}Notes - VariationI recommend adding an image variation to the theme called "large" or "layout-width" with a width of 940px. This would then fill the full width of the bootstrap layout. The textImage & teaser components both use the ImageModel class which will pickup the value of a parameter named "imageVariation" in the template definition.Therefore, a possible path is to create new templateDefintions for the teasers and textImage components in the travel-demo module (which reference the mte script and dialog) and add this parameter to them - and of course update the content bootstraps to use these. :( 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLDEMO-101) Images in Demo should be sized to fit the layout

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-101 
 
 
 
  Images in Demo should be sized to fit the layout  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 Currently if you add an image to a "Text and Image" component, or to a teaser component the original image is included.A. A rendition should be included rather than the original.B. The image should not expand wider than its container - it should be resized.Notes - CSS: CSS classes should be added so that the images behave as if they have the bootstrap css class "img-responsive". Basically they should have a full width.A way to implement this for the teasers and text-image would be something like the following rules:{code :css }/* IMAGES-- */.teaser img{max-width:100%;}.text-image-section img{max-width:100%;}.content-image-wrapper{position: relative;}{code}Notes - VariationI recommend adding an image variation to the theme called "large" or "layout-width" with a width of 940px. This would then fill the full width of the bootstrap layout. The textImage & teaser components both use the ImageModel class which will pickup the value of a parameter named "imageVariation" in the template definition.Therefore, a possible path is to create new templateDefintions for the teasers and textImage components in the travel-demo module (which reference the mte script and dialog) and add this parameter to them - and of course update the content bootstraps to use these. :( 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLDEMO-102) Ad-hoc Images in demo should be loaded efficiently

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-102 
 
 
 
  Ad-hoc Images in demo should be loaded efficiently  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 MGNLDEMO-101 should be considered or completed first.  By "Ad-hoc" images - I mean images that a user can add anywhere (not those "managed" in specific tour components). When a user places a textimage or teaser - in this responsive layout - ideally the site should not always load the same variation of an image. It should load an image with roughly the size that the element takes on the page.This can be achieved using the srcSet attribute of the image tag - as is done for the tour images (see related ticket) But this is configuration intensive - and better suited to situations where we know the actual likely sizes. For the ad-hoc images I recommend a lighter approach based on the "lazySizes" _javascript_ library. The key benefit is that no-one has to configure which size of image should be used based on browser-width as one must do with the srcSet attribute. The library uses the actual size of the element on the page - you must only specify the URL's of the images to use at different sizes of that image.The benefit of "lazySizes" over the popular "Imager.js"  is that it falls back gracefully where no _javascript_ is available.Notes:See working example of proposed implementation on branch MGNLDEMO-102-ex.Create image variations for typical bootstrap widths, 1920, 1366, 960, 480, 320, 240. (variations should not define heights)Add the lazySizes.min.js to the theme.Add the polyfill for srcSet attribute, respimage.min.js to the theme.Create a new ftl include based on mte's image.ftl, maybe called imageResponsive.ftl in travel-demo module. Which contains methods to easily generate the lazySizes syntax (lazyload css class, data-sizes="auto" attribute, data-srcset attribute.Use the 240 variation as the src of the image tag. So this image will be loaded first when the page loads, but then when the image is scrolled into view, then the proper sized image will be loaded and displayed.A possible alternative implementation would be to have no src in the image tag and depend on the _javascript_ working. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
  

[magnolia-dev] [JIRA] (MGNLDEMO-100) Responsive columns component

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-100 
 
 
 
  Responsive columns component  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 Why: A columns component will allow pages of the demo to have unique and customizable layouts. It will allow evaluators to see how they can easily create layouts. It will show evaluators how they can integrate a css layout framework such as Twitter Bootstrap.  This is important in part to demonstrate how to build up rich pages with just a few components. Component name: Column layoutThe component should work similarly to the row component of Tomas' Twitter bootstrap template set on the Forge.The dialog for a row contains a "Layout" selector with the following options:The values of the select should simply be the list of column widths delimited by spaces. ||Label||Value |||2 cols (1:1)|6 6||2 cols (2:1)|8 4||2 cols (1:2)|4 8||2 cols (3:1)|9 3||2 cols (1:3)|3 9||3 cols (1:1:1)|4 4 4||3 cols (2:1:1)|6 3 3||3 cols (1:2:1)|3 6 3||3 cols (1:1:2)|3 3 6||4 cols (1:1:1:1)|3 3 3 3|Based on the selection - between one and four columns are displayed, which are areas where a user can add components. The area should have all MTE components available.Of course the column div for each of the areas must have the appropriate bootstrap css. The four areas should be created only once upon component creation - so that after a user enters components into the areas the user can still change the layout and the components will remain intact.I recommend using the bootstrap "sm" classes for all layouts except those with a col width of 3 where I would use "md" classes.The component html should output a "row" css class at the top level - but not a bootstrap "container" class as it will be used in the context of the demo where container classes are already specified.Dialog Description: Add a column layout to a page.Field Description: Select the number of columns. The ratios indicate the width of the columns relative to one another.Usage in demo:This component should be available in the main area of home and standard pages. (magnolia-travel-demo home.yaml & standard.yaml).Use the Columns Layout component on the "about" page to create a "2 cols (1:1)" layout under the jumbotron.On the left side: The video (see https://jira.magnolia-cms.com/browse/MGNLDEMO-92)On the right side: the "Learn more" and the teasers to the sub pages. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLDEMO-100) Responsive columns component

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-100 
 
 
 
  Responsive columns component  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Labels:
 
 selected-for-backlog 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-101) Images in Demo should be sized to fit the layout

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-101 
 
 
 
  Images in Demo should be sized to fit the layout  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 Currently if you add an image to a "Text and Image" component, or to a teaser component the original image file is included, and it totally breaks the layout.A. A rendition should be included rather than the original.B. The image should not expand wider than its container - it should be resized.Notes - CSS: CSS classes should be added so that the images behave as if they have the bootstrap css class "img-responsive". Basically they should have a full width.A way to implement this for the teasers and text-image would be something like the following rules:{code}/* IMAGES-- */.teaser img{max-width:100%;}.text-image-section img{max-width:100%;}.content-image-wrapper{position: relative;}{code}Notes - VariationI recommend adding an image variation to the theme called "large" or "layout-width" with a width of 940px. This would then fill the full width of the bootstrap layout. The textImage & teaser components both use the ImageModel class which will pickup the value of a parameter named "imageVariation" in the template definition.Therefore, a possible path is to create new templateDefintions for the teasers and textImage components in the travel-demo module (which reference the mte script and dialog) and add this parameter to them - and of course update the content bootstraps to use these. :( Tip: consider performing MGNLDEMO-102 in the same sprint. 102 builds on this ticket, so there's not really wasted work doing them separately - but might be most efficient to do both at the same time. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
   

[magnolia-dev] [JIRA] (MGNLUI-3591) CommandActionTriggerListener sends pulse message with SystemContext's user

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3591 
 
 
 
  CommandActionTriggerListener sends pulse message with SystemContext's user  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.3.11 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 framework 
 
 
 

Created:
 

 16/Sep/15 5:05 PM 
 
 
 

Fix Versions:
 

 5.3.x 
 
 
 

Labels:
 

 async support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Mikaël Geljić 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (MGNLDEMO-103) Demo advanced form including Multi-Step

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-103 
 
 
 
  Demo advanced form including Multi-Step  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Labels:
 
 selected-for-backlog 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-99) Some pages of the MTE demo are not published

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-99 
 
 
 
  Some pages of the MTE demo are not published  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Priority:
 
 Critical Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-103) Demo advanced form including Multi-Step

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-103 
 
 
 
  Demo advanced form including Multi-Step  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 0.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 16/Sep/15 5:45 PM 
 
 
 

Fix Versions:
 

 0.8 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 
Why: Advanced forms are an important part of demoing Magnolia. 
The form should be designed to include all of the out-of-the-box form elements. The form should include three steps. And show off the available validation. 
When a user clicks the Book Tour button on a tour page, the demo should no longer launch the modal popup. It should rather link to a new page (not in the navigation) containing the form. So the form should look something like an order form - collecting customer information etc. 
After the final submission of the form on the third step - the dialog with the "end of the world" message could be displayed - or a page with that message if the implemetation is signicantly easier.