Support/Comments for QuickManager+ 1.3--

634 Posts

Lammikko Reply #11, 17 years, 1 month ago

Quote from: AspenDew at Aug 11, 2009, 02:28 PM

I can’t get TinyMCE to work in QuickManager. It shows up in the Manager, but it doesn’t show up in the QuickManager. The option for TinyMCE is there, but nothing happens when it’s selected. The content editing window is the same as it is when "None" is selected, which is just plain HTML.

There should be no conflicts with MODx basic install. As Cipa said it’s propably JavaScript conflict. What snippets/plugins/modules/JavaScripts you have installed?

By the way, did you try to clear MODx cache and your browser cache?

Mikko Lammi, Owner at Maagit

91 Posts

Nic Boyde Reply #12, 17 years, 1 month ago

I’ve just started using MODx 1.0 after some years of MODx 9xx.

QM comes with the package and starts up just as QE used to. But I can’t make the banner move out of the way like I could with QE’s start-up banner.

It sits there at the top of the screen, just where my website has its login fields, and i can’t access the fields - QM covers the whole width of the screen.

I’m using Firefox 3.5.2. I can’t work out from the documentation (well, the configuration choices) what to do.

I came across a sentence saying that QM had been upgraded to be in a fixed position.

Anyone else found this problem?

Yours

Nic

MODX Revolution 2.6.5-pl (traditional)

Hosted on MODX Cloud

Skype: nicbaldeagle

634 Posts

Lammikko Reply #13, 17 years, 1 month ago

Quote from: nicboyde at Aug 12, 2009, 03:07 AM

QM comes with the package and starts up just as QE used to. But I can’t make the banner move out of the way like I could with QE’s start-up banner.

This may surely be a problem but only if you are logged in MODx manager. You can modify the style.css file to remove hover behavior. Delete or comment out line 4:

position:fixed;

Moving the banner is unfortunately impossible at least for now.

Mikko Lammi, Owner at Maagit

31 Posts

AspenDew Reply #14, 17 years, 1 month ago

Quote from: Cipa at Aug 11, 2009, 02:54 PM

I suspect a javascript conflict.
Any javascript errors in Firebug?

Quote from: Lammikko at Aug 12, 2009, 12:57 AM

There should be no conflicts with MODx basic install. As Cipa said it’s propably JavaScript conflict. What snippets/plugins/modules/JavaScripts you have installed?
By the way, did you try to clear MODx cache and your browser cache?

Thank you both for your responses. I have cleared the browser and MODx caches (also tried in 3 different browsers: FF 3.0.10, Safari 4.02, and Opera 9.52. )

Installed version of MODx is Evo 1.0. I followed the "Alternative method" in the Wiki for upgrading from 9.6.3, ie, I copied the site to my local machine, downloaded & extracted 1.0, then copied my customised snippets to it, uploaded all and ran the install, choosing to upgrade/install any updated snippets.

I have installed no javascripts apart from what has come in the below snippets / plugins, etc. (I have not added any to my pages. I do alright with HTML and CSS, but I haven’t quite got my old brain around javascript or PHP yet.)

Plugins:
QuickManager 1.3.1
TinyMCE 3.2.4.1 (version 3.2.0.1 from the 9.6.3 install is disabled & greyed out.) I have made two changes in tiny_mce.js for forced root block and valid child elements:

forced_root_block : false
valid_child_elements : "td/th[a|#text]"

I am also using the customised editor with the default TinyMCE plugins plus the table plugin. TinyMCE works in the Manager as expected, but not in QuickManager. The customised parts of TinyMCE with regard to the Web plugins, as set in Elements / Manage Elements / Plugins / TinyMCE / Configuration, are:

