[magnolia-dev] [JIRA] (NPMCLI-25) Local mgnl cli configuration should be used automatically

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-25 
 
 
 
  Local mgnl cli configuration should be used automatically  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 When running the mgnl command, use the mgnl cli config file (ie mgnl-config.json) in the current directory or any of its parents. If none exists, then fall back to the global one defined by the MGNLCLI_HOME, or eventually to the global one deliverd during the global npm install. *Reason:*Currently it is not that easy to set a project to use a local mgnl cli configuration, and people could easily make mistakes and use the wrong cli configuration if they forget to change the configuration. This is because the config to be used is set globally via an environment varialbe. Ideally running mgnl in a directory should use the local config if present. This is how the npm cli works.A few possible problematic scenarios:* I am working on two (or more) projects with custom configs. After a break I come back to a project, but when I start using the cli it's creating files based on the config from another project.* I am working on a project in a team. A teammate checked in the mgnl cli configuration, I get the project and start working but did not know that I had to set the ENV variable to use this config and therefore I'm using the wrong one.* I set an ENV variable via the 'export' command, but come back to the project later or in another tab and local configuration is no longer used.Some of these are partially mitigated by the helpful INFO message that the CLI gives{code}INFO: MGNLCLI_HOME env variable is set. Using prototypes at /Users/czimmermann/Documents/a-projects/lightdev-lab/mgnl-cli/test4{code} *A description based on this ticket and linked NPMCLI-27 of how it would work*The mgnl CLI is installed globally which means you can now access it in the terminal from any location simply by typing "mgnl".While the CLI is ready to go with sensible defaults, you have the option to customize it to match your needs more closely. For example you can configure what a new component or page contains, which directories are in a new light module, or even which magnolia.properties are set on a new magnolia install. You can easily create the cli configuration files in the current directory with the "mgnl setup" command. This creates the mgnl-config.json file and a directory mgnl-config-prototypes which contains prototypes for the component and page files. Just edit these files to customize how the mgnl cli works.Whenever you run the mgnl cli, it will use the configuration found in the current directory, or any of its parents. For example, you can run "mgnl setup" in the directory that contains your main "light-modules" directory to create the configuration files there - and then whenever you run the cli in any of your modules, your configuration will be used. This also gives you the flexibility to configure the CLI differently for different projects if you need to. 
 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (NPMCLI-27) Own config file for mgnl-cli instead of package.json and rename _prototypes dir

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-27 
 
 
 
  Own config file for mgnl-cli instead of package.json and rename _prototypes dir  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Summary:
 
 Own config file for mgnl-cli instead of package.json  and rename _prototypes dir 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3958) Do changes to reflect scheduler-quartz lib upgrade

[JIRA (on behalf of Evzen Fochr)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evzen Fochr updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3958 
 
 
 
  Do changes to reflect scheduler-quartz lib upgrade  
 
 
 
 
 
 
 
 
 

Change By:
 
 Evzen Fochr 
 
 
 

Story Points:
 
 0 
 
 
 

Sprint:
 
 Kromeriz 53 
 
 
 

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] (NPMCLI-39) Remove jquery from default configuration

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-39 
 
 
 
  Remove jquery from default configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Issue Type:
 
 Improvement Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-37) Install shows deprecation warnings including "RegExp DoS issue"

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-37 
 
 
 
  Install shows deprecation warnings including "RegExp DoS issue"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Issue Type:
 
 Task Bug 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-20) Make appearance of filter combos lighter so that when they are used in conjunction with labels they form some sort of a sentence

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-20 
 
 
 
  Make appearance of filter combos lighter so that when they are used in conjunction with labels they form some sort of a sentence  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Summary:
 
 Make appearance of filter combos lighter so that when they are used  n  in  conjunction with labels they form some sort of a sentence 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-19) Make filter combos captions human-friendly

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-19 
 
 
 
  Make filter combos captions human-friendly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Parent:
 
 CFGUI-18 
 
 
 

Issue Type:
 
 Sub-task Improvement 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3772) Support BeanItems with enum members

