HTML Logo by World Wide Web Consortium (www.w3.org). Click to learn more about our commitment to accessibility and standards.

Moving forward with Composr

ocPortal has been relaunched as Composr CMS, which is now in beta. ocPortal 9 will be superseded by Composr 10.

Head over to compo.sr for our new site, and to our migration roadmap. Existing ocPortal member accounts have been mirrored.


Members' submitting/editing of Comcode pages

Login / Search

 [ Join | More ]
 Add topic 
Posted
Rating:
#103168 (In Topic #20202)
Avatar

Well-settled

Two Privileges-related questions

Greetings!

I've two questions that I'd really appreciate some information about, concerning Members' ability to create/submit/edit Comcode-based pages...

1. Members can't create standard (high-impact) Comcode pages unless they have the Global Privilege "Edit other users' high-impact content" - merely allowing "Edit own high impact content" isn't sufficient. But I definitely don't want my members editing each other's high-impact contributions, only their own.

2. Is there a setting anywhere that will allow Members/Supermembers (i.e. non-staff) use of the full WYSIWYG toolbar? They currently get only a reduced set of buttons, which excludes all the special Comcode tools, the horizontal rule and (particularly important) the Source viewer. So they're greatly limited as regards what they can include - not even attachments!

Thanks in anticipation!

(I'm running v9.0.9, btw.)
Back to the top
 
Posted
Rating:
#103172
Avatar

Well-settled

Update: 

re my second question: The full toolbar is now displaying for members - since granting the group "Subject to a more liberal HTML" privilege and then un-granting it! I'm not quite sure why that should have succeeded though.

re my first: No headway figuring this out for myself, so I'm still pleading for info from any of you who might know!

Thanks as before!
Back to the top
 
Posted
Rating:
#103174
Avatar

We have reimplemented how Comcode page permissions work for v10. I don't think you can do this in v9, because it's based on the assumption that non-staff users aren't editing the main pages of the site.

"Subject to a more liberal HTML" is hooked into how advanced the WYSIWYG is, via this line in WYSIWYG_SETTINGS.tpl:

Code

var precision_editing=((typeof window.take_errors!='undefined') && window.take_errors) || (get_elements_by_class_name(document.body,'comcode_button_box').length>1); // Look to see if this Comcode button is here as a hint whether we are doing an advanced editor. Unfortunately we cannot put contextual Tempcode inside a Javascript file, so this trick is needed.

It's quite intentional. If users do not have that permission, a lot of their HTML would be stripped out or heavily simplified anyway.


Become a fan of ocPortal on Facebook or add me as a friend. Add me on on Twitter.
Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about ocPortal whenever you see the opportunity.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying ocPortal on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Back to the top
 
Posted
Rating:
#103179
Avatar

Well-settled

Many thanks, Chris - both of your points give me bearings and will save me a whole load of time spent experimenting in the dark!

Regarding my wanting to grant Comcode Page permission for members: that would be to enable them to work on-site on major articles they're aiming to publish within the site, and from that standpoint they're obviously doing something equivalent to what, for the majority of sites, staff alone would be doing. Failing that, of course, they'd be obliged to upload remotely composed content and run against the inconvenience of having to replace their current work each time they needed to edit it.

I'm envisioning that such articles would comprise a discrete collection of child Comcode pages that could readily lend itself to hierarchical structuring.  But, given v9's Permissions limitations, perhaps I should be looking instead at whether its blogging functionality wouldn't be the better option here - or perhaps just waiting until v10's release before committing myself to a definite choice of implementation. Either way, I should probably also be exploring the Authors system and taking advantage of whatever it offers in this respect.

Thanks again, and kind regards,

Richard 


Back to the top
 
1 guests and 0 members have just viewed this: None
Control functions:

Quick reply   Contract

Your name:
Your message: