Downloading Revolution via SVN

while trying to install 0.9.7 I’m getting the following error - all the prior checks were successfull:

Fatal error: Call to a member function install() on a non-object in C:\Documents and Settings\User\My Documents\My Web Sites\www\cms\modx97\setup\includes\modinstall.class.php on line 474

any ideas what’s causing this?

Thanks

I have the exact same error message. The short answer seems to be that transport.zip is missing from our /core/packages directory.

I’ll mention some details (assuming that I’m not full of crap in my reading of the code) in case it helps make the install package more robust:

It appears that $package is being set to what
xPDOTransport :: retrieve() returns. It looks to me like retrieve() is looking for /core/packages/transport.zip but my /packages directory is empty.

Having that file there would probably solve the problem but some more error checking might be in order:

If that file isn’t there --

"If (file_exists)" fails (in xpdotransportclass.php, line 270) and the else statement returns null. No error is logged. I think retrieve() assumes that the value it returns will be checked.

$package is set to null, but there’s no error check in modinstall.class.php (it would go at about line 468) to see if $package is non-null, so the call on line 474 is to null->install(), which generates the screen error we’re seeing.

Hope this helps . . .

Bob

The short answer is actually here. And if you want to help us track bugs, go here.

But please, this is still early alpha software and is not ready for use in any way closely resembling the current 0.9.6 branches. I will have an alpha build to distribute which includes the core.transport.zip already built when it is ready for general use.

Sorry Jason,

Didn’t mean to waste your time.

I wasn’t at all confident that this qualified as a bug and was trying, in my clumsy way, to be helpful. You probably have way more important things to do right now than make setup more robust.

Bob

Quote from: OpenGeek at Nov 02, 2007, 05:36 PM

The short answer is actually here. And if you want to help us track bugs, go here.

Following the directions in the link, the php command doesn’t complete (on Win XP). This error shows up:

connect() failed
OSERR:10061: No connection could be made because the target machine actively refused it.

After a pause, a ton of stuff is printed to stdout. Then ultimately, I get an "out of memory" error.

Most of the files are created (probably not all) and transport.zip is there.

The install was successful with no error messages and I can get a partial manager login screen but get a blank screen or "file not found" when I log in.

I tried turning off the Windows Firewall but it made no difference.



Bob

If you get an out of memory error, then increase your memory in your php.ini file. I think I had to increase mine to like 32MB. Folowing Jason’s instructions verbatim, I was able to successfully install the 097 SVN version on an XP machine running WAMP.

Also regarding the connect error, did you make sure to perform this step:

If this is the first time you are building from SVN, copy the file build.config.sample.php to build.config.php and edit the properties to point at a valid database with proper credentials. NOTE that this database does not have to contain anything; the build script just needs to be able to make a connection to a MySQL database.

If you are not extremely comfortable with alpha code, I would wait until the public preview alpha is released that Jason is talking about.

Quote from: BobRay at Nov 02, 2007, 10:19 PM

connect() failed
OSERR:10061: No connection could be made because the target machine actively refused it.

This is likely related to OpenSSL/certificates. A quick search on google revealed this; but should not be related to MODx at all.

Quote from: BobRay at Nov 02, 2007, 10:19 PM

After a pause, a ton of stuff is printed to stdout. Then ultimately, I get an "out of memory" error.

Most of the files are created (probably not all) and transport.zip is there.

The install was successful with no error messages and I can get a partial manager login screen but get a blank screen or "file not found" when I log in.

First, I recommend running this only on a local development environment. Did you run the script from the browser or the command line? The latter is definitely preferred, so you avoid Apache or browser timeouts as well. Definitely increase the memory; this process creates a bunch of files representing rows to be added to the database, copies all of the core files, and zips them into the package. It can probably be made a more efficient process, but for now, yes, you need to up your memory limit. I use 32M myself with no problem.

The reason it tried to install anyway is that part of the package was created before the memory limit was reached, but there is no full validation on the extracted contents before proceeding.

I bumped the memory to 32M and the command-line process completed. I still got the "connect() failed" error but it appears that all the files were created.

I emptied the DB and ran a full new install.

I’ve got 38 tables in the database, some with data, but I still get the blank screen when I log on through the manager in either Firefox or IE6. Maybe the connect() error crapped something up after all.

BTW, it may just be my installation but, for me, IE6 doesn’t show the "remember me" box or the login button. Firefox does.

Bob

Success!

I ran transport.core.php from my browser and avoided the connect() error message but the install hung. An update install also failed.

I wiped out the whole modx directory (except for _build/build.config.php), emptied the database, and started over. I ran transport.core.php from the browser again and the final number was 2603 (instead of 2601 in the previous run).

Everything went fine from there on and I have a good install. I’m guessing that transport.core.php failed to overwrite some existing corrupted files.

IE6 still mungs up the login screen but I can log in by pressing enter.

Bob

Quote from: Jesse at Nov 03, 2007, 11:49 AM

If you are not extremely comfortable with alpha code, I would wait until the public preview alpha is released that Jason is talking about.

Are you kidding? I ran Windows 98 for almost two years.

Bob