Error on r2871 Install

I got the package from Mark, and ran the http://localhost/dev/097/_build/transport.core.php on XAMPP, but I cant see the zip file in the core\packages, except zip files for Ditto, Wayfinder and TinyMCE

Installer just loads blank page after checklist... (PHP Version: OK etc...)

Apache/2.0.54 (Win32) PHP/5.0.4
MySQL 4.1.13

Any clues?

Hi,

there is a missing "(" in modxLight/layout/ext/topbar
If you add a module then the topbar dissapears as it breaks the js code.

Around Line 66 in topbar.tpl

{if $modx->hasPermission(’exec_module’)}
{foreach from=$modules item=module}{literal}
modTopMenu.addMenuItem(’modules’,{
text: (’{/literal}{$module->name}{literal}’),
icon: MODX_MEDIA_PATH+’/style/MODxLight/images/icons/module.gif’,
href: ’index.php?a=112&id={/literal}{$module->id}{literal}’
});
{/literal}{/foreach}
{/if}

:-)

Quote from: zi at Aug 08, 2007, 01:39 AM

I got the package from Mark, and ran the http://localhost/dev/097/_build/transport.core.php on XAMPP, but I cant see the zip file in the core\packages, except zip files for Ditto, Wayfinder and TinyMCE

zi: I suggest running the process from the command line rather than via the web server. The script takes about 200 seconds on my machine to create the core zip package. You are probably getting a timeout, if not in PHP, from Apache. And make sure you check both the Core package has been manually extracted and Files already in-place options to avoid the unnecessary re-extraction and copying of files during the process.

The distribution files will contain the core zip file already, so this step is only necessary when grabbing the SVN copy.

Quote from: heliotrope at Aug 08, 2007, 06:37 AM

Hi,

there is a missing "(" in modxLight/layout/ext/topbar
If you add a module then the topbar dissapears as it breaks the js code.

Around Line 66 in topbar.tpl

:-)

Fixed! Thanks!

r2877

Is there any documentation on installing the SVN? I don’t seem to be able to get it to work... running the transport.core.php file either from the webpage or from command line doesn’t do anything; it just seems to exit immediately.

[edit]Ok, got that I have to edit the config file. This took about 35 seconds on my iBook.

Installed OK, but now I get a long list of warnings and notices similar to the one heliotrope mentioned earlier.

Hmmm... the /manager/index.php just requires the includes/init/index.php file. This file immediately starts in with $modx stuff... where does the $modx get defined???

Quote from: sottwell at Aug 24, 2007, 11:40 PM

Hmmm... the /manager/index.php just requires the includes/init/index.php file. This file immediately starts in with $modx stuff... where does the $modx get defined???

Hmm, I guess it should only be on everything after phase2.php is required; I must have gotten a little overanxious when forcing the configurable paths in front of these files. But, I also must have subconsciously wanted to refactor that whole thing: to reduce the number of separate files being included, and so that the modX class (and a specific configuration) gets loaded earlier to determine the paths to the default manager context (mgr).

Each context you deploy in 0.9.7, be it the web or mgr contexts, or a custom context of your own making, will be deployed in a configurable directory. The index.php (we’ll call it a gateway or front-controller) in each context should simply know how to get to and instantiate the MODx core (which will work from a configurable location), and everything else from there should be controlled by the instance of the MODx core, initialized to that context. My vision is to have a tool that uses simple templates (a la core/config/config.inc.tpl) to setup these modX gateways with the proper paths to the core classes, and somehow registers this context gateway with the core. These gateways could be used as-is to provide entry-points to specific contexts, or extended to be a complex manager interface (as it is here), included in other scripts for access to the API’s and data in a specific context, supplemented by companion .htaccess generators and other utilities, etc.

I’ll get this part of the manager initialization cleaned up and in-line with what I just said as soon as I can. Just thinking of how best to register contexts in the default manager, deal with context-specific configurations, multi-sites, sub-sites, etc.

That’ll be great; I’m looking forward to getting this to working so I can start digging into its guts and figuring it out. It’ll take me a few months, but I’ll get there.