This is a humble suggestion to the hardworking maintainers of this module to add a feature whereby the Import feature could be used to update existing views in addition to importing new views.
Case in point: Developer makes a change to a view on his dev server. The view already exists on the production server. Sure, he could delete the old version on the production server and reimport the updated view, but this can sometimes be risky, as Views may have problems importing a new view for whatever reason.
An update feature would compare the imported view with the existing view and make whatever changes needed. The developer could then upload his templates and CSS quickly.
Thanks for a great module
Comments
Comment #1
merlinofchaos commentedhttp://drupal.org/node/474926 (patch attached)
Comment #2
eusebius commentedThanks for the quick response, but the link seems to be pointing to another issue related to exposed filters not showing. Is this the right link?
Comment #3
jeffschulerThe issue Merlin referenced as duplicated is indeed unrelated to this one.
Comment #4
dawehnerThat's right.
I would mark this issue as won't fix. There are already different solutions for this problem
a) export the views into code and let version control merge the views.
b) export the views into code with features module and let features and version control merge the views :)
Both ways works much much better then a build in views solution, from my perspective.
Comment #5
jeffschulerI agree that exporting views to code and tracking with version control is ultimately a more robust solution.
However, this feature would still be helpful in a good many cases where such a solution is not [yet] in place.
At any rate, this looks to actually be a duplicate of #421842: Allow imported views to overwrite existing views.