We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 14673
    • 18 Posts
    Hi everyone

    I’m having some problems with my form customisation setup in 2.0.7. I’ve only just started playing with customisation since updating from 2.0.0 (I missed a few versions wink). I basically decided to start from scratch with a new profile, new sets etc.

    What I’ve found is that any rule I try to customise just doesn’t save. The Action, Template, Description, Constraints etc all save just fine. But if I try to change a rule (hide any fields or tabs, or move any TVs to a different tab etc), even after hitting save (and getting a Safe successful message), the rules don’t apply. Then, if I refresh the page and browse back to the rule set i just created, I find that all the rules/tabs/TVs have gone back to their default settings - everything ticked etc.

    I have not seen any error messages.

    Is this a bug or am I doing something wrong?

    If it helps:

    • MODx version: MODx Revolution 2.0.7-pl (advanced)
    • PHP version: 5.2.5
    • MySQL version: 5.0.91
    • Server OS: Linux/Unix-based, unsure what distro specifically.
    • Browsers: Tested in Chrome and Firefox on Mac, happens the same in both

    I’ve attached a copy of two errors from the MODx error log; there are several dozen instances of each error from the time period I’ve been trying to set this up.
      • 14673
      • 18 Posts
      Just bumping this up as I’m still having the issue and am no closer to an idea of what the problem is.

      Any ideas?
        • 14673
        • 18 Posts
        According to the MySQL site:
        Error: 1054 SQLSTATE: 42S22 (ER_BAD_FIELD_ERROR)
        
        Message: Unknown column '%s' in '%s'

        From: http://dev.mysql.com/doc/refman/5.0/en/error-messages-server.html#error_er_bad_field_error
          • 19364
          • 0 Posts
          Got the same issue and solved it.

          You gonna have this problem when you updated your MODx installation to e.g. 2.08.

          In your database you have an table named ’modx_actiondom’, this table is missing the row ’rank’. Below the query that solved the issue, you can see the latest row is named ’rank’.


          DROP TABLE IF EXISTS `modx_actiondom`;
          CREATE TABLE IF NOT EXISTS `modx_actiondom` (
          `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
          `set` int(11) NOT NULL DEFAULT ’0’,
          `action` int(11) NOT NULL DEFAULT ’0’,
          `name` varchar(255) NOT NULL DEFAULT ’’,
          `description` text,
          `xtype` varchar(100) NOT NULL DEFAULT ’’,
          `container` varchar(255) NOT NULL DEFAULT ’’,
          `rule` varchar(100) NOT NULL DEFAULT ’’,
          `value` text NOT NULL,
          `constraint` varchar(255) NOT NULL DEFAULT ’’,
          `constraint_field` varchar(100) NOT NULL DEFAULT ’’,
          `constraint_class` varchar(100) NOT NULL DEFAULT ’’,
          `active` tinyint(1) unsigned NOT NULL DEFAULT ’1’,
          `for_parent` tinyint(1) unsigned NOT NULL DEFAULT ’0’,
          `rank` int(11) NOT NULL DEFAULT ’0’,
          PRIMARY KEY (`id`),
          KEY `set` (`set`),
          KEY `action` (`action`),
          KEY `name` (`name`),
          KEY `active` (`active`),
          KEY `for_parent` (`for_parent`),
          KEY `rank` (`rank`)
          ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=57 ;
            • 14673
            • 18 Posts
            LEGENDARY! Thankyou! That worked beautifully!

            ... well, the MySQL query came up with a syntax error when I tried to run it. So instead I just went in via PHPMyAdmin and added in the column and key manually. Still, worked great after that.

            Thanks !! laugh