Are the php scripts on the same server as the mysql database?
It seems like your project settings got corrupted or did not persist. Did you start with a non server project and later on changed it to php or modified the server settings? This issue is fixed in our latest builds.
For you currently the workaround will be to create a new project again and select server type as PHP at the creation time itself. Then you can follow the regular 'generate from data base' or import workflow.
Thanks for replying, it works now!
At first I got the error below, but after putting a ZendFramework folder in the /Library/Webserver/Documents folder my settings got accepted.
Warning: require_once(Zend/Loader/Autoloader.php) [function.require-once]: failed to open stream: No such file or directory in /Users/johan/Sites/test/tempgateway.php on line 27
Fatal error: require_once() [function.require]: Failed opening required 'Zend/Loader/Autoloader.php' (include_path='.:/usr/lib/php:/Library/WebServer/Documents/ZendFramework/library') in /Users/johan/Sites/test/tempgateway.php on line 27
I think this is some kind of bug too, since I let the project wizard create a local ZendFramework folder in my project automatically, but it did not get used.
It would really be great to have the webroot on a remote server through ftp or maybe afp in a private network to the remote server, but with only tapping into the remote database already solves a lot of problems for the workflow.
In order to make this work (mysql remote connection) one should create a user on the mysql server with host '%' instead of 'localhost'.
Since this is not very secure, you could also set the host to your external IP (if its not dynamic), or give that user only rights to your testdatabase.
No, the php files and the mysql server are
not on the same server. The php files are local and the mysql server is remote over the internet.
Gaurav P gave the solution in a workaround for a bug that should have been solved in a next release of Flash Builder 4
The bug you are mentioning is already resolved in our latest builds. This should be available in the next public release.