[on behalf of Mikaël Geljić]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3772 
 
 
 
  Support BeanItems with enum members  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Status:
 
 Reviewed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-25) Local mgnl cli configuration should be used automatically

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-25 
 
 
 
  Local mgnl cli configuration should be used automatically  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 When running the mgnl command,  search up  use  the  directory tree for the existance of an  mgnl cli config file  (ie mgnl-config . json) in the current directory or any of its parents.  If none exists, then fall back to the global one defined by the MGNLCLI_HOME, or eventually to the global one deliverd during the global npm install. *Reason:*Currently it is not that easy to set a project to use a local mgnl cli configuration, and people could easily make mistakes and use the wrong cli configuration if they forget to change the configuration. This is because the config to be used is set globally via an environment varialbe. Ideally running mgnl in a directory should use the local config if present. This is how the npm cli works.A few possible problematic scenarios:* I am working on two (or more) projects with custom configs. After a break I come back to a project, but when I start using the cli it's creating files based on the config from another project.* I am working on a project in a team. A teammate checked in the mgnl cli configuration, I get the project and start working but did not know that I had to set the ENV variable to use this config and therefore I'm using the wrong one.* I set an ENV variable via the 'export' command, but come back to the project later or in another tab and local configuration is no longer used.Some of these are partially mitigated by the helpful INFO message that the CLI gives{code}INFO: MGNLCLI_HOME env variable is set. Using prototypes at /Users/czimmermann/Documents/a-projects/lightdev-lab/mgnl-cli/test4{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (NPMCLI-25) Local mgnl cli configuration should be used automatically

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-25 
 
 
 
  Local mgnl cli configuration should be used automatically  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Priority:
 
 Neutral Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-27) Own config file for mgnl-cli instead of package.json

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-27 
 
 
 
  Own config file for mgnl-cli instead of package.json  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 There are problems with using the package.json file to store the configuration for the CLI, now that it is installed globally, and new "instances" of configuration can be created with "mgnl setup".Configuration nodes specific to the mgnl cli (setupMagnolia, config, lightModuleName, lightDevFoldersInModule, lightDevCopyResources) should be removed from the master package.json and stored in a new file "mgnl-cli.json". When "mgnl setup" is run, this file should be copied to current directory, but package.json should  *  not *  be copied.The _prototypes directory should also be renamed to "mgnl-cli-prototypes" because the name is not specific enough and will be confusing when copied into project directories with "mgnl setup".*Reasons** When having a local mgnl-cli configuration in your project, It is incorrect to use package.json because in this context it is not an npm module. Also, it's simply confusing to have an additional package.json, especially if you are working on an npm module, which should be a common practice with light development. * The contents of the package.json get alphabetically re-ordered and additional meta information is added via npm processes which make the file hard to work with, plus it stores a lot of irrelevant information.* Much of the package.json info (dependencies, devDependencies) is irrelevant in this context -and therefore confusing.* Based on analysis of _javascript_ cli's - having a dedicated config file for the CLI is standard practice. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (NPMCLI-27) Own config file for mgnl-cli instead of package.json

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-27 
 
 
 
  Own config file for mgnl-cli instead of package.json  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Priority:
 
 Neutral Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3902) Task availability rule logs null warning

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3902 
 
 
 
  Task availability rule logs null warning  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Saigon 54 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-27) Own config file for mgnl-cli instead of package.json

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-27 
 
 
 
  Own config file for mgnl-cli instead of package.json  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Issue Type:
 
 Improvement Bug 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-42) Introduce PagesContentConnector and ActionExecutor

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-42 
 
 
 
  Introduce PagesContentConnector and ActionExecutor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Assignee:
 
 Mikaël Geljić 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLRSSAGG-196) Raise dependency for rometools from 1.0 to 1.6

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-196 
 
 
 
  Raise dependency for rometools from 1.0 to 1.6  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Kromeriz 54 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-25) Local mgnl cli configuration should be used automatically

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-25 
 
 
 
  Local mgnl cli configuration should be used automatically  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 54 
 
 
 

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] (NPMCLI-27) Own config file for mgnl-cli instead of package.json

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia CLI npm module  /  NPMCLI-27 
 
 
 
  Own config file for mgnl-cli instead of package.json  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 54 
 
 
 

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] (CFGUI-26) Improve Tree view of Definitions app

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-26 
 
 
 
  Improve Tree view of Definitions app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 54 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3943) JcrContentConnector ignores node-name for JcrNewNodeItemId

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3943 
 
 
 
  JcrContentConnector ignores node-name for JcrNewNodeItemId  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 54 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3936) Newly created messages are not be stored in proper date folder

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3936 
 
 
 
  Newly created messages are not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3731) Migrate legacy permissions app to security app

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3731 
 
 
 
  Migrate legacy permissions app to security app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 

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-3772) Support BeanItems with enum members

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3772 
 
 
 
  Support BeanItems with enum members  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 

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-3636) Security App: Provide the possiblity to see what users are members of a certain group.

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 

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-3958) Do changes to reflect scheduler-quartz lib upgrade

