next »

This is an auto-generated topic for ManagerManager 0.3.8-release by ncrossland.

Brief Description:
ManagerManager allows you to:

Change field names

Hide fields

Change the help text for fields

Rename tabs

Hide tabs

Create new tabs

Move fields to different tab

sInherit field values from parent documents

Prefill date values with customisable values

Link fields together so their values always match

Rename and move sections of the document editing page

Add widgets to Manager fields - e.g. Del.icio.us-like tag interface, color picker, image preview

Make fields required



All these features can be enabled for any manager role, any template, or any combination of these.



The plugin was inspired by HideManagerFields by Brett @ The Man Can. It uses the Jquery library to modify the document management pages after they have been created (no server side transformations are done). It improves on HideManagerFields by adding a standardised API for manipulating fields, adds many new features, and removed the nasty "jump" and flash of hidden fields while the Javascript is manipulated.



Please note that while most features work in older versions, any changes in ModX have an impact on this plugin, therefore development is concentrated on working with the latest version of ModX Evo (currently 1.0.3).

[rthrash]

Great work Nick, keep it up. Would be interesting to see being able to apply rules based on a parent container. E.g., apply rules to the basic template under the blog container.

[Eol]

Great work Nick, keep it up. Would be interesting to see being able to apply rules based on a parent container. E.g., apply rules to the basic template under the blog container.

You mean something like this:
http://modxcms.com/forums/index.php/topic,40937.msg246803.html#msg246803
?

[flughund]

dam, havent seen that MM ints compatible with 1.0.3 and have already updated. Have you already found some bugs/changes why MM is not working under 1.0.3?

[flughund]

sorry for that, works perfect. update overwrited demo_mm-chunk... now just have this alert left:


do you know whats wrong here? I'm using the mg_backend_manager...

[onepack]

mm_hideTemplates('0', '!1') rule and other hide template ruses don't work since the recent upgrade. Did other people run into this?

[fixedmachine]

mm_hideTemplates('0', '!1') rule and other hide template ruses don't work since the recent upgrade. Did other people run into this?

Yeah... I've got the same error :/

EDIT:
Ok here is my solution (patch) for this problem.

I don't know why, but for some reasons Chrome, Opera, IE8 don't apply .hide() for <option> elements. It's already a well known issue.

So replace this code in managermanager/functions/templates.inc.php

Code:

foreach ($tplIds as $tpl) {
$output .= 'if ($j("select#template").val() != '.$tpl. ') { '. "\n";
$output .= '$j("select#template option[value='.$tpl.']").hide();' . "\n";
$output .= '}' . "\n";
}

with something like this:

Code:

foreach ($tplIds as $tpl) {
$output .= 'if ($j("select#template").val() != '.$tpl. ') { '. "\n";
$output .= '$j("select#template option[value='.$tpl.']").remove();' . "\n";
$output .= '$j("select#template optgroup:not(:has(*))").remove();' . "\n";
$output .= '}' . "\n";
}

And btw. there is no <optgroup> tag in /manager/actions/mutate_content.dynamic.php before line 585 so it could determine additional problems.

There should be something like this:

Code:

<optgroup label="blank">
<option value="0">(blank)</option>

sorry for that, works perfect. update overwrited demo_mm-chunk... now just have this alert left:


do you know whats wrong here? I'm using the mg_backend_manager...

Same error here, but only in Google Chrome. It's something with <iframe></iframe>. When you modify - in the mg_backend_manager.php - <iframe> into anything else that error will not occur. But of course it's not the solution but only indication where the problem lies.

EDIT:
For avoid displaying alert you can just comment 412 line in managermanager/mm.inc.php:

Code:

// alert("ManagerManager: An error has occurred: " + e.name + " - " + e.message);

But of course it's not the solution. This will only cause that you won't get this (and any other) error displayed.

It's really interesting, because despite this error everything works just fine.

[Donatas]

Hi there,
just found out, that mm_moveFieldsToTab(); doesn't work in Chrome, works in other browsers well.

[gusdecool]

Excelent Plugin, but need more imporevent in feature