MODx Revolution 2.0.0 (formerly MODx 0.9.7)

I recently installed modx.2.0-alpha6 on my PC (windows XP) but I still have an error in index.php with $modx= new modX(). This statement raised an 503 error "site unavailable’. php_PDO extension is installed. I don’t find where the error is.

[FIXED] I have to run ’setup’ first

[TODO] The behaviour of new modX (modx.class.php) is strange when the config file doesn’t exists. I don’t see the need of including ’unavailable.error’ just before die.. because the 503 error is not clear and the user don’t understand the problem with config.ini because the die(message) is never displayed.

Quote from: alain91 at Jan 25, 2009, 08:32 AM

[TODO] The behaviour of new modX (modx.class.php) is strange when the config file doesn’t exists. I don’t see the need of including ’unavailable.error’ just before die.. because the 503 error is not clear and the user don’t understand the problem with config.ini because the die(message) is never displayed.

This was 100% intentional. You can customize the included error page to your heart’s content; the die() is last resort and only shown if the include fails.

Unfortunately, I’m unable to install the latest SVN - filling out all the database stuff first and then I’m getting a white page - turning on PHP errors, I’m getting the following:


Warning: modContext::include(/Users/Marco/Sites/cms/revolution/core/cache/mgr/context.cache.php) [modcontext.include]: failed to open stream: No such file or directory in /Users/Marco/Sites/cms/revolution/core/model/modx/modcontext.class.php on line 49

Warning: modContext::include() [function.include]: Failed opening ’/Users/Marco/Sites/cms/revolution/core/cache/mgr/context.cache.php’ for inclusion (include_path=’.:/Applications/MAMP/bin/php5/lib/php’) in /Users/Marco/Sites/cms/revolution/core/model/modx/modcontext.class.php on line 49

Fatal error: Call to a member function execute() on a non-object in /Users/Marco/Sites/cms/revolution/core/model/modx/modx.class.php on line 2252

Does anybody knows how to fix this and what’s causing this error?

Thank you in advance for your help.

mmjager,

check out this thread. http://modxcms.com/forums/index.php/topic,32865.0.html (page 2)

I had the same problem and solved it by running the build script and then re-running the setup scripts.

Running into troubles installing from the latest SVN (rev# 4832):

transport.core.php is now working again per the recently updated /core/xpdo/cache/xpdocachemanager.class.php, however when I try to go through the /setup, I can only get as far as "Connection Information" page.
I can test my database connection fine (Database connection successful!) but when I try to advance to the next page, I get the following error upon clicking "Next":

Error: invalid flag after regular expression
Source File: setup/assets/js/mootools.js
Line: 3, Column: 11
Source Code:
<b>Warning</b>:  array_merge() [<a href=’function.array-merge’>function.array-merge</a>]: Argument #2 is not an array in <b>core/model/modx/modx.class.php</b> on line <b>2520</b>

NOTE: This was attemptted via both "Upgrade Existing Install" & "Advanced Upgrade Install"

Have a look at this ticket, http://svn.modxcms.com/jira/browse/MODX-682, you need to clear your cache.

Quote from: shamblett at Mar 16, 2009, 06:20 PM

Have a look at this ticket, http://svn.modxcms.com/jira/browse/MODX-682, you need to clear your cache.

Ok, thanks shamblett. Tried this and setup worked as expected! Much appreciated

NOTE: Did notice a bunch of warnings...

Is it recommended to completely re-install during Alpha testing? (e.g. remove DB tables, etc)

Quote from: "Install

#

Error upgrading table for class modResource
Array
(
[0] => 42000
[1] => 1061
[2] => Duplicate key name ’published’
)
#

Error upgrading table for class modResource
Array
(
[0] => 42000
[1] => 1061
[2] => Duplicate key name ’pub_date’
)
#

Error upgrading table for class modResource
Array
(
[0] => 42000
[1] => 1061
[2] => Duplicate key name ’unpub_date’
)
#

Error upgrading table for class modResource
Array
(
[0] => 42000
[1] => 1061
[2] => Duplicate key name ’menuindex’
)

// etc...

Is it recommended to completely re-install during Alpha testing? (e.g. remove DB tables, etc)

Personally I’ve never had to do this, the upgrade function has always worked, so far anyway. To be honest I’ve not looked to much at warnings, if it doesn’t stop the rebuild/upgrade I haven’t pursued it too much. I’ll do an upgrade later, maybe we should start posting stuff like this in JIRA.

Quote from: shamblett at Mar 16, 2009, 07:12 PM

Personally I’ve never had to do this, the upgrade function has always worked, so far anyway. To be honest I’ve not looked to much at warnings, if it doesn’t stop the rebuild/upgrade I haven’t pursued it too much. I’ll do an upgrade later, maybe we should start posting stuff like this in JIRA.

The upgrade itself was successful, it preserved my content elements and sample documents, etc. The warnings I posted were "hidden" on the last step of the install, revealed by clicking on "Toggle" link. As far as I can tell, seems to be just fine...I certainly enjoy MODx’s short & sweet upgrade path

I’ve built and upgraded dozens of times and always get those "warnings." I have yet to lose any content. They aren’t really "warnings," more progress messages. If any real error or warning comes up, I don’t think you’ll have to toggle anything to see it.