[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kovařík reopened MAGNOLIA-4756:
-
{noformat}
79 SystemProperty.setProperty(magnolia.author.key.location,
[
http://jira.magnolia-cms.com/browse/MGNLACTIVATION-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kovařík reopened MGNLACTIVATION-9:
{noformat}
79 SystemProperty.setProperty(magnolia.author.key.location,
[
http://jira.magnolia-cms.com/browse/MGNLRES-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka updated MGNLRES-54:
---
Description:
Steps to reproduce: Create new item in Templating Kit/resources, click Edit
item:
Show all tabs puts group titles below tab content
-
Key: MGNLUI-601
URL: http://jira.magnolia-cms.com/browse/MGNLUI-601
Project: Magnolia UI
Issue Type: Sub-task
Security Level: Public
Dear all,
We are in the middle of the migration to 4.5 of our project. And as we know and
still believe:
migration is possible...
But now we are facing now an issue by rendering our test page, in the log-file
we see the following
error messages:
Caused By:
[
http://jira.magnolia-cms.com/browse/MGNLSTK-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Geljic reopened MGNLSTK-1058:
In {{STKTemplatingFunctions}}
{{getAssetsFromFolder}} calls {{dam.getAssetsFromFolder}}
but
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kovařík reopened MAGNOLIA-4756:
-
key.store.properties file should be deleted after the tests
Allow to obtain public key,
[
http://jira.magnolia-cms.com/browse/MGNLACTIVATION-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kovařík reopened MGNLACTIVATION-9:
key.store.properties file should be deleted after the tests
CLONE -Allow to
Hello Dominik
This means that something somewhere has not been updated yet (did you run the
content migration as well?), because [b]js[/b] should in fact be
[b]resources:js[/b] now (javascript type for the scripts in the resources
workspace).
If it's not the issue with the content, then it
[
http://jira.magnolia-cms.com/browse/MGNLUI-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Hechinger reopened MGNLUI-548:
---
Create adminInterface legacy module
---
Key:
Hi Natascha,
we are migrating from Magnolia 4.4.9-jr24 to 4.5.7 and yes, we did run the
migration scripts.
resources are exactly how you have them on Demo author.
Do you mean the theme modul? By the way, what do you mean with resources:js?
templating-kit/resources/js??
Thanks for your
No horizontal separators in Show all tab when using tabbed editing
Key: MGNLUI-602
URL: http://jira.magnolia-cms.com/browse/MGNLUI-602
Project: Magnolia UI
Issue Type: Bug
[
http://jira.magnolia-cms.com/browse/MGNLACTIVATION-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kovařík updated MGNLACTIVATION-9:
---
Comment: was deleted
(was: {noformat}
79
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kovařík updated MAGNOLIA-4756:
Comment: was deleted
(was: {noformat}
79
Hello again
Sorry to not have been clearer enough. This error is related to the resources
module (not only exclusively the path /templating-kit/resources/js). When you
add or edit an item in there, you can select its type from a dropdown. In fact,
if you see a column where it says Missing: js
Current implementation of TemplateCategoryUtil#isContentPage results into
infinite loop
---
Key: MGNLSTK-1075
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1075
[
http://jira.magnolia-cms.com/browse/MGNLSTK-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Lipp updated MGNLSTK-1075:
-
Summary: Infinite loop in TemplateCategoryUtil#isContentPage (was: Current
implementation of
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MGNLMIGRATION-212:
---
How is this resolved? There's no code change linked to this issue no comment
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MGNLMIGRATION-207:
---
Link this issue using caused by to one in which this file was accidentally
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MGNLMIGRATION-210:
---
First of all there is a typo in the title that should be fixed and second title
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kovařík updated MAGNOLIA-4791:
Description:
keystore.getParentFile().mkdirs(); - NPE
{noformat}
SecurityUtil.updateKeys() results in NPE when keystore is in current folder
---
Key: MAGNOLIA-4791
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4791
Project: Magnolia
[
http://jira.magnolia-cms.com/browse/MGNLACTIVATION-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kovařík reopened MGNLACTIVATION-9:
fix test after MAGNOLIA-4791 will be solved
CLONE -Allow to obtain public key,
Thanks Natascha,
this and a script from will fixed the issue.
Cheers
dominik
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=98fa688c-68a4-41c4-a6af-78225debb124
For list details, see:
[
http://jira.magnolia-cms.com/browse/MGNLUI-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Pchelintcev updated MGNLUI-603:
-
Labels: BL-97 (was: )
Allow arbitrary controls/indicators in form header.
Allow arbitrary controls/indicators in form header.
---
Key: MGNLUI-603
URL: http://jira.magnolia-cms.com/browse/MGNLUI-603
Project: Magnolia UI
Issue Type: Task
Security Level: Public
Show asset title in the form header for Asset editor sub-app form.
--
Key: MGNLDAM-91
URL: http://jira.magnolia-cms.com/browse/MGNLDAM-91
Project: Magnolia DAM Module
Issue
Hey there
Glad you got it working in the end. Is there any chance you could disclose what
the script looks like or at least describe what the script is doing
(conceptually) in case someone else finds this thread looking for answers?
Thank you :)
Cheers
Natascha
--
Context is everything:
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Lipp reopened MAGNOLIA-4787:
---
Pls add unit tests to cover new behavior.
Add executeCommand() method to the CommandsManager
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MGNLMIGRATION-203:
---
The above mentioned commit is about EOL change in
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Schmitt updated MGNLMIGRATION-211:
-
Summary: Transformation of extra area is not correct, custom template
[
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 has a conceptual issue, read the
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MGNLMIGRATION-206:
---
First commit seems to be completely unrelated to this ticket. Perhaps it
belongs
Hi Natascha
We have the standard setup for bigger projects (website module, theme module
and webapp in separate maven modules). We did upgrade the website module
according to the migration guidelines and (after a few hickups that we
already bothered you with) things seemed to have worked fine.
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MGNLMIGRATION-212:
---
Autobootstaping stkHome and stkSection override the template definitions with
an
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Schmitt updated MGNLMIGRATION-211:
-
Summary: Transformation of extra area is not correct, custom template
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Espen Jervidalo reopened MAGNOLIA-4783:
---
#ATTRIBUTE_SYNDICATOR never used
info.magnolia.cms.exchange.Syndicator#init deprecated
[
http://jira.magnolia-cms.com/browse/MGNLDAM-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Lipp reopened MGNLDAM-85:
We should not rely on exceptions for control flow. Looks like a could easily
check the type before
[
http://jira.magnolia-cms.com/browse/MGNLACTIVATION-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Grilli updated MGNLACTIVATION-8:
-
Description: After moving activation commands from adminInterface to this
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jozef Chocholacek updated MAGNOLIA-4784:
Description: Move the {{BaseRepositoryCommand}}, {{RuleBasedCommand}},
Rewrite commands w/o using deprecated code
--
Key: MAGNOLIA-4792
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4792
Project: Magnolia
Issue Type: Task
Security Level: Public
[
http://jira.magnolia-cms.com/browse/MGNLACTIVATION-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Grilli updated MGNLACTIVATION-10:
--
Affects Version/s: 5.0 Alpha2 s011
Description:
-
[
http://jira.magnolia-cms.com/browse/DOCU-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antti Hietala updated DOCU-369:
---
Description: Update [Templates
page|http://documentation.magnolia-cms.com/templates.html] to 4.5 (was:
[
http://jira.magnolia-cms.com/browse/MGNLPUR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Gange updated MGNLPUR-83:
-
Description:
This issue can best be reproduced using the demo site. Here are the steps:
1. Log
[
http://jira.magnolia-cms.com/browse/MGNLPUR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Gange updated MGNLPUR-83:
-
Description:
This issue can best be reproduced using the demo site. Here are the steps:
1. Log
[
http://jira.magnolia-cms.com/browse/MGNLPUR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated MGNLPUR-83:
--
Fix Version/s: 1.4.3
Priority: Critical (was: Neutral)
Change the editor used for the
Long tab name do not fit in space reserved
--
Key: MGNLUI-604
URL: http://jira.magnolia-cms.com/browse/MGNLUI-604
Project: Magnolia UI
Issue Type: Sub-task
Security Level: Public
App gets positioned wrong after browser resize
--
Key: MGNLUI-605
URL: http://jira.magnolia-cms.com/browse/MGNLUI-605
Project: Magnolia UI
Issue Type: Sub-task
Security Level: Public
48 matches
Mail list logo
