First of all, congrats, this is an awesome new feature in DNP and a far cry better than the app packs...I had to reverse engineer a few of those to update them and its just tedious.
I will be writing a general post about my wordpress install and success, however, now I'm trying to get the web gallery to install wordpress and I'm having a bit of an issue.
First all the mandatory intel...
DNP 2.8.3
Win server 2003, sp2, Enterprise Edition, 32 bit
3rd party version: MySQL 5.0.67-community-nt 64 bit
Error thrown by web app gallery installer when installing wordpress:
The following errors have been occured:
- GENERAL_INSTALL_ERROR:The database 'yful' could not be created.
A bit of possible useful information is that I have MySQL running on a non-standard port, which I have configured accordingly in DNP. Maybe this is an issue with the web gallery softwere? DNP doesn't seem to care, and it creates databases just fine with the non-standard port.
No Stack trace, but the following status message from the gallery installer:
| Source: |
WAG_INSTALLER |
| Task Name: |
INSTALL_WEB_APP |
| Item Name: |
WordPress |
| User: |
| |
|
| Started: |
5/8/2009 7:04:15 PM |
| Finished: |
5/8/2009 7:04:44 PM |
| Duration: |
00:00:28 |
| Severity: |
Information | |
Package ID: 61
00:00:00Site Name: yful.com
00:00:00Title: WordPress
00:00:00Version: 2.7.1
00:00:00Author: WordPress
00:00:00Last Updated: 3/18/2009 12:30:02 PM
00:00:00Unique Key for Passwords: put your unique phrase here
00:00:00Unique Key for Secure Passwords: put your unique phrase here
00:00:00Unique Key for Authentication: put your unique phrase here
00:00:00Second Unique Key for Authentication: put your unique phrase here
00:00:00Database Username: yful
00:00:00Database Password: jetlink1
00:00:00Database Name: yful
00:00:00WAG_INSTALLER_GET_APP_PARAMS_TASK
The problem is that the install of wordpress succeeds, in that it installs wordpress files and correctly configures the wordpress config file with the correct settings, etc. And in the audit log, the message is blue, like all went well, however, after you have filled in the info on the wordpress install page in the web gallery installer, and then click install, after is finishes, it displays a red error banner simply saying it could not "create" the database. In this instance, I had already created the database and user and told it to just use the existing db and user.
Now, if you try to create a new mysql database, you get:
The following errors have been occured:
- Web Gallery Application installation failure
- Please check audit log for additional information or contact your hosting service provider to resolve the error.
00:00:00Package ID: 61
00:00:00Site Name: yful.com
00:00:00Title: WordPress
00:00:00Version: 2.7.1
00:00:00Author: WordPress
00:00:00Last Updated: 3/18/2009 12:30:02 PM
00:00:00Unique Key for Passwords: put your unique phrase here
00:00:00Unique Key for Secure Passwords: put your unique phrase here
00:00:00Unique Key for Authentication: put your unique phrase here
00:00:00Second Unique Key for Authentication: put your unique phrase here
00:00:00Database Username: yfull
00:00:00Database Password: jetlink1
00:00:00Database Name: yfull
00:00:00WAG_INSTALLER_GET_APP_PARAMS_TASK
00:00:06Could not create MySQL5 database. Error code: -902.
...and nothing works. Yes, I verified that there is enough quota for the mysql database for this web site
and I was able to create it manually from dnp after the app gallery freaked out.
In the case where I had pre-created the mysql db, when you run the install.php file from wordpress directly, it creates its own database just fine, with the credentials encoded in the pre-configured wp-config.php file, so that is a curiosity.
So, the flaw I'm reporting is that the installer is throwing an unnecessary red flag (when you seperately pre-create the mysql db and user) that confuses users and (will, I'm quite sure) prompt an immediate support call, when it actually worked fine. Why does the installed want to "create" the database when I told it to use an existing one? And why the hard crash when I ask it to create a fresh database?
//
//
//