Allow imported views to overwrite existing views

@Moonshine: this is great btw :)
one thing i noticed -- page displays that were in the initial view are still there even if replaced with a view that has no displays

=)

Though I'm not sure why the existing displays remain. The save routine SHOULD remove them.

well... I should clarify my results -- the displays do *appear* removed in the Views UI, but when i visit the old path for a page display - it's still there :p

I cleared the caches for good measure too.

actually I don't even remember how I tried this... maybe i got there from clicking the [edit] link above the view so I returned after importing... anyway, this is what seemed kind of interesting -- that a diff view seemed to be there than what was available in the UI

Also Moonshine mentioned that it might be trying to merge -- which i agree could be a cool option if that was possible :D

Is this still actually a problem that requires patching? If it is, the patch needs to be re-checked for consistency with the current version

No updates for more than 30 days.

I added this issue before and it was marked as duplicate pointing here. But now I'm here it's closed because no work was done for 30 days.

Please @moonshine I hope you will finish this and add it to the module.

Thanks

The patch works great when updating settings for the same view. I didn't test the removed display issue, but I'd say this is usable for most cases.
Thanks!

I am dying for this feature too. For Content Types, also. I'm making the exact same (many!) changes to 9 websites! Incredibly time consuming. (If only Features modules was reliable.)

Anyone know if that patch still works for Views 2 -- specifically Views 6.x-2.12 (and Drupal 6.22)?

UPDATE: Well, I just went for it. And, so far, so good. Moonshine, you rock.

@greta_drupal
The views specific part of features just uses the views module functionality, which works really fine.

Additional this part would only be commited to 6.x-3.x and for 7.x-3.x a patch against ctools would have to be created.

Well, with this sad fact and this recent experience, nothing for me to do but retire. Life off the land. No, no. Don't try to talk me out of it!

Just tested the patch

* A new display display saved is replaced
* A property stored on the view itself is replaced as well.
* A property on a display is replaced as well.
* If the view has more displays in the database the import with override kills them.

So from my perspective it's RTBC. Perhaps this was an old bug?

That's a great feature! Commited to 6.x-3.x

I think this would be certainly a great addition for 7.x as well.

Ported the patch to 7.x-3.x and it works great.

@dereine, can you review? We are looking forward to this feature for all of our installs. Helps us with migrating across environments.

The patch looks fine, thanks for porting the patch! Just committed it to 7.x-3.x.