&customparams=Custom Parameters;textarea; &tinyFormats=Block Formats;text;p,h1,h2,h3,h4,h5,h6,div,blockquote,code,pre,address &entity_encoding=Entity Encoding;list;named,numeric,raw;named &entities=Entities;text; &tinyPathOptions=Path Options;list;rootrelative,docrelative,fullpathurl;docrelative &tinyCleanup=Cleanup;list;enabled,disabled;enabled &tinyResizing=Advanced Resizing;list;true,false;false &advimage_styles=Advanced Image Styles;text; &advlink_styles=Advanced Link Styles;text; &disabledButtons=Disabled Buttons;text; &tinyLinkList=Link List;list;enabled,disabled;enabled &webtheme=Web Theme;list;simple,advanced,editor,custom;custom &webPlugins=Web Plugins;text;style,advimage,advlink,searchreplace,print,contextmenu,paste,fullscreen,nonbreaking,xhtmlxtras,visualchars,media &webButtons1=Web Buttons 1;text;undo,redo,selectall,separator,pastetext,pasteword,separator,search,replace,separator,nonbreaking,hr,charmap,separator,image,link,unlink,anchor,media,separator,cleanup,removeformat,separator,fullscreen,print,code,help &webButtons2=Web Buttons 2;text;bold,italic,underline,strikethrough,sub,sup,separator,separator,blockquote,bullist,numlist,outdent,indent,separator,justifyleft,justifycenter,justifyright,justifyfull,separator,styleselect,formatselect,separator,styleprops &webButtons3=Web Buttons 3;text; &webButtons4=Web Buttons 4;text; &webAlign=Web Toolbar Alignment;list;ltr,rtl;ltr

Other plugins installed but not in use:
Bottom Button Bar (greyed out/disabled)
Forgot Manager Login
Image TV Preview 1.2.0.4
Inherit Parent Template
Search Highlighting 1.4
TransAlias 1.0

Snippets:
Actively using:
AjaxSearch 1.8.3
Breadcrumbs 1.0.1
eForm 1.4.4.6
Wayfinder 2.0
WebLoginPE 1.2.0

Installed but not in use:
autoGallery 1.0-rc2
Ditto 2.1+
FirstChildRedirect 1.0
Jot 1.1.4
ListIndexer 1.0.1
MemberCheck 1.0
NewsPublisher 1.4
Personalize 2.0
Reflect 2.1
Ultimate Parent 2.0 beta
WebChangePwd 1.0
WebLogin 1.0
WebSignup 1.1

Modules
DocManager 1.0
QuickEdit - Disabled.

I am getting six javascript errors when loading QuickManager to the "Edit Resources" window. When this happens, it has loaded with the default editor, which is "none."

parent.tree is undefined
parent.tree.ca = "open";\nindex.ph...ager=true (line 28)

parent.tree is undefined
parent.tree.saveFolderState();\nindex.ph...ager=true (line 117)

When I choose TinyMCE as the Editor to use, I get the following errors:

top.mainMenu is undefined
top.mainMenu.work();\nindex.ph...ager=true (line 23)

(All three of the above errors are in index.php?a=27&id=13&quickmanager=true )

The other errors that come up are: (the first two are the same as the first two above)

parent.tree is undefined
parent.tree.ca = "open";\nindex.php (line 28)

parent.tree is undefined
parent.tree.saveFolderState();\nindex.php (line 117)

illegal character
var tinymce={majorVersion:"3",minorVersi...hanged();return true}return false})})();tiny_mce.js (line 1)
This file begins as:
var tinymce={majorVersion:"3",minorVersion:"2.4.1",releaseDate:"2009-05-25" ,

tinyMCE is not defined
tinyMCE.init({\r\nindex.php (line 756)
about 40 lines of code here; I can attach a test file of this and the code from all other errors if necessary; again, I don’t know Javascript, so I don’t know what is useful or not useful.)

illegal character
(no source for http://lrcgs.org/assets/p...nymce3241/jscripts/tiny_mce/tiny_mce.js)tiny_mce.js (line 1)
But the source - the entire tinyMCE.js - comes up with clicking on the error within Firebug. However, it does return a 404 when directly clicking the link in the browser, as I have all sub-directories set to no indexing. Does QuickManager need this to be set up differently in order for it to call TinyMCE?

Otherwise, the error messages referencing TinyMCE make me think there is a problem with TinyMCE, but if that is the case, I wouldn’t have thought it would work in the Manager. But it works just fine there.

Still, I am hoping these error messages will shed some light on the problem. Thank you again for your assistance.

634 Posts

Lammikko Reply #15, 17 years, 1 month ago

JavaScript warnings parent.tree.* and top.mainMenu* are harmless. They are there because MODx manager has two frames that are missing when using QuickManager+.

TinyMCE warnings are alarming. They should not be there and that is probably the problem. Source of these errors is unknown to me. Try to upload TinyMCE files again if there is a corrupted file. This seems very unlikely since TinyMCE is working in manager but still.

Mikko Lammi, Owner at Maagit

1,624 Posts

cipa Reply #16, 17 years, 1 month ago

Quote from: Lammikko at Aug 12, 2009, 04:41 AM

Quote from: nicboyde at Aug 12, 2009, 03:07 AM

QM comes with the package and starts up just as QE used to. But I can’t make the banner move out of the way like I could with QE’s start-up banner.

This may surely be a problem but only if you are logged in MODx manager. You can modify the style.css file to remove hover behavior. Delete or comment out line 4:
position:fixed;
Moving the banner is unfortunately impossible at least for now.

What about making QM a small square in the top right and when you click it slides horizontally.
You can show only the modx logo with a QM on top.

Responsive CSS Grid: cipalabs.com/projects/metal/
Blog: MODX Tutorials & Articles

MODX Staff
12,272 Posts

Ryan Thrash Reply #17, 17 years, 1 month ago

Quote from: Cipa at Aug 12, 2009, 06:08 AM

What about making QM a small square in the top right and when you click it slides horizontally.
You can show only the modx logo with a QM on top.

Definitely one of the items that needs to be tackled for 1.0.1, and that solution exactly has been discussed.

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

1,624 Posts

cipa Reply #18, 17 years, 1 month ago

^ Im thinking that thing can be used as a "Front End Manager". Developers could add new functionalities in that sliding box.
Nothing comes to mind.

Responsive CSS Grid: cipalabs.com/projects/metal/
Blog: MODX Tutorials & Articles

59 Posts

Mar Reply #19, 17 years, 1 month ago

Hello,

I’m trying to build a website where a privileged user is able to create new documents, but not sub-childs (restricting creation to level 1 in the crude illustration below). It seems as if QM+ overrules the ’container’ property of the parent document and activates it if I try to create a document at any Level 2 node.

I would much prefer if QM+ honoured the container property and created the document in the parent folder (unless the parent folder is root and root is restricted in the server settings, in which case the ’Create new document’-button should be grayed out). I’d also like being able to configure the plugin so that the browser stays at the current page instead of loading the newly created document.

Maybe this is already possible? I apologize if that’s the case; I’ve looked around and haven’t found anything.

Root
  |
  +-- Level 1
        |
        +-- Level 2
        |
        +-- Level 2

31 Posts

AspenDew Reply #20, 17 years, 1 month ago

Quote from: Lammikko at Aug 12, 2009, 05:48 AM

JavaScript warnings parent.tree.* and top.mainMenu* are harmless. They are there because MODx manager has two frames that are missing when using QuickManager+.

TinyMCE warnings are alarming. They should not be there and that is probably the problem. Source of these errors is unknown to me. Try to upload TinyMCE files again if there is a corrupted file. This seems very unlikely since TinyMCE is working in manager but still.

Thank you for your help. I copied the TinyMCE directory from the Evo 1.0 distro to the server again, and that seems to have done it.

I’ve noticed a couple of posts in this thread regarding the QM interface. Just wondering if the idea in my post over in the Evo discussion has any merit? (Regarding placement of the Cancel & Delete buttons)

http://modxcms.com/forums/index.php/topic,38613.msg232927.html#msg232927

Thanks again for the RTE help!