[magnolia-dev] [JIRA] (SUGGEST-68) Deprecate the property "type" for area configuration

[JIRA (on behalf of Christian Ringele)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Ringele updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-68  
 
 
  Deprecate the property "type" for area configuration   
 

  
 
 
 
 

 
Change By: 
 Christian Ringele  
 
 
Attachment: 
 Root-by-type.png  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLUI-4184) SelectField: field property 'selected' is ignored

[JIRA (on behalf of Christian Ringele)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Ringele created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4184  
 
 
  SelectField: field property 'selected' is ignored   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.2  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 dialogs, forms  
 
 
Created: 
 06/Apr/17 9:20 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Christian Ringele  
 

  
 
 
 
 

 
 

 

- name: maxLevels
  class: info.magnolia.ui.form.field.definition.SelectFieldDefinition
  label: Maximum Levels
  description: Maximum of level of pages shown in this recursion.
  type: Long
  options:
- name: 1
  value: 1
  label: 1
- name: 2
  value: 2
  label: 2
- name: 3
  value: 3
  selected: true
  label: 3
- name: 4
  value: 4
  label: 4
- name: 5
  value: 5
  label: 5
 

 The property 'selected: true' is ignored, with this configuration the option '1' is used when opening first time the dialog.  
 

  
 
 
 
 

 
 

[magnolia-dev] [JIRA] (DOCU-983) Provide new/updated Diagram of an old 4.5 Diagram about "template structure aligning the stored content structure" -> it was extremly valuable

[JIRA (on behalf of Christian Ringele)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Ringele created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-983  
 
 
  Provide new/updated Diagram of an old 4.5 Diagram about "template structure aligning the stored content structure" -> it was extremly valuable   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Left-Side.png  
 
 
Created: 
 03/Apr/17 10:06 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christian Ringele  
 

  
 
 
 
 

 
 Hi all  The original Diagram was this one: https://documentation.magnolia-cms.com/display/DOCS45/Rendering+and+templating+diagrams https://documentation.magnolia-cms.com/display/DOCS45/Rendering+and+templating+diagrams?preview=/57192316/58262632/Pages-and-paragraphs.png It was extremely valuable as it showed in a very easy way the correlation between the created and processes content structure to the rendered output one sees: starts with the page, then the area, then the components I think it would be great, if the left side would also contain the node types, so one could see that the node type even represents what you see: I attached a print screen from JCR browser of what I mean -> Left-Side.png The right side I think the travel demo is a bad show case -> A jumbotron component is just not page content... and the page content stored on page level you see only in navigation... very bad example for showing exactly this essentials... -> Maybe the base template could be used for it?  
 

  
 
 
 
 

 
 
 

 
  

[magnolia-dev] [JIRA] (MGNLGA-23) Properly Update GA module to 5.4 & 5.5 (& light development) world: Processes Recoures are deprectaed and cumbersome to use

[JIRA (on behalf of Christian Ringele)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Ringele created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Google Analytics /  MGNLGA-23  
 
 
  Properly Update GA module to 5.4 & 5.5 (& light development) world: Processes Recoures are deprectaed and cumbersome to use   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 1.3.2  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 24/Jan/17 1:43 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christian Ringele  
 

  
 
 
 
 

 
 The 'init-gatracker.js' relies on the old processed resources. It plugs itself into the former STK theme: https://documentation.magnolia-cms.com/display/DOCS53/Google+Analytics+module?preview=/105684977/105684981/_javascript_s.png (Also MGNLGA-19) This does not really match the Magnolia 5.4 and 5.5 world, especially not the Light Development world. The old processed resources are: 
 
deprecated 
cumbersome to use 
very confusing when knowing the new resource loading 
contradicting the light development 
 The PM & PD has stated, that the 'the old processed resources' are not needed in the new world. So it would be nice to proof it with a proper solution not using it, but using the possibilities of 5.4 & 5.5. Its easy to say its not needed, but then rolling out a jar that relies on it as we don't have a better current solution...  
 

  
 
 
 
 

 
 

[magnolia-dev] [JIRA] (MGNLGA-23) Properly Update GA module to 5.4 & 5.5 (& light development) world: Processed Recoures are deprectaed and cumbersome to use

[JIRA (on behalf of Christian Ringele)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Ringele updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Google Analytics /  MGNLGA-23  
 
 
  Properly Update GA module to 5.4 & 5.5 (& light development) world: Processed Recoures are deprectaed and cumbersome to use   
 

  
 
 
 
 

 
Change By: 
 Christian Ringele  
 
 
Summary: 
 Properly Update GA module to 5.4 & 5.5 (& light development) world:  Processes  Processed  Recoures are deprectaed and cumbersome to use  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLGROOVY-147) Provide general Command that can execute Groovy scripts

[JIRA (on behalf of Christian Ringele)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Ringele reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Groovy Module /  MGNLGROOVY-147  
 
 
  Provide general Command that can execute Groovy scripts   
 

  
 
 
 
 

 
Change By: 
 Christian Ringele  
 
 
Resolution: 
 Not an issue  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCI-16) Error on Import: Error Message doesn't say a reason && stacktrace looks odd

[JIRA (on behalf of Christian Ringele)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Ringele updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Importer Module /  MGNLCI-16  
 
 
  Error on Import: Error Message doesn't say a reason && stacktrace looks odd   
 

  
 
 
 
 

 
Change By: 
 Christian Ringele  
 
 
Summary: 
 Error on  Impot  Import : Error Message doesn't say a reason && stacktrace looks odd  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCI-16) Error on Impot: Error Message doesn't say a reason && stacktrace looks odd

[JIRA (on behalf of Christian Ringele)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Ringele created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Importer Module /  MGNLCI-16  
 
 
  Error on Impot: Error Message doesn't say a reason && stacktrace looks odd   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 1.0.1  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 config.modules.site.config.site.i18n.xml, ImportMessage.png, SiteModule-SiteConfig.png  
 
 
Created: 
 21/Dec/16 4:26 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Christian Ringele  
 

  
 
 
 
 

 
 I use the first time the content importer module. I was able to import various node, but having a error on importing into: config:/modules/site/config/site The error message problem: The pulse error message says no reason why its not working. The error - stacktrace: 

 

2016-12-21 16:18:27,272 ERROR tral.shellapp.pulse.task.action.AbstractTaskAction: An error occurred while trying to execute task [info.magnolia.task.Task@1659dc1e[path=/tasks/2016/11/21/1482332195799,id=9a798f6f-6350-41fc-b72e-4fe33456d78d,name=content,status=InProgress,priority=0,requestor=superuser,comment=config.modules.site.config.site.i18n.xml,groupIds=,actorIds=[superuser],actorId=superuser,skippable=false,content={path=/Users/cringele/workspaces/training_workspace-trainer-5.4.x/training-front-end-result/data/config.modules.site.config.site.i18n.xml, 

[magnolia-dev] [JIRA] (SUGGEST-65) Generally: Re-concept app (and Action) permissions settings -> with Yamls it doesn't work at all in System Administration scope.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-65 
 
 
 
  Generally: Re-concept app (and Action) permissions settings -> with Yamls it doesn't work at all in System Administration scope.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 While creating a System Administration training we realized some problems with Magnolia in the scope if Administrating the System from within Magnolia.Meaning a Magnolia System Administrator does work like- Creating roles & groups & users- Anything  within  being  logged in Magnolia which is more then normal Author work/need more rights and knowledge.Problem generally:The app sets on its configuration itself the permissions who can open the app.I think this is the wrong place, and with Yaml it leads to a lot of problems.How it should be:As "Web Access; & "Content Security" is set on a role, it should also be defined on the role "Apps allowed to open". And not that the app defines which roles are allowed to open it.Problem with Yaml:Before the Yaml world, one could argue that a System Administrator was still able to do it, just in a not so nice way:Open "Configurations" app, and set the permission on the app config (and hopefully inform the dev team).*But* this doesn't work with Yaml based app configuration...So in the end only the light module developer can do it on the FS...Hotfixing its not an option, or the light module developer can not change the app via FS anymore at all. And when removing the hot fix the permissions would be gone...I think its very silly, and hard to justify, why a Sys Admin has to call a LM developer after creation a new role, just to manage the permissions on an app using this role.  And that in the end the permissions on who can open an app is in some file of a light module. Suggested Solution: Decouplde Decouple  all configurations from any permission setting.Define all  thiese permisions  these permissions  based on the role/within the role/within the security app. Always  form  from  roles -> target config and not the other way around. SO So  basically decouple all configs from the permissions on them, as its done with the content and its ACLs.Which would also solve the following problem:In Test Systems & QA Systems the roles are often different.So the same configs (after load of production  contnent  content  & configs) won't work out of the box in a Test Systems & QA Systems,  ass  and all  permissions have to be changes . !  Which can be really hard to achieve if you even think about Actions with Permissions or configurations based on Yaml. If its decoupled, one set of permissions/roles could be provided per system/instance, and it would just work OTB.   This would be a bigger refining in the product.But currently the reality is that:- We never have set a proper focus on Sys Administrators and what they have to be able to achieve and how.- We have never thought about the problem of defining permissions in configurations in scope of yaml- We have never thought about the problem of defining permissions when interchanging the content between test and QA system which often have a different set of roles. 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (SUGGEST-65) Generally: Re-concept app (and Action) permissions settings -> with Yamls it doesn't work at all in System Administration scope.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-65 
 
 
 
  Generally: Re-concept app (and Action) permissions settings -> with Yamls it doesn't work at all in System Administration scope.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 05/Dec/16 12:08 PM 
 
 
 

Environment:
 
   
 
 
 

Labels:
 

 collector-0cf1239d 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
While creating a System Administration training we realized some problems with Magnolia in the scope if Administrating the System from within Magnolia. Meaning a Magnolia System Administrator does work like 
 

Creating roles & groups & users
 

Anything within logged in Magnolia which is more then normal Author work/need more rights and knowledge.
 
 
Problem generally: The app sets on its configuration itself the permissions who can open the app. I think this is the wrong place, and with Yaml it leads to a lot of problems. 
How it should be: As "Web Access; & "Content Security" is set on a role, it should also be defined on the role "Apps allowed to open". And not that the app defines which roles are allowed to open it. 
Problem with Yaml: Before the Yaml world, one could argue that a System Administrator 

[magnolia-dev] [JIRA] (SUGGEST-64) M5.5 & LM: Import of JCR content -> provide additional Action in Pulse message "Import and Publish"

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-64 
 
 
 
  M5.5 & LM: Import of JCR content -> provide additional Action in Pulse message "Import and Publish"  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 05/Dec/16 11:44 AM 
 
 
 

Environment:
 
   
 
 
 

Labels:
 

 collector-0cf1239d 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
I like the new possibility in M5.5 that one can have JCR content being imported: 
 

Dropping into a folder
 

Pulse message that you can import something new.
 
 
Problem: This would have to be done on all instances, also the public instances. But Authors are not used to log on into a public instance. 
Current best approach: 
 

Trigger/approve on author the import over pulse message
 

Navigate manually to the place of the imported node and activate it manually The problem I see is that its maybe hard for the approve to really know, where he can find the imported content.
  

[magnolia-dev] [JIRA] (MGNLCACHE-149) No Browser Cache control for images without file extension

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-149 
 
 
 
  No Browser Cache control for images without file extension  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 browser cache 
 
 
 

Created:
 

 29/Sep/16 3:46 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Value 600 seconds coming from: /modules/cache/config/contentCaching/defaultPageCache/browserCachePolicy/policies/default 
Uri: https://demopublic.magnolia-cms.com/.imaging/mte/travel-demo-theme/480x360/dam/tours/flickr-grand-canyon-grand-canyon-national-park-12094069375_881928ee56_k.jpg/jcr:content/flickr-grand-canyon-grand-canyon-national-park-12094069375_881928ee56_k.jpg.jpg Produces: Cache-Control max-age=600, public 
Uri: https://demopublic.magnolia-cms.com/.imaging/mte/travel-demo-theme/480x360/dam/tours/flickr-grand-canyon-grand-canyon-national-park-12094069375_881928ee56_k.jpg/jcr:content/flickr-grand-canyon-grand-canyon-national-park-12094069375_881928ee56_k Produces: Cache-Control  no-cache, no-store, must-revalidate, max-age=0 
Same with: curl -u superuser:superuser -v https://demo.magnolia-cms.com/dam/jcr:5b9ee0d9-9ee2-4943-ba91-ff8240065fda/youtube.png and curl -u superuser:superuser -v 

[magnolia-dev] [JIRA] (MGNLUI-4028) Reflect Authoring locale in Pages app's location fragment

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4028 
 
 
 
  Reflect Authoring locale in Pages app's location fragment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Project:
 
 Magnolia  pages module  UI 
 
 
 

Key:
 
 PAGES MGNLUI - 93 4028 
 
 
 

Security:
 
 Public 
 
 
 

Affects Version/s:
 
 5.4.7 
 
 
 

Affects Version/s:
 
 5.4.7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: 

[magnolia-dev] [JIRA] (PAGES-93) Reflect Authoring locale in Pages app's location fragment

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-93 
 
 
 
  Reflect Authoring locale in Pages app's location fragment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 pages.patch 
 
 
 

Attachment:
 
 DetailLocation.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-93) Reflect Authoring locale in Pages app's location fragment

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-93 
 
 
 
  Reflect Authoring locale in Pages app's location fragment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Patch included:
 
 Yes 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4023) SelectField options don't allow to set the same value into two different select options.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4023 
 
 
 
  SelectField options don't allow to set the same value into two different select options.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4023) SelectField options don't allow to set the same value into two different select options.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4023 
 
 
 
  SelectField options don't allow to set the same value into two different select options.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 SelectFieldFactory.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4023) SelectField options don't allow to set the same value into two different select options.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4023 
 
 
 
  SelectField options don't allow to set the same value into two different select options.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 SelectFieldFactory.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4023) SelectField options don't allow to set the same value into two different select options.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4023 
 
 
 
  SelectField options don't allow to set the same value into two different select options.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 SelectFieldFactory.patch 
 
 
 

Components:
 

 forms 
 
 
 

Created:
 

 22/Sep/16 4:57 PM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (PAGES-93) Reflect Authoring locale in Pages app's location fragment

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-93 
 
 
 
  Reflect Authoring locale in Pages app's location fragment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-93) Reflect Authoring locale in Pages app's location fragment

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-93 
 
 
 
  Reflect Authoring locale in Pages app's location fragment  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 22/Sep/16 11:21 AM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Currently the authoring local chosen over the language drop-down is not a part of the location fragment. This has as a consequence, that one can not send the URL of editing the page in a certain non-default language to other editors or via a location call by code. Also the Favorites store and won't react to it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4014) Investigate into corner cases: Wrong timezone calculation in DateFieldFactory

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4014 
 
 
 
  Investigate into corner cases: Wrong timezone calculation in DateFieldFactory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4014) Investigate into corner cases: Wrong timezone calculation in DateFieldFactory

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4014 
 
 
 
  Investigate into corner cases: Wrong timezone calculation in DateFieldFactory  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.9, 5.4.8, 5.4.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 forms 
 
 
 

Created:
 

 12/Sep/16 9:25 AM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
We should investigate into time zone corner cases as switching from winter to summer time and CET vs CUT time calculations: 
From the support ticket: 
Nr1: 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3996) Multiple Dialog box opens up when an edit component tried multiple time

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3996 
 
 
 
  Multiple Dialog box opens up when an edit component tried multiple time  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3996) Multiple Dialog box opens up when an edit component tried multiple time

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3996 
 
 
 
  Multiple Dialog box opens up when an edit component tried multiple time  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Labels:
 
 support 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3928) Security Problem Sample-App: Allows cross site scriting

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3928 
 
 
 
  Security Problem Sample-App: Allows cross site scriting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3928) Security Problem Sample-App: Allows cross site scriting

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3928 
 
 
 
  Security Problem Sample-App: Allows cross site scriting  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 30/Jun/16 10:19 AM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Try this on calling the sample app: https://demo.magnolia-cms.com/.magnolia/admincentral#app:sample:editor;%3Cimg%20src=y%20onerror=alert(String.fromCharCode(88,83,83,32,97,116,32)+document.domain)%3E 
