[magnolia-dev] Re: I can't get it working: Magnolia-Webdav-Module

2014-09-18 Thread Natascha Desmarais (via Magnolia Forums)
Hi Tobias

This forum is actually synched with the mailing list: 
http://documentation.magnolia-cms.com/display/DOCS/Stay+updated#Stayupdated-Mailinglists

What you want to subscribe to is the User List primarily.
HTH
Natascha

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=877d4d54-5687-41bf-9c3b-1356e067e091



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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] Re: I can't get it working: Magnolia-Webdav-Module

2014-09-18 Thread via Magnolia Forums
Hello Natascha, 

thank you for this information - that's was an good idea to sync mailing list 
and forum together. I can't top this!
I have subscribe me to all mailing lists, is good to get much informations form 
different perspectives.

TX
Tobias

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=877d4d54-5687-41bf-9c3b-1356e067e091



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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] (MGNLUI-3109) In the page editor, a component selected should always remain within view

2014-09-18 Thread JIRA (on behalf of Federico Grilli)














































Federico Grilli
 updated  MGNLUI-3109


In the page editor, a component selected should always remain within view
















Change By:


Federico Grilli
(18/Sep/14 10:05 AM)




Fix Version/s:


5.2.10





Fix Version/s:


5.3.4





Fix Version/s:


5.2.x





Fix Version/s:


5.3.x



























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-3109) In the page editor, a component selected should always remain within view

2014-09-18 Thread JIRA (on behalf of Federico Grilli)














































Federico Grilli
 updated  MGNLUI-3109


In the page editor, a component selected should always remain within view
















Change By:


Federico Grilli
(18/Sep/14 10:05 AM)




Priority:


Neutral
Major



























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-3159) Suggestion: task in ui-admincentral for adding apps

2014-09-18 Thread JIRA (on behalf of Natascha Desmarais)














































Natascha Desmarais
 created  MGNLUI-3159


Suggestion: task in ui-admincentral for adding apps















Issue Type:


Improvement



Affects Versions:


5.3.3



Assignee:


Unassigned


Components:


admincentral, configuration



Created:


18/Sep/14 11:04 AM



Description:


Instead of having to bootstrap apps being added to the appslauncher, it would be nice to have a task instead where modules can register their apps to the appslauncher menus

Suggestion:
function1 that takes "appName" and "group"
function2 that takes "appName", "group" and "fallbackGroup"

function1 could call function2 with "fallbackGroup" = dev or tools for example.

This would avoid having to run a check manually for existing app groups.




Fix Versions:


5.3.4



Project:


Magnolia UI



Priority:


Minor




Reporter:


Natascha Desmarais



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-3159) Suggestion: task in ui-admincentral for registering apps into the UI/Shell

2014-09-18 Thread JIRA (on behalf of Christian Ringele)














































Christian Ringele
 updated  MGNLUI-3159


Suggestion: task in ui-admincentral for registering apps into the UI/Shell
















Change By:


Christian Ringele
(18/Sep/14 11:20 AM)




Summary:


Suggestion:taskinui-admincentralfor
adding
registering
apps
intotheUI/Shell



























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-3159) Suggestion: task in ui-admincentral for registering apps into the UI's app launcher

2014-09-18 Thread JIRA (on behalf of Christian Ringele)














































Christian Ringele
 updated  MGNLUI-3159


Suggestion: task in ui-admincentral for registering apps into the UIs app launcher
















Change By:


Christian Ringele
(18/Sep/14 11:21 AM)




Summary:


Suggestion:taskinui-admincentralforregisteringappsintotheUI
/Shell
sapplauncher



























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] Re: I can't get it working: Magnolia-Webdav-Module

2014-09-18 Thread Natascha Desmarais (via Magnolia Forums)
Hello again

Hope that will help with getting some more infos :) however, just as a 
side-note, the dev list gets all notifications from our issue tracker JIRA as 
well, so that might be a bit traffic heavy. Just in case, on the same page that 
I posted earlier you can also find all the unsubscribe links should it become 
too heavy.

As for the WebDAV issue itself I’m afraid I can’t be of much help, but I am 
wondering as to why you need it in the first place? Unless there is a specific 
requirement for it, you could also just write the templates directly in your 
IDE [1]. You just need to enable hot deployment on your server and that’s it, 
development from within your IDE.
If you need to be able to modify templates within Magnolia as well, you could 
additionally install the inplace-templating module [2]. It comes with an app 
that you can add, which lets you modify templates directly inside Magnolia if 
you enable them [3].

Hope this helps you get started :)


[1] Have a look at 
http://academy.magnolia-cms.com/display/MA/U2+Custom+template+overview  and 
watch that video there, it is shown nicely how that works.

