[MGNLACTIVATION-62] Warning message for template between servers Created: 18/Mar/08 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Activation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | William Cai | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Apache Tomcat/5.5.25, JVM1.5.0_11-b03, Linux 2.6.18-5-vserver-amd64 |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
For the following Scenario, I received some information regards with this issue from Boris (thank you very much indeed) and find out this is not a magnolia issue, the problem is with the system admin/web masters. But I really want to know, if there were more than 2 people in charge of taking care of magnolia and the above scenario happen, is there any method can take the precaution or damage control? Like, if one does not know there's no such template for every subscriber servers (or assume the other one did, but actually not) still directly make the deployment and activate the pages via magnolia GUI, would magnolia be able to detect the templates are the same version or at least the desired one does exist in the system? If anyone has any thoughts or having the similar question as mine, let discuss the resolution together. cheers |
| Comments |
| Comment by Boris Kraft [ 23/Mar/08 ] |
|
The packager (part of Enterprise Edition) can be used to keep installations in sync. Also, if you do your templating "right", you will have a custom module containing your custom templates and logic. This module should obviously be installed on all instances. |
| Comment by Jan Haderka [ 21/Sep/09 ] |
|
With 4.x and inplace-templating, this scenario is becoming again more likely since it is now possible to create templates on the fly directly in the author instance. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |