[MAGNOLIA-1504] dev tool: scheduled exports Created: 03/May/07 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
When developing a site or module, it oftens happen that you modifiy dialogs, paragraphs or other configuration items, then for some reason have to start from a clean repo... and sometimes forget to export the modified items first. This tool would simply allow to have backups and be safer |
| Comments |
| Comment by Magnolia International [ 07/Apr/08 ] |
|
This will hopefully be realized with 3.6 |
| Comment by Magnolia International [ 27/Jun/08 ] |
|
http://openutils.sourceforge.net/openutils-mgnlbootstrapsync/ looks like a viable alternative to implementing this ourselves |
| 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. |