The <code> tag is usually formatted with a fixed width font by default and probably won’t automatically scroll. However, you can easily override the font and turn all CODE elements into fixed height block elements very easily via CSS. That’s the beauty of using a tag like this. It’s far more descriptive than a plain-Jane DIV tag. Sematically, you’re telling the reader exactly what kind of content it is...it’s "code"! And again, you can make it look however you want. I would probably style all CODE tags with the Courier font at maybe a 10 to 12 point size...not too big, not too small. Then, you could make all CODE elements block level elements by setting the Display CSS property to "block". That’ll allow you to set a fixed height for the CODE elements and perhaps a percentage for the width if you want it to be more dynamic.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
[solved]
i retouching the js and bring me this errors
in firefox editor show well but in ie 6 and 7 give a error delta_width is null and dont show.
yesterday all works ok Could be a server problem whith paths? i search about this and the solutions i find dont solve it?
hi
Quote from: pixelchutes at Dec 20, 2006, 05:13 PM
Quote from: xyzvisual at Dec 20, 2006, 12:58 PM
i have a problem when saving a tv from manager the value i imput dont save im using 9.5 and i reupload and renistall all modx and still happens.
Any sugestions?
This is a bug that has been bothering me as well. It’s almost picky the way it sometimes saves and sometimes does not?
My temporary solution is to view the page and edit the section directly via QuickEdit. QuickEdit edits save for me every time. 
Definitely a bug and one that isn’t related to TinyMCE. I think another quick workaround is to set a default value in the TV configuration itself. Weird, I know...but apparently it works.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Quote from: Dr. at Dec 20, 2006, 10:49 AM
Quote from: Bravado at Dec 20, 2006, 10:12 AM
Honestly...this is not recommended right now.
LOL... I sort of expected that answer 
, but I did not ask (nor do I care) if it is recommended. I just wanted to know if it could be done. If it can, I am probably going to do it.
Quote from: Bravado at Dec 20, 2006, 10:12 AM
The primary reason is that in doing so you would enable front-end users to see and possibly modify and/or delete any and all images, files, and directories in the resource browser for the site[...]
I understand the permissions that I would be granting these so-called front end users would be equivical to or greater than the permissions of most managerial roles, but There is only one front end user, who is also a manager (the only other manager account would be me, who set up the site). I showed him how to use NewsPublisher, and he loved it, except he can’t upload images and almost every one of his blogs has at least one image. So this is a deal breaker.
I looked into manager/media/browser/mcpuk/connectors/php/ and tried to edit the config and the files in the /Auth/ folder. That lead me to manager/includes/user_settings.php where I tried commenting out the if in manager check. I am getting lost here, and like I said earlier, I am not that concerned about tight web security, I don’t really care at this point. I just want to know where to start looking so that when any user with front end publishing access edits with TinyMCE the resource browser button is not hidden. I hope I am not opening a can of worms where you would hold back info because you don’t personally like the idea.
-sD-
scotty Delicious
Alright, Scotty, here’s the scoop. To allow for using the file browser on the front-end would require alot of rewriting of the MCPUK file browser script, specifically the connector scripts themselves. We had to lock everything down and change the way paths are handled due to some serious code injection issues...especially with the Thumbnail.php and iconlookup.php scripts. This basically makes it pretty difficult to allow any access on the front-end without causing some serious security issues.
There just isn’t any easy way of coding the MCPUK file browser script for use on the front-end right now...even for web users. We really need a full replacement that has more robust capabilities for setting access rights and permissions. I’ve been looking at a number of solutions and would very much like to nail this down very soon. The MCPUK file browser script has pretty much outlived its usefulness and we really need something that ties into the scope of what we’re doing with MODx.
In the meantime, why don’t you just allow that user access to the manager? You could easily create a user group and lock everything down to where the user only sees what you want them to see. The user won’t need to see the Resources tab or any of that stuff so just lock it down and call it a day. At least that way he’ll be able to do everything without restrictions.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Hi Everybody, hope Im right here.
I just upgradet to modx 0.9.5 and would like to use the TinyMCE, but the letters in the editor are so small, it makes me crying while working.
Can I change the letter size?
Thank you and hope you’r prepared best for christmas so you have still time to answer dummy-questions
Nudibranch
Smile, it confuses people!
you can change editing the css of the template into the assets/plugins/tinymce....
hi
Quote from: Dr. at Dec 22, 2006, 11:57 AM
Jeff, I appreciate your time in answering my question.
As I re-read my post that you quoted, I sound harsh and angry... I should have re-read that earlier, because I am definitely neither harsh nor angry
Anyway... yeah I kind of found it’s paths to be hard coded in most places, and as you said, it is for security purposes. I should not have said I did not care about security. that is not true. I am on a shared server, so I hope that other developers are as careful as you have been in making a potentially leaky application type (file browser/uploader) as safe as possible.
Are we talking about writing a MODx specific file manager/uploader? I would be interested in donating my time and knowledge to the project... or at least get something started. Is something started already?
-sD-
Dr. Scotty Delicious, Scientist.
It’s alright, Scotty! I always try to answer questions as thoroughly as possible and tone things down to a more reasonable level. No biggie!
As far as a new file manager is concerned, I have two or three candidates that I’m looking at and hopefully will have more info very soon. I’m still researching everything at the moment.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Hi all... what is the right way to change the TinyMCE settings?
The easier way is to edit the plug-in code in the manager, adding settings in the init call of TinyMCE. This will be eventually overwritten by upgrades.
And... another question: I see that the html code generated by the plug-in script are full of {$_lang[’stuff’];} or {$someVariable} ... so, what is this syntax? {$variable} seems to me to be not documented, is it?
Daniele "MadMage" Calisi
