Alpha 6 Update problem

Hi !

I’m working on an Alpha-5 installation, and for my tests I’ve made several chunks, snippets, templates and TV.
I tried upgrading it to Alpha-6, and encountered several problems :
- at first, the installer stays blank after upgrading, it doesn’t get to the exit screen saying everything went ok and where you can delete the setup folder.
That’s not a very big problem, since the site sorta works afterwards... sorta.
- in the manager, almost everything seems to work... except for templates, TV and chunks which disapeared ! I mean the folders are here in the treeview, but they are empty.

For the moment, that’s all I see.
Will the beta version, and the final release, be able to upgrade from alpha versions ?

Quote from: Thalion at Dec 05, 2008, 05:19 AM

Hi !

I’m working on an Alpha-5 installation, and for my tests I’ve made several chunks, snippets, templates and TV.
I tried upgrading it to Alpha-6, and encountered several problems :
- at first, the installer stays blank after upgrading, it doesn’t get to the exit screen saying everything went ok and where you can delete the setup folder.
That’s not a very big problem, since the site sorta works afterwards... sorta.
- in the manager, almost everything seems to work... except for templates, TV and chunks which disapeared ! I mean the folders are here in the treeview, but they are empty.

For the moment, that’s all I see.
Will the beta version, and the final release, be able to upgrade from alpha versions ?

You should be able to no problem - I ran quite a few tests on this beforehand. A few questions:

1. Is there anything in your core/cache/logs/error.log that would shed light on the situation?
2. Try clearing your browser’s cache.
3. Try downloading alpha-6 again and running install again.

If those don’t work, post your server info and stuff and we’ll try and debug it.

Tried again with a new download, still the same : I click on the "install" button, it works a little then dispays a blank page (setup/index.php?action=install) -> it’s an error page "can not display this page" in IE (I use Firefox mostly)
Error.log is empty.
cache was cleared, both on the server and the browser.

My config :
Windows XP SP3
xampplite 1.6.8 :
# Apache HTTPD 2.2.9 + Openssl 0.9.8i
# MySQL 5.0.67
# PHP 5.2.6

I can’t understand what’s wrong, as a fresh install works perfectly !

I’m having a similar problem with pretty much the same setup (except I have Vista) on XAMPP 1.6.8.

I’ve updated from SVN and done a build but when I click on the install button, Apache crashes and I get the "cannot display page" error. Nothing in the MODx error log, the Apache error log shows "process exited with code 255" message, which I think means an infinite loop somewhere.

On another different localhost site, I had that problem with FF but not IE. After installing with IE, I had an Apache crash on that site only when I tried to access the front end. The Manager worked, but trying to preview the site didn’t. If I came at the front end directly, I could see the home page, but clicking on a link to any other page crashed Apache (255 again). I spent a several hours trying to debug it and narrowed it down to the document parser and parsing the tags in the page but couldn’t zero in on any particular code.

I did find that if I commented out line 419 of modparser.class.php, Apache didn’t crash, but I didn’t get any closer than that.



It didn’t crash the first time that line was hit, but did the second time. Unfortunately, I’ve updated that site too and now have the problem Thalian has so I can’t debug it any further.

I also tried uninstalling XAMPP completely and installing an older version, but that didn’t help so it’s not XAMPP 1.6.8 that’s causing the problem.

I’m afraid to update any more sites until I figure this out.

I did notice that in modparser.class.php:

function processElementTags() contains a call to the processTag() function

and

function processTag() contains a call to processElementTags()

so an infinite loop is theoretically possible.

I’ve replicate Thalion’s experience (using XAMPP 1.6.8 on Vista -- though, as I wrote in the post above, using earlier versions of XAMPP didn’t help).

I did a fresh checkout from SVN to an empty directory and created a new database.
Did a build and setup with no problems.
Logged in to the Manager, cleared the cache just in case.
Went directly to setup and selected Update with files built and in place.

Clicking on the install button immediately crashed Apache.

Apache error log: [notice] Parent: child process exited with status 255 -- Restarting.
There is no modx error log.

OK, on my Windows XAMPP installation I’m getting this backtrace when I press ’Install’

# Time Memory Function Location
1 0.0037 115968 {main}( ) ..\index.php:0
2 0.0471 920448 modInstallRequest->handle( ) ..\index.php:90
3 0.0686 937448 include( ’C:\Program Files\xampp\htdocs\revdev\setup\controllers\install.php’ )

..\modinstallrequest.class.php:70
4 0.0691 946584 modInstall->execute( ) ..\install.php:15
5 0.3200 5581992 modInstallVersion->install( ) ..\modinstall.class.php:309
6 0.4205 5789976 include_once( ’C:\Program Files\xampp\htdocs\revdev\setup\includes\upgrades\2.0.0-alpha-1.php’ )

..\modinstallversion.class.php:91
7 2.4629 8502808 modInstallVersion->processResults( ) ..\2.0.0-alpha-1.php:133
8 2.4632 8503640 modErrorHandler->handleError( ) ..\moderrorhandler.class.php:0
9 2.4633 8505472 xPDO->log( ) ..\moderrorhandler.class.php:113
10 2.4633 8505472 modX->_log( ) ..\xpdo.class.php:1359
11 2.4633 8507376 xPDO->_log( ) ..\modx.class.php:2533
12 2.4637 8511552 xPDOCacheManager->writeFile( ) ..\xpdo.class.php:1413
13 2.4656 8512704 xPDO->log( ) ..\xpdocachemanager.class.php:153
14 2.4656 8513064 modX->_log( ) ..\xpdo.class.php:1359
15 2.4657 8515272 xPDO->_log( ) ..\modx.class.php:2533
16 2.4660 8519512 xPDOCacheManager->writeFile( ) ..\xpdo.class.php:1413
17 2.4678 8520832 xPDO->log( ) ..\xpdocachemanager.class.php:153
18 2.4678 8521288 modX->_log( ) ..\xpdo.class.php:1359
19 2.4678 8523520 xPDO->_log( ) ..\modx.class.php:2533
20 2.4682 8527640 xPDOCacheManager->writeFile( ) ..\xpdo.class.php:1413
21 2.4699 8528960 xPDO->log( ) ..\xpdocachemanager.class.php:153
22 2.4699 8529464 modX->_log( ) ..\xpdo.class.php:1359
23 2.4699 8531744 xPDO->_log( ) ..\modx.class.php:2533
24 2.4703 8536000 xPDOCacheManager->writeFile( ) ..\xpdo.class.php:1413

Forever, it then crashes with a

Maximum function nesting level of ’100’ reached, aborting!

. Looks as though there’s a recursion with the logging/caching somehow.

Can you tell me how to get that backtrace output? I’d like to try it on my machine and maybe use it to investigate another Apache crash I’m getting with MODx.

Shamblett/BobRay,

Can you tell me, if after the initial install, if there is a row in modx_system_settings with key ’settings_version’ ?

This seems to have been a bug with settings_version not being added to system settings. This has been fixed in SVN.

I haven’t updated yet, but I was able to run the complete install in my Editor’s debugger. I stepped through line by line and, of course, the install completed normally.

I did Notice that $managerTheme and $managerLanguage were both NULL.


On the version I stepped through successfully in the debugger, settings_version exists and is set. I can now do an Update install with it (not under the debugger) so apparently that missing system setting was the problem.

In the version I didn’t debug, setting_version doesn’t exist.

Neither site has been updated to the new fix for this.

BTW, the site I debugged, which now installs fine, still crashes Apache when I try to visit anything but the home page.


Let me know if there’s anything else you want me to check before I update the sites.