As the sample-app is not product critical, the workaround is simple: Exclude it from the webapp's pom. 
Excluding it: The app is Maven wise: 

 


  info.magnolia.sample
  magnolia-sample-app

 

 

[magnolia-dev] [JIRA] (MGNLGROOVY-147) Provide general Command that can execute Groovy scripts

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Groovy Module /  MGNLGROOVY-147 
 
 
 
  Provide general Command that can execute Groovy scripts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Labels:
 
 support 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLGROOVY-147) Provide general Command that can execute Groovy scripts

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Groovy Module /  MGNLGROOVY-147 
 
 
 
  Provide general Command that can execute Groovy scripts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLGROOVY-147) Provide general Command that can execute Groovy scripts

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Groovy Module /  MGNLGROOVY-147 
 
 
 
  Provide general Command that can execute Groovy scripts  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 2.4.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 integration 
 
 
 

Created:
 

 22/Jun/16 12:42 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
From a support ticket a needed functionality, which I think is not that exotic many others could benefit: Executing a groovy script on scheduled regular bases. 
The way to implement it with the tools given would be: 
 

Have a scheduled Job executing a command
 

The command to execute is capable of running any groovy script in the goovy script 

[magnolia-dev] [JIRA] (MGNLUI-3901) Link Field Label: Ugly styling

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3901 
 
 
 
  Link Field Label: Ugly styling  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Summary:
 
 Link  Field  Label: Ugly styling 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3901) Link Label: Ugly styling

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3901 
 
 
 
  Link Label: Ugly styling  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
  See attachment.How long will it take until we resolve this?I see it since Magnolia 5.0... I think this is a bit embarrassing, since 3 years people see this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3901) Link Label: Ugly styling

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3901 
 
 
 
  Link Label: Ugly styling  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3901) Link Label: Ugly styling

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3901 
 
 
 
  Link Label: Ugly styling  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.6, 5.3.14, 5.2.13 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 LinkLabel-FromDemo.png 
 
 
 

