[FLOW3-general] Help needed - test migration tools for FLOW3 1.0.0 alpha 7!

[Lucas Thurston]

I had forgotten to copy my .htaccess file. Package working!

Lucas Thurston wrote:
> I'm having a little less success. Here's what I did:
> 
> 1) pulled in the new source
> 2) copied the package I'm working on into the right spot
> 3) ran "migrate classnames" with no problems (nor did I have any 
> classnames that needed to be changed)
> 4) ran "migrate persistence" and got a PDOException (see below)
> 5) made the change to the flow3 shell script as Zach describes in his issue
> 6) activated my package successfully.
> 
> I'm getting a package not activated message on the front end though.
> 
> I'll keep plugging away, try to figure it out.
> 
> Here's my PDO exception:
> 
> $ ./flow3 migrate persistence
> 
> Fatal error: Uncaught exception 'PDOException' with message 
> 'SQLSTATE[HY000]: General error: 1 no such table: nodes' in 
> /opt/local/apache2/htdocs/flow3-a7/Packages/Framework/FLOW3/Scripts/migratepersistence.php:97 
> 
> Stack trace:
> #0 
> /opt/local/apache2/htdocs/flow3-a7/Packages/Framework/FLOW3/Scripts/migratepersistence.php(97): 
> PDO->prepare('SELECT "identif...')
> #1 
> /opt/local/apache2/htdocs/flow3-a7/Packages/Framework/FLOW3/Scripts/migratepersistence.php(80): 
> Migrator->export(Resource id #5)
> #2 
> /opt/local/apache2/htdocs/flow3-a7/Packages/Framework/FLOW3/Scripts/migratepersistence.php(810): 
> Migrator->run(Array)
> #3 {main}
>   thrown in 
> /opt/local/apache2/htdocs/flow3-a7/Packages/Framework/FLOW3/Scripts/migratepersistence.php 
> on line 97
> 
> thanks,
> Lucas
> 
> 
> Zachary Davis, Cast Iron Coding LLC wrote:
>> Karsten,
>>
>> Ok - took my time this time and upgraded the source correctly from 
>> SVN. Migration went of painlessly. I did notice that the package 
>> controller in the ./flow3 script is wrong, and I put in an issue on 
>> Forge. After updating to what's in trunk, I'm getting some new 
>> permission errors on directories being created in 
>> /Data/Temporary/###HASH###/Cache/Tags -- it seems that group write 
>> access isn't beein set. Could be a problem with how I've setup 
>> permissions, although I believe I ran setfilepermissions correctly.
>>
>> Zach