Pathauto Persist is now obselete

[govcms]

Pathauto Persist is now obselete

[fiasco]

Yeah I agree that we do it with an update hook. I think that we'd also have to keep pathauto_persist in the codebase for at least one release until we could be assured that everyone has had the opportunity to uninstall the module.

[typhonius]

Could we follow a similar approach to that in #50 whereby we disable/uninstall pathauto persist (and remove it from the list of modules allowed to be enabled) in an update hook in one release. Then, in a following release we can remove it from the repo.

[mstrelan]

I don't think module_uninstall() exists. This also wouldn't cover the case where someone updates two versions in one hit.

[typhonius]

We'd have to use drupal_uninstall_modules(). For the govCMS platform, each site would be updated concurrently so no site would miss an update.

[mstrelan]

You'll also have to make sure pathauto_update_7006() runs before the govcms_update_N() function.

For the govCMS platform, each site would be updated concurrently so no site would miss an update.

Theoretically anyone can download the installation profile from drupal.org and update as they please, so I guess it depends if you want to support that or not.

[aleayr]

#355 is merged.