Components:
 

 forms 
 
 
 

Created:
 

 31/May/16 4:09 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
See attachment. 
How long will it take until we resolve this? I see it since Magnolia 5.0...I think this is a bit embarrassing, since 3 years people see this. 
 
 
 
 
   

[magnolia-dev] [JIRA] (SUGGEST-36) New i18n mechanism: Provide a conveniant way to get the complete list of the auto generated keys.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-36 
 
 
 
  New i18n mechanism: Provide a conveniant way to get the complete list of the auto generated keys.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 Hi,I discussed it quickly with  topher  Yopher  yesterday:I think we need to provide the possibility to get all keys of a certain module (light & non light modules) in a  conveniant  convenient  way.I love the new  mechanis  mechanism , as it prevents me of having to define all the keys in the config manually.But it has a big downside:The keys get generated by a certain  pattern.So its hard to know for the developer, which keys will be in the end expected by Magnolia.Having to do that manually uses even more time then having to add them manually to the configuration, because there I can just use any key I want (foo.blah would work).There is a config that can be used to get a out for apps:config:modules/i18n/config@debug=trueThen it shows the list in the ActionBar (looks  awefull  awe full , but at least you have all keys needed to be translated for an app).But of course this works only for apps.Meaning that the code base would already be there, not that much of backend development needed.So the goal:I can tell the system " * Get me a complete list of all key generated/expected by the system, to copy it manually into a empty message bundle file * ".This would not even need a fancy app. All what the dev needs (minimum thinking) would be a  propert  proper  console out with the list of all empty keys.Nice would be, if I can also target a single configuration.But the real need is to be able to  gat  get  all of a module:I just create my configs, then trigger the list, and can start translating them.This is generally the first thing I get asked in every training, when showing the i18n mechanism:How do I know all concrete keys?Can I get them form the system?Why not, the system knows what it expects?Cheers 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (SUGGEST-36) New i18n mechanism: Provide a conveniant way to get the complete list of the auto generated keys.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-36 
 
 
 
  New i18n mechanism: Provide a conveniant way to get the complete list of the auto generated keys.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 28/Apr/16 11:18 AM 
 
 
 

Environment:
 
   
 
 
 

Labels:
 

 collector-0cf1239d 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Hi, 
I discussed it quickly with topher yesterday: 
I think we need to provide the possibility to get all keys of a certain module (light & non light modules) in a conveniant way. I love the new mechanis, as it prevents me of having to define all the keys in the config manually. 
But it has a big downside: The keys get generated by a certain pattern. So its hard to know for the developer, which keys will be in the end expected by Magnolia. Having to do that manually uses even more time then having to add them manually to the configuration, because there I can just use any key I want (foo.blah would work). 
There is a config that can be used to get a out for apps: config:modules/i18n/config@debug=true Then it shows the list in the ActionBar (looks awefull, but at least you have all keys needed to be translated for an app). But of course this works only for apps. Meaning that the code base would already be there, not that much of backend development needed. 
So the goal: I can tell the system "Get me a complete list of all key generated/expected by the system, to copy it manually into a empty message bundle file". This would not 

[magnolia-dev] [JIRA] (PAGES-70) Regarding page (script) rendering: Remove warn message when not rendering a 'cma:area' but a component directly in a page script.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-70 
 
 
 
  Regarding page (script) rendering: Remove warn message when not rendering a 'cma:area' but a component directly in a page script.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 TemplateWarnMessage.png 
 
 
 

Created:
 

 11/Apr/16 12:56 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
There are many situations in real projects, where page scripts needs to render components from another page.  
Situations where there are news pages in a dedicated top level tree in "website" workspace which then get concretely linked by other pages that rendered their content/components. Like a news pages pool (I'm aware that its explicit not a news content-app, as the content of such a news is different on every news page). 
Many things can be achieved, by rendering areas (their components) from other pages. 
Here a code example form the page script for reproducing the message: 

 


"en" lang="en" class="no-js">


[@cms.page /]
"viewport" 

[magnolia-dev] [JIRA] (MGNLUI-3782) TreeView: Adding a property 'value' to a node, it's node also displays the same value. (Used for StaticField)

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3782 
 
 
 
  TreeView: Adding a property 'value' to a node, it's node also displays the same value. (Used for StaticField)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 PropertyValue.png 
 
 
 

Components:
 

 forms, tree/list 
 
 
 

Created:
 

 18/Feb/16 8:57 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
The for field static expects to properties: 
 

label
 

[magnolia-dev] [JIRA] (MGNLUI-3774) Content Apps: Shoult provide a muti-capable "defaultAction" possibility.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Content Apps: Shoult provide a muti-capable "defaultAction" possibility.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3774) Content Apps: Shoult provide a muti-capable "defaultAction" possibility.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Content Apps: Shoult provide a muti-capable "defaultAction" possibility.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 We allow and explicit provide the possibility, to add and manage different JCR Nodes in one content app.But there is only one 'defaultAction" you can define on a content app.So you can have multiple different nodes in one content app, but you can't map to each of the nodes a different detail app to edit them. I think this should be provided out of the box. There is such a class/Action in Jan's twigs already.   
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3774) Content Apps: Shoult provide a muti-capable "defaultAction" possibility.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Content Apps: Shoult provide a muti-capable "defaultAction" possibility.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 content app 
 
 
 

Created:
 

 16/Feb/16 9:28 AM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
We allow and explicit provide the possibility, to add and manage different JCR Nodes in one content app. But there is only one 'defaultAction" you can define on a content app. So you can have multiple different nodes in one content app, but you can't map to each of the nodes a different detail app to edit them. I think this should be 

[magnolia-dev] [JIRA] (MGNLDEMO-144) Make the w3 validation proof: Mainly the earch result page.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-144 
 
 
 
  Make the w3 validation proof: Mainly the earch result page.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLDEMO-144) Make the w3 validation proof: Mainly the earch result page.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-144 
 
 
 
  Make the w3 validation proof: Mainly the earch result page.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 0.8.1, 0.9, 0.8 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 magnolia-travels 
 
 
 

Created:
 

 09/Feb/16 11:15 AM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Checking the travels demo's search result page w3 validation errors show up: https://validator.w3.org/nu/?doc=https%3A%2F%2Fdemopublic.magnolia-cms.com%2Ftravel%2Fmeta%2Fsearch-results.html%3FqueryStr%3Dtours 
One reason is a missing  in the searchResults.ftl (see print screen). But also because it uses result html snippets within "" created by info.magnolia.jackrabbit.lucene.SearchHTMLExcerpt there are invalid strcutres creaded, such as P-tags around a div: 

 

[magnolia-dev] [JIRA] (MGNLDEMO-144) Make the w3 validation proof: Mainly the earch result page.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-144 
 
 
 
  Make the w3 validation proof: Mainly the earch result page.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 searchResults.ftl.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-14) LightModule resources life distribution: Define a conveniant best practice

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-14 
 
 
 
  LightModule resources life distribution: Define a conveniant best practice  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Christopher Zimmermann 
 
 
 

Created:
 

 25/Jan/16 2:31 PM 
 
 
 

Environment:
 
   
 
 
 

