ManagerManager-integration bugs

Hi,

I’m integration YAMS into a MODx 1.0.3 installation using ManagerManager 0.3.8.

I have set it up according to the specs and tried setting up ManagerManager as I understand it in the specs. What I did was put the line "require( $modx->config[’base_path’] . ’assets/modules/yams/yams.mm_rules.inc.php’ );" at the bottom of /assets/plugins/managermanager/mm_rules.inc.php.

Then I set up the configurations tab for ManagerManager to use the mm_rules chunk and local jquery.

The result is that when I edit a resource I get one "General"-view with all my language-specific editing following each other. But I also have one tab for each language (in my case English, Swedish and Norwegian) that doesn’t contain any data at all.

What did I likely configure wrong?

Cheers!
Christoffer

It could be a MODx 1.0.3 specific issue. I haven’t tested YAMS with the security update yet. I’ll try to test it this evening and get back to you.

When I tried with ManagerManager 0.3.8 I got one error. Apparently there is a call to htmlentities on line 80 of assets\plugins\managermanager\functions\utilities.inc.php which makes use of the fourth parameter, "double encode". However, according to the PHP docs this parameter wasn’t made available until PHP 5.2.3. If you are using a version of PHP earlier than that then it would cause MM to fail. I "fixed" it by simply removing the last argument.

Is that the same problem that you have?

No, I’m running PHP 5.3.1.

I don’t seem to get an error at all. It’s just that the language specific template variables aren’t moved to the tabs that are set up for the languages. It might be that YAMS doesn’t recognise the variables as language specific and therefore doesn’t move them to the tabs.

When I inspect the HTML code, the template variables for language specific settings aren’t enclosed in a <div> that could be used with the tabs js, they are just <tr>-elements like everything else.

Thank you for helping me.

When I tried with a fresh MODx 1.0.3 install it was working for me. Perhaps your ManagerManager plugin configuration has lost the link to your mm_rules chunk during the upgrade then? By default it gets set to mm_demo_rules or something similar.

It might certainly be that.

Can you give my a "total idiot’s guide" to set it up? It’s the first MODx site I’m building and I may be missing something very simple that is taken for granted I know

Cheers!

Please see the ManagerManager installation instructions in the YAMS documentation. If you have any problems following any of the steps, please report back here.

I just found the latest alpha-release which I updated to. Now it works just fine