We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 2206
    • 22 Posts
    I’m trying t install revo beta 4 but I got just a white screen. I checked all the usual things (chmod, ram, ecc). I found an error log in the core/cache dir but i can’t fugure how to fix the problem:

    This was in instal.config

    [2009-11-13 09:11:45] (ERROR @ /setup/index.php) Error preparing statement for query: SELECT `modWorkspace`.`id` AS `modWorkspace_id`, `modWorkspace`.`name` AS `modWorkspace_name`, `modWorkspace`.`path` AS `modWorkspace_path`, `modWorkspace`.`created` AS `modWorkspace_created`, `modWorkspace`.`active` AS `modWorkspace_active`, `modWorkspace`.`attributes` AS `modWorkspace_attributes` FROM `modx_workspaces` AS `modWorkspace` WHERE `modWorkspace`.`id` = ?
    [2009-11-13 09:11:45] (ERROR @ /setup/index.php) Error saving vehicle object: Array
    (
    [resolve_files] => 1
    [package_action] => 0
    [vehicle_package] => transport
    [vehicle_class] => xPDOObjectVehicle
    [class] => modWorkspace
    [guid] => 3fa6044aab4131e40f132cd110b15685
    [native_key] => 1
    [filename] => modWorkspace/07d2cb946194ebd3950e51be5fd170c6.vehicle
    [preserve_keys] => 1
    [update_object] =>
    [package] => modx
    [signature] => 07d2cb946194ebd3950e51be5fd170c6
    [object] => {"id":1,"name":"Default MODx workspace","path":"","created":null,"active":1,"attributes":null}
    )

    This was is error.log

    [2009-11-13 11:03:16] (ERROR @ /index.php) Error preparing statement for query: SELECT `modSystemSetting`.`key` AS `modSystemSetting_key`, `modSystemSetting`.`value` AS `modSystemSetting_value`, `modSystemSetting`.`xtype` AS `modSystemSetting_xtype`, `modSystemSetting`.`namespace` AS `modSystemSetting_namespace`, `modSystemSetting`.`area` AS `modSystemSetting_area`, `modSystemSetting`.`editedon` AS `modSystemSetting_editedon` FROM `modx_system_settings` AS `modSystemSetting`
    [2009-11-13 11:03:16] (ERROR @ /index.php) Error preparing statement for query: SELECT `modSystemSetting`.`key` AS `modSystemSetting_key`, `modSystemSetting`.`value` AS `modSystemSetting_value`, `modSystemSetting`.`xtype` AS `modSystemSetting_xtype`, `modSystemSetting`.`namespace` AS `modSystemSetting_namespace`, `modSystemSetting`.`area` AS `modSystemSetting_area`, `modSystemSetting`.`editedon` AS `modSystemSetting_editedon` FROM `modx_system_settings` AS `modSystemSetting`
    [2009-11-13 11:03:16] (FATAL) Could not load core MODx configuration!


    Enviroment:

    shared hosting (steadfast)
    ram 64M, exe time 30 sec
    mysql server: 5.0.86-community-log
    mysql client: 5.0.67
    litespeed (not apache)
    phpinfo: http://wintetast.nozonenet.com/info.php

    PS: beta 4 installation was fine in local attempts with MAMP, 64M ram and 30 sec exe time

    Any idea?
      • 2206
      • 22 Posts
      i transfered a local installation with files and database, and everything is fine. I suppose that the issue is the installation process. Maybe litespeed servers requires more than 64mb ram in the installation process


      PS: PDO stuff works fine. It’s on the bottom of the phpinfo page
        • 28215
        • 4,149 Posts
        Try upping the memory_limit to 128M.
          shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
          • 22303 MODX Staff
          • 10,725 Posts
          Quote from: arx707 at Nov 15, 2009, 07:17 PM

          i transfered a local installation with files and database, and everything is fine. I suppose that the issue is the installation process. Maybe litespeed servers requires more than 64mb ram in the installation process


          PS: PDO stuff works fine. It’s on the bottom of the phpinfo page
          PDO existing on phpinfo page does not mean it works. This is concerning:
          mysql server: 5.0.86-community-log
          mysql client: 5.0.67
          Those should match; this means PHP was compiled against a different mysql client library than the mysql server, and this is a frequent source of problems with PDO.