Labels:
 

 collector-0cf1239d 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Using light module development approach for front end leaves a couple of questions open in regards of: How to use it and distribute changes on life systems. 
A main problems I see is: 
 

how to guarantie that the newest changes in light modules are distributed 100% equally trough all instances?
 

how can a customer know which node has wich state of resources loaded? (How can I be sure public2 has the same resources as public1 or public3).
 

When setting magnolia.develop=false changes in the light modules (file system) are detected, BUT the JS & CSS is still served cached. And we have no mechanism to flush the caceh on public instances (except activating something).
 
 
My suggestion: We could define a simple best practice approach: They are observed & loaded & managed on the author, and 

[magnolia-dev] [JIRA] (MGNLUI-3745) Pages Detail-App: Missing & strange ActionBar behaviour with missing cms:page and/or cma:area directives

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3745 
 
 
 
  Pages Detail-App: Missing & strange ActionBar behaviour with missing cms:page and/or cma:area directives  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 During training material creation I have encountered bad and strange behavior of the ActionBar of the page's detail subApp.*Generally:*When using a script not containing cms:page and cms:area no ActionBar is displayed in the page's detail app.I think this can be defined as a bug -> why should the outer Content App framework react in its ActianBar to the inner rendered item within the subApps workbench?=> the ActionBar should always be there.*Reproduce:*- Create a type Freemarker page template-- Have a 'main' area of type 'list' in it-- Don’t add any components into the main (no component content)- Use this code in its script:{code} [#--[@cms.page /]--] Hello Test [#--[@cms.area name="main" /]--]{code}Be aware:The cms:page and cms:area are commented out. I will use them for the different scenario explanation.*Situation 1.: Bug*(Use the code as it is)Setup:Mode of editor: view or edit the samecms:page -> NOT usedcms:area -> NOT usedResult: No ActionBar*Situation 2.: Strange behaviour (Bug)*Setup:Mode of editor: *view*cms:page -> NOT usedcms:area -> IS usedResult: - Has ActionBar, but wrong -> as if you had clicked on the area itself- BUT the area itself is not rendered *Situation 3.: Strange behaviour (Bug)*Setup:Mode of editor: *edit*cms:page -> NOT usedcms:area -> IS usedResult: - Has ActionBar, but wrong -> it does not change from the 'view' state. Still having "Preview Page". But its not reacting at all, not able to switch back to the 'view' mode.- BUT the area itself is not rendered*Situation 4.: Correct behaviour*Setup:Mode of editor: *edit* and *view*cms:page -> IS usedcms:area -> NOT usedResult: Correct behaviour*Situation 5.: Correct behaviour*Setup:Mode of editor: *edit* and *view*cms:page -> IS usedcms:area -> IS usedResult: Correct behaviour, also the area is rendered as expected.h5. For a second round of test scenarios use now this code:{code}[#--[@cms.page /]--]Hello Test[#--[@cms.area name="main" /]--]{code}Be aware again:The cms:page and cms:area are commented out. I will use them for the different scenario explanation.*Situation 6.: Bug*(Use the code as it is)Setup:Mode of editor: view or edit the samecms:page -> NOT usedcms:area -> NOT usedResult:Same as in situation 1. (Problem)*Situation 7.: Strange behaviour (Bug)*Setup:Mode of editor: *view*cms:page -> NOT usedcms:area -> IS usedResult: Same as in situation 2. (Problem) *Situation 8.: Strange behaviour (Bug)*Setup:Mode of editor: *edit*cms:page -> NOT usedcms:area -> IS usedResult: Same as in situation 3. (Problem)*Situation 9.: Correct behaviour*Setup:Mode of editor: *edit* and *view*cms:page -> IS usedcms:area -> NOT usedResult: Same as in situation 4. (Correct)*Situation 10.: Correct behaviour*Setup:Mode of editor: *edit* and *view*cms:page -> IS usedcms:area -> IS usedResult:  {color:red} Different {color}  to situation 5.- Same behaviour with the ActionBar as in Situation 2.- Main problem: the area-bar itself is not rendered at all.=> I think with even no html doc tag etc the area 

[magnolia-dev] [JIRA] (MGNLUI-3745) Pages Detail-App: Missing & strange ActionBar behaviour with missing cms:page and/or cma:area directives

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3745 
 
 
 
  Pages Detail-App: Missing & strange ActionBar behaviour with missing cms:page and/or cma:area directives  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.3 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 page editor, pages app 
 
 
 

Created:
 

 12/Jan/16 12:36 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
During training material creation I have encountered bad and strange behavior of the ActionBar of the page's detail subApp. 
Generally: When using a script not containing cms:page and cms:area no ActionBar is displayed in the page's detail app. I think this can be defined as a bug -> why should the outer Content App framework react in its ActianBar to the inner rendered item within the subApps workbench? => the ActionBar should always be there. 
Reproduce: 
 

[magnolia-dev] [JIRA] (MGNLDEMO-127) 5.4 STK Demo: ClientCallBack of PUR doesn't work anymore

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-127 
 
 
 
  5.4 STK Demo: ClientCallBack of PUR doesn't work anymore  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 24/Nov/15 12:16 PM 
 
 
 

Labels:
 

 STK 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Jan told me to create the issue in here, also for the STK demo. 
The clientCallback of the PUR does not work. But I'm quite sure it worked before when I tested it and used it in the last training -> so I think its not a problem of PUR or the client callback, but of the demo itself. 
When calling this page/URL:  https://demopublic-stk.magnolia-cms.com/members-area/protected.html The normal Magnolia login form appears, instead of this one:  https://demopublic-stk.magnolia-cms.com/members-area/login.html 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3636) Security App: Provide the possiblity to see what users are memebers of a certain group.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3636 
 
 
 
  Security App: Provide the possiblity to see what users are memebers of a certain group.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.2, 5.3.11 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 security app 
 
 
 

Created:
 

 28/Oct/15 4:20 PM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Currently its impossible to find out over our AdminCnentral & Apps, what users are members of a certain group. 
This is a very default behavior of almost any other systems, finding out what users are a part of a certain group. And for an administrator (think at 

[magnolia-dev] [JIRA] (MGNLUI-3614) Tests needed: Chrome & Windows & AdminCnetral JCR Tree is not usable at all.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3614 
 
 
 
  Tests needed: Chrome & Windows & AdminCnetral JCR Tree is not usable at all.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.2, 5.4.1, 5.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 admincentral, content app, design 
 
 
 

Created:
 

 05/Oct/15 12:20 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Chrome on Windows is not usable. A lot of problems appear, also depends a bit on which Windows version. I can confirm various problems on Chrome & Windows7 and Windows8. 
Examples: 
 

Screen does not refresh after creation of nodes and properties
 

Tree is not clickable at all after a short while
 

[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] (MGNLSITE-38) Provide in SiteFunctions: Nested call to get theme and additonal null handling.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-38 
 
 
 
  Provide in SiteFunctions: Nested call to get theme and additonal null handling.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Component/s:
 
 api 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-38) Provide in SiteFunctions: Nested call to get theme and additonal null handling.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-38 
 
 
 
  Provide in SiteFunctions: Nested call to get theme and additonal null handling.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Affects Version/s:
 
 1.0.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-38) Provide in SiteFunctions: Nested call to get theme

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-38 
 
 
 
  Provide in SiteFunctions: Nested call to get theme  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 When you need the current configured theme you need to retrieve it with two calls:{code}[#assign currentSite = sitefn.site(content)][#assign currentTheme = sitefn.theme(currentSite)]//Clear, you can also do it in one line of code, but its still two calls:[#assign currentTheme = sitefn.theme(sitefn.site(content)))]{code}Which is a bit confusing for beginners. And also its more error prone and less straight forward.It would be easy to provide it in one method fir getting the theme accepting Node, doing the nested call:{code}[#assign currentTheme = sitefn.theme(content)]{code}Would look like this:{code}public Theme theme(Node content) { if(content == null) return null; Site site = this.site(content); return (site == null) ? null : this.theme(site);}{code}I included a patch containing the code, and also a version for ContentMap.Also I added some missing null handling in :{code}{code}And{code}{code}  the 'getTheme(Node content)' 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-38) Provide in SiteFunctions: Nested call to get theme and additonal null handling.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-38 
 
 
 
  Provide in SiteFunctions: Nested call to get theme and additonal null handling.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 When you need the current configured theme you need to retrieve it with two calls:{code}[#assign currentSite = sitefn.site(content)][#assign currentTheme = sitefn.theme(currentSite)]//Clear, you can also do it in one line of code, but its still two calls:[#assign currentTheme = sitefn.theme(sitefn.site(content)))]{code}Which is a bit confusing for beginners. And also its more error prone and less straight forward.It would be easy to provide it in one method fir getting the theme accepting Node, doing the nested call:{code}[#assign currentTheme = sitefn.theme(content)]{code}Would look like this:{code}public Theme theme(Node content) { if(content == null) return null; Site site = this.site(content); return (site == null) ? null : this.theme(site);}{code}I included a patch containing the code, and also a version for ContentMap.Also I added some missing null handling in:{code} public Theme theme(Site site) { code}  And // site.getTheme().getName(); will produce NPE {code} And {code}  the 'getTheme public Site site ( Node ContentMap  content) '  {  // content.getJCRNode(); will produce NPE{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: 

[magnolia-dev] [JIRA] (MGNLSITE-38) Provide in SiteFunctions: Nested call to get theme and additonal null handling.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-38 
 
 
 
  Provide in SiteFunctions: Nested call to get theme and additonal null handling.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Summary:
 
 Provide in SiteFunctions: Nested call to get theme  and additonal null handling. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-38) Provide in SiteFunctions: Nested call to get theme

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-38 
 
 
 
  Provide in SiteFunctions: Nested call to get theme  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 15/Sep/15 2:05 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
When you need the current configured theme you need to retrieve it with two calls: 

 

[#assign currentSite = sitefn.site(content)]
[#assign currentTheme = sitefn.theme(currentSite)]

//Clear, you can also do it in one line of code, but its still two calls:
[#assign currentTheme = sitefn.theme(sitefn.site(content)))]
 

 
Which is a bit confusing for beginners. And also its more error prone and less straight forward. 
It would be easy to provide it in one method fir getting the theme accepting Node, doing the nested call: 

 

[#assign currentTheme = sitefn.theme(content)]
 

 
Would look like this: 

 

public Theme theme(Node content) {
	if(content == null) return null;
	Site site = this.site(content);
	return (site == null) ? null : this.theme(site);
}
 

 
I included a patch containing the code, and also a version for ContentMap. Also I added some 

[magnolia-dev] [JIRA] (MGNLSITE-38) Provide in SiteFunctions: Nested call to get theme and additonal null handling.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-38 
 
 
 
  Provide in SiteFunctions: Nested call to get theme and additonal null handling.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 When you need the current configured theme you need to retrieve it with two calls:{code}[#assign currentSite = sitefn.site(content)][#assign currentTheme = sitefn.theme(currentSite)]//Clear, you can also do it in one line of code, but its still two calls:[#assign currentTheme = sitefn.theme(sitefn.site(content)))]{code}Which is a bit confusing for beginners. And also its more error prone and less straight forward.It would be easy to provide it in one method fir getting the theme accepting Node, doing the nested call:{code}[#assign currentTheme = sitefn.theme(content)]{code}Would look like this:{code}public Theme theme(Node content) { if(content == null) return null; Site site = this.site(content); return (site == null) ? null : this.theme(site);}{code}I included a patch containing the code, and also a version for ContentMap.  Also I added  into the patch  some missing null handling in:{code}public Theme theme(Site site) {// site.getTheme().getName(); will produce NPE{code}And{code}public Site site(ContentMap content) {// content.getJCRNode(); will produce NPE{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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, 

[magnolia-dev] [JIRA] (MGNLSITE-38) Provide in SiteFunctions: Nested call to get theme and additonal null handling.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-38 
 
 
 
  Provide in SiteFunctions: Nested call to get theme and additonal null handling.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 SiteFunctions-MGNLSITE-38.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-38) Provide in SiteFunctions: Nested call to get theme and additonal null handling.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-38 
 
 
 
  Provide in SiteFunctions: Nested call to get theme and additonal null handling.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 site-MGNLSITE-38.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-38) Provide in SiteFunctions: Nested call to get theme and additonal null handling.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-38 
 
 
 
  Provide in SiteFunctions: Nested call to get theme and additonal null handling.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 site-MGNLSITE-38.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3539) Favorites: After opening a bookmark in favorites, most clicks don't react anymore

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3539 
 
 
 
  Favorites: After opening a bookmark in favorites, most clicks don't react anymore  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.1, 5.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 favorites 
 
 
 

Created:
 

 31/Aug/15 11:49 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Reproduce: 
Create a link in Favorites. Try to use it (sometimes works the first time). 
Then try to use it again, or close an app. depended on the OS and the browser sometimes all clicks are hooked, or just certain. But what appears in all situations not to work is: 
 

Favorites can't be clicked again
 

  

[magnolia-dev] [JIRA] (MGNLSITE-28) Provide an app to CRUD themes

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-28 
 
 
 
  Provide an app to CRUD themes  
 
 
 
 
 
 
 
 
 
 
Work around: Here the two bootstrap files needed to add them manually if the App is needed. 
For Product: Attention, they contain hard-coded labels. The rest is 1:1 the Site App with the needed change 
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 config.modules.ui-admincentral.config.appLauncherLayout.groups.stk.apps.theme.xml 
 
 
 

Attachment:
 
 config.modules.site-app.apps.theme.xml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-26) Don't allow freemarker page templates to be added into an explicit mapped site.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-26 
 
 
 
  Don't allow freemarker page templates to be added into an explicit mapped site.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.0 
 
 
 

Assignee:
 
 Philip Mundt 
 
 
 

Attachments:
 

 SiteAwareTemplateAvailability.patch 
 
 
 

Components:
 

 api 
 
 
 

Created:
 

 10/Aug/15 10:51 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
The current implementation of SiteAwareTemplateAvailability  ConfiguredSiteTemplateAvailability does not allow you to achieve following: 
 

Filter out pages of renderType freemarker.
 
 
This means: If you add a freemarker page into any module, it will be available in any site of the whole system. No way you can filter them out via site.getTemplates().getAvailability(). 
The 

[magnolia-dev] [JIRA] (MGNLSITE-26) Don't allow freemarker page templates to be added into an explicit mapped site.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-26 
 
 
 
  Don't allow freemarker page templates to be added into an explicit mapped site.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 SiteAwareTemplateAvailability.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-26) Don't allow freemarker page templates to be added into an explicit mapped site.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-26 
 
 
 
  Don't allow freemarker page templates to be added into an explicit mapped site.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 SiteAwareTemplateAvailability.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLUI-3505) Disapearing ActionBar on freemarker errors and/or missing html headbody markup

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3505 
 
 
 
  Disapearing ActionBar on freemarker errors and/or missing html headbody markup  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4, 5.3.10 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 page editor, pages app 
 
 
 

Created:
 

 23/Jul/15 2:35 PM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Problem: Sometimes on freemarker errors in page/component scripts the right hand ActionBar has no Actions anymore. 
I have seen this also in trainings. Also other support cases were opened with this problem. But we were never able to break it down into a reproducible situation 

[magnolia-dev] [JIRA] (MGNLUI-3501) Add possibility to force users to change passwords periodically

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3501 
 
 
 
  Add possibility to force users to change passwords periodically  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4, 5.3.10 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 security app 
 
 
 

Created:
 

 22/Jul/15 4:52 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
A customer in support asked this: Is it possible to force used to change periodically their passwords? for example all 30 days 
I think this is a interesting requirement from which many projects could benefit. 
What also would make sense is: Manually invalidate a users password and force him to set a new one. So not periodically, just once where it needs to be ensured that a new password is set by the user once. 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-310) Unplushing a page breaks the workflow. No workflows can be triggered until restart. Unpublishing not possible at all.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-310 
 
 
 
  Unplushing a page breaks the workflow. No workflows can be triggered until restart. Unpublishing not possible at all.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 Reproduce:-Downloadthe5.4bundledeploy-Publishapage-UnpublishthesamepageUnpublishing(approvingtheunpublishing)resultsthiserror:{code}2015-07-2110:54:55,169WARNinfo.magnolia.event.SimpleEventBus:Exceptioncaughtwhendispatchingaclassinfo.magnolia.task.event.TaskEventeventwithclassinfo.magnolia.module.workflow.jbpm.humantask.ProcessTaskEventHandlereventHandler.org.jbpm.workflow.instance.WorkflowRuntimeException:[info.magnolia.workflow.Publication:1,437,468,825,294-:9]--ExceptionwhentryingtoevaluateconstraintAbortedinsplit atorg.jbpm.workflow.instance.node.SplitInstance.internalTrigger(SplitInstance.java:67) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:364) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:323) atorg.jbpm.workflow.instance.node.JoinInstance.triggerCompleted(JoinInstance.java:266) atorg.jbpm.workflow.instance.node.JoinInstance.internalTrigger(JoinInstance.java:62) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:364) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerConnection(NodeInstanceImpl.java:379) atorg.jbpm.workflow.instance.node.SplitInstance.executeStrategy(SplitInstance.java:117) atorg.jbpm.workflow.instance.node.SplitInstance.internalTrigger(SplitInstance.java:63) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:364) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:323) atorg.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:73) atorg.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:44) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35) atorg.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:236) atorg.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:389) atorg.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:195) atorg.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:204) atorg.drools.core.impl.StatefulKnowledgeSessionImpl.startProcessInstance(StatefulKnowledgeSessionImpl.java:1911) atorg.drools.core.command.runtime.process.StartProcessInstanceCommand.execute(StartProcessInstanceCommand.java:52) atorg.drools.core.command.runtime.process.StartProcessInstanceCommand.execute(StartProcessInstanceCommand.java:29) atorg.drools.core.command.impl.DefaultCommandService.execute(DefaultCommandService.java:36) 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-310) Unplushing a page breaks the workflow. No workflows can be triggered until restart. Unpublishing not possible at all.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-310 
 
 
 
  Unplushing a page breaks the workflow. No workflows can be triggered until restart. Unpublishing not possible at all.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Labels:
 
 Support 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLWORKFLOW-310) Unplushing a page breaks the workflow. No workflows can be triggered until restart. Unpublishing not possible at all.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-310 
 
 
 
  Unplushing a page breaks the workflow. No workflows can be triggered until restart. Unpublishing not possible at all.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 Reproduce:-Downloadthe 5.4 bundledeploy-Publishapage-UnpublishthesamepageUnpublishing(approvingtheunpublishing)resultsthiserror:{code}2015-07-2110:54:55,169WARNinfo.magnolia.event.SimpleEventBus:Exceptioncaughtwhendispatchingaclassinfo.magnolia.task.event.TaskEventeventwithclassinfo.magnolia.module.workflow.jbpm.humantask.ProcessTaskEventHandlereventHandler.org.jbpm.workflow.instance.WorkflowRuntimeException:[info.magnolia.workflow.Publication:1,437,468,825,294-:9]--ExceptionwhentryingtoevaluateconstraintAbortedinsplit atorg.jbpm.workflow.instance.node.SplitInstance.internalTrigger(SplitInstance.java:67) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:364) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:323) atorg.jbpm.workflow.instance.node.JoinInstance.triggerCompleted(JoinInstance.java:266) atorg.jbpm.workflow.instance.node.JoinInstance.internalTrigger(JoinInstance.java:62) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:364) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerConnection(NodeInstanceImpl.java:379) atorg.jbpm.workflow.instance.node.SplitInstance.executeStrategy(SplitInstance.java:117) atorg.jbpm.workflow.instance.node.SplitInstance.internalTrigger(SplitInstance.java:63) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:364) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:323) atorg.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:73) atorg.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:44) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35) atorg.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:236) atorg.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:389) atorg.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:195) atorg.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:204) atorg.drools.core.impl.StatefulKnowledgeSessionImpl.startProcessInstance(StatefulKnowledgeSessionImpl.java:1911) atorg.drools.core.command.runtime.process.StartProcessInstanceCommand.execute(StartProcessInstanceCommand.java:52) atorg.drools.core.command.runtime.process.StartProcessInstanceCommand.execute(StartProcessInstanceCommand.java:29) atorg.drools.core.command.impl.DefaultCommandService.execute(DefaultCommandService.java:36) 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-310) Unplushing a page breaks the workflow. No workflows can be triggered until restart. Unpublishing not possible at all.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-310 
 
 
 
  Unplushing a page breaks the workflow. No workflows can be triggered until restart. Unpublishing not possible at all.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 jBPM 
 
 
 

