We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 3749
    • 24,544 Posts
    No, sottwell’s recommendation is to upload *everything* but the assets/snippets folder. Then uncheck all the snippet and sample content boxes during the install.

    Just to be clear, the site should be a working version of the old site (with all its content) before doing anything.

    Copy the new files (Except assets/snippet), then do an upgrade install with the snippet and sample content boxes unchecked.
      Did I help you? Buy me a beer
      Get my Book: MODX:The Official Guide
      MODX info for everyone: http://bobsguides.com/modx.html
      My MODX Extras
      Bob's Guides is now hosted at A2 MODX Hosting
      • 18337
      • 19 Posts
      Thanks for the clarification, Bob.

      And, yes. I have the site working on 0.9.5 now in the development environment. I was just poring over the 1.0.2 folders and moving in things specific to the site itself, like all folders named "agenthunter".

      Thanks so much for putting up with my newbie-ness and answering my questions.
        • 3749
        • 24,544 Posts
        Quote from: MarjWyatt at Nov 30, 2009, 10:22 PM

        Thanks for the clarification, Bob.

        And, yes. I have the site working on 0.9.5 now in the development environment. I was just poring over the 1.0.2 folders and moving in things specific to the site itself, like all folders named "agenthunter".

        Thanks so much for putting up with my newbie-ness and answering my questions.

        Just to be sure, that development environment site is the one you’re upgrading to 1.0.2, right? If possible, you always want to be upgrading a working site.

        PS: Don’t thank me until it works. wink
          Did I help you? Buy me a beer
          Get my Book: MODX:The Official Guide
          MODX info for everyone: http://bobsguides.com/modx.html
          My MODX Extras
          Bob's Guides is now hosted at A2 MODX Hosting
          • 18337
          • 19 Posts
          Bob,

          It seems like a good idea to successfully update a development installation before working on the active site so, yes, I am updating the development area which is currently a mirror of the working site. Well ... not anymore. smiley

          Here are the specifics of the installation:

          http://newmarketer.us
          PHP 5.x
          MySQL 5.0
          Browser FF 3.0.15
          GoDaddy Shared Hosting Linux version 2 | http://help.godaddy.com/topic/412/article/1076
          MODx 1.0.2
          No tables greater than 1MB

          Anyone can login as an end user on the home page with these credentials:

          ID: testing suppliers
          PW: testing1

          I am getting the following error when logging in:

          INCLUDE_ORDERING_ERROR

          Please use the MODx Content Manager instead of accessing this file directly.


          This same problem was reported for MODx 0.9.6.3 at this link:
          http://modxcms.com/forums/index.php/topic,42769.0.html

          I saw this error in the database.php script that I brought along from the old site in the following folder tree:

          assets/modules/database3

          Here is the contents of that script:

          [tt]<?php
          if(IN_MANAGER_MODE!="true") die("<b>INCLUDE_ORDERING_ERROR</b>

          Please use the MODx Content Manager instead of accessing this file directly.");
          unset($_SESSION[’itemname’]); // clear this, because it’s only set for logging purposes
          ?>
          <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
          <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
          <head>
          <title>Manage Termbase</title>
          <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
          <link rel="stylesheet" type="text/css" href="media/style/<?php echo $modx->config[’manager_theme’]; ?>/style.css?" />
          <script type="text/javascript" src="media/script/scriptaculous/prototype.js"></script>
          <script type="text/javascript" src="media/script/scriptaculous/scriptaculous.js"></script>
          <script type="text/javascript" src="../assets/modules/database3/grid.js">></script>
          <link rel="stylesheet" type="text/css" href="../assets/modules/database3/grid.css" />
          <style type="text/css">
          #termbase td{
          padding:3px;
          color:darkblue;
          }
          #termbase td.editor{
          width:180px;
          }
          #termbase td.edit, #termbase td.delete{
          width:40px;
          }
          #termbase th.nohead{
          background:transparent;
          color:black;
          font-weight:normal;
          border:1px solid #aaaaaa;
          }
          </style>
          <script type="text/javascript">

          function uploadNew() {
          var url = ’../assets/modules/database3/insertcsv.php’;
          var sx=document.getElementsByName(’options’);
          for(var j=0;j<sx.length;j++){
          if(sx[j].checked==true){
          var s=sx[j].value;
          break } }
          var pars = ’newclient=’ + $(’newClient’).value + ’&oldclient=’ + $(’oldClient’).value + ’&options=’ + s;
          var myAjax = new Ajax.Updater( ’ajaxContainer’, url, {method: ’get’, parameters: pars});
          }

          function loadNewClient() {
          var url = ’../assets/modules/database3/newStuff.php’;
          var pars = ’’;
          var myAjax = new Ajax.Updater( ’ajaxContainer’, url, { method: ’get’, parameters: pars });
          }

          function loadDatabase() {
          var url = ’../assets/modules/database3/loadDatabase.php’;
          var pars = ’client=’ + $F(clientSelect);
          var myAjax = new Ajax.Updater( ’ajaxContainer’, url, { method: ’get’, parameters: pars, });
          }

          function searchDatabase() {
          var url = ’../assets/modules/database3/search.php’;
          var pars = ’term=’ + $F(searchField);
          var myAjax = new Ajax.Updater( ’ajaxContainer’, url, { method: ’get’, parameters: pars });
          }

          </script></head>
          <body>
          <div class="subTitle" style="margin-bottom:0px">
          <span class="right"><img src="media/style/<?php echo $modx->config[’manager_theme’]; ?>/style/MODxBlack/images/_tx_.gif" width="1" height="5">
          <img src="media/style/<?php echo $modx->config[’manager_theme’]; ?>/images/icons/context_view.gif" align="absmiddle" />&nbsp;<?php echo "Manage Termbase"; ?></span>
          </div>

          <form name="resource" method="post">
          <input type="hidden" name="id" value="<?php echo $modId; ?>" />
          <input type="hidden" name="op" value="" />
          <div class="sectionHeader"><img src=’media/style/<?php echo $modx->config[’manager_theme’]; ?>/images/misc/dot.gif’ alt="." />&nbsp;Termbase Management</div><div class="sectionBody">
          <!-- load modules -->
          <p><img src=’media/style/<?php echo $modx->config[’manager_theme’]; ?>/images/icons/modules.gif’ alt="." width="32" height="32" align="left" hspace="10" />Here you can manage the termbases for your clients. Add a new client’s database, browse and edit the database for a given client, or search for a specific term.</p>
          <div class="searchbar">
          <table border="0" style="width:100%">
          <tr>
          <td><a class="searchtoolbarbtn" href="#" onClick="loadNewClient();return false;"><img src="media/style/<?php echo $modx->config[’manager_theme’]; ?>/images/icons/save.gif" align="absmiddle" /> New Client</a></td><td>&nbsp;&nbsp;&nbsp;&nbsp;
          <select name="clients" id="clientSelect" onChange="loadDatabase();return false;"><option value="0">Select</option>

          <?php
          $query = "SELECT DISTINCT * FROM ah_members";
          $result = $modx->db->query($query);
          if($result) {
          while($row = $modx->db->getRow($result)) {
          echo ’<option value="’.$row[’list_user’].’">’.ucfirst($row[’list_user’]).’</option>’;
          }
          }
          ?>

          </select> Browse Database</td>
          <td nowrap="nowrap">
          <table border="0" style="float:right"><tr><td>Search </td><td><input class="searchtext" id="searchField" name="search" type="text" size="15" value="" /></td>
          <td><a href="javascript:;" class="searchbutton" title="Search" onClick="searchDatabase();return false;">Go</a></td>
          </tr>
          </table>
          </td>
          </tr>
          </table>
          </div>



          <div id="ajaxContainer">

          <?php echo "manage termbase"; ?>
          </div>
          </div>
          </form>
          </body>
          </html>
          [/tt]

          I didn’t write this script but, if anyone notices glaring errors that would caus MODx to dislike it, I sure would appreciate your pointing them out to me.

          If you want to login as admin, I can provide those credentials too but would prefer to use email to deliver that sort of info so post an email address for me to use.

          Thanks in advance.
            • 28042 ☆ A M B ☆
            • 24,524 Posts
            That’s a module I put up on my site as a demo. Are you trying to use it on the front-end? It’s a module; it has to be installed in the manager Modules section.
              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
              • 18337
              • 19 Posts
              Hello,

              No, I’m not overtly trying to use it on the front end. I read through much of the code when I did the upgrade and that is the only file I found with that error message in it.

              Installed Modules are Doc Manager, KoopsMailingListx and QuickEdit

              What module would need to be installed, or uninstalled?

              Thanks!
              Marj
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                Well, something you have "live" is including that file, which was written to be included by a module (thus from the Manager). A snippet, most likely, which is why it’s throwing that message.
                  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