By bs on

Hi all,
I am planning to create a site based on Drupal 4.6.5. But my hosting provider’s MYSQL and PHP versions are latest. Is Drupal support this new versions? What should I do? Please help me.

⋅ Categories: Drupal 4.6.x

Comments

Jo Wouters’s picture

Jo Wouters commented

In the Handbook (Installation and upgrading / System requirements, http://drupal.org/node/270 ) you can find the PHP and MySQL-versions that are supported by Drupal:

As of Drupal 4.6, the CMS requires PHP version 4.3.3+ (PHP 5 is supported for the 4.6 release).

Recommended: MySQL, v3.23.17 or newer (for our use of INNER JOIN's with join_condition's). MySQL 4 is fine.

So I do not expect you will encounter problems.

heine’s picture

heine commented

1. As far as I know PHP 5.05+ is not compatible with the default Bluemarine and other XTemplate themes. Right after installation you'll have to switch to chameleon or marvin and download other themes from drupal.org.

Does anyone know if all modules on the download page are php5 compatible?

2. MySQL 5 can be run in strict mode. This mode causes some problems eg: upon posting:

user error: Field 'revisions' doesn't have a default value
query: INSERT INTO node [snip]

The chances are low your host is running mysql in this mode, because it breaks a lot of applications.

To see if your host runs MySQL in strict mode execute the query SELECT @@sql_mode.

Workarounds:
1- executing the query: SET GLOBAL sql_mode='MYSQL40'
2- starting mysqld with the option --sql-mode="MYSQL40"
3- changing sql-mode to "MYSQL40" in my.ini (Windows only?)

Only 1 is a viable solution for you, but requires SUPER priviliges on the database. If not and your host can't won't change that for you, you'll have to adapt drupal to execute SET SESSION sql_mode='MYSQL40' at the beginning of each connection.

--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

Jo Wouters’s picture

Jo Wouters commented

Thanks Heine,
I'm learning a lot here. :)

We might consider updating the handbook-page i referred to, so all this information is in the right spot and the handbook becomes more reliable.

heine’s picture

heine commented

You're welcome.

I'll file an issue against the system requirements page so someone with more rights than me can edit.

I'll also post a new entry in the troubleshooting faq.

--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

CnnmnSchnpps’s picture

CnnmnSchnpps commented

So if I upgrade to mysql 5, I would have to run it in strict mode for it to work with Drupal? Would I still be able to use any of the advanced features? (views, etc..)

heine’s picture

heine commented

The important phrase is probably:

MySQL 5 can be run in strict mode. This mode causes some problems [snip]

--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

bs’s picture

bs commented

Thank you very much for your detailed reply. I really love Drupal family because of this helping attitude. What about version 4.7.x? I know it is not fully ready. But I am ready to take risks.

heine’s picture

heine commented

Sorry for not answering earlier, but I didn't know before.
I've read somewhere (http://drupal.org/node/43827) that 4.7 core will not have this problem. This doesn't mean contributed modules will work in strict mode.

Developers are encouraged to run MySQL in the strictest mode and test queries for compatibility.
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

heine’s picture

heine commented

(duplicate)

heine’s picture

heine commented

I've done some more searching around @ MySQL.com Resources and need to add the following:

- SET GLOBAL sql_mode = 'modes' works on the entire server, not the database

- According to the MySQL.com sources MySQL 5 has no modes set by default. Some users however reported problems with strict mode on new MySQL installations, but I'm not sure that's because of the installer they used (XAMPP/whatever/?) or because the MySQL docs are incorrect.

Turns out: the docs are incorrect for Windows. When you install mysql-5.0.18-win32.zip from MySQL.com the setup gives you two options: Detailled Configuration and Standard Configuration.

Detailled Configuration will get you lots of screens where you have to choose option; near the end there's a screen with a prechecked [ ] Enable Strict mode checkbox with the helptext: This option forces the server to behave more like a traditional database server. It is recommended to enable this option. It is very likely that most people will leave strict mode on.

Standard configuration will result in a default configuration file in your install directory (my.ini). You won't be asked anything about strict mode. My.ini does contain the line:

# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

Clearly sql-mode is not '' by default on windows...

--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.