ModxCMS RTE from the front end?

Hi Bob,

IT works - Thank you! Will do some testing, initial tests and the RTE in the front end looks ace. I uninstalled the tinyMCE package and reinstalled it, so Ive got a little configuring to do in the backend now and see if I can get my modredirect and furls working again

Thanks again for your patience and help

This is going to sound stupid, but I’m involved in several different ongoing threads on TinyMCE and/or NewsPublisher and I was positive (though wrong) that reinstalling TinyMCE was the first thing I had suggested to you.

TinyMCE is a cranky install/upgrade for some reason and uninstalling and reinstalling it is sometimes necessary to get it working.

Anyway, I’m glad you got it sorted.

Wish I did that a couple of days ago. Just been playing with the newsplublisher CSS, removing the padding etc around the fields, so I get virtually a true frontend wysiwyg editing experience. If I wanted to add a couple of carriage returns tags after the label so the fields drop down to the next line on the form wheres the best place to add this?

I did a number of "newspublisher" searches in the modx forum, any ideas why i dont see any recent threads. I’m only seeing stuff that was posted in 2006 and I know we’ve used the term in this thread and I’m sure Ive seen you use it in other threads.

You should be able to make the form look the way you want just by editing the CSS. FireBug will be a big help for that. Every field in the form will have its own ID so you can make any of them display:block or display:inline and set the desired margins and padding on them.

If they are on the same line now, that suggests that maybe the newpublisher.css file isn’t being found (or the page has no template or a funky template).

As for the references, there was a version of NewsPublisher written long ago (pre-Evolution). I’m not sure if it will work in Evolution or not. My Revo version was just released a short while ago.

Thanks, got the form to look how I want it now. Just applied the fix for the buttons bruno17 suggested in the other thread so its working great. Only ’final’ thing I need to work out is how to get my styles showing in the drop down list in the front end. Ive added the &cssfile parameter as follows:

[[!NewsPublisher? &show=`pagetitle,content` &initrte=`1` &tinywidth=`1000px` &tinyheight=`400px` &rtcontent=`1` &cssfile=`/css/styles3.css`]]

but doesnt seem to be showing up in the dropdown list. I think all the otherbuttons are working ok (although can’t see the table buttons but ive seen that asked before so ill do a search on the forums for that)

The &cssfile parameter is for the file containing the CSS for the NewsPublisher form. TinyMCE uses its own CSS file for formatting inside the editor. I looked, but couldn’t find any way to set it. It seems to me that it used to be in the Plugin Properties, but I don’t see anything there. Maybe someone else knows.

Thanks for looking Bob,

Hopefully someone with a little bit more experience with TinMCE will chime in, however will us it without the CSS selectors for the time being.

Cheers

Chaps

Heres a strange one, I was having problems with the EDIT button working on different pages/templates. With this call:
It would give me the error: could not set the np_id...etc


I would press the "Could not set the Np_ID..." edit button and it would go to the correct edit page (meaning it worked)

Now all of a sudden it shows this error: No context Save_document permission. Just out of the blue.

First, just set the np_id default property of the NpEditThisButton snippet to the ID of the NewsPublisher Resource (or, better, add the &np_id=`##` property to the NpEditThisButton snippet tag, replacing ## with the Id of the NewsPublisher Resource). That will bypass the code that tries to set it.

To use NewsPublisher, you need to be logged in in the front end. The Context Access ACL entry giving you access to the 'web' context needs to have a policy with save_document checked.

If you're previewing from the Manager, you're not really logged in in the front end (more correctly, you're the '(anonymous)' user, so you don't have most permissions), so that could be it.

Something is not quite right there, as a logged-in sudo Manager user doesn't need to log in to the front-end to access protected pages there - I haven't experimented with lesser Manager users. Unless his permissions are limited, perhaps? Again, I haven't done any experimenting on this.