Downloading Revolution via SVN

Quote from: MasterzDee at Apr 25, 2008, 11:13 AM

I download build ver.: 3653

follow this guide, step by step:
http://svn.modxcms.com/docs/display/MODx097/Development+and+Testing+Notes

Everything ran smoothly till I ran setup and it was totaly blank, empty.
Yes, I have installed PDO mysql driver, also tested PDO driver with my own script and PDO mysql works fine.

PHP ver.: 5.2.5
PDO Driver for MySQL, client library version: 5.1.23-rc
PDO drivers: sqlite, mysql

Okay, a few questions just to make sure:

• You ran the build script? (transport.core.php)
• Before running the build script, you setup the proper build.config.php file?
• Can you verify there is a ’core/packages/core/’ directory, with a manifest.php file inside as well as a few (11 or so) subdirectories?
• Is there a core/packages/core.transport.zip file?

Exactly like in the tutorial

You need to make your setup/templates/_compiled/ directory writable by the PHP process.

Quote from: OpenGeek at Apr 25, 2008, 12:21 PM

You need to make your setup/templates/_compiled/ directory writable by the PHP process.

Now setup works, this MUST be written in testing notes doc.

thanks OpenGeek

in the end of installation I again got blank page:
http://blog.xydomain.eu/setup/index.php?action=install

here is everything cool:
http://blog.xydomain.eu/setup/index.php?action=summary
Checking PHP version: OK!
Checking if sessions are properly configured: OK!
Checking if core/cache directory exists: OK!
Checking if core/cache directory is writable: OK!
Checking if core/export directory exists: OK!
Checking if core/export directory is writable: OK!
Checking if core/packages directory exists: OK!
Checking if /home/hdd1/xydomain/ directory exists: OK!
Checking if config/config.inc.php exists and is writable: OK!
Creating connection to the database: OK!
Checking table prefix `modx_`: OK!

I press button Install, this page open:
http://blog.xydomain.eu/setup/index.php?action=install
and here I got blank page and 50 db tables created

root page "http://blog.xydomain.eu" show a lot errors, like this:
Warning: modContext::include().....

Hello Masterz,
i know both, the blank page and the errors.
http://modxcms.com/forums/index.php/topic,15816.msg124117.html#msg124117
may this can help you.
good luck!
adios, Stefan

The other possibility for that blank page is memory_limit. If you have the default 8M limit as many local installations do, you will currently not be able to run the install process. This is a known issue and being worked on, but bump that up to at least 32M and all should be fine. I always set mine to 128M.

thanks for reply.

nope memory limit is not, server show:
memory_limit: 200M : 16M

The config.core.php needs to be in every directory that serves as an entry point (or gateway) to a MODx Context. There are three contexts in a basic core installation (or export from SVN), mgr, connectors, and web. These are the locations of those three contexts (unless you configure them and move them to another location) when exported from SVN:

* web @ MODX_BASE_PATH/ (the directory you installed/exported into)
* mgr @ MODX_BASE_PATH/manager/
* connectors @ MODX_BASE_PATH/connectors/

I may make this optional before we release, but it is required for now in order to support configurable locations for any Context or the MODx core. This file basically just allows you to define the location of your core installation, which can located anywhere accessible to the user executing the PHP process, and specify named configurations for use in multi-site configurations with a single, shared core.

In any case, I’ll make sure I add something to the setup to check these permissions before attempting the install.

this msg I don’t understand completely:
http://modxcms.com/forums/index.php/topic,15816.msg124117.html#msg124117

config.core.php:
define (’MODX_CORE_PATH’, MODX_INSTALL_PATH . ’core/’);
define (’MODX_CONFIG_KEY’, ’config’);

so what do I need here to do and copy to where

Quote from: MasterzDee at Apr 26, 2008, 11:15 AM

this msg I don’t understand completely:
http://modxcms.com/forums/index.php/topic,15816.msg124117.html#msg124117

config.core.php:
define (’MODX_CORE_PATH’, MODX_INSTALL_PATH . ’core/’);
define (’MODX_CONFIG_KEY’, ’config’);

so what do I need here to do and copy to where

If you have it set up so that the root directory MODx is installed in, and all it’s subdirectories, are writable by the PHP user (will be the user account the web server is running as for Server API configurations or your user account in (Fast)CGI configurations), these files will be automatically written into each directory representing a MODx Context with the actual path to your MODx core along with a config key you want to use. If this user does not have permission to write these files, you will need to copy them to each context location, as indicated in that message, using the actual absolute path to your MODx core/ directory (e.g. ’/var/www/html/modx/core/’).

A Context is an entry point or gateway to MODx, and typically includes an index.php responsible for instantiating the MODx class. Each of the standard Contexts that come with MODx (web, mgr, and connectors) have paths defined by the setup process that allows the MODx core to know where each context is located. Likewise, these config.core.php files help each Context to know where the MODx core is located.

In addition single MODx core can serve multiple configurations; this is the purpose of the MODX_CONFIG_KEY. By providing a specific name (the default is ’config’), you are configuring this Context to communicate with a specific MODx core configuration, with it’s own configuration file and it’s own cache directory location. At the current time, you can customize the MODX_CORE_PATH and MODX_CONFIG_KEY in setup/includes/config.core.php before running setup.

There is still a lot of work to be done on the new setup process; when the zip releases of 0.9.7-alpha-1 are publicly distributed in the next day or two, there will be two packages to choose from and we’ll provide you with more information on how to overcome all these new challenges the power and flexibility of 0.9.7 has brought upon us.

Quote from: OpenGeek

There is still a lot of work to be done on the new setup process; when the zip releases of 0.9.7-alpha-1 are publicly distributed in the next day or two, there will be two packages to choose from and we’ll provide you with more information on how to overcome all these new challenges the power and flexibility of 0.9.7 has brought upon us.

this is great OpenGeek, I’ll wait for alpha release (just 2 days ). So far I don’t understand logic behind MODx core and all that stuff, a brief info doc would be great so we can dig into MODx well