Tomas Brimor
Tomas
Tomas
Tomas
Tomas Brimor
Tomas
Tomas
ItemNotFoundException thrown by DelegateNodeWrapper
Key: MAGNOLIA-4725
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4725
Project: Magnolia
Issue Type: Bug
Security Level:
[
http://jira.magnolia-cms.com/browse/BLOSSOM-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated BLOSSOM-103:
-
Priority: Trivial (was: Neutral)
Description: Issue was that we had not updated our
info.magnolia.module.dms.beans.Document cannot get JCR node
Key: MGNLDMS-255
URL: http://jira.magnolia-cms.com/browse/MGNLDMS-255
Project: Magnolia DMS Module
Issue Type:
No contextAttributes set in renderer when executing web flow component
--
Key: BLOSSOM-103
URL: http://jira.magnolia-cms.com/browse/BLOSSOM-103
Project: Magnolia Blossom Module
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated MGNLMIGRATION-170:
---
Priority: Blocker (was: Critical)
Magnolia migration module does not migrate
Magnolia migration module does not migrate templates using instead of []
---
Key: MGNLMIGRATION-170
URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-170
Project: Magnolia
Migration module breaks code which is using instead of [] when combined on
in a single expression
Key: MGNLMIGRATION-171
URL:
info.magnolia.module.blossom.template.TemplateDefinitionBuilder#resolveTemplateId
throws IllegalStateException (with empty error string) when class is missing
Template annotation
http://wiki.magnolia-cms.com/display/DEV/Using+the+Migration+module#UsingtheMigrationmodule-Process
is confusing
Key: DOCU-339
URL:
http://wiki.magnolia-cms.com/display/DEV/Running+the+migration+tool#Runningthemigrationtool-Whatthemigrationtooldoes
confuses reader as it references two specific modules
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated MGNLMIGRATION-160:
---
Description:
Running the MigrationRunner script without touching the
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated MGNLMIGRATION-160:
---
Environment: Magnolia 4.5.4 (during/post upgrade from 4.4.6)
Cannot cast
[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated MGNLMIGRATION-160:
---
Priority: Critical (was: Blocker)
Cannot cast object
Upgrading from 4.4.6 to 4.5.3 not possible due to no previous version of
Magnolia Pop Theme Module
--
Key: MAGNOLIA-4638
URL:
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated MAGNOLIA-4638:
---
Priority: Blocker (was: Major)
Upgrading from 4.4.6 to 4.5.3 not possible due to no
:magnolia-module-blossom-extension-data 2.0.1 has transative dependency on
info.magnolia:magnolia-module-scheduler 1.4.2 which is not compatible with
Magnolia 4.5.4
[
http://jira.magnolia-cms.com/browse/BLOSSOM-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated BLOSSOM-97:
Summary: magnolia-module-blossom-extension-data 2.0.1 has transative
dependency on
[
http://jira.magnolia-cms.com/browse/BLOSSOM-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated BLOSSOM-97:
Summary: magnolia-module-blossom-extension-data 2.0.1 has transitive
dependency on
Improve security API to allow testing arbitrary user's permissions
--
Key: MAGNOLIA-4589
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4589
Project: Magnolia
Issue Type:
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated MAGNOLIA-4589:
---
Priority: Major (was: Neutral)
Improve security API to allow testing arbitrary user's
Cannot start Magnolia with JRebel
-
Key: MAGNOLIA-4455
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4455
Project: Magnolia
Issue Type: Bug
Security Level: Public
Affects Versions: 4.5.3
Migration module script
scripts.migration.from4_4To4_5.general.UpdateMetaDataTemplateId does not handle
Blossom templates
-
Key: MGNLMIGRATION-29
blossom-extension-data magnolia module description depends on data 1.7-SNAPSHOT
version
---
Key: BLOSSOM-93
URL: http://jira.magnolia-cms.com/browse/BLOSSOM-93
Unable to delete nodes from UI with [ in the name
-
Key: MAGNOLIA-4429
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4429
Project: Magnolia
Issue Type: Bug
Security Level: Public
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated MAGNOLIA-4429:
---
Attachment: badname1.png
Unable to delete nodes from UI with [ in the name
10(?) seconds delay before templates are updated (blossom paragraphs with
templates stored in jcr)
--
Key: MGNLWEBDAV-30
URL:
Broken diff view - NullPointerException
---
Key: MAGNOLIA-4420
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4420
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components:
Consistent date display for website pages and website page versions
---
Key: MAGNOLIA-4403
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4403
Project: Magnolia
Issue Type:
35 matches
Mail list logo