[MAGNOLIA-2282] Content of mgnl-files is no longer installed on the server when deploying our custom module Created: 14/Jul/08  Updated: 17/Mar/09  Resolved: 23/Jul/08

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: Stéphane Gauthier Assignee: Philipp Bärfuss
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Version EE 3.5.8


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

We have custom module developped with version 3.0.5 that no longer copies the content of mgnl-files to our server, we are about to migrate magnolia to the version 3.5.8 and we are blocked by this issue. Many thanks in advance for your help. Could you update the documentation regarding the custom modules too?



 Comments   
Comment by Magnolia International [ 14/Jul/08 ]

is this related to the poll module ?

Comment by Magnolia International [ 23/Jul/08 ]

Please use the users list (http://documentation.magnolia.info/#Mailinglists) or the appropriate support channel if you have a support contract with us (http://documentation.magnolia.info/support.html)

(mgnl-files contents get extracted on each update (ie your module's version number need to be different) as long as the extracted content hasnt' changed (md5 of extracted content is stored and checked before overwriting files)

Generated at Mon Feb 12 03:35:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.