[2] 
http://documentation.magnolia-cms.com/display/DOCS/In-place+Templating+module
 
[3] To install your templates into Magnolia/the templates workspace, you can 
use info.magnolia.module.inplacetemplating.setup.TemplatesInstallTask in your 
module version handler as such:
[code]new TemplatesInstallTask(“/your-module-name/.*\\.ftl, true)[/code]

If you are using the STK, you can find the templates workspace app under STK  
Templates in your admincentral, otherwise you can add the app (name: 
“inplace-templating”) manually to any of the existing groups. See the following 
documentation page on how to do this:
https://documentation.magnolia-cms.com/display/DOCS/Configuring+an+app#Configuringanapp-Applauncher

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=877d4d54-5687-41bf-9c3b-1356e067e091



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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] Re: I can't get it working: Magnolia-Webdav-Module

2014-09-18 Thread via Magnolia Forums
That will help. I will do it without webdav module. When I have more 
experience, it will be easier for me to understand what's the reason of the 
error which I got above.

Thanks you for pulling me back to red line.

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=877d4d54-5687-41bf-9c3b-1356e067e091



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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] Re: I can't get it working: Magnolia-Webdav-Module

2014-09-18 Thread via Magnolia Forums
[quote][s]That will help.[/s][/quote]

That helps!

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=877d4d54-5687-41bf-9c3b-1356e067e091



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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] Re: I can't get it working: Magnolia-Webdav-Module

2014-09-18 Thread Gavan Stockdale (via Magnolia Forums)
Hello again Tobias.

Thanks for the emails today and for posting again on Forum. As you see, there 
is a solution. Thanks Natascha for a very helpful reply. 

Keep at it and keep us informed of your progress!

Gavan

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=877d4d54-5687-41bf-9c3b-1356e067e091



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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] (MGNLUI-3160) Do not align the selected row to the center of the viewport with RowScroller extension if it is already in view.

2014-09-18 Thread JIRA (on behalf of Aleksandr Pchelintcev)














































Aleksandr Pchelintcev
 created  MGNLUI-3160


Do not align the selected row to the center of the viewport with RowScroller extension if it is already in view.















Issue Type:


Bug



Affects Versions:


5.3.3, 5.2.8



Assignee:


Aleksandr Pchelintcev



Created:


18/Sep/14 12:53 PM



Description:


In case the selected row is already in view and the server-side invokes the RowScroller a distracting table bounce might be encountered. The reason is that RowScroller puts the scroll top so that the selected row is in the center. When such row is visible RowScrollers' involvement is not needed.




Fix Versions:


5.3.4, 5.2.9



Project:


Magnolia UI



Priority:


Neutral




Reporter:


Aleksandr Pchelintcev




























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] (FORMDB-1) Form2DB module fails to register formNode node type on Magnolia 5.3.3

2014-09-18 Thread JIRA (on behalf of Edgar Vonk)














































Edgar Vonk
 created  FORMDB-1


Form2DB module fails to register formNode node type on Magnolia 5.3.3















Issue Type:


Bug



Assignee:


Marvin Kerkhoff



Created:


18/Sep/14 2:00 PM



Description:


As reported on http://wiki.magnolia-cms.com/display/WIKI/Form2DB+App?focusedCommentId=88445853#comment-88445853 the form2db module fails to start properly in our (customised) Magnolia 5.3.3 project. In the logs we see:



2014-09-18 11:27:16,574 ERROR info.magnolia.module.ModuleManagerImpl: 
javax.jcr.RepositoryException
	at info.magnolia.jackrabbit.ProviderImpl.registerNodeTypes(ProviderImpl.java:389)
	at info.magnolia.jackrabbit.ProviderImpl.registerNodeTypes(ProviderImpl.java:293)
	at info.magnolia.module.ModuleManagerImpl.registerNodeTypeFile(ModuleManagerImpl.java:672)
	at info.magnolia.module.ModuleManagerImpl.loadRepository(ModuleManagerImpl.java:639)
	at info.magnolia.module.ModuleManagerImpl.loadModulesRepositories(ModuleManagerImpl.java:576)
	at info.magnolia.module.ModuleManagerImpl.checkForInstallOrUpdates(ModuleManagerImpl.java:195)
	at info.magnolia.cms.beans.config.ConfigLoader.load(ConfigLoader.java:148)
	at info.magnolia.init.MagnoliaServletContextListener$1.doExec(MagnoliaServletContextListener.java:248)
	at info.magnolia.context.MgnlContext$VoidOp.exec(MgnlContext.java:414)
	at info.magnolia.context.MgnlContext$VoidOp.exec(MgnlContext.java:411)
	at info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:385)
	at info.magnolia.init.MagnoliaServletContextListener.startServer(MagnoliaServletContextListener.java:245)
	at info.magnolia.init.MagnoliaServletContextListener.contextInitialized(MagnoliaServletContextListener.java:171)
	at info.magnolia.init.MagnoliaServletContextListener.contextInitialized(MagnoliaServletContextListener.java:125)
	at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
	at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:446)
	at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:792)
	at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:296)
	at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1341)
	at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1334)
	at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:744)
	at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:497)
	at org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:281)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
	at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
	at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:154)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
	at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
	at org.eclipse.jetty.server.Server.start(Server.java:357)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
	at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
	at org.eclipse.jetty.server.Server.doStart(Server.java:324)
	at org.eclipse.jetty.maven.plugin.JettyServer.doStart(JettyServer.java:68)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.eclipse.jetty.maven.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:564)
	

