Issues with reverted features / lost nodeaccess settings when migrating / importing / cloning websites [#1062070]

Importat precondition:
- the installation you migrate / import must have different module paths then the old one

(10:24:33) EugenMayer: It seems like D6 has an issue when bootstrapping, when module-paths have been changed. I think this is very specific to features and also taxonomys. It seems like those things are disabled shorty, wiping the settings, and then enabled ( as found on a different place )
(10:24:40) EugenMayer: i could verify this:
(10:25:18) EugenMayer: 1. verify a site which just has been created deletes all nodeaccess entrys and node_type<->taxonomy entries
(10:25:56) EugenMayer: 2. copying the system table from that installation, importing it into the old database ( before truncate system ) and then boostrapping the old site
(10:26:45) EugenMayer: In step 1 you would have issues name above, in step 2 you can now perfectly import the site and no issues are there. I can reproduce this for all websites.
(10:27:09) EugenMayer: Just to mention, this is not an aegir issue, rather an Drupal 6 issue. But we might want to make this the default behavior.

Solution
(10:27:28) EugenMayer: 1. Boostrap database
(10:27:40) EugenMayer: 2. updatedb && cacheclear
(10:27:47) EugenMayer: 3. dump system table
(10:27:56) EugenMayer: 4. Wipe database & reimport database
(10:28:09) EugenMayer: 5. truncate system table + reimport dump

Iam not the only one having this issue, at least one person second me. "Reverted features after import".

beta2

Comments

Comment #1

EugenMayer CreditAttribution: EugenMayer commented 15 February 2011 at 09:36

Title:

Issues when migrating / importing / cloning websites

» Issues with reverted features / lost nodeaccess settings when migrating / importing / cloning websites

Comment #2

anarcat CreditAttribution: anarcat commented 11 March 2011 at 19:59

Status:

Active

» Fixed

i think i fixed this in git: we flush caches before running deploy now.

Comment #3

EugenMayer CreditAttribution: EugenMayer commented 11 March 2011 at 20:10

"you think" -> fixed. No comment. You did not even try to see if it is fixed.
An issue can also be a "conversation", it could be even a discussion.

You dont touch the issues for (1) week and then rush over to close them as fast as possible. You are not even giving me the slightest impression that you even try to test / reproduce the issues. Your goal is kind of to get rid of them as fast as possible.

But hey, just close it or whatever..

And no, its not fixed by that ( not even scratched it )

Comment #4

anarcat CreditAttribution: anarcat commented 11 March 2011 at 20:37

Dude, calm down. We can have a discussion if you don't freak out and start yelling at me.

I'm rolling out a new release. I'm processing all issues in the queue. I am sorry that the response time is not to your satisfaction, but if you would be willing to go forward, Koumbit would be happy to provide consulting to help you out with the issues you have with Aegir.

In the mean time, please describe how this is still a problem. I would like also a clarification on what exactly the issue *is*: from what I understand, it's related to modules being moved around.

I understand you may be frustrated by the discussion here, but here, I have no way to reproduce the issue. The bug report is essentially intelligible for me. Now that could be a language issue: english is not my native language. Please describe clearly what the symptoms are and what we can do to reproduce the problem.