Created:
 

 21/Jul/15 11:00 AM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Reproduce: 
 

Download the bundle  deploy
 

Publish a page
 

Unpublish the same page
 
 
Unpublishing (approving the unpublishing) results this error: 

 

2015-07-21 10:54:55,169 WARN  info.magnolia.event.SimpleEventBus: Exception caught when 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-310) Unplushing a page breaks the workflow. No workflows can be triggered until restart. Unpublishing not possible at all.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-310 
 
 
 
  Unplushing a page breaks the workflow. No workflows can be triggered until restart. Unpublishing not possible at all.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 Reproduce:-Downloadthe5.4bundledeploy-Publishapage-Unpublishthesamepage Canalsobereproducedonourdemo. Unpublishing(approvingtheunpublishing)resultsthiserror:{code}2015-07-2110:54:55,169WARNinfo.magnolia.event.SimpleEventBus:Exceptioncaughtwhendispatchingaclassinfo.magnolia.task.event.TaskEventeventwithclassinfo.magnolia.module.workflow.jbpm.humantask.ProcessTaskEventHandlereventHandler.org.jbpm.workflow.instance.WorkflowRuntimeException:[info.magnolia.workflow.Publication:1,437,468,825,294-:9]--ExceptionwhentryingtoevaluateconstraintAbortedinsplit atorg.jbpm.workflow.instance.node.SplitInstance.internalTrigger(SplitInstance.java:67) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:364) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:323) atorg.jbpm.workflow.instance.node.JoinInstance.triggerCompleted(JoinInstance.java:266) atorg.jbpm.workflow.instance.node.JoinInstance.internalTrigger(JoinInstance.java:62) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:364) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerConnection(NodeInstanceImpl.java:379) atorg.jbpm.workflow.instance.node.SplitInstance.executeStrategy(SplitInstance.java:117) atorg.jbpm.workflow.instance.node.SplitInstance.internalTrigger(SplitInstance.java:63) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:364) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:323) atorg.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:73) atorg.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:44) atorg.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:171) atorg.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35) atorg.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:236) atorg.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:389) atorg.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:195) atorg.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:204) atorg.drools.core.impl.StatefulKnowledgeSessionImpl.startProcessInstance(StatefulKnowledgeSessionImpl.java:1911) atorg.drools.core.command.runtime.process.StartProcessInstanceCommand.execute(StartProcessInstanceCommand.java:52) atorg.drools.core.command.runtime.process.StartProcessInstanceCommand.execute(StartProcessInstanceCommand.java:29) atorg.drools.core.command.impl.DefaultCommandService.execute(DefaultCommandService.java:36) 

