| Kingsley |
|
||||
|---|---|---|---|---|---|
|
Oke, so I want to address the choosing of the editor: At this moment you have to set what editor you choose on 'x' locations. In pages, in html parser, in bb code parser, in main settings (did I miss one??) My question: is there logic behind the way it is done now? I understand the need for multiple editors, for each site has different needs, but I find the different locations to change settings somewhat confusing, and well, not needed. From my point of view it's not very clear if there is a setting that is incorrect, or i didnt edit yet, or that the problem lies in my creation. I use a freshly installed
|
| lukgoh |
|
|---|---|
|
I have had this problem for a long time now, I struggled to get one working, so I am happy now... lol. |
| Trustmaster |
|
|---|---|
|
To make matters worse, each page has its own "Parser" setting which switches an editor too. By the way users are often confused when they try to edit Welcome page and no editor appears. This is because the Welcome page is plain text. However, if you leave "HTML parser" and "CKEditor" plugins checked upon installation as by default, HTML + CKEditor becomes default everywhere (except for that "Welcome"). I don't think we're going to remove all those degrees of freedom in parser/editor choice because some people claimed they'll quit Cotonti if they don't have this feature. Basicly I tried to simplify it this way: if you install just 1 parser and 1 editor, that should be used by default. However, if you think that there really must be a big red button to set all parsers to just 1 value, that could be done by introducing an option in config.php. May the Source be with you!
|
| GHengeveld |
|
|---|---|
|
The thing with parsers is that sometimes you'll want to be able to choose a different parsing method for a specific page. For example, I may want to write my blog posts using BBcode, but a 'portfolio' page might be in HTML. Some wiki systems have even more parsing options, e.g. Github has 9 different dialects of text-to-html markup. A common markup language used in the development world is Markdown (Cotonti plugin), which has my personal preference over BBcode or HTML in most cases (most notably documentation). |
| Kingsley |
|
|---|---|
|
I understand the need for multiple parsers/editors, as I said, but I was merely addressing the fact that the way it is now, it is confusing to get to work. why not round all those options up into one place? I mean, I still have no editor to use anywhere, but to my knowledge I set everything right, have checked the forums for answers, etc.
never really had that problem until I started using siena. and seeing Lukgoh struggled with it to, I'd say it's a (minor) thing that needs to be rethought/refurbished a bit, that's all.. |
| Trustmaster |
|
|---|---|
|
Where do you think those options should be placed? May the Source be with you!
|
| Kingsley |
|
|---|---|
|
config -> parser/editor options? |
| lukgoh |
|
|---|---|
|
Editors are working perfect since updating to 0.9.8. Thanks guys! Having said that, any ideas why this is happening --> http://www.bidfish.co.uk/clan/1.png Using:
cot_textarea('rulestext', $rowrules['rules_text'], 16, 56, '', 'input_textarea_medieditor')
|
|
| This post was edited by lukgoh (2012-04-07 21:07, 12 years ago) |
| Trustmaster |
|
|---|---|
|
@lukgoh, it seems like the template is missing some wrapper divs. @Kingsley: I'll have a look how hard it can be. May the Source be with you!
|
| lukgoh |
|
|---|---|
|
No its has the div tags, any other ideas? |
| Trustmaster |
|
|---|---|
|
Looking at the breadcrumbs position and padding on the left side, it's obviously outer markup, not the editor itself. May the Source be with you!
|
| lukgoh |
|
|---|---|
|
Yeah, apologies it's the symisun-03 theme. Thank you. |
