On March 26, 2019 we launched new MODX Forums. Please join us at the new MODX Community Forums.
Subscribe: RSS
  • MySQL 5.0.51 database server is the only version stated as not being recommended for use with the MODx application framework. Unfortunately, this version of the server is the latest stable release designed for the Slackware 12.0 operating system. After upgrading MySQL to 5.0.51, users with MODx-based sites are experiencing unpredictable behavior of their CMS. This issue was discussed extensively on this forum — a practical solution is to refrain from obtaining the upgrade. I was following the development of this scenario for many months, hoping that someday I’ll be able to upgrade the entire OS (along with an improved MySQL server application)…

    But that day did not arrive — each month brought new projects, developments, databases and web applications, supplanting my ambitious project of upgrading the entire system.

    Recently, I came to the conclusion that under the circumstances, such an upgrade is pointless — I simply cannot afford to experiment with a system, while its resources are being shared by many users/customers. However, I decided to put some effort into fine-tuning system components (the main reason we love Linux is its built-in ability to produce new versions of software using the source code).

    Compiling software by issuing the standard sequence:
    ./configure
    make
    make install
    

    results in building a private copy of the application under „/usr/local” folder and is regarded as somewhat messy in terms of style. A better way is to build a standard (distributive) package that may subsequently be used to upgrade the old version. My efforts yielded three crucial (from a web developer’s point of view) packages for Slackware 12.0:
      httpd-2.2.11-i486-1_slack12.0.tgz
      mysqld-5.0.77-i486-2_slack12.0.tgz
      php-5.2.9-i486-1_slack12.0.tgz

    All packages can be installed by issuing Slackware’s standard command (within root’s console):
    upgradepkg <new-package-name>
    


    Of course, it is a good idea to stop the server applications prior to the upgrade...
    rc.httpd stop
    rc.mysqld stop
    

    ... and reboot the system after the upgrade is complete — in order to have all newly-installed libraries properly started.

    Some additional remarks regarding the PHP package. I’ve compiled it after MySQL’s upgrade, so PHP’s extension „mysqli” is based on the new 5.0.77 libraries. I’ve also added two extra extensions to the PHP build: „mcrypt” (I was annoyed by phpMyAdmin constantly issuing a „cannot load mcrypt extention, please check your PHP configuration” message) and „mssql” (an interface layer for the MSSQL database). These extentions are NOT activated by default – in order to use them, you need to add the following to your php.ini (in the extension section):
    extension=mcrypt.so
    extension=mssql.so
    


    Done. Ah, not quite. My packages can be found at http://setpro.net.pl/software/Slack12#attachments
    • Good job! I run also run MODx on Slack servers. The upgrades from 12.0 to 12.1 and 12.2 usually only took 30 minutes following the upgrade.txt instructions. I recommend you also use slackpkg to keep up with the changes in either the stable or current changelog.