[magnolia-dev] [JIRA] (MGNLUI-3473) Tranformer for TwinColumnField: Provide transformers alike the DelegatingMultiValueFieldTransformer and DelegatingMultiValueSubnodeTransformer for the TwinColumnFi

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3473 
 
 
 
  Tranformer for TwinColumnField: Provide transformers alike the DelegatingMultiValueFieldTransformer and DelegatingMultiValueSubnodeTransformer for the TwinColumnField  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.3.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 forms 
 
 
 

Created:
 

 25/Jun/15 2:46 PM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
The TwinColumnField (actually a ComboBox) stores the data by default into a JCR MultiValue property. Same as the as the MultiField does by default. 
There is also the need for TwinColumnField to have this 

[magnolia-dev] [JIRA] (MGNLUI-3339) Vaadin Communication Problem error message on slow connections

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3339 
 
 
 
  Vaadin Communication Problem error message on slow connections  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Labels:
 
 OnDemand support 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLWORKFLOW-302) Provide Configurable E-Mail based workflow out of the box: Provide solid replacement for openWFE e-mail sending workflow.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-302 
 
 
 
  Provide Configurable E-Mail based workflow out of the box: Provide solid replacement for openWFE e-mail sending workflow.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.5, 5.3.5, 5.2.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 jBPM 
 
 
 

Created:
 

 28/May/15 9:41 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
IN 4.5 we had a OpenWFE workflow, where the customers were able to have Emials send by the single steps very simply. All they had to do was uncomment a part in the workflow definition. 
I'm aware that JBPM workflow is much more powerful, but also less flexible as it needs to be compiled and so on. 
But the simple use case sending an EMail is so widely common, that it can't be that every client needs to create their own workflow implementation just to sent a email. It just sending an email, and almost everybody would like to have/use this. 
I am aware of this: https://academy.magnolia-cms.com/display/MA/M3+Custom+workflows+in+5.3+plus But its not really helping. T mail addresses to use are simply coded in the Java code, not a real help for a real use case in a project. Usually the ones triggering a workflow and the once 

