CMS Made Simple Forums

New version looks great! Really excited to start playing around with it.

A quick (dumb) question.... where do I get the FCKeditor and HtmlArea Plugins since they aren't included in this release?

Also, as a footnote, when trying to upload an image using TinyMCE I get the following error after the file has been uploaded, "WARNING: move_upload_file(): open_basedir restriction in effect.... file is not within the allowed path(s). Any ideas on that?

Thanks much in advance!!!

I was wondering the same. I guess the modules must come with an extention tailored for the CMS API.

I am specifically interested in FCKEditor, since it seems to provide a better support for tables than TinyMCE.

The only way I find a way to download the modules at the moment is from the subversion link http://cmsmadesimple.org/cms-daily.tar.gz.
However, these modules are not always stable.

Any better idea?

Yeah, that's the only way at the moment. HTMLArea still doesn't work yet, and I think there are still a few issues with FCKeditor. If you do find that FCKeditor does work ok, I'll tar/zip it up and post it somewhere.

I got htmlarea working on a minimal basis last night. It will only work with svn, though, because I had to add a new callback function to get it to work.

Greg/Patricia, if you guys could test it out (I know you both want it to work), that would be great.

Thanks!

You have a security concious network admin and he's making everyone use IE? Seems like a contradiction to me.

It works well for me in Firefox, actually. I'll try it in IE after I get to work.

Hi Wishy and Patricia,

Same here, have to work today and no access. Also work for people that use Microsoft products exclusively and lock down everything (including the mouse right click).

Will test everything this evening!

There are some admins that really need to get a life. There is a fine line between being security concious and being on a power trip over your users. How do people (especially in IT) get any work done if they're so limited on what they can do?

HTMLArea works in both IE and Firefox with all plugins. Thanks to Patricia for figuring it out. I would've pulled my hair out all evening trying to find it.

Let me know how it works.

Thanks.

OK I'm up to changeset 1157 on my local set-up.
HtmlArea
Doesn't show at all when editing existing pages.

Path problem with inserting Links to files again. (fix from before)

Added 'uploads' to line 159 of htmlarea/plugins/insertfile/config.php

$MY_LINK_FORMAT = ' IF_CAPTION  IF_SIZE  IF_DATE ';

Still uploading to my live site ............

Same on live site. On creating a new page as soon as I select one of my templates the WYSIWYG disappears. Works fine with your default and alternate templates. Will need to do more testing to see what breaks it.

More to follow ....

First Update:
If I remove the css it works.. something in there !
Second update:
I removed the css association from one of my templates and then copied the css back in selector by selector into the stylesheet area on the template page. Found one line that HTMLArea didn't like, I had quotes around a font "Comic Sans MS" removed the quotes and HTMLArea worked again with that template. SO, I took that CSS from that template copied it into css under css management. Associated my template with the css file and HTMLArea quit working with this template again.

This is the css that, line for line, worked in the css box on the template page but does not work from an associated file.

Appears HTMLArea does not work with templates that have associated CSS. Workaround is to put all the css in the template css stylsheet textarea and don't use associated css.

I bet it's CSS related... Might be a bug making an invalid html character somewhere.

I took all the CSS out of the associated file except for 2 selectors

img{
border: 0;
}
acronym {
border-bottom: 1px dotted #000;
cursor: help;
}

And HTMLArea still does not show up...

Took that out just put this in

/* nothing here */

And HTMLArea still does not show up...

It is just the fact it is an associated file ...

Ignore my reply. I had the box open for like an hour before I hit the submit button.

You do that too

I guess you could use this as a feature. A quick way to turn the WYSIWYG on or off. Have a template with 'associated CSS' and use this to turn HTMLArea off, any template with the 'CSS in the template' could then turn it back on.

When the bug is tracked down maybe the solution can be used to build a switch right on the page you are editing (which would be handy).