General Questions
Topic: PHP and MySQL versions for myPHPNuke

Greetings,

Am getting errors when trying to access the Admin manual at http://www.myphpnuke.com/manual188/

Am trying to verify the PHP and MySQL versions myPHPNuke 1.8.8_8rc2 will function with.

I currently have PHP version 4.3.10 and MySQL version 4.0.25-standard.

The server admin would like to upgrade to PHP version 4.4.1 & MySQL version 4.1.x

Kindly advise.


-----------------
Cyrus
PromotionData.com
(A division of ThePromotionGroup network)

Thank you for your report. The domain has been moved this week to a new server and some hard paths had to be changed.

They are fixed by now and the manual is online available again.

I quote from the manual - an early 2005 user contributed note :



Another note in response says :



Would be grateful if the developers can clarify this for laymen like me.....is it possible to run myPHPNuke with PHP version 4.4.1 & MySQL version 4.1.x

Regards


-----------------
Cyrus
PromotionData.com
(A division of ThePromotionGroup network)

PHP not a problem providing you keep error reporting off.

For mysql, as far as I know mpn does not use the "password" column type. Beyond that, most of the changes required will be done by your hosting service. There are other changes that may or may not affect MPN, but most likely will not.

It is highly recommended you fully backup your database before they upgrade. In the worst case senario (i.e. table(s) incompatibility) you will need to dump and recreate the database/tables to upgrade them to 4.1. As far as I'm concerned your hosting service should do this for you, but probably will not.

http://dev.mysql.com/doc/refman/4.1/en/upgrading-from-4-0.html

And then there is certain a problem with wrong index definitions that we allowed in MySQL 3.x where 4.x will dump those index or even fail to create the table.

This is in particular the case with mpn_links_links, make sure that all duplicate fields (linkratingsummary) in the index definitions are removed before you transfer the table to your new server. Like I said, the index definition is wrong, duplicate fields are not needed but as they are around, they will fail to load on MySQL 4.1.

After that change, your myPHPNuke database will run fine on MySQL4.1.

A note on indexes. Repairing the tables may be the only step required to fix any index problems, however on new installs mysql will probably fail to install any table that has duplicate indexed columns. I am running my dev db on MySQL5 and all I did was optimized the tables from a db I was previously running on MySQL 4.0.x and have yet run into any problems accessing the db.