[magnolia-dev] [JIRA] (MGNLUI-3446) RichTextField: reguired=true validator is ignored when using a jsConfig file

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3446 
 
 
 
  RichTextField: reguired=true validator is ignored when using a jsConfig file   
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Summary:
 
 RichTextField:reguired=truevalidatoris if ignored whenusingajsConfigfile 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLUI-3446) RichTextField: reguired=true validator is if when using a jsConfig file

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3446 
 
 
 
  RichTextField: reguired=true validator is if when using a jsConfig file   
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Summary:
 
 RichTextField:reguired=truevalidatoris ifnored if whenusingajsConfigfile 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLUI-3446) RichTextField: reguired=true validator is ifnored when using a jsConfig file

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3446 
 
 
 
  RichTextField: reguired=true validator is ifnored when using a jsConfig file   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.3.8 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 dialogs, forms 
 
 
 

Created:
 

 27/May/15 12:46 PM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
When using a jsConfigFile the required validator is ignored. 
This is NOT related to MGNLUI-3445 as it also happens on new creating component where there is not property yet. 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3445) RichTextField: Emptying the fields content and saving does not remove the property, just empties it - reuired validation does not work

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3445 
 
 
 
  RichTextField: Emptying the fields content and saving does not remove the property, just empties it - reuired validation does not work  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.3.8 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 dialogs, forms 
 
 
 

Created:
 

 27/May/15 12:39 PM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
When removing the content of an existing RichTextField and saving, the property is not removed but just emptied. 
This has as a consequence, that the required=true validator is not reacting, it accepts as the property exists. 
   

[magnolia-dev] [JIRA] (MGNLUI-3443) Trinity Icons: Consider labeling the trinity icons.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3443 
 
 
 
  Trinity Icons: Consider labeling the trinity icons.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.3.8 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 admincentral, design 
 
 
 

Created:
 

 26/May/15 3:54 PM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Consider labeling the trinity Icons. 
The input comes form a support case: SUPPORT-4663 
Summarized (for more details see support case):  For beginners of the system it is quite unclear, what the trinity icons are for. 
  

[magnolia-dev] [JIRA] (MGNLDEMO-23) Dialogs: Don't use extends for no reson (or some might possible future easons)

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-23 
 
 
 
  Dialogs: Don't use extends for no reson (or some might possible future easons)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.0 
 
 
 

Assignee:
 
 Philip Mundt 
 
 
 

Attachments:
 

 Demo_TextImage_DialogExtends.png 
 
 
 

Components:
 

 magnolia-travels 
 
 
 

Created:
 

 06/May/15 12:13 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Something that killed STK is the way to complex referencing of configurations via extends. 
Extends is a really cool feature, if there is a good reason to use it (real need of variations). But until there is a real need of it, using if for future possible extensions is contradicting this: 
 

the goal should be that it is straight forward and by this easy to understand for beginners
 
 
 

[magnolia-dev] [JIRA] (MTE-20) Don't store html elements in website workspace, use named/speaking headlineLevels instead

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-20 
 
 
 
  Don't store html elements in website workspace, use named/speaking headlineLevels instead  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Summary:
 
 Don'tstorehtmlelementsinwebsiteworkspace,usenamed /speaking headlineLevelsinstead 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-20) Don't store html elements in website workspace, use named headlineLevels instead

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-20 
 
 
 
  Don't store html elements in website workspace, use named headlineLevels instead  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 Demo_TxtImage_CurrentImpl_HeadinLevels.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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




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] (MGNLDEMO-22) Freemarker Scripts: Should be simplified and best practices should be used

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-22 
 
 
 
  Freemarker Scripts: Should be simplified and best practices should be used  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Philip Mundt 
 
 
 

Components:
 

 magnolia-travels 
 
 
 

Created:
 

 06/May/15 11:50 AM 
 
 
 

Fix Versions:
 

 1.0 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
I see in many scripts parts which are either too complicated or do not use scripting best practices. This should be changes to make the readability and understandability much better. 
One example (textImage.ftl): Original 

 

[#assign headingLevel = h2]
[#if content.headingLevel?has_content]
[#assign headingLevel = content.headingLevel]
[/#if]

[#if content.headline?has_content]
${headingLevel}${content.headline!}/${headingLevel}
[/#if]
 

 
Replacing with (using properly !): 

 

[#assign headingLevel = content.headingLevel!h2]
[#if content.headline?has_content]

[magnolia-dev] [JIRA] (PAGES-16) Pages Brwoser SubApp: Pages can't be moved

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia pages module /  PAGES-16 
 
 
 
  Pages Brwoser SubApp: Pages can't be moved  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.x 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 

Created:
 

 31/Mar/15 1:14 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Version 5.4-m4 
Pages can not be moved in the page's browser sub app. Not with drag  drop nor with the move action. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This 

[magnolia-dev] [JIRA] (PAGES-16) Pages Browser SubApp: Pages can't be moved

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia pages module /  PAGES-16 
 
 
 
  Pages Browser SubApp: Pages can't be moved  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Summary:
 
 Pages Brwoser Browser SubApp:Pagescan'tbemoved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (DOCU-547) URL selectors should be documented

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 created  DOCU-547


URL selectors should be documented















Issue Type:


Task



Assignee:


Antti Hietala



Components:


content



Created:


13/Jan/15 2:31 PM



Description:


URL selectors should be documented.

It was mentioned in SUPPORT-4305 see Milan's comment of 12/Jan/15 12:34 PM

I hope its correct that I create an issue here regarding this.




Project:


Documentation



Labels:


support




Priority:


Neutral




Reporter:


Christian Ringele




























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] (MGNLUI-3290) Field properties: Combination of i18n=true readOnly=true results in Exception Dialog or subApp does not open.

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 created  MGNLUI-3290


Field properties: Combination of i18n=true  readOnly=true results in Exception  Dialog or subApp does not open.















Issue Type:


Bug



Affects Versions:


5.3.5



Assignee:


Unassigned


Attachments:


Form-readOnly-ContactsApp.png, Form-readOnly-TextImageDialog.png



Components:


forms



Created:


10/Dec/14 9:51 AM



Description:


The combination of these two properties on a form field does not work:

	i18n = true
	readOnly = true



The the detail subapp of the contacts app does not open and trows:


2014-12-10 09:49:48,033 ERROR agnolia.ui.framework.app.AppInstanceControllerImpl: Sub-app detail failed to start: Invocation of method valueChange in info.magnolia.ui.dialog.formdialog.ItemFormView$2 failed.
com.vaadin.event.ListenerMethod$MethodException: Invocation of method valueChange in info.magnolia.ui.dialog.formdialog.ItemFormView$2 failed.
	at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:528)
	at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:167)
	at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:969)
	at com.vaadin.ui.AbstractField.fireValueChange(AbstractField.java:1126)
	at com.vaadin.ui.AbstractField.setValue(AbstractField.java:542)
	at com.vaadin.ui.AbstractSelect.setValue(AbstractSelect.java:702)
	at com.vaadin.ui.AbstractSelect.setValue(AbstractSelect.java:671)
	at info.magnolia.ui.dialog.formdialog.ItemFormView.setCurrentLocale(ItemFormView.java:143)
	at info.magnolia.ui.dialog.formdialog.FormBuilder.buildForm(FormBuilder.java:132)
	at info.magnolia.ui.contentapp.detail.DetailPresenter.setItemView(DetailPresenter.java:159)
	at info.magnolia.ui.contentapp.detail.DetailPresenter.start(DetailPresenter.java:138)
	at info.magnolia.ui.contentapp.detail.DetailEditorPresenter.start(DetailEditorPresenter.java:122)
	at info.magnolia.ui.contentapp.detail.DetailEditorPresenter.start(DetailEditorPresenter.java:101)
	at info.magnolia.ui.contentapp.detail.DetailSubApp.start(DetailSubApp.java:118)
	at info.magnolia.ui.contentapp.detail.DetailSubApp.start(DetailSubApp.java:1)



In the textImage component the dialog does not open and trwos:


2014-12-10 09:51:04,699 ERROR info.magnolia.pages.app.editor.PageEditorPresenter: An error occurred while executing action [editComponent]
info.magnolia.ui.api.action.ActionExecutionException: Action execution failed for action: editComponent
	at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:64)
	at info.magnolia.pages.app.editor.PageEditorPresenter.onAction(PageEditorPresenter.java:127)
	at info.magnolia.ui.vaadin.editor.PageEditor$1.editComponent(PageEditor.java:93)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:168)
	at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:118)
	at com.vaadin.server.communication.ServerRpcHandler.handleBurst(ServerRpcHandler.java:214)
	at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:111)
	at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(UidlRequestHandler.java:91)
	at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:37)
	at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1371)
	at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:238)