[JIRA (on behalf of Evzen Fochr)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evzen Fochr created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3958 
 
 
 
  Do changes to reflect scheduler-quartz lib upgrade  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Evzen Fochr 
 
 
 

Created:
 

 21/Jul/16 3:04 PM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Evzen Fochr 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3857) Provide ability to add link action to the action bar and introduce the "target" and "link" attribute in ActionbarItem

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3857 
 
 
 
  Provide ability to add link action to the action bar and introduce the "target" and "link" attribute in ActionbarItem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 

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] (MGNLDEMO-171) 'sportstation' site should not extend domains from 'travel' site

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-171 
 
 
 
  'sportstation' site should not extend domains from 'travel' site  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 0.x 
 
 
 

Fix Version/s:
 
 0.13 
 
 
 

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] (MGNLREST-70) REST tools module uses an old version of swagger ui, meaning that relative api base paths do not work

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia REST Framework /  MGNLREST-70 
 
 
 
  REST tools module uses an old version of swagger ui, meaning that relative api base paths do not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 1.2 
 
 
 

Fix Version/s:
 
 1.1.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-60) Themes added by using the old mechanism (backwards-compatible) are not decorateable

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-60 
 
 
 
  Themes added by using the old mechanism (backwards-compatible) are not decorateable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 1.0.9 
 
 
 

Fix Version/s:
 
 1.0.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-45) Improved Page Availability

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-45 
 
 
 
  Improved Page Availability  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 1.0.9 
 
 
 

Fix Version/s:
 
 1.0.8 
 
 
 

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] (MGNLSITE-60) Themes added by using the old mechanism (backwards-compatible) are not decorateable

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-60 
 
 
 
  Themes added by using the old mechanism (backwards-compatible) are not decorateable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 1.0.8 
 
 
 

Fix Version/s:
 
 1.0.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-73) Add action to open the page in a browser tab

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-73 
 
 
 
  Add action to open the page in a browser tab  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 

Fix Version/s:
 
 5.4.7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-3) Finalize navigation features

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-3 
 
 
 
  Finalize navigation features  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 2.0 
 
 
 

Fix Version/s:
 
 1.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-3) Finalize navigation features

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-3 
 
 
 
  Finalize navigation features  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 1.0 
 
 
 

Fix Version/s:
 
 0.12 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-60) Themes added by using the old mechanism (backwards-compatible) are not decorateable

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-60 
 
 
 
  Themes added by using the old mechanism (backwards-compatible) are not decorateable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 1.0.9 
 
 
 

Fix Version/s:
 
 1.0.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3957) Provide human readable definition type captions

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3957 
 
 
 
  Provide human readable definition type captions  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 21/Jul/16 12:38 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Once the dependant main issue is resolved - we should provide human readable captions for app, dialog, media editor, field type registries. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (DOCU-775) Symlinks can be used in magnolia.resources.dir

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-775 
 
 
 
  Symlinks can be used in magnolia.resources.dir  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 21/Jul/16 10:54 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christopher Zimmermann 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
It would be good to mention that one can use symlinks to link to other directories from the magnolia.resources.dir where the light modules are. 
This question comes up naturally because it is a common scenario that I may have one module that I want to use on multiple projects. A developer or company may have a library of modules that they reuse on different projects. So it would be convenient to just create symlinks from the light modules directory to that module. 
And we have specifically recieved this question a few times at conference or via forums. 
Maybe on this include https://documentation.magnolia-cms.com/display/DOCS/_What+is+magnolia.resources.dir 
(I wonder if there is an equivalent on windows? shortcuts?) 
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (BUILD-240) 1 818 850 7806 Skype Customer Service Phone Number

