[MGNLRSSAGG-94] Add default node data in config workspace for backup setting of RSSFeedImportHandler Created: 06/Aug/13 Updated: 06/Dec/13 Resolved: 26/Aug/13 |
|
| Status: | Closed |
| Project: | Magnolia RSS Aggregator Module |
| Component/s: | None |
| Affects Version/s: | 1.2.4 |
| Fix Version/s: | 1.2.5, 1.4.3, 2.0.3 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Nils Breunese | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: |
| Description |
|
I noticed that since configuring the RSS aggregator to automatically import an external feed every hour I noticed that Magnolia started creating backup files every hour as well. It took some code digging to find that this behavior can be controlled by adding a node data called backup and setting it to false (since RSSFeedImportHandler extends ImportHandler and that class creates backups based on a property called backup which can be set via Content2Bean). It would be helpful if a default node data backup would have been bootstrapped by the RSS aggregator module and if the RSS aggregator module documentation would have mentioned this behavior. |
| Comments |
| Comment by Jan Haderka [ 26/Aug/13 ] |
|
Changes on master are in VH for 2.0.2, but release version in jira is set to 2.0.3 ... which is correct? |