[magnolia-dev] [JIRA] Created: (DOCU-367) Ability to set maximum number of components in areas
Ability to set maximum number of components in areas Key: DOCU-367 URL: http://jira.magnolia-cms.com/browse/DOCU-367 Project: Documentation Issue Type: Task Security Level: Public Components: templating Affects Versions: mid term Reporter: Roman Kovařík Assignee: Antti Hietala Fix For: mid term Attachments: maxComponents.png In STK 2.0.9 is possible to set maximum number of components in areas (see attached screenshot). The components above the limit won't be added. When adding/removing directly on page, add button disappear when the limit is reached. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLFORM-147) Previous *and* next steps of a form should be displayed.
Previous *and* next steps of a form should be displayed. Key: MGNLFORM-147 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-147 Project: Magnolia Form Module Issue Type: Improvement Affects Versions: 1.4.4 Reporter: Grégory Joseph Fix For: 1.4.x The form dialog has an option to display steps of a form on each page/step: "Check to display a step-by-step form navigation. The navigation will appear, if form sub-steps are defined." It currently only display previous steps. While that might be a valid behavior in some cases, in other cases, people expect to also see how much they still have to go through before being done with the form. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLSCH-37) Job persistence and reliability
Job persistence and reliability
---
Key: MGNLSCH-37
URL: http://jira.magnolia-cms.com/browse/MGNLSCH-37
Project: Magnolia Scheduler Module
Issue Type: Improvement
Reporter: Grégory Joseph
Assignee: Philipp Bärfuss
Priority: Major
This is perhaps a topic that needs discussions before implementation. Here's a
couple of examples. Let's say I have 3 configured jobs.
# configured to run every 5 minutes.
# configured to run once a day at 4pm.
# one-shot, set to run on Jan 15 at 3pm.
Now, assume my server goes down on Jan 15 at 2pm for 3 hours. It comes back up
at 5pm (I know this example is highly unrealistic ;))
Here's what I'd want to happen, ideally:
* Job {{3}} gets executed once, at startup or shortly thereafter. Ideally, it
logs that it was supposed to be executed earlier.
* Job {{2}} gets executed at startup or shortly thereafter. Ideally, it logs
that it was supposed to be executed earlier. The following days, it falls back
into it's regular 4pm schedule.
* Job {{1}} gets executed again, starting at 5pm, then 5.05, 5.10, etc. This
already works.
** Since it's such a short-repeat job, I wouldn't want it to be execute 36
times to compensate for the 3 hours down time.
I guess what I'm getting at is we'd need
- a mechanism that would ensure jobs gets executed even if their scheduled time
has passed. I think what we have today is a warning that "this job will never
be executed", when restarting the server.
- a way to enable/disable the above behavior, because it is not always
desirable (cfr example 1)
If I recall correctly, Quartz has an API to store job states - but our current
implementation uses an in-memory implementation.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLDMS-259) Toolbar can appear in browse mode of dms tree popup
[
http://jira.magnolia-cms.com/browse/MGNLDMS-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated MGNLDMS-259:
---
Summary: Toolbar can appear in browse mode of dms tree popup (was: Browse
mode of DMS tree doesn't refresh itself properly)
Priority: Major (was: Neutral)
> Toolbar can appear in browse mode of dms tree popup
> ---
>
> Key: MGNLDMS-259
> URL: http://jira.magnolia-cms.com/browse/MGNLDMS-259
> Project: Magnolia DMS Module
> Issue Type: Bug
>Affects Versions: 1.6.5
>Reporter: Grégory Joseph
>Priority: Major
> Attachments: Screen Shot 2013-01-15 at 14.55.38.png
>
>
> When opening a {{dms}} tree in browse mode - i.e when selecting a document
> for linking to from a page - one can double-click on items. While this has
> some advantages (is this "new" btw ?), like the fact one can see more details
> about a document, or a preview of an image, it also lets them modify the
> document. Worse, when saving such dialog, the tree refreshes itself in normal
> mode, i.e with the function bar and all. See attached screenshot.
> To reproduce:
> * http://demoauthor.magnolia-cms.com/demo-project/about/history.html
> * Edit header
> * Select a DMS image, click "internal link" to browse (why is that button not
> labeled "Browse"?)
> * Double-click on any image in the newly opened popup tree
> * Click on Save in the newly opened DMS edit dialog.
> * -> The tree popup has been refreshed and now has a semi-broken toolbar.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLDMS-259) Browse mode of DMS tree doesn't refresh itself properly
Browse mode of DMS tree doesn't refresh itself properly
---
Key: MGNLDMS-259
URL: http://jira.magnolia-cms.com/browse/MGNLDMS-259
Project: Magnolia DMS Module
Issue Type: Bug
Affects Versions: 1.6.5
Reporter: Grégory Joseph
Attachments: Screen Shot 2013-01-15 at 14.55.38.png
When opening a {{dms}} tree in browse mode - i.e when selecting a document for
linking to from a page - one can double-click on items. While this has some
advantages (is this "new" btw ?), like the fact one can see more details about
a document, or a preview of an image, it also lets them modify the document.
Worse, when saving such dialog, the tree refreshes itself in normal mode, i.e
with the function bar and all. See attached screenshot.
To reproduce:
* http://demoauthor.magnolia-cms.com/demo-project/about/history.html
* Edit header
* Select a DMS image, click "internal link" to browse (why is that button not
labeled "Browse"?)
* Double-click on any image in the newly opened popup tree
* Click on Save in the newly opened DMS edit dialog.
* -> The tree popup has been refreshed and now has a semi-broken toolbar.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4773) Remove "keep versions" checkbox from Import/Export Tool
Remove "keep versions" checkbox from Import/Export Tool --- Key: MAGNOLIA-4773 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4773 Project: Magnolia Issue Type: Improvement Security Level: Public Components: admininterface Reporter: Richard Gange Priority: Minor Attachments: Screen Shot 2013-01-15 at 1.08.07 PM.png, Screen Shot 2013-01-15 at 1.09.00 PM.png Hide/Remove the "keep versions" checkbox option from the Import/Export tool in adminCentral -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLSTK-1070) Teste Magnolia Template Kit
Teste Magnolia Template Kit --- Key: MGNLSTK-1070 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1070 Project: Magnolia Standard Templating Kit Issue Type: Task Affects Versions: 2.5 Environment: Magnolia 5.0 Reporter: Meio e Mensagem Development Team Attachments: search - magnolia tempalte kit.PNG I try to use a test from magnolia template kit. i'm using the template search with model info.magnolia.module.templatingkit.search.SearchResultModel i'm try to retrieve files im documents too. how i can include this files in result search? i checked in API, you need to pass the repository, but i dont find where this repository is defined to retrieve only contents in repository i'm looking for. the question is, I'want to include the files in my result search. what i need to do? Thanks -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-563) Content App: switching between tabs throws client side exception
Content App: switching between tabs throws client side exception Key: MGNLUI-563 URL: http://jira.magnolia-cms.com/browse/MGNLUI-563 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Components: content app Affects Versions: 5.0 Alpha2 s011 Reporter: Espen Jervidalo Priority: Blocker Fix For: 5.0 Alpha2 s012 Open contact in tab, switch to address tab, co to contacts list and back, bam! -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (DOCU-366) More detailed and centralized documentation about inheritance
More detailed and centralized documentation about inheritance
-
Key: DOCU-366
URL: http://jira.magnolia-cms.com/browse/DOCU-366
Project: Documentation
Issue Type: Task
Security Level: Public
Components: content
Reporter: Natascha Desmarais
Assignee: Antti Hietala
Fix For: mid term
When writing some training material I came across the question what the
difference was between having {{components=none}} or {{enabled=false}} for an
{{inheritance}} node in areas/components.
The difference is that you can have inheritance enabled, but you do not want to
inherit the data, only the settings, so {{components=none}} makes sense if you
combine it with {{properties=all}} for example. {{properties=all}} enables the
inheritance of the properties set in the area's definition, such as title,
description, etc.
However, I wasn't even aware of the {{properties}} property and I couldn't find
any place where this was mentioned. Another problem with that is that there are
several places where inheritance is used but it is not detailed enough and you
can get lost while looking for it.
Therefore this is a recommendation on what to do:
* Detailed reference for the inheritance feature and its settings ^[1]^
(properties, default values, explanation)
* Centralized information under
http://documentation.magnolia-cms.com/reference.html for example (or any better
suiting place)
These are all the pages that contain some pieces of valuable information about
inheritance:
*
(http://documentation.magnolia-cms.com/reference/components.html#Relateddocumentation
- links to the next link)
* http://wiki.magnolia-cms.com/display/WIKI/Inheritable+components
*
http://documentation.magnolia-cms.com/templates/stk/template-prototype.html#Componentinheritance
* http://documentation.magnolia-cms.com/reference/areas.html - The image on the
bottom actually contains all of the properties ^[2]^ I would be interested in
for inheritance!
^[1]^,^[2]^ possible properties for inheritance:
* components - all | filtered | none
* enabled - true | false
* nodeComparatorClass -
* predicateClass -
* properties - all | none
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-562) Replace MGWT's ScrollPanel in MagnoliaTabSheet
Replace MGWT's ScrollPanel in MagnoliaTabSheet -- Key: MGNLUI-562 URL: http://jira.magnolia-cms.com/browse/MGNLUI-562 Project: Magnolia UI Issue Type: Improvement Security Level: Public Components: tablet, user interaction Reporter: Mikael Geljic MagnoliaTabSheetViewImpl uses a ScrollPanel from MGWT to scroll content within one tab/or all at once with show all. Supposedly, this was preferred over a plain GWT ScrollPanel because the latter does seem to play nicely with touch (see http://gwt.googleusercontent.com/samples/Showcase/Showcase.html#!CwDockPanel). However the Panel component, as seen on the vaadin sampler, seems to handle touch nicely - it has momentum, bounces, feels native. We should use MGWT for touch events only, not for UI components, because MGWT theme introduces inline styles that interfere with our own styles (e.g. fonts, as seen in SCRUM-1688) -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-210) Step Remove template redundancy is only triggered when the migration is done on 1 site defintion
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-210: - Summary: Step Remove template redundancy is only triggered when the migration is done on 1 site defintion (was: Remove the step Remove template redundancy from the default migration) Description: By defintion this step is doing: After the migration of the templates it could happen that a property has the same value on the prototype and on a template. When a property has the same value in the prototype and in a concrete template, this property is defined as redundant and could be removed. In this logic we think that a page template is only referenced by one site definition. But this is wrong ! So we can only run this task when we have 1 site definition to migrate. The task can be triggered by the version of a module if the developer knows that the pages templates of its module are only used by one site def. Then this task is helpful to do a kind of cleanup. was: By defintion this step is doing: After the migration of the templates it could happen that a property has the same value on the prototype and on a template. When a property has the same value in the prototype and in a concrete template, this property is defined as redundant and could be removed. In this logic we think that a page template is only referenced by one site definition. But this is wrong ! So the logic is not relevant and this step must be remove from the process. The task can be triggered by the version of a module if the developer knows that the pages templates of its module are only used by one site def. Then this task is helpful to do a kind of cleanup. > Step Remove template redundancy is only triggered when the migration is done > on 1 site defintion > > > Key: MGNLMIGRATION-210 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-210 > Project: Magnolia Migration > Issue Type: Bug > Components: Migration Task >Affects Versions: 1.2 >Reporter: Samuel Schmitt >Assignee: Samuel Schmitt >Priority: Major > Fix For: 1.2.1 > > > By defintion this step is doing: > After the migration of the templates it could happen that a property has the > same value on the prototype and on a template. > When a property has the same value in the prototype and in a concrete > template, this property is defined as redundant and could be removed. > In this logic we think that a page template is only referenced by one site > definition. But this is wrong ! > So we can only run this task when we have 1 site definition to migrate. > The task can be triggered by the version of a module if the developer knows > that the pages templates of its module are only used by one site def. Then > this task is helpful to do a kind of cleanup. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4745) Name of uploaded logo image is used as headline text
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kovařík updated MAGNOLIA-4745: Attachment: info.zip Hello Leo, you can avoid this issue manually by adding fixed class to your WEB-INF folder. Extract attached info.zip into your apache-tomcat-6.0.32/webapps/magnoliaAuthor/WEB-INF/classes folder. The resulting structure of folders will be WEB-INF/classes/info/magnolia/module/admininterface/SaveHandlerImpl.class. Best regards, Roman > Name of uploaded logo image is used as headline text > > > Key: MAGNOLIA-4745 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4745 > Project: Magnolia > Issue Type: Bug > Security Level: Public > Components: admininterface >Affects Versions: 4.5.7 > Environment: http://demo.magnolia-cms.com/demo-project.html >Reporter: Jan Christian Haddorp >Assignee: Roman Kovařík > Fix For: 4.5.8 > > Attachments: home_props.png, info.zip > > > When uploading a logo image (no DMS image) then the image name is used as > headline. > Even when changing the headline text it is reset to the image name. > Can be reproduced on the STK test instance. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLUI-504) Security App: Does not close normally
[ http://jira.magnolia-cms.com/browse/MGNLUI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp updated MGNLUI-504: --- Description: Sometimes it closes after you click the close button a few times. Sometimes it closes, but the app tile on the apps launcher screen is still hilighted. Perhaps this has to do with having many subapps open. If you close all the subapps by hand, and then close the app it appears to close correctly. was: Sometimes it closes after you click the close button a few times. Sometiems it closes, but the app tile on the apps launcher screen is still hilighted. Perhaps this has to do with having many subapps open. If you close all the subapps by hand, and then close the app it appears to close correctly. > Security App: Does not close normally > - > > Key: MGNLUI-504 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-504 > Project: Magnolia UI > Issue Type: Sub-task > Security Level: Public >Affects Versions: 5.0 Alpha2 s011 >Reporter: Christopher Zimmermann >Assignee: Aleksandr Pchelintcev > Fix For: 5.0 Alpha2 s011 > > > Sometimes it closes after you click the close button a few times. > Sometimes it closes, but the app tile on the apps launcher screen is still > hilighted. > Perhaps this has to do with having many subapps open. > If you close all the subapps by hand, and then close the app it appears to > close correctly. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-205) The message [ERROR] Error while finding script of update-training:pages/updateHome: Couldn't assign any prototype for this template! must be chang
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-205: - Component/s: Report Template Script Migration > The message [ERROR] Error while finding script of > update-training:pages/updateHome: Couldn't assign any prototype for this > template! must be change > -- > > Key: MGNLMIGRATION-205 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-205 > Project: Magnolia Migration > Issue Type: Bug > Components: Report, Template Script Migration >Affects Versions: 1.2 >Reporter: Samuel Schmitt > Fix For: 1.2.1 > > > This message is displayed in the TemplateMigration report. > It is displayed because no templateScript is found in a template definition. > In my case updateHome extends stkHome and overrride the title... nothing more. > My template definition is correct and so I dont expect any error message. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-561) Get rid of a hacked workaround for Vaadin #10663
Get rid of a hacked workaround for Vaadin #10663 Key: MGNLUI-561 URL: http://jira.magnolia-cms.com/browse/MGNLUI-561 Project: Magnolia UI Issue Type: Task Security Level: Public Affects Versions: 5.0 Alpha2 s012 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s012 -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-209) In the migration report a step has the name of the task that calls it - so all the tasks have the same name
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-209: - Component/s: Report > In the migration report a step has the name of the task that calls it - so > all the tasks have the same name > --- > > Key: MGNLMIGRATION-209 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-209 > Project: Magnolia Migration > Issue Type: Improvement > Components: Report >Reporter: Samuel Schmitt >Assignee: Jozef Chocholacek > Fix For: 1.2.1 > > Attachments: Screen Shot 2013-01-11 at 3.38.52 PM.png > > > When you open a report you will see that all the task have the same name even > if they are not the same. I think that a task take the name of its parent > task. This must be improved. > See the screenshot. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-195) Parsing error on tags with interpolation
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Schmitt updated MGNLMIGRATION-195:
-
Component/s: Template Script Migration
> Parsing error on tags with interpolation
>
>
> Key: MGNLMIGRATION-195
> URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-195
> Project: Magnolia Migration
> Issue Type: Bug
> Components: Template Script Migration
>Affects Versions: 1.1.5
>Reporter: Robert Šiška
>Assignee: Robert Šiška
> Fix For: 1.2.1
>
>
> Parser fails on following code:
> {code}
> <${some code}>
> content
>
> {code}
> Parser expects alphanumerical name of the tag after '<' symbol, not
> interpolation.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLUI-561) Get rid of a hacky workaround for Vaadin #10663
[ http://jira.magnolia-cms.com/browse/MGNLUI-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Pchelintcev updated MGNLUI-561: - Summary: Get rid of a hacky workaround for Vaadin #10663 (was: Get rid of a hacked workaround for Vaadin #10663) > Get rid of a hacky workaround for Vaadin #10663 > --- > > Key: MGNLUI-561 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-561 > Project: Magnolia UI > Issue Type: Task > Security Level: Public >Affects Versions: 5.0 Alpha2 s012 >Reporter: Aleksandr Pchelintcev >Assignee: Aleksandr Pchelintcev >Priority: Critical > Fix For: 5.0 Alpha2 s012 > > -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-213) UpdateExtendsMigrationTask fails on relative paths
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-213: - Component/s: Migration Task > UpdateExtendsMigrationTask fails on relative paths > -- > > Key: MGNLMIGRATION-213 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-213 > Project: Magnolia Migration > Issue Type: Bug > Components: Migration Task >Affects Versions: 1.2 >Reporter: Ondřej Chytil > Fix For: 1.2.1 > > > See linked support ticket for details. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-198) Migration report of a component FTL is not clear enough, version handler code is missing.
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-198: - Component/s: Report Template Script Migration > Migration report of a component FTL is not clear enough, version handler code > is missing. > - > > Key: MGNLMIGRATION-198 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-198 > Project: Magnolia Migration > Issue Type: Improvement > Components: Report, Template Script Migration >Affects Versions: 1.2 >Reporter: Samuel Schmitt >Assignee: Robert Šiška >Priority: Major > Fix For: 1.2.1 > > Attachments: Screen Shot 2013-01-08 at 9.59.23 AM.png > > > Please have a look at the screenshot. > When you read that you understand that a area colLeft is detected. > Then you have a code snippet after [code] > Is it relevant? What information should it give to the developer? > At least we could mention that from this code we detected a area to create. > I also expect that the code that creates colLeft definition is available on > the page. > The code snippet to add in the version handler must be available. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-201) Detected area template script should not be created with the name of the node collection
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Schmitt updated MGNLMIGRATION-201:
-
Component/s: Template Script Migration
> Detected area template script should not be created with the name of the node
> collection
>
>
> Key: MGNLMIGRATION-201
> URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-201
> Project: Magnolia Migration
> Issue Type: Bug
> Components: Template Script Migration
>Affects Versions: 1.2
>Reporter: Samuel Schmitt
>Assignee: Robert Šiška
>Priority: Critical
> Fix For: 1.2.1
>
>
> When in a FTL we detect something like this
> {code}
> [@cms.contentNodeIterator contentNodeCollectionName="colLeft"]
> [@cms.includeTemplate /] [/@cms.contentNodeIterator] [@cms.newBar
> contentNodeCollectionName="colLeft"
> paragraph="stkTextImage,updatePageNavigationList,updateDocumentNavigationList"
> /]
> {code}
> We create a new template script for the detected area which is named with the
> name of the node collection.
> See in the log:
> {code}
> Detected area 'colLeft' (save as /update-training/paragraphs/colLeft.ftl)
> {code}
> I could have another FTL that has a contentNodeIterator where
> nodeCollectionName is the same but need for its area a specific template
> script.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-200) Migration task that creates an Area definition is missing when in the FTL the pattern paragraph="${def.subParagraphs}" is found
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Schmitt updated MGNLMIGRATION-200:
-
Component/s: Template Script Migration
> Migration task that creates an Area definition is missing when in the FTL the
> pattern paragraph="${def.subParagraphs}" is found
> ---
>
> Key: MGNLMIGRATION-200
> URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-200
> Project: Magnolia Migration
> Issue Type: Bug
> Components: Template Script Migration
>Affects Versions: 1.2
>Reporter: Samuel Schmitt
>Assignee: Robert Šiška
>Priority: Major
> Fix For: 1.2.1
>
> Attachments: threeColumns.ftl, threeColumns_before.ftl
>
>
> Look at the two FTLs attached. One is before the FTL migration and one after.
> In the FTL threeColumns.ftl, the area tags are correctly created. I expect
> that in the report there is something about that and about the code to add is
> the version.. but nothing.
> This is the log of the report
> {code}
> updateThreeColumns
> Log records:
> [INFO] [updateThreeColumns] Migrating component updateThreeColumns
> (/update-training/paragraphs/threeColumns.ftl)
> [INFO] [updateThreeColumns] OK
> {code}
> OK is really meaningful !!
> Here I expect something that tell me that 3 areas were detected and that the
> template definitions referencing /update-training/paragraphs/threeColumns.ftl
> must be updated. If we cannot provide the code that will update these
> definitions, at least we could mention that something must be done.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-210) Remove the step Remove template redundancy from the default migration
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-210: - Component/s: Migration Task > Remove the step Remove template redundancy from the default migration > - > > Key: MGNLMIGRATION-210 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-210 > Project: Magnolia Migration > Issue Type: Bug > Components: Migration Task >Affects Versions: 1.2 >Reporter: Samuel Schmitt >Assignee: Samuel Schmitt >Priority: Major > Fix For: 1.2.1 > > > By defintion this step is doing: > After the migration of the templates it could happen that a property has the > same value on the prototype and on a template. > When a property has the same value in the prototype and in a concrete > template, this property is defined as redundant and could be removed. > In this logic we think that a page template is only referenced by one site > definition. But this is wrong ! > So the logic is not relevant and this step must be remove from the process. > The task can be triggered by the version of a module if the developer knows > that the pages templates of its module are only used by one site def. Then > this task is helpful to do a kind of cleanup. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-197) Template scripts of detected areas are not created
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-197: - Component/s: Template Script Migration > Template scripts of detected areas are not created > -- > > Key: MGNLMIGRATION-197 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-197 > Project: Magnolia Migration > Issue Type: Bug > Components: Template Script Migration >Affects Versions: 1.2 >Reporter: Samuel Schmitt >Assignee: Robert Šiška >Priority: Critical > Fix For: 1.2.1 > > > When an area is found the report tell me that a FTL is created. > Ex: Detected area 'colLeft' (save as > /update-training/paragraphs/colLeft.ftl) > But colLeft.ftl is not created !! -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-202) FTL migration doesnt detect basic STK pattern
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Schmitt updated MGNLMIGRATION-202:
-
Component/s: Template Script Migration
> FTL migration doesnt detect basic STK pattern
> -
>
> Key: MGNLMIGRATION-202
> URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-202
> Project: Magnolia Migration
> Issue Type: Bug
> Components: Template Script Migration
>Affects Versions: 1.2
>Reporter: Samuel Schmitt
>Assignee: Robert Šiška
> Fix For: 1.2.1
>
>
> After the FTL update I still have code not correctly updated
> {code}
>
> [#if def.header.enabled]
> [#include def.header.template]
> [/#if]
>
>
> [#if def.platformArea.enabled]
> [#include def.platformArea.template]
> [/#if]
>
> [#if def.breadcrumb.enabled]
> [#include def.breadcrumb.template]
> [/#if]
> [#--OLD [#include def.mainArea.template] --][@cms.area
> name = "main" content=content /]
> {code}
> Header, platform, breadcrumd are standard STK pattern. We must do something.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-199) Template Script Migration report is not correctly setup in the main migration page
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-199: - Component/s: Report > Template Script Migration report is not correctly setup in the main migration > page > -- > > Key: MGNLMIGRATION-199 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-199 > Project: Magnolia Migration > Issue Type: Improvement > Components: Report >Affects Versions: 1.2 >Reporter: Samuel Schmitt > Fix For: 1.2.1 > > Attachments: Screenshot_1_8_13_10_09_AM.png > > > When you open the report (from the ZIP) the part regarding the Template > Script Migration is a bit weird. > First you see in the list of modules TemplateMigration, but this is not a > module. > Template Migration report must have an independant section... and maybe must > be renamed Template SCRIPT migration. > Second, you have another section called Components. This section displays > links to Components templates script migration report BUT also to Pages > template script migration report. > Maybe it will be more clear if we create a section called Template Script > Migration report where the first link is the link TemplateMigration and then > the list of links to the pages and components. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-560) Add an installation task that will delete commands from the admin interface module to the legacy module's version handler
Add an installation task that will delete commands from the admin interface module to the legacy module's version handler - Key: MGNLUI-560 URL: http://jira.magnolia-cms.com/browse/MGNLUI-560 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-559) Create Link to Download (DMS) field
Create Link to Download (DMS) field --- Key: MGNLUI-559 URL: http://jira.magnolia-cms.com/browse/MGNLUI-559 Project: Magnolia UI Issue Type: Task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Eric Hechinger Assignee: Eric Hechinger Fix For: 5.0 Alpha2 s012 Add a Dialog migration task allowing to create a Dam link field for the download link dialog For example under: demo-project/home, on a link list add a Download link. This download link should open a DAM selection dialog. Currently it's a static field with a unsuported field comment. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-558) Fields: number fields using default converter and introduces number format point
Fields: number fields using default converter and introduces number format point Key: MGNLUI-558 URL: http://jira.magnolia-cms.com/browse/MGNLUI-558 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Espen Jervidalo Assignee: Espen Jervidalo Fix For: 5.0 Alpha2 s012 see https://vaadin.com/forum/-/message_boards/view_message/2237684 -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-557) Fields: can not use empty string as default value for objects not equal string
Fields: can not use empty string as default value for objects not equal string -- Key: MGNLUI-557 URL: http://jira.magnolia-cms.com/browse/MGNLUI-557 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Espen Jervidalo Assignee: Espen Jervidalo Fix For: 5.0 Alpha2 s012 Due to changes in vaadins field implementation, we can no longer use empty string for values different than string. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLSTK-1069) When migrating from 4.4.x to 4.5, the complete definition of stkHome and stkSection are bootstrapped in the PostMigration and it adds the wrong configura
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Natascha Desmarais updated MGNLSTK-1069: Summary: When migrating from 4.4.x to 4.5, the complete definition of stkHome and stkSection are bootstrapped in the PostMigration and it adds the wrong configuration (was: When migration from 4.4.x to 4.5, the complete definition of stkHome and stkSection are bootstrapped in the PostMigration and it add add wrong configuration) > When migrating from 4.4.x to 4.5, the complete definition of stkHome and > stkSection are bootstrapped in the PostMigration and it adds the wrong > configuration > - > > Key: MGNLSTK-1069 > URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1069 > Project: Magnolia Standard Templating Kit > Issue Type: Bug > Components: templates >Reporter: Samuel Schmitt >Assignee: Samuel Schmitt > Fix For: 2.0.9 > > > Remove from > /mgnl-bootstrap/migration/standard-templating-kit/config/templates the 2 > wrong definition and add only the piece of the configuration that must be > changed. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLSTK-1069) When migration from 4.4.x to 4.5, the complete definition of stkHome and stkSection are bootstrapped in the PostMigration and it add add wrong configurat
When migration from 4.4.x to 4.5, the complete definition of stkHome and stkSection are bootstrapped in the PostMigration and it add add wrong configuration Key: MGNLSTK-1069 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1069 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: templates Reporter: Samuel Schmitt Assignee: Samuel Schmitt Fix For: 2.0.9 Remove from /mgnl-bootstrap/migration/standard-templating-kit/config/templates the 2 wrong definition and add only the piece of the configuration that must be changed. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-206) Inheritance - it should not be configured in a page definition but only in the site definition
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-206: - Component/s: Migration Task > Inheritance - it should not be configured in a page definition but only in > the site definition > -- > > Key: MGNLMIGRATION-206 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-206 > Project: Magnolia Migration > Issue Type: Bug > Components: Migration Task >Affects Versions: 1.2 >Reporter: Natascha Desmarais >Assignee: Samuel Schmitt > Fix For: 1.2.1 > > Attachments: > config.modules.extended-templating-kit.config.sites.update-training.xml, > migration_inheritance_behavior.png > > > As we set by default an inheritance configuration on all extra nodes (site > def and pages template), this has a drawback when we want to change the > default setting. > Let's say by default it's on "components=all" and i want "components = > filtered". I have to update the sitedef and remove it form all the pages > templates. > For this reason we must just put the inheritance config in the site def. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-211) Transformation of extra area is not correct
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-211: - Component/s: Migration Task > Transformation of extra area is not correct > --- > > Key: MGNLMIGRATION-211 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-211 > Project: Magnolia Migration > Issue Type: Bug > Components: Migration Task >Affects Versions: 1.2 >Reporter: Samuel Schmitt >Assignee: Samuel Schmitt >Priority: Critical > Fix For: 1.2.1 > > > Many issues identified: > - if you define your own ftl for the extra, it's simply overridden by the > migration > - extra 1 is not created for a page template, extra is in fact not well > created for a page > Things has to be reviewed in > info.magnolia.migration.task.stk.TransformStkBasedTemplateMigrationTask.transformExtrasToSubAreas(Node) > -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLWORKFLOW-22) Use thread-safe parser
[
http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Grilli updated MGNLWORKFLOW-22:
Priority: Major (was: Critical)
> Use thread-safe parser
> --
>
> Key: MGNLWORKFLOW-22
> URL: http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-22
> Project: Magnolia Workflow Module
> Issue Type: Task
> Components: jBPM
>Reporter: Federico Grilli
>Assignee: Federico Grilli
>Priority: Major
> Fix For: 1.0 Alpha2 s012
>
>
> Currently {{info.magnolia.module.workflow.jbpm.JbpmWorkflowUtil}} is using a
> class-level instance of non thread-safe {{java.text.SimpleDateFormat}} to
> perform some parsing in method {{computeDelay()}}. True that method is
> synchronized but since we use joda-time anyway, we could just take advantage
> of its thread-safe {{DateTimeFormatter}} object and remove synchronization.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLWORKFLOW-21) Update project setup
[ http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLWORKFLOW-21: Fix Version/s: 1.0 Alpha2 s012 (was: 1.0) > Update project setup > > > Key: MGNLWORKFLOW-21 > URL: http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-21 > Project: Magnolia Workflow Module > Issue Type: Task > Components: Base, Build, jBPM >Reporter: Federico Grilli >Assignee: Federico Grilli >Priority: Major > Fix For: 1.0 Alpha2 s012 > > > We need proper setup for the workflow-module and the driving webapp (the one > coming with the EE bundle) > - cleanup of poms > - change Maven groupId to info.magnolia.workflow (pattern) > - update the embedded webapp config -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLWORKFLOW-22) Use thread-safe parser
[
http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Grilli updated MGNLWORKFLOW-22:
Fix Version/s: 1.0 Alpha2 s012
(was: 1.0)
> Use thread-safe parser
> --
>
> Key: MGNLWORKFLOW-22
> URL: http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-22
> Project: Magnolia Workflow Module
> Issue Type: Task
> Components: jBPM
>Reporter: Federico Grilli
>Assignee: Federico Grilli
>Priority: Critical
> Fix For: 1.0 Alpha2 s012
>
>
> Currently {{info.magnolia.module.workflow.jbpm.JbpmWorkflowUtil}} is using a
> class-level instance of non thread-safe {{java.text.SimpleDateFormat}} to
> perform some parsing in method {{computeDelay()}}. True that method is
> synchronized but since we use joda-time anyway, we could just take advantage
> of its thread-safe {{DateTimeFormatter}} object and remove synchronization.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (DOCU-304) Documentation for subtemplates being treated same as variations since 4.5
[ http://jira.magnolia-cms.com/browse/DOCU-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antti Hietala updated DOCU-304: --- Attachment: variation.png > Documentation for subtemplates being treated same as variations since 4.5 > - > > Key: DOCU-304 > URL: http://jira.magnolia-cms.com/browse/DOCU-304 > Project: Documentation > Issue Type: Task > Security Level: Public > Components: content >Affects Versions: short term >Reporter: Jan Haderka >Assignee: Ruth Stocks >Priority: Major > Fix For: short term > > Attachments: variation.png > > > Since fixing MAGNOLIA-4412 subtemplates are variations in MAgnolia 4.5. > Documentation needs to reflect this. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (DOCU-304) Documentation for subtemplates being treated same as variations since 4.5
[
http://jira.magnolia-cms.com/browse/DOCU-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antti Hietala updated DOCU-304:
---
Comment: was deleted
(was: Tips:
* Configure the variation under each page template where you need it. "Site
wide" variations configured under the site definition cannot be triggered by
extension. So if you have five page templates in your site (home, article, news
etc.) and you want to configure a {{smartphone}} variation for all of them, you
need to create the variation five times, once under each page template.
* The demo-project has an example variation configured in *Templating Kit >
Template Definitions >* {{/pages/stkHome/variations/smartphone}}. This
variation disables the {{stage}} area.
* To trigger the variation, request the page with the variation content node
name as the extension.
http://demopublic.magnolia-cms.com/demo-project.smartphone
* When a variation is resolved by extension, no theme is applied. Themes are
configured in a site definition. Only in the case of variation resolved by
channel do we merge the site definition and its variation. This means that a
variation triggered by extension cannot have a different theme. The default
theme is used. Compare:
** Requesting the page with a channel attribute applies a theme.
http://demopublic.magnolia-cms.com/demo-project.html?mgnlChannel=smartphone
** Requesting the page with an extension does not apply a theme.
http://demopublic.magnolia-cms.com/demo-project.smartphone)
> Documentation for subtemplates being treated same as variations since 4.5
> -
>
> Key: DOCU-304
> URL: http://jira.magnolia-cms.com/browse/DOCU-304
> Project: Documentation
> Issue Type: Task
> Security Level: Public
> Components: content
>Affects Versions: short term
>Reporter: Jan Haderka
>Assignee: Antti Hietala
>Priority: Major
> Fix For: short term
>
> Attachments: variation.png
>
>
> Since fixing MAGNOLIA-4412 subtemplates are variations in MAgnolia 4.5.
> Documentation needs to reflect this.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLWORKFLOW-22) Use thread-safe parser
[
http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Grilli updated MGNLWORKFLOW-22:
Fix Version/s: 1.0
Description: Currently
{{info.magnolia.module.workflow.jbpm.JbpmWorkflowUtil}} is using a class-level
instance of non thread-safe {{java.text.SimpleDateFormat}} to perform some
parsing in method {{computeDelay()}}. True that method is synchronized but
since we use joda-time anyway, we could just take advantage of its thread-safe
{{DateTimeFormatter}} object and remove synchronization.
> Use thread-safe parser
> --
>
> Key: MGNLWORKFLOW-22
> URL: http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-22
> Project: Magnolia Workflow Module
> Issue Type: Task
> Components: jBPM
>Reporter: Federico Grilli
>Assignee: Federico Grilli
>Priority: Critical
> Fix For: 1.0
>
>
> Currently {{info.magnolia.module.workflow.jbpm.JbpmWorkflowUtil}} is using a
> class-level instance of non thread-safe {{java.text.SimpleDateFormat}} to
> perform some parsing in method {{computeDelay()}}. True that method is
> synchronized but since we use joda-time anyway, we could just take advantage
> of its thread-safe {{DateTimeFormatter}} object and remove synchronization.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLWORKFLOW-22) Use thread-safe parser
Use thread-safe parser -- Key: MGNLWORKFLOW-22 URL: http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-22 Project: Magnolia Workflow Module Issue Type: Task Components: jBPM Reporter: Federico Grilli Assignee: Federico Grilli Priority: Critical -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLWORKFLOW-19) Upgrade to JUnit 4.11
[ http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLWORKFLOW-19: Fix Version/s: 1.0 Alpha2 s011 Affects Version/s: (was: 1.0 Alpha2 s011) > Upgrade to JUnit 4.11 > - > > Key: MGNLWORKFLOW-19 > URL: http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-19 > Project: Magnolia Workflow Module > Issue Type: Improvement >Reporter: Daniel Lipp >Assignee: Daniel Lipp > Fix For: 1.0 Alpha2 s011 > > -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-556) iPhone: Admincentral wont start
iPhone: Admincentral wont start --- Key: MGNLUI-556 URL: http://jira.magnolia-cms.com/browse/MGNLUI-556 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Reporter: Samuli Penttilä Priority: Major After login progress bar keeps going forever on white blank background and admincentral will not load. Tested with simulator and device. iPhone iOS version 6.0 -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLUI-555) iPad simulator: Buttons wont respond
[ http://jira.magnolia-cms.com/browse/MGNLUI-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuli Penttilä updated MGNLUI-555: --- Summary: iPad simulator: Buttons wont respond (was: iOS simulator: Buttons wont respond) > iPad simulator: Buttons wont respond > > > Key: MGNLUI-555 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-555 > Project: Magnolia UI > Issue Type: Sub-task > Security Level: Public >Reporter: Samuli Penttilä >Priority: Major > > App launcher buttons get selected but not pressed with iOS simulator. Haven't > tested with real hardware so this may be reproducible with HW as well. > Impossible to launch any apps. > Simulator iOS version 6.0 -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLUI-555) iOS simulator: Buttons wont respond
[ http://jira.magnolia-cms.com/browse/MGNLUI-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuli Penttilä updated MGNLUI-555: --- Description: App launcher buttons get selected but not pressed with iOS simulator. Haven't tested with real hardware so this may be reproducible with HW as well. Impossible to launch any apps. Simulator iOS version 6.0 was:App launcher buttons get selected but not pressed with iOS simulator. Haven't tested with real hardware so this may be reproducible with HW as well. Impossible to launch any apps. > iOS simulator: Buttons wont respond > --- > > Key: MGNLUI-555 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-555 > Project: Magnolia UI > Issue Type: Sub-task > Security Level: Public >Reporter: Samuli Penttilä >Priority: Major > > App launcher buttons get selected but not pressed with iOS simulator. Haven't > tested with real hardware so this may be reproducible with HW as well. > Impossible to launch any apps. > Simulator iOS version 6.0 -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLUI-548) Create adminInterface legacy module
[ http://jira.magnolia-cms.com/browse/MGNLUI-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Chocholacek updated MGNLUI-548: - Component/s: legacy > Create adminInterface legacy module > --- > > Key: MGNLUI-548 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-548 > Project: Magnolia UI > Issue Type: Task > Security Level: Public > Components: legacy >Reporter: Jozef Chocholacek >Assignee: Jozef Chocholacek > Fix For: 5.0 Alpha2 s012 > > > # create infrastructure for the module (maven module in magnolia_ui) > # move commands sources from the 4.5.x magnolia_main to the new module -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-554) Add bootstrap files to the legacy module
Add bootstrap files to the legacy module Key: MGNLUI-554 URL: http://jira.magnolia-cms.com/browse/MGNLUI-554 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLUI-549) Fix VersionCommandTest to use new MetaData API
[ http://jira.magnolia-cms.com/browse/MGNLUI-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Chocholacek updated MGNLUI-549: - Component/s: legacy > Fix VersionCommandTest to use new MetaData API > -- > > Key: MGNLUI-549 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-549 > Project: Magnolia UI > Issue Type: Sub-task > Security Level: Public > Components: legacy >Reporter: Jozef Chocholacek >Assignee: Jozef Chocholacek > Fix For: 5.0 Alpha2 s012 > > > The VersionCommandTest uses old MetaData API (expects MetaData sub-node to > exist). Has to be rewritten in respect to changes in that API (to use mgnl: > properties). -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-555) iOS simulator: Buttons wont respond
iOS simulator: Buttons wont respond --- Key: MGNLUI-555 URL: http://jira.magnolia-cms.com/browse/MGNLUI-555 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Reporter: Samuli Penttilä Priority: Major App launcher buttons get selected but not pressed with iOS simulator. Haven't tested with real hardware so this may be reproducible with HW as well. Impossible to launch any apps. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-214) The folder /resources/auto_bootstraps_after_migration is no more use by PostMigrationTask
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-214: - Component/s: Migration Task > The folder /resources/auto_bootstraps_after_migration is no more use by > PostMigrationTask > - > > Key: MGNLMIGRATION-214 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-214 > Project: Magnolia Migration > Issue Type: Bug > Components: Migration Task >Affects Versions: 1.2 >Reporter: Samuel Schmitt >Assignee: Samuel Schmitt > Fix For: 1.2.1 > > > Since 1.2, if you want to bootstrap configuration with the task > PostMigrationTask, you have to add these configuration under > /mgnl-bootstrap/migration/module-name. > Folder /resources/auto_bootstraps_after_migration can be deleted. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLUI-552) Vertical alignments and heights need review after update to HTML5 doctype
[
http://jira.magnolia-cms.com/browse/MGNLUI-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Geljic updated MGNLUI-552:
-
Summary: Vertical alignments and heights need review after update to HTML5
doctype (was: Vertical alignments and heights need review)
> Vertical alignments and heights need review after update to HTML5 doctype
> -
>
> Key: MGNLUI-552
> URL: http://jira.magnolia-cms.com/browse/MGNLUI-552
> Project: Magnolia UI
> Issue Type: Sub-task
> Security Level: Public
> Components: design
>Reporter: Mikael Geljic
>
> Upgrade to vaadin 7 also brought in the HTML5 doctype, which treats height,
> line-height and vertical alignment of elements differently.
> The sensible part is when using the CSS rule {{display:inline-block}}.
> There's a nice detailed explanation of this in the following thread:
> http://stackoverflow.com/questions/3003051/why-does-the-html5-doctype-mess-with-my-padding.
> We should make sure to use inline-block sparingly.
> As a result, some elements in the UI are no longer in line with the
> guidelines for visual styles, including but not only:
> - Main launcher divet position
> - Apps launcher position
> - Content view padding around the table
> - Action bar position
> - Height and paddings of table lines and headers
> - Search bar position
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-81) Create PostMigration Task
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Natascha Desmarais updated MGNLMIGRATION-81: Release notes required: [Yes] > Create PostMigration Task > - > > Key: MGNLMIGRATION-81 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-81 > Project: Magnolia Migration > Issue Type: Sub-task >Affects Versions: 1.1.2 >Reporter: Eric Hechinger >Assignee: Eric Hechinger > Fix For: 1.2 > > -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-553) Split views are broken on client restore
Split views are broken on client restore Key: MGNLUI-553 URL: http://jira.magnolia-cms.com/browse/MGNLUI-553 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Reporter: Mikael Geljic Split views, as used in favorites or pulse dashboard for instance, are not visible between the immediate client transition and the server update. This is a size calculation problem, when hiding those views (e.g. switching to another shellapp), their width is set to 0, and is only restored when going through server update. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLUI-553) Split views are broken on client restore
[ http://jira.magnolia-cms.com/browse/MGNLUI-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Geljic updated MGNLUI-553: - Component/s: user interaction > Split views are broken on client restore > > > Key: MGNLUI-553 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-553 > Project: Magnolia UI > Issue Type: Sub-task > Security Level: Public > Components: user interaction >Reporter: Mikael Geljic > > Split views, as used in favorites or pulse dashboard for instance, are not > visible between the immediate client transition and the server update. > > This is a size calculation problem, when hiding those views (e.g. switching > to another shellapp), their width is set to 0, and is only restored when > going through server update. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-552) Vertical alignments and heights need review
Vertical alignments and heights need review
---
Key: MGNLUI-552
URL: http://jira.magnolia-cms.com/browse/MGNLUI-552
Project: Magnolia UI
Issue Type: Sub-task
Security Level: Public
Components: design
Reporter: Mikael Geljic
Upgrade to vaadin 7 also brought in the HTML5 doctype, which treats height,
line-height and vertical alignment of elements differently.
The sensible part is when using the CSS rule {{display:inline-block}}. There's
a nice detailed explanation of this in the following thread:
http://stackoverflow.com/questions/3003051/why-does-the-html5-doctype-mess-with-my-padding.
We should make sure to use inline-block sparingly.
As a result, some elements in the UI are no longer in line with the guidelines
for visual styles, including but not only:
- Main launcher divet position
- Apps launcher position
- Content view padding around the table
- Action bar position
- Height and paddings of table lines and headers
- Search bar position
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLMIGRATION-214) The folder /resources/auto_bootstraps_after_migration is no more use by PostMigrationTask
The folder /resources/auto_bootstraps_after_migration is no more use by PostMigrationTask - Key: MGNLMIGRATION-214 URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-214 Project: Magnolia Migration Issue Type: Bug Affects Versions: 1.2 Reporter: Samuel Schmitt Assignee: Samuel Schmitt Fix For: 1.2.1 Since 1.2, if you want to bootstrap configuration with the task PostMigrationTask, you have to add these configuration under /mgnl-bootstrap/migration/module-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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-214) The folder /resources/auto_bootstraps_after_migration is no more use by PostMigrationTask
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-214: - Description: Since 1.2, if you want to bootstrap configuration with the task PostMigrationTask, you have to add these configuration under /mgnl-bootstrap/migration/module-name. Folder /resources/auto_bootstraps_after_migration can be deleted. was:Since 1.2, if you want to bootstrap configuration with the task PostMigrationTask, you have to add these configuration under /mgnl-bootstrap/migration/module-name > The folder /resources/auto_bootstraps_after_migration is no more use by > PostMigrationTask > - > > Key: MGNLMIGRATION-214 > URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-214 > Project: Magnolia Migration > Issue Type: Bug >Affects Versions: 1.2 >Reporter: Samuel Schmitt >Assignee: Samuel Schmitt > Fix For: 1.2.1 > > > Since 1.2, if you want to bootstrap configuration with the task > PostMigrationTask, you have to add these configuration under > /mgnl-bootstrap/migration/module-name. > Folder /resources/auto_bootstraps_after_migration can be deleted. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
