We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 16183
    • 1,390 Posts
    Quote from: OpenGeek at Aug 19, 2009, 05:30 PM

    Quote from: OpenGeek at Aug 19, 2009, 04:12 PM

    I’m working on the table_prefix issue on new installs in the development branch; could have sworn this was working, but anyway...(sigh) BTW, if you had upgraded from previous revisions, you would have not been affected.
    Ok, the problem with new installs not adding the table_prefix should now be fixed.

    Testing now....

    cheers/k
      • 16183
      • 1,390 Posts
      Works like a charm smiley....install completes and correct table prefix pre-pended. Thanks for the fix.

      The core/cache/logs still reports this error though
      [2009-08-19 23:57:37] (ERROR @ /setup/index.php) Error SQLER executing statement: 
      Array
      (
          [0] => SQLER
          [1] => 1146
          [2] => Table 'revosvn.modx_access_permissions' doesn't exist
      )


      revosvn is the name of my test database, btw. Should I mark this as solved then?

      Now back, to work.

      cheers/k
        • 22303 MODX Staff
        • 10,725 Posts
        Quote from: kongondo at Aug 19, 2009, 06:01 PM

        Works like a charm smiley....install completes and correct table prefix pre-pended. Thanks for the fix.

        The core/cache/logs still reports this error though
        [2009-08-19 23:57:37] (ERROR @ /setup/index.php) Error SQLER executing statement: 
        Array
        (
            [0] => SQLER
            [1] => 1146
            [2] => Table 'revosvn.modx_access_permissions' doesn't exist
        )


        revosvn is the name of my test database, btw. Should I mark this as solved then?
        Great; please mark as resolved for beta-4 if you don’t mind. As for the SQLER, that’s not really an error, though it does indicate that Shaun didn’t add the new class he authored to the list of tables to create during install. But xPDO is smart and creates it since it doesn’t exist. The SQLER is just informing us that it didn’t exist when it was queried the first time, but it should immediately after that message appears.
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          Ok, after a night’s sleep I exported from SVN and tried it again. Now the tables are being created with the modx_ prefix. However, the installer still won’t allow me to check the first box about the files being already unpacked, and it fails with the
          (ERROR @ /2.0-5681/setup/index.php) Package /Applications/MAMP/htdocs/2.0-5681/core/packages/core.transport.zip not found. SIG:

          This is on a stock MAMP installation (PHP 5.2.6, MySQL 4.0.41), with FF 3.5.2 and Safari 4.0.3
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 22303 MODX Staff
            • 10,725 Posts
            Did you follow the pre-installation steps, like creating the core transport? You have to build this before you can install... see http://svn.modxcms.com/docs/display/revolution/Development+and+Testing+Notes
              • 28042 ☆ A M B ☆
              • 24,524 Posts
              er... no, I just presumed that since the beta 3 installed just fine that the export from SVN would likewise. <sigh> that’ll teach me not to be so presumptuous!

              Ok, on my elderly iBook, it took 27 seconds to build, and not much more to install successfully. Such a small thing to cause so much annoyance!
                Studying MODX in the desert - http://sottwell.com
                Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                Join the Slack Community - http://modx.org
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                My 7-step setup process:
                1. Create a database: CREATE DATABASE `revolution_5681` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
                1. Export from svn @ http://svn.modxcms.com:80/svn/tattoo/ (with login and password); root->tattoo->branches->2.0.
                2. Make a copy of _build/build.config.sample.php to _build/build.config.php.
                3. Edit the new build.config.php file to have the correct database connection information:

                // define the connection variables
                define(’XPDO_DSN’, ’mysql:host=localhost;dbname=revolution_5681;charset=utf8’);
                define(’XPDO_DB_USER’, ’root’);
                define(’XPDO_DB_PASS’, ’root’);
                define(’XPDO_TABLE_PREFIX’, ’revo_’);

                4. Open a terminal and cd to the _build directory: cd /Applications/MAMP/htdocs/2.0-5681/_build/
                5. Run the build script: php transport.core.php
                6. Load the setup in the browser: http://localhost/2.0-5681/setup
                7. Follow the setup instructions, filling in the required fields for database connection and admin user.
                  Studying MODX in the desert - http://sottwell.com
                  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                  Join the Slack Community - http://modx.org
                  • 25663 MODX Staff
                  • 12,272 Posts
                  Susan, I think you have your first Revo documentation wiki article! tongue
                    Ryan Thrash, MODX Co-Founder
                    Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                    • 28042 ☆ A M B ☆
                    • 24,524 Posts
                      Studying MODX in the desert - http://sottwell.com
                      Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                      Join the Slack Community - http://modx.org
                      • 17499 ☆ A M B ☆
                      • 872 Posts
                      There is an error in the doc here

                      http://svn.modxcms.com/docs/display/revolution/modUser.changePassword

                      boolean changePassword (string $newPassword, string $oldPassword)

                      And you explain the inverse below:
                      //Change the password from 'boo123' to 'b33r4me'
                      $modx->changePassword('boo123','b33r4me');