Answered Local Install won't test selection of created database - MODX REVOLUTION VERSION 2.2.9-PL

One thing that I have noted is that there is a change in PHP 5.5.x that can cause issues to go messy during installation. You -need- to ensure that the new PHP 5.5 opcode caching is disabled during the installation.

If this is not done, the installation will go wonky in various ways.

One such thing I experienced was that the install would complete (on my own setup.) but would not allow me to login thereafter.

My first guess here would be that you have the PHP opcode caching enabled. (This is by the module name: opcache.so (or .dll on windows).

It should be loaded with a line along the following lines:

zend_extension=opcache.so

Disabling this should get you moving in the right direction.

Thanks for this post! I had also trouble installing modx since i upgraded to php 5.5.3. Disabling opcache solved the problem for now...

My pleasure! You can also re-enable the opcode caching after installation, and everything seems to work just fine.

Quote from: flanger at Oct 24, 2013, 03:48 AM

Thanks for this post! I had also trouble installing modx since i upgraded to php 5.5.3. Disabling opcache solved the problem for now...

Ok, this allows MAMP 2.2 to work with PHP 5.5.3. Does anyone know why it's doing this? Could it be the "memory_consumption" setting of 128 isn't enough?

[edit] Changing the "memory_consumption" setting to 256 appears to have solved the problem. Installation of the latest Revo 2.3 goes smoothly. [ed. note: sottwell last edited this post 12 years, 9 months ago.]

I'm not experiencing any issues with installing Revo on PHP 5.5 with the Zend opcode cache enabled. If you are experiencing these issues still, any additional details you can provide would be appreciated.

@sottwell: I also have not had any problem installing with memory_limits of 64M or 128M. Are you upgrading a particularly large installation when this occurs?

New installation of 2.3. I installed another copy and even with the memory limit set to 256 it still wouldn't create a database or connect to an existing one. It may have been an issue with the servers being restarted, so it needs more experimentation. Sometimes it'll do it and sometimes it won't.

Just to chirp in that I'm having this issue too.
The install looks to go OK but then i'm unable to log in to the Manager and it appeared no tables were created in the database.
I commented out all instances of 'opache' in my php.ini file as discussed here: http://stackoverflow.com/questions/19073270/stop-caching-for-php-5-5-3-in-mamp - but this didn't help either.
The only way I got 2.3 to set up correctly was to change to PHP version 5.2.17 in the MAMP preferences.

FWIW, I plan to do some additional testing with MODX 2.3 and specifically PHP 5.5 (w/ Zend OPcache kept enabled), so I will be sure to update this group in the event I run into any similar issues. Appreciate the heads up!

Any other known issues w/ MODX and PHP 5.5+ that I should be aware of? (looking into potential upgrade in the coming weeks...)

UPDATE:
Bug # 9037 seems to be related, more findings here: https://github.com/modxcms/revolution/issues/9037#issuecomment-35756827 [ed. note: pixelchutes last edited this post 12 years, 7 months ago.]