Symphony.

Helooo,

I've had to do a little customising the blueprints > pages core for a little project, yes an extension is the way forward on this one and Page_Prototypes would be ideal, but this is a good way for me to learn.

What I'd like to do is append MarkitUp of CKeditor to a textarea that I've appended in the content.blueprintspage.php file.

Could someone point me in the right direction as to how I would go about hooking a WYSIWYG onto that textarea at all?

Thanks in advance.

Edit

Used nickdunns ui_realign as a basis for my own extension and appended ckeditor stylesheets and scripts to the the head of blueprints/pages/ and all is well! woop.

Hmm. I wonder how you've added a textarea to the Symphony Pages html. How is this content saved to the db etc?

Delegates!

yeah 'delegates' sound good ("l will have one of my minions look into them" - get it?! #imsofunneh)

So, this could easily be used to 'enrich' Symphony Pages with more 'content' fields and create a very(!) simple 'page-based' CMS structure, a simple frog|radiant-cms-like? Not adviseable maybe, but looks like the simplest solution to the simplest static-page-cms requests.

I've added an extra table to the pages table in the DB and created a simple extension that hooks into the ckeditor WYSIWYG to achieve this.

It's a quick and dirty approach to achieve a textarea.

2 Core files with amended to achieve this as well. Like I said, it's not for everyone.

The ideal the scenario would be to create a full extension that appends the content to the blueprints/pages code. I'm not that good yet, but managed to dig around in the code with help from the API to grasp what the delegates we're doing.

The one reason, I want to make a full extension for it in the future is A. to understand a lot more about the core, and B. To not be using a param to render the textarea out to the page. That's what it's doing at the moment.. bad idea? possibly, but it's working like a charm right now.

Edit

It's a private repo on bitbucket right now but will happily share what I've done with you davidlund.. like I said, it works for me but others might not like this approach.

Could it not be done by adding some Javascript that automatically converts any textarea to a rich editor?

That's how I'm doing it... grabbing the ckeditor js made a little extension off the back of nickdunns ui_realign extension and adding a class of ckeditor in the blueprintspage.php file. hardcoded, but I'm not up to speed with extensions fully yet.

So, this could easily be used to 'enrich' Symphony Pages with more 'content' fields and create a very(!) simple 'page-based' CMS structure, a simple frog|radiant-cms-like? Not adviseable maybe, but looks like the simplest solution to the simplest static-page-cms requests

This is what Jonas has done. I'm trying to prise a prototype from him, but apparently it's not stable enough for an alpha release yet.

Having seen what Jonas was working on at the Symposium, I would love to see that released into the wild as well, but these things take time and effort. So I was just looking for a short term fix and this seemed to be (in my mind anyways) :) a neat little addition. Just plain and simple textarea. There are reservations to allowing clients access to the Blueprints area and that's understandable... horses for courses at it were.

Please close thread. Am exploring this as an extension. Which should be good to go in a week or so.