After upgrading a site to a new platform the symlink in ~/clients/me/example.com is still pointing to the old platform location.

In the code I saw that _provision_client_create_symlink() is called on install and verify, not on migrate.

In my opinion either _provision_client_create_symlink() should be added to the migrate process or a migrate should trigger a verify of the site.

Comments

anarcat’s picture

anarcat commented

I think you are correct. Care to try out a patch? :)

helmo’s picture

helmo commented

I'd prefer to first get consensus on the proper solution.

Adding it to the migrate process would probably be the quickest, but always running the verify might be more robust.

anarcat’s picture

anarcat commented

If we're not already running verify, I don't think we should be running it just for this.

omega8cc’s picture

omega8cc commented

I think that migrate (and clone) should trigger a (full) verify of the site, also to fix the other issue with not updated aliases in vhosts: #1004526: Automatic aliases are not persisted across rename and clone

steven jones’s picture

steven jones commented
Status: Active » Closed (cannot reproduce)

I'm fairly certain that this isn't an issue any more, since I know that the symlink is updated on migrate. Feel free to re-open if it still doesn't work with the latest version of Aegir.