[magnolia-dev] [JIRA] (MGNLUI-4188) nodes instead of properties in hiddenApps

[on behalf of Tomáš Gregovský]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomáš Gregovský created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4188  
 
 
  nodes instead of properties in hiddenApps   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 5.5.3  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 11/Apr/17 12:40 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Tomáš Gregovský  
 

  
 
 
 
 

 
 Would be possible to change entries in hiddenApps (/modules/ui-admincentral/config/appLauncherLayout/hiddenApps) from properties to nodes?  Reason: apps entries in groups are already nodes, so to hide them is easiest just to move them to 'hiddenApps' node, but thats not possible because as nodes they doesn't count. So each entry I have to remove from groups and manually recreate as property (even if property name doesn't matter) in hiddenApps  (instead of 1 drag step, I have to do 4 steps for each app I want to hide) Additionally, empty "hiddenApps" should exists by default, same for empty property 'defaultGroup' (or this may be by default 'edit')?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

 

[magnolia-dev] [JIRA] (MGNLUI-4188) improvement of hiddenApps and defaultGroup

[on behalf of Tomáš Gregovský]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomáš Gregovský updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4188  
 
 
  improvement of hiddenApps and defaultGroup   
 

  
 
 
 
 

 
Change By: 
 Tomáš Gregovský  
 
 
Summary: 
 nodes instead improvement  of  properties in  hiddenApps  and defaultGroup  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-105) change option field in dialog

[on behalf of Tomáš Gregovský]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomáš Gregovský created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-105  
 
 
  change option field in dialog   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 14/Feb/17 4:15 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Tomáš Gregovský  
 

  
 
 
 
 

 
 when CLI generates dialog component, last field is option, each option has name and value, but its missing label, which means it's expect i18n and so far render long i18n property name. place change 'name' to 'label' so option field should looks like:  

 

- name: option
  class: info.magnolia.ui.form.field.definition.SelectFieldDefinition
  label: Option
  options:
- label: A
  value: a
- label: B
  value: b
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
   

[magnolia-dev] [JIRA] (MGNLCACHE-156) improve browser in cache tools app

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-156 
 
 
 
  improve browser in cache tools app  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 30/Nov/16 9:53 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
on corporate website (eepro, 5.4.9) we have around 3k entries in browser in cache tools app. With current browser is quite complicated find something there.  
 

Search field will be useful.
 

Also when I change order by 'extension' (for example), its is still first ordered by 'domain' and then by 'extension'. So to delete one entry from everywhere (all publics) is not intuitive at all.
 

some filter options similar to definition app will be useful too. something like I want to display only extension=css, etc...
 
 
Thank you! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
   

[magnolia-dev] [JIRA] (MGNLCACHE-155) cache tools app - error when scrolling through too many files

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-155 
 
 
 
  cache tools app - error when scrolling through too many files  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 magnolia-error.log 
 
 
 

Created:
 

 30/Nov/16 9:46 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
Corporate website - eepro - 5.4.9 
when scrolling in browser in cache tools I got this error:  

 

ERROR  info.magnolia.ui.admincentral.AdmincentralErrorHandler 30.11.2016 09:39:15 -- AdmincentralUI has encountered an unhandled exception.
java.lang.RuntimeException: Unable to get item id for index: 2519 from container using Container.Indexed#getIdByIndex() even though container.size() > endIndex. Returned item id was null. Check your container implementation!
 

 
log file attached. 
 
 
 
 
 
 
 
 
 
 
 
 

 
  

[magnolia-dev] [JIRA] (PAGES-110) copy and paste component doesn't work in personalized component

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-110 
 
 
 
  copy and paste component doesn't work in personalized component  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 22/Nov/16 7:46 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
In a case like: page with section component and 6 other components in section component... When used component personalization for section component and having variants of section. Then when on one of variants copy and paste some of subcomponents, this is placed into original variant, not personalized one. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 

[magnolia-dev] [JIRA] (NOWDEMO-11) Now Sales Demo

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-11 
 
 
 
  Now Sales Demo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 Ideal for marketing campaigns, showing CMS (editors experience - text, image).Showing NOW dev workflow (git pull > edit > push).- responsive modern landing page:- -  bootstrap framework template [x]- -  btk [x]- personalisation:- -  component (country) [x]- -  component (trait from Silverpop?) [ ]- analytics:- -  marketing tags [x]- -  google analytics module [ ]- -  ga module - real stats? [ ]- Silverpop:- -  external form [ ]- -  trait for personalisation? [ ]- comments [ ]- social:- -  twitter [x]- -  facebook? [ ]- content app:- -  content-type module [ ]- -  offices list [ ] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NOWDEMO-11) Now Sales Demo

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-11 
 
 
 
  Now Sales Demo  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 17/Nov/16 4:15 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
Ideal for marketing campaigns, showing CMS (editors experience - text, image). Showing NOW dev workflow (git pull > edit > push). 
 

responsive modern landing page:
 

bootstrap framework template [x]
 

btk [x]
 

personalisation:
 

component (country) [x]
 

component (trait from Silverpop?) [ ]
 

analytics:
 

marketing tags [x]
 

google analytics module [ ]
 

ga module - real 

[magnolia-dev] [JIRA] (MGNLUI-4082) drag & drop can't move on root (pages)

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4082 
 
 
 
  drag & drop can't move on root (pages)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 17/Nov/16 1:23 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Locally same as on demoauthor. In Chrome and also in Safari. 
Want to move page to change their orders on root level of pages. Simply use drag to change order of travel and sportstation but without result. Playing around a bit, I can move into some node (page) and also change order of subpages, but then I am not able to move something from subpages to root. Same problem when using 'move action/dialog'. Same issues seems to be in JCR browser. So once I moved sportstation into travel, I can't get it back to root! 
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4077) Switchable field do not render descriptions, values and other strings for subfields

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4077 
 
 
 
  Switchable field do not render descriptions, values and other strings for subfields  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-4077) Switchable field do not render descriptions, values and other strings for subfields

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4077 
 
 
 
  Switchable field do not render descriptions, values and other strings for subfields  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 switchable.png 
 
 
 

Created:
 

 11/Nov/16 1:47 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Switchable field to switch between link field and static field, eg: 

 

- name: bbLinkOrPupup
  description:
  label: Link Or Popup
  class: info.magnolia.ui.form.field.definition.SwitchableFieldDefinition
  fields:
- name: link
  appName: pages
  label: Link to internal
  description: "Select an internal page"
  required: false
  targetWorkspace: website
  type: String
  class: 

[magnolia-dev] [JIRA] (MGNLUI-4077) Switchable field do not render descriptions, values and other strings for subfields

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský deleted an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4077 
 
 
 
  Switchable field do not render descriptions, values and other strings for subfields  
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NPMCLI-54) fix double slash in resources path in current page ftl prototype

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-54 
 
 
 
  fix double slash in resources path in current page ftl prototype  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 24/Oct/16 8:26 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
fix double slash in resources path in current page ftl prototype, e.g. : $ {ctx.contextPath} 
/.resources//test/webresources/css/bootstrap.css 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  

[magnolia-dev] [JIRA] (NPMCLI-53) improve scripts adding something to existing yaml (adding availability)

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-53 
 
 
 
  improve scripts adding something to existing yaml (adding availability)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 24/Oct/16 8:23 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
If you have customized page definition, e.g added comments, including something, or just using empty lines to make code easy to read. but when creating new component which has parameter for availability which at the end modifies customized page definition, all that fancy stuff (named above) are removed... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 

[magnolia-dev] [JIRA] (NOWDEMO-4) angular gallery component (SPA like)

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-4 
 
 
 
  angular gallery component (SPA like)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Summary:
 
 angular  SPA  gallery  component  (SPA like) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NOWDEMO-4) angular SPA component

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-4 
 
 
 
  angular SPA component  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 - new LM which will provide angular resources (js - will be loaded directly in component  tempalte  template  script) and new component (and decorate  abailability  availability  in btk:components/section). Component should works like SPA, investigate also routing functionality in magnolia.- use case: image gallery (with folder support)- diaglo: to select folder from DAM (nothing selected = use root)- component: use angular to render all items (first level of childs) from selected folder (or root). If item is image, display it as a image (thumbnail). If item is folder, display folder icon and on click this angular app wil swith view into this folder and again list folders and images from it. And have a way back to parrent (e.g. '../' as forst folder?). - advanced tasks #1  Two views :  make images clickable for popup  1) a.k.a. finder  ( bootstrap modal effect folders + items in grid ) , 2) item detail    - advanced tasks  #2 : not only images, but also pdf, videos, etc.. with dropdown to filter 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NOWDEMO-4) angular SPA component

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-4 
 
 
 
  angular SPA component  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 * investigate and found if we can create 'single page app' like angularjs component - new LM  which will  have at least two views  provide angular resources  ( list js  -  folders?, detail - items?) * page  will  not reload, just inside  be loaded directly in  component  it will switch between views  tempalte script) and new component  ( ideally some slide effect and decorate abailability in btk:components/section ) * so far content is not specified . Component should works like SPA ,  lets just used data  investigate also routing functionality in magnolia.- use case: image gallery (with folder support)- diaglo: to select folder  from  any  DAM (nothing selected = use root)- component: use angular to render all items (first level  of  existing  childs) from selected folder  ( automatically installed content app or root ) . If item is image ,  ideally  display it as a  image  gallery  ( dam thumbnail ) . If item is folder ,  but not sure if  display folder icon and on click this  angular +jsonfn+damImages is  app wil swith view into this folder and again list folders and images from it. And have  a  best combination  way back to parrent (e.g. '../' as forst folder?).- advanced tasks #1: make images clickable  for  demo  popup (bootstrap modal effect)- advanced tasks #2: not only images, but also pdf, videos, etc.. with dropdown to filter 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (NOWDEMO-9) use navfn

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-9 
 
 
 
  use navfn  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 07/Oct/16 12:01 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
temporary with SNAPSHOT libraries 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MTE-91) searchfn is not searching in parent page

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-91 
 
 
 
  searchfn is not searching in parent page  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 0.13 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 07/Oct/16 11:57 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
When multiple root pages exists (e.g. /en, /de, /es, ) then when want to search for something only in /en tree have to use this: 

 
searchfn.searchPages(queryStr, "/en") 
 

 
then results are only from subpages of /en and if match is also on /en page itself then its ignored. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 

[magnolia-dev] [JIRA] (NOWDEMO-8) use Glyphicons instead of Fontawsome

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-8 
 
 
 
  use Glyphicons instead of Fontawsome  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 06/Oct/16 3:12 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
to stay as much bootstrap as we can, pls change functionality to use icons in components (such as teaser, textImage, etc.) to work with Glyphicons which are already in Bootstrap bundle. instead of Fontawesome used in in prev version of BF module. 
Ideally also change input text field to select field with all available icons. there is more then 260 of them, hope (this part of dialog should be included) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 

[magnolia-dev] [JIRA] (NOWDEMO-6) page+component: search + results

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-6 
 
 
 
  page+component: search + results  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NOWDEMO-3) new component carousel

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-3 
 
 
 
  new component carousel  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Assignee:
 
 Tomáš Gregovský Michal Novak 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NOWDEMO-7) minor/unrelated changes

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-7 
 
 
 
  minor/unrelated changes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 05/Oct/16 10:42 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NOWDEMO-5) page+component: list of contacts + contact detail

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-5 
 
 
 
  page+component: list of contacts + contact detail  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 05/Oct/16 10:06 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 

page with autogenerated compoennt in man area, component description see below:
 

idea: one component which if doesn't have selector/parameter will show list of all, where links will link to same page with item in selector and then if there is selector this one component will show detail
 

freemarker only
 

check for this page template in navigation and then render dropdown menu
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
   

[magnolia-dev] [JIRA] (NOWDEMO-6) page+component: search + results

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-6 
 
 
 
  page+component: search + results  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 05/Oct/16 10:08 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 

use searchfn
 

check for this pagetemplate in navigation and then render search input field
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
   

[magnolia-dev] [JIRA] (NOWDEMO-4) angular SPA component

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-4 
 
 
 
  angular SPA component  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Michal Novak 
 
 
 

Created:
 

 05/Oct/16 10:06 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 

investigate and found if we can create 'single page app' like angularjs component which will have at least two views (list - folders?, detail - items?)
 

page will not reload, just inside component it will switch between views (ideally some slide effect)
 

so far content is not specified, lets just used data from any of existing (automatically installed content app), ideally image gallery (dam), but not sure if angular+jsonfn+damImages is a best combination for demo
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (NOWDEMO-3) new component carousel

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-3 
 
 
 
  new component carousel  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 05/Oct/16 9:57 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
with teaser for carousel and image for carousel available as options for slides 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (NOWDEMO-2) migrate components from existing bootstrap framework

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-2 
 
 
 
  migrate components from existing bootstrap framework  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Michal Novak 
 
 
 

Created:
 

 05/Oct/16 9:55 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
migrate 5 basic components from https://marketplace.magnolia-cms.com/bootstrap.html (jcr) to btk light module (yaml) and make them available in btk:components/section 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 

[magnolia-dev] [JIRA] (NOWDEMO-1) scss - commands for compiling with readme

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 NOW demo /  NOWDEMO-1 
 
 
 
  scss - commands for compiling with readme  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Michal Novak 
 
 
 

Created:
 

 05/Oct/16 9:52 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-186) remove Clicky icon from demo

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-186 
 
 
 
  remove Clicky icon from demo  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 demo_clicky.png 
 
 
 

Created:
 

 22/Sep/16 1:31 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
https://demopublic.magnolia-cms.com/ same as travel demo on 5.5-snapshot has entry in Tools > marketing tags which adds clicky snipet in to pages, but first line of this code is no need becasue its only displaying clicky logo on page (see screenshot).  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 

[magnolia-dev] [JIRA] (NPMCLI-49) mgnl-cli.json improvements

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-49 
 
 
 
  mgnl-cli.json improvements  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 0.0.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 31/Aug/16 10:18 AM 
 
 
 

Fix Versions:
 

 0.0.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
while doing 'mgnl setup' and going to edit mgnl-cli.json I see and may edit 'downloadUrl' for Magnolia tomcat, but instead of version number I see $ {magnoliaVersion} 
 and this one is not editable in mgnl-cli.json which probably will be nice to have, or don't use this property at all. Don't we have on nexust something for always downloading latest version? Maybe this will be useful instead of changing default cli configuration everytime new Magnolia version is released. 
Another question: is "lightModuleName": "sampleModule" used anywhere by CLI tool? It seems like after latest changes in create-light-module and jumpstart this is not used, so then I would suggest to remove it from mgnl-cli.json ... 
Thank you 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (NPMCLI-48) add-availability not using main area when there is no area specified

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-48 
 
 
 
  add-availability not using main area when there is no area specified  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 0.0.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 31/Aug/16 9:59 AM 
 
 
 

Fix Versions:
 

 0.0.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
command like $ mgnl add-availability mtk:components/link pages/home finish with error: Could not resolve area for undefined but would be nice to use 'main' area when there is no one specified. same as for create-component command 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3990) multivalue field is not working from yaml until there is no field > label/name

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3990 
 
 
 
  multivalue field is not working from yaml until there is no field > label/name  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 1.png 
 
 
 

Created:
 

 18/Aug/16 11:45 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
While doing migration for corporate website and while migrating jcr configuration to yaml we had couple of multivalue fields defined like on attachment 1.png. The point is in categoriesFilter/field it was working without 'name' or 'label' property but after doing 'Download as YAML' and using this yaml definition dialog is not working. Technically dialog opens but without actions buttons and any dialog tab including and nexts after this multivalue field. And with error in log http://pastebin.com/NgJRhBzR  
This is how field looks like after "Download as YAML": 

 

- name: categoriesFilter
  description:
  label: Show filter for
  class: info.magnolia.ui.form.field.definition.MultiValueFieldDefinition
  field:
appName: categories
fieldEditable: false
targetWorkspace: category
 

[magnolia-dev] [JIRA] (NPMCLI-6) do not duplicate areas

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-6 
 
 
 
  do not duplicate areas  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NPMCLI-6) do not duplicate areas

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-6 
 
 
 
  do not duplicate areas  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 currently add-availability script when it doesn't find proper area in yaml configuration (page definition) will create this configuration and into ftl file will add freemarker code to render that area. Unfortunately for pages we have one ftl file - main.ftl and if add-availability for compA into homePage it will does it (add area configuration, add ftl to render area). But then if add-availability for compB to standardPage which share same main.ftl, then this area is added into ftl again (duplication).So modify add-availability script to first check if that area '[#cms.area name="< areaNam areaName >" ' (do not close, there can be extra parameters for area) already exist in ftl file. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NPMCLI-23) referencing with names with dash "-" doesn't work

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-23 
 
 
 
  referencing with names with dash "-" doesn't work  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 10/Jul/16 8:41 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
$ mgnl create-component video-list -a pages/video-list Expected a value in the form e.g. [pages/]myHome@someArea but was pages/video-list INFO: No path option provided, component will be created in the current folder. Error: video-list doesn't match definitionId pattern 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  

[magnolia-dev] [JIRA] (NPMCLI-21) issue while creating light module

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-21 
 
 
 
  issue while creating light module  
 
 
 
 
 
 
 
 
 
 
screenshot of log 
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Attachment:
 
 package_json_-_gruenthalPOC_-Magnolia_git_repo_user_miruela_gruenthalpoc_.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NPMCLI-22) make "export MGNLCLI_HOME" easier

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-22 
 
 
 
  make "export MGNLCLI_HOME" easier  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 08/Jul/16 2:58 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