Project:


Magnolia UI



Priority:


Neutral




 

[magnolia-dev] [JIRA] (MGNLUI-3283) Search View value: Don't reset search value after load of the tree view's content

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 created  MGNLUI-3283


Search View value: Dont reset search value after load of the tree views content















Issue Type:


Improvement



Affects Versions:


5.3.5, 5.2.10



Assignee:


Unassigned


Components:


content app



Created:


04/Dec/14 10:53 AM



Description:


Example form the Contacts app:
"When having a lot of contacts in the contacts app, the tree view might load a while.
Imagine a scenario, where the editor enters a search term into the search field before the tree load completes.
Unfortunately, the search field is reset after load is completed and the search term must be entered again."

It would be great, if the search term would not be resetted after the tree view loading is finished.




Project:


Magnolia UI



Labels:


support




Priority:


Neutral




Reporter:


Christian Ringele




























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] (MGNLUI-3283) Search View value: Don't reset search value after initial load of the tree view's content

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLUI-3283


Search View value: Dont reset search value after initial load of the tree views content
















Change By:


Christian Ringele
(04/Dec/14 10:54 AM)




Summary:


SearchViewvalue:Dontresetsearchvalueafter
initial
loadofthetreeviewscontent



























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] (MGNLUI-3240) UI From: Add cross field validation feature

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLUI-3240


UI From: Add cross field validation feature
















Change By:


Christian Ringele
(04/Nov/14 1:50 PM)




Description:


Crossfieldvalidationwouldbeahelpfulfeatureinmanyusecases.Herethreeexamples:1.Ifyouenteravalueforanassetfield,youalsomustprovideavaluefortheassetdescriptionfieldthatispresentinthedialog.2.IntheCompositefieldPointofinterest,youmustalwaysfillinalongitudeandalatitude,orleavebothempty.3.Twofields,ageparentsnames:Ifage18onemustenteraparentsname.Thiswouldbeaveryhelpfulfeaturetomaketheusageofformsmoreflexible.IhavecreatedanissuewhereItriedacrossfieldvalidationonaCompositeField(constrainedscope)asaPOC,thePOCwouldbeusable:

MGNLUI-3241



























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] (MGNLUI-3241) Composite Field: Add cross field validation between the subfields of the composite field

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 created  MGNLUI-3241


Composite Field: Add cross field validation between the subfields of the composite field















Issue Type:


New Feature



Assignee:


Unassigned


Attachments:


AllEmptyOrNoneEmpty.java, config.modules.training-templating.dialogs.myTextImage.form.tabs.tabMain.fields.pointOfInterest.xml, config.modules.ui-framework.fieldTypes.crossValidatingCompositeField.xml, CrossFieldsComparator.java, CrossFieldsValidatingCompositeField.java, CrossFieldsValidatingCompositeFieldDefinition.java, CrossFieldsValidatingCompositeFieldFactory.java



Created:


04/Nov/14 1:50 PM



Description:


Cross field validation is not a feature of the current Magnolia Form UI implementation.

I have created a general issue for requesting this feature as a general feature throughout form fields: MGNLUI-3240

In this ticket the the idea is to implement it for the CompositeField, as it would be a alternative to handle many of the use cases that occur of fields that need to be cross validated.
Possible use cases:

	A "point of interest" CompositeField with the sub-fields "Longitude' and 'Latitude'. The field is not required, BUT if in one sub field a value is entered, the other also needs a value (no value or all have a value situation).



Idea:
Extending the CompositeField by a cross field validation of its sub fields.
Overriding the validate() method and delegating to a configurable field comparator class.

POC implementation:
I tried quickly such an implementation to test if it is possible.
I created:

	CrossFieldsValidatingCompositeField.java which extends the CompositeField and its definition  factory class.
The field delegates to an implementation of the CrossFieldsComparator.java interface to do the field comparison.
	CrossFieldsComparator.java does the field comparison.
	AllEmptyOrNoneEmpty.java is the implementation for this use case, checking if one field ha a value.



Attention: This is just a POC, not product ready code! It can be used in projects, but will probably need some adaptions.

Usage:

	Add a 'fieldTypes' mapping of the FieldDefinition and the FieldFactory class. (added bootstrap file)
	Use the CrossFieldsValidatingCompositeField class for a composite field.
	Define the crossFieldsComparator property pointing to the implementation CrossFieldsComparator for the specific use case, in this case here the AllEmptyOrNoneEmpty.



Other use cases:
Just implement another version of CrossFieldsComparator.




Project:


Magnolia UI



Labels:


support




Priority:


Neutral




Reporter:


Christian Ringele



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








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] (MGNLUI-3240) UI From: Add cross field validation feature

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 created  MGNLUI-3240


UI From: Add cross field validation feature















Issue Type:


New Feature



Affects Versions:


5.3.5



Assignee:


Unassigned


Components:


forms



Created:


04/Nov/14 1:47 PM



Description:


Cross field validation would be a helpful feature in many use cases.

Here three examples:
1. If you enter a value for an asset field, you also must provide a value for the asset description field that is present in the dialog.
2. In the Composite field "Point of interest", you must always fill in a longitude and a latitude, or leave both empty.
3. Two fields, age  parents names: If age  18 one must enter a parents name.

This would be a very helpful feature to make the usage of forms more flexible.

I have created an issue where I tried a cross field validation on a CompositeField (constrained scope) as a POC, the POC would be usable: 




Project:


Magnolia UI



Labels:


support




Priority:


Neutral




Reporter:


Christian Ringele



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








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] (MGNLUI-3241) Composite Field: Add cross field validation between the subfields of the composite field

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLUI-3241


Composite Field: Add cross field validation between the subfields of the composite field
















Change By:


Christian Ringele
(04/Nov/14 1:52 PM)




Attachment:


CrossFieldsValidatingCompositeField-Configuration.jpg



























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] (MGNLUI-3227) Field Validation: Don't ignore 'required' property on the CompositeField itself.

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLUI-3227


Field Validation: Dont ignore required property on the CompositeField itself.
















Change By:


Christian Ringele
(04/Nov/14 2:17 PM)




Attachment:


CompositeField.patch



























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] (MGNLUI-3227) Field Validation: Don't ignore 'required' property on the CompositeField itself.

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLUI-3227


Field Validation: Dont ignore required property on the CompositeField itself.
















Change By:


Christian Ringele
(04/Nov/14 2:16 PM)




Attachment:


CompositeField-Required.patch



























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] (MGNLUI-3227) Field Validation: Don't ignore 'required' property on the CompositeField itself.

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLUI-3227


Field Validation: Dont ignore required property on the CompositeField itself.
















Change By:


Christian Ringele
(04/Nov/14 2:16 PM)




Attachment:


CompositeField-Required.patch



























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] (MGNLUI-3227) Field Validation: Don't ignore 'required' property on the CompositeField itself.

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLUI-3227


Field Validation: Dont ignore required property on the CompositeField itself.
















Change By:


Christian Ringele
(04/Nov/14 2:15 PM)




Description:


SettingontheCompositeFieldDefinitiontherequiredpropertyitisignored.Soifoneneedstoensurethatallfieldsinthecompositeneedtobefilledout,onemustsettoallsubfieldsarequiredproperty.Mucheasierwouldbeiftherequiredcouldbesetonthecompositeitself.Usecasedefinition:IftheCompositefieldsetsrequired=true,everysubfieldinthecompositeneedsavalue.Problem:CompositeFieldDefinitiondoesnotimplementisValid(),andthesupersisValidisonlycheckingthevalidationofthesubfields.Thiscodesolvestheproblem,Iincludedapatch.{code}@OverridepublicbooleanisValid(){booleanisValid=super.isValid();if(this.isRequired()){
//Ifrequiredissetonthecompositeitselfthenitchecks
if
oneofthesub-fieldsisempty-allmusthaveavalueListAbstractFieldPropertysetItemfields=getFields
(
this,false);for(AbstractFieldPropertysetItemfield:fields){if(
isEmpty()){isValid=false;}}
}
returnisValid;}{code}



























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] (MGNLUI-3227) Field Validation: Don't ignore 'required' property on the CompositeField itself.

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLUI-3227


Field Validation: Dont ignore required property on the CompositeField itself.
















Change By:


Christian Ringele
(04/Nov/14 2:17 PM)




Attachment:


CompositeField.patch



























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