[magnolia-dev] [JIRA] (FORMDB-2) Git web view does not show latest version of form2b module

2014-09-18 Thread JIRA (on behalf of Edgar Vonk)














































Edgar Vonk
 created  FORMDB-2


Git web view does not show latest version of form2b module















Issue Type:


Bug



Assignee:


Marvin Kerkhoff



Created:


18/Sep/14 2:23 PM



Description:


The Git web view currently does not show the latest develop branch and it does not show the 1.0.1 version of the form2db module. I only see the master branch and it seems to be stuck at version 1.0.0.

http://git.magnolia-cms.com/gitweb/?p=forge/form2db.git;a=tree




Project:


Form2DB



Priority:


Neutral




Reporter:


Edgar Vonk




























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-3161) Offer different layout options in list and tree views

2014-09-18 Thread JIRA (on behalf of Andreas Weder)














































Andreas Weder
 updated  MGNLUI-3161


Offer different layout options in list and tree views
















Change By:


Andreas Weder
(18/Sep/14 2:33 PM)




Description:


Thelayoutofthelistandtreeviewisacompromisebetweenacompactlistofelementsandagenerousenoughlayouttoworkwellontabletdevices.Itworkswellfore.g.asmallsetofpages,butwealsoknow(andalsogetfeedbackthatsupportsthis)thatitfailsinavarietyofothercases:-Tree*levelsarenotalwaysclearlydiscernible*asthepaddingbetweenrowsisbig,whichdissociatescontentthatwouldbeeasiertoreadifclosertogether.-Wehavesometreesandlistswithalotofnodes,sometimesevenonasinglelevel.Forthesetrees,itwouldbe*beneficialtoseesignificantlymorerowsatatime*toavoidheavyscrolling.-The*rowsandarrowsontabletdevicesareactuallystilltoosmallontablets*toworkcomfortablyandsafely-wehadalargerpaddingbefore,whichworkedbest.Theres*actuallynoonelayoutthatworkswellonalldevicesandinallviews*.Weshouldthus*offertheuserthechoicebetweenasmallsetoflayoutoptionswithdifferentdensitylevels*,e.g.agenerous,thecurrentandacompactviewofalistandatree.-Fornon-technicalcontentsuchasPagesandAssets,wecouldshowlistsandtreesusingthecurrent,normallayoutondesktops,thegenerouslayoutontablets.-Fortechnicalcontentorsetswithlotsofitems,wewouldusethecurrent,compactlayoutondesktops,thenormallayoutontablets.-Foreverytreeandlist,the
*
userhastheoptiontochooseadifferentlayout
*still
.Note:thisissueisforrecordingtheneedfordifferentlayoutoptions.Whetheralayoutsettingispersistedornot,whetheritsdefinedpervieworperappandwhethertheresaglobalsettingsinauserprofiletopickadefaultlayoutforalltreeshastobediscussedstill.



























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-3161) Offer different layout options in list and tree views

2014-09-18 Thread JIRA (on behalf of Andreas Weder)














































Andreas Weder
 created  MGNLUI-3161


Offer different layout options in list and tree views















Issue Type:


Improvement



Affects Versions:


5.3.3, 5.2.9



Assignee:


Unassigned


Components:


tree/list



Created:


18/Sep/14 2:32 PM



Description:


The layout of the list and tree view is a compromise between a compact list of elements and a generous enough layout to work well on tablet devices. It works well for e.g. a small set of pages, but we also know (and also get feedback that supports this) that it fails in a variety of other cases:

	Tree levels are not alwasy clearly discernible as the padding between rows is big, which dissociates content that would be easier to read if closer together.
	We have some trees and lists with a lot of nodes, sometimes even on a single level. For these trees, it would be beneficial to see significantly more rows at a time to avoid heavy scrolling.
	The rows and arrows on tablet devices are actually still too small on tablets to work comfortably and safely - we had a larger padding before, which worked best.



There's actually no one layout that works well on all devices and in all views. We should thus offer the user the choice between a small set of layout options with different density levels, e.g. a generous, the current and a compact view of a list and a tree.

	For "non-technical" content such as Pages and Assets, we could show lists and trees using the current, normal layout on desktops, the generous layout on tablets.
	For "technical" content or sets with lots of items, we would use the current, compact layout on desktops, the normal layout on tablets.
	For every tree and list, the user has the option to choose a different layout.



Note: this issue is for recording the need for different layout options. Whether  a layout setting is persisted or not, whether it's defined per view or per app and whether there's a global settings in a user profile to pick a default layout for all trees has to be discussed still.




Project:


Magnolia UI



Labels:


ux
usability




Priority:


Neutral




Reporter:


Andreas Weder



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-3161) Offer different layout options in list and tree views

2014-09-18 Thread JIRA (on behalf of Andreas Weder)














































Andreas Weder
 updated  MGNLUI-3161


Offer different layout options in list and tree views
















Change By:


Andreas Weder
(18/Sep/14 2:33 PM)




Description:


Thelayoutofthelistandtreeviewisacompromisebetweenacompactlistofelementsandagenerousenoughlayouttoworkwellontabletdevices.Itworkswellfore.g.asmallsetofpages,butwealsoknow(andalsogetfeedbackthatsupportsthis)thatitfailsinavarietyofothercases:-Tree*levelsarenot
alwasy
always
clearlydiscernible*asthepaddingbetweenrowsisbig,whichdissociatescontentthatwouldbeeasiertoreadifclosertogether.-Wehavesometreesandlistswithalotofnodes,sometimesevenonasinglelevel.Forthesetrees,itwouldbe*beneficialtoseesignificantlymorerowsatatime*toavoidheavyscrolling.-The*rowsandarrowsontabletdevicesareactuallystilltoosmallontablets*toworkcomfortablyandsafely-wehadalargerpaddingbefore,whichworkedbest.Theres*actuallynoonelayoutthatworkswellonalldevicesandinallviews*.Weshouldthus*offertheuserthechoicebetweenasmallsetoflayoutoptionswithdifferentdensitylevels*,e.g.agenerous,thecurrentandacompactviewofalistandatree.-Fornon-technicalcontentsuchasPagesandAssets,wecouldshowlistsandtreesusingthecurrent,normallayoutondesktops,thegenerouslayoutontablets.-Fortechnicalcontentorsetswithlotsofitems,wewouldusethecurrent,compactlayoutondesktops,thenormallayoutontablets.-Foreverytreeandlist,theuserhastheoptiontochooseadifferentlayout.Note:thisissueisforrecordingtheneedfordifferentlayoutoptions.Whetheralayoutsettingispersistedornot,whetheritsdefinedpervieworperappandwhethertheresaglobalsettingsinauserprofiletopickadefaultlayoutforalltreeshastobediscussedstill.



























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-3120) Windows all browsers: On various actions the whole tree shifts quickly down and up again

2014-09-18 Thread JIRA (on behalf of Federico Grilli)














































Federico Grilli
 updated  MGNLUI-3120


Windows all browsers: On various actions the whole tree shifts quickly down and up again
















Change By:


Federico Grilli
(18/Sep/14 2:42 PM)




Fix Version/s:


5.2.10





Fix Version/s:


5.3.4



























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] (VANITY-8) Import + export creates duplicate entries

2014-09-18 Thread JIRA (on behalf of Jan Christian Haddorp)














































Jan Christian Haddorp
 created  VANITY-8


Import + export creates duplicate entries















Issue Type:


Bug



Affects Versions:


1.3.0



Assignee:


Frank Sommer



Created:


19/Sep/14 1:49 AM



Description:


After imported an existing XML dump the Vanity URL shows all entries twice.

Seems the entries have an identical ID as it is not possible to select just one.

Newly added entries behave normally.

Is there anything I can check? Sounds little strange; but I could reproduce it 2-3 times.




Project:


Vanity URL app



Priority:


Neutral




Reporter:


Jan Christian Haddorp




























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] (MGNLRSSAGG-185) Proposal: Replace crontab setting with interval

2014-09-18 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 updated  MGNLRSSAGG-185


Proposal: Replace crontab setting with interval
















Change By:


Cheng Hu
(19/Sep/14 4:38 AM)




Assignee:


AleksandrPchelintcev



























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