would be possible to have easier command which will setup MGNLCLI_HOME to current folder? something like run"mgnl home" (in folder I want to work in) instead of 'export MGNLCLI_HOME="/Users/tomas/Magnolia/git_repo/user/miruela/gruenthalpoc"' (which is different for each project.  also maybe to have this command automatic after npm install of cli will be nice  Thank you! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
  

[magnolia-dev] [JIRA] (NPMCLI-21) issue while creating light module

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-21 
 
 
 
  issue while creating light module  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 package.json 
 
 
 

Created:
 

 08/Jul/16 2:54 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
I am using npm cli to create light module. my project directory is ~/Magnolia/git_repo/user/miruela/gruenthalpoc.  I did full new npm install of cli. Did "mgnl setup", exported MGNCLI_HOME. Edited package.json (set lightModuleName and few others, "outputhPath" is still there). Then I run command "mgnl create-light-module gruenthal" and what I would expected (and was happening before) that light module "gruenthal" will be created in "light-modules" folder (which will be also created same time. But is not and "gruenthal" is created directly in project folder. Maybe I am just doing wrong some steps i configuration. Can somebody please double check and let me know. thank you! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
   

[magnolia-dev] [JIRA] (NPMCLI-20) update package json "lightDevFoldersInModule" to create all folders for light development

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-20 
 
 
 
  update package json "lightDevFoldersInModule" to create all folders for light development  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 08/Jul/16 2:38 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
decorations fieldTypes i18n messageViews 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
   

[magnolia-dev] [JIRA] (BF-11) Twitter Bootstrap kit in a light module

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-11 
 
 
 
  Twitter Bootstrap kit in a light module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Fix Version/s:
 
 3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (BF-11) Twitter Bootstrap kit in a light module

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-11 
 
 
 
  Twitter Bootstrap kit in a light module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Project:
 
 Twitter  Bootstrap  Theme and Definition  Framework 
 
 
 

Key:
 
 TWBTSTRP BF - 30 11 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (SUGGEST-38) add neat-resources (hcmcfn) into product

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-38 
 
 
 
  add neat-resources (hcmcfn) into product  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 20/May/16 3:35 PM 
 
 
 

Environment:
 
   
 
 
 

Labels:
 

 collector-0cf1239d 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
https://github.com/rah003/neat-resources - Neat-resources (hcmcfn) I am using a lot right now, so far it is for me best resources loading into page. Especially for light modules where you don't have to think about exporting/importing theme definition. Compare to theme you can even handle different resources (js) in header and on the bottom of page (which you can't with theme). And with option to cache there is almost none disadvantage to use them. So will be really nice to move them into product itself, maybe rename to resourcesfn. 
Just comparison example: 
Manually add resources: 

 
 
 
 
 

 
Using theme: 

 
[#assign site = sitefn.site()!] 
[#assign theme = sitefn.theme(site)!] 
[#list theme.cssFiles as cssFile] 
  
[/#list] 
 

 
Neat resources:  
   

[magnolia-dev] [JIRA] (NPMCLI-9) update mgnlbuild in cli

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-9 
 
 
 
  update mgnlbuild in cli  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 14/Apr/16 5:13 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
Currently mgnlbuild (build) is hardcoded in cli, it is lightly modified one old version of original mgnlbuild (version which not supports @magnolia scope, and probably more). we need to update this one, ideally just over dependency to original mgnlbuild instead of being in cli/bin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 

[magnolia-dev] [JIRA] (NPMCLI-4) improve yaml modifications

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-4 
 
 
 
  improve yaml modifications   
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Issue Type:
 
 Task Bug 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NPMCLI-5) improve npm link

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-5 
 
 
 
  improve npm link  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Issue Type:
 
 Task Bug 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NPMCLI-7) improve add-component, add-page to define path

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-7 
 
 
 
  improve add-component, add-page to define path  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 05/Apr/16 9:05 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
currently you can only do 'add-component link' which will be created in /templates/componets/...  
but will be nice to have option to specify path if need, e.g addComp components/links/internalLink (light module will be same, path match with exactly this one) addComp anotherModule:someComponents/link (will create new light module folder if doesn't exists yet, with custom path to file definition) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 

[magnolia-dev] [JIRA] (NPMCLI-6) do not duplicate areas

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-6 
 
 
 
  do not duplicate areas  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Issue Type:
 
 Task Bug 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (NPMCLI-6) do not duplicate areas

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-6 
 
 
 
  do not duplicate areas  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 05/Apr/16 9:00 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
currently add-availability script when it doesn't find proper area in yaml configuration (page definition) will create this configuration and into ftl file will add freemarker code to render that area. Unfortunately for pages we have one ftl file - main.ftl and if add-availability for compA into homePage it will does it (add area configuration, add ftl to render area). But then if add-availability for compB to standardPage which share same main.ftl, then this area is added into ftl again (duplication). 
So modify add-availability script to first check if that area '[#cms.area name="" ' (do not close, there can be extra parameters for area) already exist in ftl file. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
   

[magnolia-dev] [JIRA] (NPMCLI-5) improve npm link

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-5 
 
 
 
  improve npm link  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 05/Apr/16 8:53 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
sometimes, when bins are already linked to be executed in command line. when doing new cli installation with new 'sudo npm link' then sometimes it fails because of permissions, and to move over these linked script has to manually removed from /usr/... folder  
better understanding how they are linked and if we need to re-link them with every new cli installation will help. then if they have to be re-linked we will need probably some permission check or 'remove them first' step... or ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message 

[magnolia-dev] [JIRA] (NPMCLI-4) improve yaml modifications

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-4 
 
 
 
  improve yaml modifications   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 05/Apr/16 8:49 PM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
scripts which are editing yaml configuration (e.g. add-availability) right now they take yaml code, transform it in to json, add/edit whats need and transform back to yaml. unfortunately during first transform from yaml to json, what doesn't looks like json is removed, so all comments '#...' or includes '!include' etc... ale lost during this edit. 
potential fixes: 1. (idealy) do not use yaml > json > yaml conversion, but edit configuration directly in yaml format or 2. improve yaml > json > yaml do not remove this things (propably !extends in future as well) or 3. maybe use some wrapper around this special entries, before they are transformed to json, that transformation itself will not remove them, and then when transforming back to yaml, remove this wrapper as well or ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (NPMCLI-3) investigate if there is option to use autosuggest for cli tool

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-3 
 
 
 
  investigate if there is option to use autosuggest for cli tool  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 05/Apr/16 8:42 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (SUGGEST-23) in resources app move 'upload file' to top

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-23 
 
 
 
  in resources app move 'upload file' to top  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Christopher Zimmermann 
 
 
 

Created:
 

 15/Mar/16 8:30 AM 
 
 
 

Environment:
 
   
 
 
 

Labels:
 

 collector-0cf1239d 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
It is just a small change but will be nice to have 'upload button' in same action group as 'add file', 'add folder' (bellow this two will be best) in resources app. Thank you! 
(on EE 5.4.4) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (SUGGEST-18) option to distinguish instances (author, public1,...)

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-18 
 
 
 
  option to distinguish instances (author, public1,...)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Christopher Zimmermann 
 
 
 

Created:
 

 24/Feb/16 5:17 PM 
 
 
 

Environment:
 
   
 
 
 

Labels:
 

 collector-0cf1239d 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
It was mentioned today during workshop in Berlin from one of attendees. But I was already thinking about similar before.  
The story is that usually if you developing with Magnolia and especially if you discover any issue on production and going to check it, first on prod, then trying to reproduce on local and maybe later on test server. Then in one day, maybe in one hour you may found yourself to having opened production author, public1, public2, test-author, test-public, local author, local public, etc... at same time, all of them looks absolutely same except url in browsed address bar all looks same and its really easy to do mistake and remove or edit something on wrong instance because of that. 
So the idea is to have for example optional string, or box, or colored box, or colored background, or "prefix" around Magnolia logo, etc... which may be defined in properties file, because you may have different property file for each webapp setup.  
I attached screenshot of what I can imagine works well in case I may have property in magnolia.properties like:  magnolia.instance.label="www.mgnl.com - localhost" 
 
 
 
 
 

[magnolia-dev] [JIRA] (MTE-75) allow 'order by' in searchfn

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-75 
 
 
 
  allow 'order by' in searchfn  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 03/Feb/16 3:16 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
searchfn is cool feature of 5.4, also it is only one way how to list of content from custom content app across multiple folders.  But will be nice to have more options around, for example to change order (eg. name/title aplhabet, mgnl:created, custom property date or just same order as it is in jcr). With DESC option.  
additionally will be nice to have also: A) "... where jcrName = '%%'" which is good when you want to get content just based on name. B) "... where date < now()" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (NPMBUILD-2) When name: @magnolia/ magnolia-build ignore it

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia light-module build tools /  NPMBUILD-2 
 
 
 
  When name: @magnolia/ magnolia-build ignore it  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 

Created:
 

 25/Jan/16 2:17 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
if name of light module in package.json is scoped to magnolia, e.g.: 

 
"name": "@magnolia/hello-magnolia",
 

 
and when project is installed (npm install), this "hello-magnolia" is placed into node_modules/@magnolia/hello-magnolia , (one folder deeper) and magnolia-build can't found it and just print "No Magnolia light modules found." 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (NPMBUILD-3) magnolia-build copy module into resources folder including package.json

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia light-module build tools /  NPMBUILD-3 
 
 
 
  magnolia-build copy module into resources folder including package.json  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 

Created:
 

 25/Jan/16 2:27 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
magnolia-build copy module into resources folder including package.json that one is then visible in magnolia resources app... and simply shouldn't be copied. I guess similar for some kind on readme files, etc... maybe just folders should be? or something like ignore list in magnolia-build package.json?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
  

[magnolia-dev] [JIRA] (BF-3) carousel component

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-3 
 
 
 
  carousel component  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Fix Version/s:
 
 2.2 
 
 
 

Fix Version/s:
 
 2.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (BF-5) add [#compress] to all ftl

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-5 
 
 
 
  add [#compress] to all ftl  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Fix Version/s:
 
 2.2 
 
 
 

Fix Version/s:
 
 2.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (BF-4) image direct upload

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-4 
 
 
 
  image direct upload  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Fix Version/s:
 
 2.2 
 
 
 

Fix Version/s:
 
 2.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (BF-6) polish ftl and css

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-6 
 
 
 
  polish ftl and css  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 28/Dec/15 9:53 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (BF-6) polish ftl and css

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-6 
 
 
 
  polish ftl and css  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Fix Version/s:
 
 2.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3685) huge select fields are not scrolling

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3685 
 
 
 
  huge select fields are not scrolling   
 
 
 
 
 
 
 
 
 
 
just for info:  tested on 5.4.3 and scroll works fine (so issues seems only on 5.3.12). On 5.4.3 there is a scroll for all options and also whole this option list begins from position of that field (compare to screenshot from 5.3.12 where list begins on top of page). 
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Attachment:
 
 Magnolia_5.jpg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3685) huge select fields are not scrolling

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3685 
 
 
 
  huge select fields are not scrolling   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.3.12 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 Magnolia_5.jpg 
 
 
 

Created:
 

 30/Nov/15 11:18 AM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
For corporate website where we are using Infusionsoft integration with select fields of more then hundreds entries, we were really looking forward to 5.3.12 because of 

MGNLUI-3600
, now I am testing it locally (working on new corpweb release) and found that transparent background is gone, but list is still not scrolling. Unfortunately before with transparent background there was hacky way still to select right option, but now with full background it's completely impossible   
Because of other issues we need to update to 5.3.12 and this 

[magnolia-dev] [JIRA] (BF-5) add [#compress] to all ftl

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-5 
 
 
 
  add [#compress] to all ftl  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 01/Dec/15 5:00 PM 
 
 
 

Fix Versions:
 

 2.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: 

[magnolia-dev] [JIRA] (BF-3) carousel component

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-3 
 
 
 
  carousel component  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 01/Dec/15 3:36 PM 
 
 
 

Fix Versions:
 

 2.1 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: 

[magnolia-dev] [JIRA] (BF-2) support for CE

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-2 
 
 
 
  support for CE  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 01/Dec/15 3:36 PM 
 
 
 

Fix Versions:
 

 2.1 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: 

[magnolia-dev] [JIRA] (BF-4) image direct upload

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-4 
 
 
 
  image direct upload  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 01/Dec/15 3:37 PM 
 
 
 

Fix Versions:
 

 2.1 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
As alternative to DAM (because of CE support) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 

[magnolia-dev] [JIRA] (BF-1) initial commit for version 2.0

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-1 
 
 
 
  initial commit for version 2.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Fix Version/s:
 
 2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3658) optionaly change order of items in Multivalue field

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3658 
 
 
 
  optionaly change order of items in Multivalue field  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 multivalue-field.jpg 
 
 
 

Components:
 

 forms 
 
 
 

Created:
 

 16/Nov/15 4:12 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
For Multivalue field will be nice to have option to change order of items. Maybe only when an property like "changeOrder" is true (default will be false). Have it in 5.4.x same as in 5.3.x will be super cool! 
Story: on corporate website, marketplace and others project in futures I am more and more using 

[magnolia-dev] [JIRA] (BF-1) initial commit for version 2.0

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Bootstrap Framework /  BF-1 
 
 
 
  initial commit for version 2.0  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomáš Gregovský 
 
 
 

Created:
 

 21/Sep/15 4:46 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3595) display theme and site in page tree view

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3595 
 
 
 
  display theme and site in page tree view  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 21/Sep/15 7:03 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Will be helpful for developing to have info about theme and site def in pages tree view. maybe only for root pages and when superuser. Thank you 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLDEMO-76) Example of form module

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Add "border: 1px solid #ccc;" into trvels-magnolia.css on line 1367 
Other then that looks fine when reviewed. 
 
 
 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-76 
 
 
 
  Example of form module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomáš Gregovský 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved 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] (TWBTSTRP-29) new how to content (demo website)

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-29 
 
 
 
  new how to content (demo website)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 13/Jul/15 6:50 PM 
 
 
 

Fix Versions:
 

 1.3 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (TWBTSTRP-28) bootstrap v3.3.5

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-28 
 
 
 
  bootstrap v3.3.5  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 10/Jul/15 5:01 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (TWBTSTRP-28) bootstrap v3.3.5

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-28 
 
 
 
  bootstrap v3.3.5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomš Gregovsk 
 
 
 

Fix Version/s:
 
 1.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLSOLR-17) optionally remove old installation in one step

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Apache Solr integration /  MGNLSOLR-17 
 
 
 
  optionally remove old installation in one step  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Milan Divilek 
 
 
 

Created:
 

 27/May/15 11:34 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
Will be nice instead of displaying message that old solr configuration needs to be manually removed first, check and if exist remove that configuration (or backup). 
Working with 2.2 version. 
 installTasks.add(new RemoveNodeTask(Remove solr-search-provider,, config, /modules/solr-search-provider)); installTasks.add(new RemoveNodeTask(Remove content-indexer,, config, /modules/content-indexer)); installTasks.add(new RemoveNodeTask(Remove SearchServlet,, config, /server/filters/servlets/SearchServlet)); installTasks.add(new RemoveNodeTask(Remove SearchServlet[2],, config, /server/filters/servlets/SearchServlet)); 
Thank you 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

  

[magnolia-dev] [JIRA] (TWBTSTRP-26) reuse textImage and image components from corporate website project

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-26 
 
 
 
  reuse textImage and image components from corporate website project  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomš Gregovsk 
 
 
 

Fix Version/s:
 
 1.3 
 
 
 

Fix Version/s:
 
 1.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (TWBTSTRP-27) super row

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-27 
 
 
 
  super row  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Attachments:
 

 config.modules.corporate-website-2015.dialogs.components.cSuperRow.xml, config.modules.corporate-website-2015.templates.components.cColInSuperRow.xml, config.modules.corporate-website-2015.templates.components.cSuperRow.xml, superRow.ftl 
 
 
 

Created:
 

 22/May/15 10:35 PM 
 
 
 

Fix Versions:
 

 1.3 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (TWBTSTRP-26) reuse textImage and image components from corporate website project

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-26 
 
 
 
  reuse textImage and image components from corporate website project  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 19/May/15 2:40 PM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (TWBTSTRP-16) simplyfy teaser

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-16 
 
 
 
  simplyfy teaser  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomš Gregovsk 
 
 
 

Summary:
 
 fixadditionaldivclassin simplyfy teaser 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (TWBTSTRP-16) simplyfy teaser

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-16 
 
 
 
  simplyfy teaser  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 removeteaserstyles,usethumbnaillayoutasdefault 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (TWBTSTRP-25) selectable title size (h1, h2, h3, h4) for row and group

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-25 
 
 
 
  selectable title size (h1, h2, h3, h4) for row and group  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 30/Apr/15 8:19 PM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (TWBTSTRP-24) inherit renderer for components in group

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-24 
 
 
 
  inherit renderer for components in group  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 1.1 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 24/Apr/15 2:37 PM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 
 
 
 
  

[magnolia-dev] [JIRA] (TWBTSTRP-21) icon sizes

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-21 
 
 
 
  icon sizes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 AddiconsizeoptiontodialogforTextandImage- normal small =100%fontsize-medium=300%fontsize-large=600%fontsize 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (TWBTSTRP-22) font-awesome 4.3

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-22 
 
 
 
  font-awesome 4.3  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.1 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 01/Apr/15 10:47 AM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
   

[magnolia-dev] [JIRA] (TWBTSTRP-21) icon sizes

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-21 
 
 
 
  icon sizes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 30/Mar/15 2:03 PM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
Add icon size option to dialog for Text and Image  
 

normal = 100% font size
 

medium = 300% font size
 

large = 600% font size
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
   

[magnolia-dev] [JIRA] (TWBTSTRP-20) override channels table in page properties dialog

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-20 
 
 
 
  override channels table in page properties dialog  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 25/Mar/15 10:37 AM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (TWBTSTRP-18) autogenerate row on every page and use an placeholder

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-18 
 
 
 
  autogenerate row on every page and use an placeholder  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 19/Mar/15 10:37 AM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (TWBTSTRP-19) fix placeholder issue for text and image

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-19 
 
 
 
  fix placeholder issue for text and image  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.1 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 19/Mar/15 2:38 PM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
  

[magnolia-dev] [JIRA] (TWBTSTRP-16) fix additional div class in teaser

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-16 
 
 
 
  fix additional div class in teaser  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 13/Mar/15 1:05 PM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (TWBTSTRP-17) add i18n=true to all dialogs fields

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-17 
 
 
 
  add i18n=true to all dialogs fields  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 13/Mar/15 2:49 PM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (TWBTSTRP-15) add sizeUp to tbGroup dialog

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-15 
 
 
 
  add sizeUp to tbGroup dialog  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Attachments:
 

 config.modules.twitter-bootstrap.dialogs.components.row.tbGroup.form.tabs.tabStyles.fields.sizeUp.xml 
 
 
 

Created:
 

 12/Mar/15 1:35 PM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 

[magnolia-dev] [JIRA] (TWBTSTRP-14) make nav-bar-fixed editable by parametrs

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-14 
 
 
 
  make nav-bar-fixed editable by parametrs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomš Gregovsk 
 
 
 

Fix Version/s:
 
 1.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (TWBTSTRP-14) make nav-bar-fixed editable by parametrs

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-14 
 
 
 
  make nav-bar-fixed editable by parametrs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 11/Mar/15 12:17 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (TWBTSTRP-13) add .inline class to mgnl.bootstrap.css

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomš Gregovsk created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Twitter Bootstrap Theme and Definition /  TWBTSTRP-13 
 
 
 
  add .inline class to mgnl.bootstrap.css  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Tomš Gregovsk 
 
 
 

Created:
 

 11/Mar/15 10:21 AM 
 
 
 

Fix Versions:
 

 1.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomš Gregovsk 
 
 
 
 
 
 
 
 
 
 
.inline  { width:auto; display:inline-block; float: none; } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 

[magnolia-dev] [JIRA] (TWBTSTRP-7) move additionalDivClass from row class to container class

[on behalf of Tomáš Gregovský]

Tomáš Gregovský
 updated  TWBTSTRP-7


move additionalDivClass from row class to container class
















Change By:


Tomáš Gregovský
(04/Mar/15 4:33 PM)




Fix Version/s:


1.0.1



























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

[magnolia-dev] [JIRA] (TWBTSTRP-12) change textImageLayout.ftl

[on behalf of Tomáš Gregovský]

Tomáš Gregovský
 updated  TWBTSTRP-12


change textImageLayout.ftl 
















Change By:


Tomáš Gregovský
(02/Mar/15 5:33 PM)




Fix Version/s:


1.0.1



























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








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (TWBTSTRP-12) change textImageLayout.ftl

[on behalf of Tomáš Gregovský]

Tomáš Gregovský
 created  TWBTSTRP-12


change textImageLayout.ftl 















Issue Type:


Task



Assignee:


Tomáš Gregovský



Created:


02/Mar/15 5:32 PM



Description:


Using "col-xx-x" in textImage added extra padding around it. to avoid this extra paddings lets use just pull-left and pull-right with 50% image width.




Project:


Twitter Bootstrap Theme and Definition



Priority:


Neutral




Reporter:


Tomáš Gregovský




























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








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (TWBTSTRP-10) option for custom column_manager

[on behalf of Tomáš Gregovský]

Tomáš Gregovský
 created  TWBTSTRP-10


option for custom column_manager 















Issue Type:


Improvement



Affects Versions:


1.0



Assignee:


Tomáš Gregovský



Created:


23/Feb/15 4:03 PM



Description:


allow option for custom column_manager.ftl which can by used just in some cases.

example:
[@cms.component content=sub_nav_item  contextAttributes=
{"specialColumnManager":"/corporate2015-FTLs/components/includes/columnManagerForNavigation.ftl"}
/]




Fix Versions:


1.0.1



Project:


Twitter Bootstrap Theme and Definition



Priority:


Neutral




Reporter:


Tomáš Gregovský




























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








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com