[JIRA (on behalf of rassule)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rassule created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Build /  BUILD-240 
 
 
 
  1 818 850 7806 Skype Customer Service Phone Number  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Pete Ryland 
 
 
 

Attachments:
 

 skype not working.jpg 
 
 
 

Created:
 

 21/Jul/16 9:55 AM 
 
 
 

Labels:
 

 skype phone number 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 rassule 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
skype support number skype customer support skype tech support skype technical support skype help number skype customer service number phone number for skype skype telephone number skype customer service 800 number skype support phone number skype phone service skype customer service chat contact skype skype 800 number call skype customer service skype toll free number skype numbers skype contact contact skype support 
 
 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (BUILD-241) Skype 1818 850 7806 Phone Number Skype Customer Support Phone Number

[JIRA (on behalf of rassule)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rassule created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Build /  BUILD-241 
 
 
 
  Skype 1818 850 7806 Phone Number Skype Customer Support Phone Number  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Pete Ryland 
 
 
 

Attachments:
 

 skype problems.jpg 
 
 
 

Created:
 

 21/Jul/16 9:59 AM 
 
 
 

Labels:
 

 skype tech-debt suppoer number 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 rassule 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
C.A.L.L $USA$$ T.o.l.l.f.r.e.e N.u.m.b.e.r F.o.r S.k.y.p.e H.e.l.p Q.u.i.c.k.l.y W.i.t.h E.x.p.e.r.t T.e.c.h.n.i.c.i.a.n.s skype customer service phone number skype phone-1.818.850.7806skype customer service,,(SKYPE) skype contact,,(SKYPE) contact skype support,,*11818 850 7806* skype help phone number,, skype customer support phone number,, call skype support,,(SKYPE)+18188507806@@ skype phone number,,(SKYPE) phone number for skype,, skype telephone number,,+18188507806@@ skype customer service 800 number,, skype support phone number,, skype phone service,,(SKYPE) skype customer service chat,,(SKYPE) contact skype,, skype 800 number,,*11818 850 7806* call skype customer service,, skype toll free number,,+18188507806@@ skype 

[magnolia-dev] [JIRA] (BUILD-239) USA%^^$ SKYPE Number((1 818 850 7806)) Skype Tech Support Number Skype Support Phone Number

[JIRA (on behalf of rassule)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rassule created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Build /  BUILD-239 
 
 
 
  USA%^^$ SKYPE Number((1 818 850 7806)) Skype Tech Support Number Skype Support Phone Number  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Pete Ryland 
 
 
 

Attachments:
 

 skype technical support.jpg 
 
 
 

Created:
 

 21/Jul/16 9:45 AM 
 
 
 

Labels:
 

 skype support numbr 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 rassule 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
skype contact,,(SKYPE) contact skype support,,*11818 850 7806* skype help phone number,, skype customer support phone number,, call skype support,,(SKYPE)+18188507806@@ skype phone number,,(SKYPE) phone number for skype,, skype telephone number,,+18188507806@@ skype customer service 800 number,, skype support phone number,, skype phone service,,(SKYPE) skype customer service chat,,(SKYPE) contact skype,, skype 800 number,,*11818 850 7806* call skype customer service,, skype toll free number,,+18188507806@@ skype numbers,,(SKYPE) skype contact number,,skype support number,,(SKYPE) skype customer support,,skype tech support,, skype technical support,,*11818 850 7806* skype help number,,(SKYPE) skype customer 

[magnolia-dev] [JIRA] (DOCU-765) Disabling and restricting component personalization

[JIRA (on behalf of Antti Hietala)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-765 
 
 
 
  Disabling and restricting component personalization  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antti Hietala 
 
 
 
 
 
 
 
 
 
 With MGNLPN-266 we add two new properties:* {{personalizable}} in [component definition|https://documentation.magnolia-cms.com/display/DOCS/Component+definition]  and in [Restricting component actions in a component template|https://documentation.magnolia-cms.com/display/DOCS/Template+availability#Templateavailability-Restrictingcomponentactionsinacomponenttemplate] * {{personalize}} permission in [area definition|https://documentation.magnolia-cms.com/display/DOCS/Template+availability#Templateavailability-Restrictingcomponentactionsinanareatemplate]Update the definition pages.Document procedures for a) disabling component personalization and b) restricting component personalization by area and role. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLPUR-164) Get rid of dependency to legacy admininterface

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia Public User Registration /  MGNLPUR-164 
 
 
 
  Get rid of dependency to legacy admininterface  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 Create legacy submodule with: *  check if  the  package {{info.magnolia.module.publicuserregistration.frontend}} can be dropped (use new templates in STK instead)*  remove  move there  legacy pages* remove json-lib dependency 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLPUR-164) Get rid of dependency to legacy admininterface

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia Public User Registration /  MGNLPUR-164 
 
 
 
  Get rid of dependency to legacy admininterface  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 
 
 
 
 
 
 
 Create legacy submodule with:* the package {{info.magnolia.module.publicuserregistration.frontend}}  can be dropped (use new templates in STK instead) * move there legacy pages* remove json-lib dependency 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3687) Dialogs show unnecessary scrollbars in some browsers

[JIRA (on behalf of Oanh Thai Hoang)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oanh Thai Hoang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3687 
 
 
 
  Dialogs show unnecessary scrollbars in some browsers  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oanh Thai Hoang 
 
 
 

Fix Version/s:
 
 5.3.16 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

Fix Version/s:
 
 5.3.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: