[magnolia-dev] [JIRA] Work started: (MGNLWEBDAV-15) Node names aren't validated before creation

[on behalf of Grégory Joseph]

 [ 
http://jira.magnolia-cms.com/browse/MGNLWEBDAV-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on MGNLWEBDAV-15 started by Grégory Joseph.

> Node names aren't validated before creation
> ---
>
> Key: MGNLWEBDAV-15
> URL: http://jira.magnolia-cms.com/browse/MGNLWEBDAV-15
> Project: Magnolia WebDAV Module
>  Issue Type: Bug
>Affects Versions: 1.0-m2
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 1.0
>
>
> When trying to create a folder with non-ascii characters (from a fs-mounted 
> WebDAV), {{pascaläöü}} in this case:
> {code}
> 2009-10-27 19:16:59,826 INFO  info.magnolia.cms.beans.config.MIMEMapping  
>   : Cannot find MIME type for extension "_pascale%CC%80u%CC%88"
> 2009-10-27 19:17:00.416::WARN:  
> /magnolia-snapshot-demo/.webdav/resources/folders/
> java.lang.RuntimeException: info.magnolia.cms.security.AccessDeniedException: 
> User not allowed to Read path [/folders/pascale?u?]
> at 
> info.magnolia.module.webdav.LocatorFactory.getResourcePath(LocatorFactory.java:76)
> at 
> org.apache.jackrabbit.webdav.AbstractLocatorFactory.createResourceLocator(AbstractLocatorFactory.java:170)
> at 
> org.apache.jackrabbit.webdav.simple.DavResourceImpl.getMembers(DavResourceImpl.java:564)
> at 
> org.apache.jackrabbit.webdav.MultiStatus.addResourceProperties(MultiStatus.java:64)
> at 
> org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.doPropFind(AbstractWebdavServlet.java:447)
> at 
> org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.execute(AbstractWebdavServlet.java:235)
> {code}
> The exception reminds of MAGNOLIA-2098. (this happened while logged in as 
> superuser)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Assigned: (MGNLWEBDAV-15) Node names aren't validated before creation

[on behalf of Grégory Joseph]

 [ 
http://jira.magnolia-cms.com/browse/MGNLWEBDAV-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph reassigned MGNLWEBDAV-15:


Assignee: Grégory Joseph  (was: Jan Haderka)

> Node names aren't validated before creation
> ---
>
> Key: MGNLWEBDAV-15
> URL: http://jira.magnolia-cms.com/browse/MGNLWEBDAV-15
> Project: Magnolia WebDAV Module
>  Issue Type: Bug
>Affects Versions: 1.0-m2
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 1.0
>
>
> When trying to create a folder with non-ascii characters (from a fs-mounted 
> WebDAV), {{pascaläöü}} in this case:
> {code}
> 2009-10-27 19:16:59,826 INFO  info.magnolia.cms.beans.config.MIMEMapping  
>   : Cannot find MIME type for extension "_pascale%CC%80u%CC%88"
> 2009-10-27 19:17:00.416::WARN:  
> /magnolia-snapshot-demo/.webdav/resources/folders/
> java.lang.RuntimeException: info.magnolia.cms.security.AccessDeniedException: 
> User not allowed to Read path [/folders/pascale?u?]
> at 
> info.magnolia.module.webdav.LocatorFactory.getResourcePath(LocatorFactory.java:76)
> at 
> org.apache.jackrabbit.webdav.AbstractLocatorFactory.createResourceLocator(AbstractLocatorFactory.java:170)
> at 
> org.apache.jackrabbit.webdav.simple.DavResourceImpl.getMembers(DavResourceImpl.java:564)
> at 
> org.apache.jackrabbit.webdav.MultiStatus.addResourceProperties(MultiStatus.java:64)
> at 
> org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.doPropFind(AbstractWebdavServlet.java:447)
> at 
> org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.execute(AbstractWebdavServlet.java:235)
> {code}
> The exception reminds of MAGNOLIA-2098. (this happened while logged in as 
> superuser)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk » magnolia-module-exchange -simple #1076

[Hudson CI]

See 





For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk #1076

[Hudson CI]

See 




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2901) Moving nodes in adminCentral shows moved node content as parent node content

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24743#action_24743
 ] 

Hudson CI server commented on MAGNOLIA-2901:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/yellow.gif! 
[magnolia_main-trunk 
#1075|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1075/]
  Do not modify the path after move/rename as it is also used during 
initialization to replace the rootPath.


> Moving nodes in adminCentral shows moved node content as parent node content
> 
>
> Key: MAGNOLIA-2901
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2901
> Project: Magnolia
>  Issue Type: Bug
>  Components: admininterface
>Affects Versions: 4.1.1
> Environment: Browsers I tested on:
> Firefox
> Safari
>Reporter: Christian Ringele
>Assignee: Philipp Bärfuss
>Priority: Critical
> Fix For: 4.1.2, 4.2
>
> Attachments: MAGNOLIA-2901-after-move.png, 
> MAGNOLIA-2901-before-move.png
>
>
> When moving a node in admin central to a different parent node, the tree only 
> shows the content of the moved node (subnodes) instead of the whole tree.
> The move occurs properly, and this is "only" a visual issue.
> It doesn't seem to be specific to any workspace (reproduced on config, 
> website, dms, ...) nor instance (reproduced on several local ones, 
> demoauthor, ...)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2901) Moving nodes in adminCentral shows moved node content as parent node content

[JIRA (on behalf of Jan Haderka)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24745#action_24745
 ] 

Jan Haderka commented on MAGNOLIA-2901:
---

Reverted fix for MAGNOLIA-2827 that was causing the issue and solved the 
problem in related issue (MGNLDATA-60) differently.
The problem is that once the path is set it will be used during the next 
initialization of the tree rather then the rootPath (or "/" if rootPath is not 
set). The code is not really clear on why this is done. See {{.init()}} method 
for details.


> Moving nodes in adminCentral shows moved node content as parent node content
> 
>
> Key: MAGNOLIA-2901
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2901
> Project: Magnolia
>  Issue Type: Bug
>  Components: admininterface
>Affects Versions: 4.1.1
> Environment: Browsers I tested on:
> Firefox
> Safari
>Reporter: Christian Ringele
>Assignee: Philipp Bärfuss
>Priority: Critical
> Fix For: 4.1.2, 4.2
>
> Attachments: MAGNOLIA-2901-after-move.png, 
> MAGNOLIA-2901-before-move.png
>
>
> When moving a node in admin central to a different parent node, the tree only 
> shows the content of the moved node (subnodes) instead of the whole tree.
> The move occurs properly, and this is "only" a visual issue.
> It doesn't seem to be specific to any workspace (reproduced on config, 
> website, dms, ...) nor instance (reproduced on several local ones, 
> demoauthor, ...)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Commented: (MGNLDATA-60) Double click on node name allows to change it without changing actual value for Categories

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLDATA-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24744#action_24744
 ] 

Hudson CI server commented on MGNLDATA-60:
--

Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia-module-data 
#437|http://hudson.magnolia-cms.com/job/magnolia-module-data/437/]
  Re-add support for syncing the name property with the node name removed 
accidentally during merge of the hierarchical types support. Construct the new 
node path information locally as it can't be provided by the parent tree.


> Double click on node name allows to change it without changing actual value 
> for Categories
> --
>
> Key: MGNLDATA-60
> URL: http://jira.magnolia-cms.com/browse/MGNLDATA-60
> Project: Magnolia Data Module
>  Issue Type: Bug
>Reporter: Boris Kraft
>Assignee: Jan Haderka
> Fix For: 1.4-m1
>
>
> If you edit categories directly in the list view by double clicking on a 
> category, the name is updated but if you then open the dialog, it is still 
> the old category name. I consider this a serious bug. The list should display 
> (and allow to change) the category name.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] Hudson build became unstable: magnolia_main-trunk #1075

[Hudson CI]

See 




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] Hudson build became unstable: ma gnolia_main-trunk » magnolia-module-exchange-si mple #1075

[Hudson CI]

See 





For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2909) POST requests to Magnolia fail if Struts filter chain is used before the Magnolia chain

[JIRA (on behalf of Andreas Antener)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24740#action_24740
 ] 

Andreas Antener commented on MAGNOLIA-2909:
---

Thank you for the hint.

I had a short look into the code. Basically what you are doing is delegating 
the action to struts for processing in a renderer, right?

In the meanwhile I tried to do something similar with a filter in the Magnolia 
filter chain. My filter just delegates the request to the struts dispacher. It 
works with post-requests if the filter is positioned after "multipartRequest". 
Also it was necessary to check on loops because struts calls Magnolia sites as 
result pages, which is why I'm not quite sure if this is the correct approach 
to solve it..

> POST requests to Magnolia fail if Struts filter chain is used before the 
> Magnolia chain
> ---
>
> Key: MAGNOLIA-2909
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2909
> Project: Magnolia
>  Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: struts 2.1.6, tomcat 6
>Reporter: Andreas Antener
>Assignee: Boris Kraft
> Attachments: stacktrace.txt, web.xml
>
>
> First, what are we trying to do:
> We have already existing applications that are using Struts and we would like 
> to integrate them in Magnolia. The idea is to use these existing applications 
> as paragraphs, which can be placed anywhere on the site.
> JSP templates came in handy to include pages that are using struts tags. We 
> added the struts filter-dispacher and mapped him BEFORE magnolia (see 
> attachement).
> From now on, struts tags get executed and they work as expected. However, the 
> thing that does not work anymore are POST requests that are directed to 
> Magnolia itself (meaning every Magnolia dialog / input etc.). Magnolia 
> terminates parsing those request with the following exception:
> java.io.IOException: Corrupt form data: premature ending
>   
> com.oreilly.servlet.multipart.MultipartParser.(MultipartParser.java:205)
>   com.oreilly.servlet.MultipartRequest.(MultipartRequest.java:222)
>   
> info.magnolia.cms.filters.CosMultipartRequestFilter.parseParameters(CosMultipartRequestFilter
>  (see attachement for full stacktrace)
> I read that this could be an MultipartParser-library related incompatibility 
> with Struts:
> http://stackoverflow.com/questions/240163/corrupt-form-data-premature-ending-resolved
> Any suggestions?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Commented: (MGNLDATA-85) Sample content for hierarchical types

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLDATA-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24738#action_24738
 ] 

Hudson CI server commented on MGNLDATA-85:
--

Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia-module-data 
#436|http://hudson.magnolia-cms.com/job/magnolia-module-data/436/]
  New sample import handler.


> Sample content for hierarchical types
> -
>
> Key: MGNLDATA-85
> URL: http://jira.magnolia-cms.com/browse/MGNLDATA-85
> Project: Magnolia Data Module
>  Issue Type: Task
>Affects Versions: 1.4-m1
>Reporter: Jan Haderka
>Assignee: Jan Haderka
> Fix For: 1.4
>
>
> Provide simple sample content of using the hierarchical types.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Commented: (MGNLDATA-85) Sample content for hierarchical types

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLDATA-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24737#action_24737
 ] 

Hudson CI server commented on MGNLDATA-85:
--

Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia-module-data 
#435|http://hudson.magnolia-cms.com/job/magnolia-module-data/435/]
  And again samples cleanup ... some people just never learn :D


> Sample content for hierarchical types
> -
>
> Key: MGNLDATA-85
> URL: http://jira.magnolia-cms.com/browse/MGNLDATA-85
> Project: Magnolia Data Module
>  Issue Type: Task
>Affects Versions: 1.4-m1
>Reporter: Jan Haderka
>Assignee: Jan Haderka
> Fix For: 1.4
>
>
> Provide simple sample content of using the hierarchical types.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Commented: (MGNLDATA-85) Sample content for hierarchical types

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLDATA-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24736#action_24736
 ] 

Hudson CI server commented on MGNLDATA-85:
--

Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia-module-data 
#434|http://hudson.magnolia-cms.com/job/magnolia-module-data/434/]
  Cleaned up, updated and extended samples.


> Sample content for hierarchical types
> -
>
> Key: MGNLDATA-85
> URL: http://jira.magnolia-cms.com/browse/MGNLDATA-85
> Project: Magnolia Data Module
>  Issue Type: Task
>Affects Versions: 1.4-m1
>Reporter: Jan Haderka
>Assignee: Jan Haderka
> Fix For: 1.4
>
>
> Provide simple sample content of using the hierarchical types.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Resolved: (MGNLPUR-32) The original sample pages using the templates from sample module should be removed

[JIRA (on behalf of Zdenek Skodik)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLPUR-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zdenek Skodik resolved MGNLPUR-32.
--

Resolution: Fixed

Done as of r29161. 

> The original sample pages using the templates from sample module should be 
> removed
> --
>
> Key: MGNLPUR-32
> URL: http://jira.magnolia-cms.com/browse/MGNLPUR-32
> Project: Magnolia Public User Registration
>  Issue Type: Task
>Affects Versions: 1.1-m2
>Reporter: Zdenek Skodik
>Assignee: Zdenek Skodik
> Fix For: 1.1
>
>
> when the PUR sample pages will be stored directly in STK there is no need to 
> hold the initial PUR samples 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Commented: (MGNLPUR-32) The original sample pages using the templates from sample module should be removed

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLPUR-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24734#action_24734
 ] 

Hudson CI server commented on MGNLPUR-32:
-

Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia-module-public-user-registration 
#23|http://hudson.magnolia-cms.com/job/magnolia-module-public-user-registration/23/]
  - remove samples


> The original sample pages using the templates from sample module should be 
> removed
> --
>
> Key: MGNLPUR-32
> URL: http://jira.magnolia-cms.com/browse/MGNLPUR-32
> Project: Magnolia Public User Registration
>  Issue Type: Task
>Affects Versions: 1.1-m2
>Reporter: Zdenek Skodik
>Assignee: Zdenek Skodik
> Fix For: 1.1
>
>
> when the PUR sample pages will be stored directly in STK there is no need to 
> hold the initial PUR samples 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Work started: (MGNLPUR-32) The original sample pages using the templates from sample module should be removed

[JIRA (on behalf of Zdenek Skodik)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLPUR-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on MGNLPUR-32 started by Zdenek Skodik.

> The original sample pages using the templates from sample module should be 
> removed
> --
>
> Key: MGNLPUR-32
> URL: http://jira.magnolia-cms.com/browse/MGNLPUR-32
> Project: Magnolia Public User Registration
>  Issue Type: Task
>Affects Versions: 1.1-m2
>Reporter: Zdenek Skodik
>Assignee: Zdenek Skodik
> Fix For: 1.1
>
>
> when the PUR sample pages will be stored directly in STK there is no need to 
> hold the initial PUR samples 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Created: (MGNLPUR-32) The original sample pages using the templates from sample module should be removed

[JIRA (on behalf of Zdenek Skodik)]

The original sample pages using the templates from sample module should be 
removed
--

 Key: MGNLPUR-32
 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-32
 Project: Magnolia Public User Registration
  Issue Type: Task
Affects Versions: 1.1-m2
Reporter: Zdenek Skodik
Assignee: Grégory Joseph
 Fix For: 1.1


when the PUR sample pages will be stored directly in STK there is no need to 
hold the initial PUR samples 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Assigned: (MGNLPUR-32) The original sample pages using the templates from sample module should be removed

[JIRA (on behalf of Zdenek Skodik)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLPUR-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zdenek Skodik reassigned MGNLPUR-32:


Assignee: Zdenek Skodik  (was: Grégory Joseph)

> The original sample pages using the templates from sample module should be 
> removed
> --
>
> Key: MGNLPUR-32
> URL: http://jira.magnolia-cms.com/browse/MGNLPUR-32
> Project: Magnolia Public User Registration
>  Issue Type: Task
>Affects Versions: 1.1-m2
>Reporter: Zdenek Skodik
>Assignee: Zdenek Skodik
> Fix For: 1.1
>
>
> when the PUR sample pages will be stored directly in STK there is no need to 
> hold the initial PUR samples 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2928) Updating our website and activatuib by Magnolia AdminCentral

[JIRA (on behalf of Zdenek Skodik)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24733#action_24733
 ] 

Zdenek Skodik commented on MAGNOLIA-2928:
-

Hi Tom,

I've updated your profile so first of all please move 
this issue into {{Magnolia - support}} project (just
click on {{Move this issue}} on the left bar). 
That issue will be private and visible only for you 
(and persons you'll specify as {{watchers}}) and 
our support team. 

Thanks,
Zdenek

> Updating our website and activatuib by Magnolia AdminCentral
> 
>
> Key: MAGNOLIA-2928
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2928
> Project: Magnolia
>  Issue Type: Task
>  Components: workflow
> Environment: Mac OSX 10.4
>Reporter: Thomas Malone
>Assignee: Zdenek Skodik
>
> My name is Thomas Malone and I am the Online and Communications Co-ordinator 
> at Maggie's Cancer Caring Centres
> We have a problem with our Magnolia licence - the licence expired on 31 
> October 2009, but we were under the assumption the payment had already 
> reached you. Unfortunately, due to the postal strikes that are currently 
> taking place in the UK we realise that this is not the case.
> As a result our licence has expired at a crucial time when we were looking to 
> make a number of critical updates to our website. We have spoken to our bank, 
> who will be in touch with you with the payment very soon, but in the 
> meanwhile, would it be possible for you to provide us with a temporary key to 
> use Magnolia to make changes to our site?
> I understand that Maria-Vittoria Burlina, from our website developers Vexed, 
> has spoken to Boris Kraft to see if we could get any support for this and she 
> directed me to send feedback to you through this portal.
> Kind regards,
> Tom Malone
> Online and Communications Co-orindator
> Maggie's Cancer Caring Centres
> +44 207 880 1730

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-2928) Updating our website and activatuib by Magnolia AdminCentral

[JIRA (on behalf of Zdenek Skodik)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zdenek Skodik reassigned MAGNOLIA-2928:
---

Assignee: Zdenek Skodik  (was: Grégory Joseph)

> Updating our website and activatuib by Magnolia AdminCentral
> 
>
> Key: MAGNOLIA-2928
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2928
> Project: Magnolia
>  Issue Type: Task
>  Components: workflow
> Environment: Mac OSX 10.4
>Reporter: Thomas Malone
>Assignee: Zdenek Skodik
>
> My name is Thomas Malone and I am the Online and Communications Co-ordinator 
> at Maggie's Cancer Caring Centres
> We have a problem with our Magnolia licence - the licence expired on 31 
> October 2009, but we were under the assumption the payment had already 
> reached you. Unfortunately, due to the postal strikes that are currently 
> taking place in the UK we realise that this is not the case.
> As a result our licence has expired at a crucial time when we were looking to 
> make a number of critical updates to our website. We have spoken to our bank, 
> who will be in touch with you with the payment very soon, but in the 
> meanwhile, would it be possible for you to provide us with a temporary key to 
> use Magnolia to make changes to our site?
> I understand that Maria-Vittoria Burlina, from our website developers Vexed, 
> has spoken to Boris Kraft to see if we could get any support for this and she 
> directed me to send feedback to you through this portal.
> Kind regards,
> Tom Malone
> Online and Communications Co-orindator
> Maggie's Cancer Caring Centres
> +44 207 880 1730

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Work started: (MAGNOLIA-2928) Updating our website and activatuib by Magnolia AdminCentral

[JIRA (on behalf of Zdenek Skodik)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on MAGNOLIA-2928 started by Zdenek Skodik.

> Updating our website and activatuib by Magnolia AdminCentral
> 
>
> Key: MAGNOLIA-2928
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2928
> Project: Magnolia
>  Issue Type: Task
>  Components: workflow
> Environment: Mac OSX 10.4
>Reporter: Thomas Malone
>Assignee: Zdenek Skodik
>
> My name is Thomas Malone and I am the Online and Communications Co-ordinator 
> at Maggie's Cancer Caring Centres
> We have a problem with our Magnolia licence - the licence expired on 31 
> October 2009, but we were under the assumption the payment had already 
> reached you. Unfortunately, due to the postal strikes that are currently 
> taking place in the UK we realise that this is not the case.
> As a result our licence has expired at a crucial time when we were looking to 
> make a number of critical updates to our website. We have spoken to our bank, 
> who will be in touch with you with the payment very soon, but in the 
> meanwhile, would it be possible for you to provide us with a temporary key to 
> use Magnolia to make changes to our site?
> I understand that Maria-Vittoria Burlina, from our website developers Vexed, 
> has spoken to Boris Kraft to see if we could get any support for this and she 
> directed me to send feedback to you through this portal.
> Kind regards,
> Tom Malone
> Online and Communications Co-orindator
> Maggie's Cancer Caring Centres
> +44 207 880 1730

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: