Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

All other Modules /

Discuss all other Modules here.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

New Simplify module v0.0.7 - Hide Delete/Unpublish buttons + Hide Security controls + Requests


Go to End


11 Posts   4774 Views

Avatar
froog

Community Member, 43 Posts

27 January 2010 at 11:04pm

Edited: 15/02/2010 10:12am

Hi all,

The latest version of Simplify (v0.0.7) has been released, with the following features:

1. Hide the Delete and/or Unpublish buttons in the CMS per Group per Page (see attached screenshot)
2. Hide controls in the Security tab (see attached screenshot)
3. Pages can be hidden in the CMS tree by selecting them in the tree under the Simplify/Fields tab
4. Several bug fixes (thanks Uncle Cheese for the Create dropdown display text fix)

Here is a list of requested features which I intend to implement -
Let me know what ones you really want, or any other suggestions!

1. Ensure compatiblity with SS 2.4 and Roles.

2. Create a "Hide tabset labels" option that uses CSS to hide whole tab sets quickly (ie; cleans up the interface even more - see http://silverstripe.org/assets/Uploads/simplifyexample.png)

3. Only allow page creation for certain Groups (eg; so some users can't create pages under the root level)

Download v0.0.7 - attached below

Regards,
Dan (froog)

Avatar
HanginClowns

Community Member, 4 Posts

26 February 2010 at 7:58am

I just installed this module on my silverstripe (v 2.4.0 I believe not sure how to check) instance, and it doesn't seem to be working for me at all. I have a group of users under the same main group, and I edited the main group, just as a test, and turned off ALL permissions that says Simplify in it, and I still have the same permissions as before. One reason this might be, is that the users are all logging in through LDAP using auth_external and I have a custom canCreate() here:

function canCreate(){
if(Permission::checkMember(Member::currentUser(),'ADMIN')){
return true;
}
else{
return false;
}
}

These are the only things I can think of that would be interrupting this plugin. If you can help with any assistance that would be great.

Attached Files
Avatar
froog

Community Member, 43 Posts

26 February 2010 at 8:28pm

Edited: 26/02/2010 8:33pm

Hi HanginClowns - one problem I can see is that you've selected the "Simplify - Global - Disable all Simplify Permissions" option - which means no Simplify permissions will be applied :)

Also I recommend changing Simplify permissions via the Simplify tab rather then the Permissions tabs - they're grouped a bit more nicely (it doesn't really matter which, the Simplify tab is just a "helper" to make your life easier).

The canCreate() shouldn't affect any Simplify permissions.

Let me know how it goes!

Regards,
Dan

Avatar
HanginClowns

Community Member, 4 Posts

27 February 2010 at 8:54am

Sorry, didn't notice that... This is actually to prove that it wasn't working. This time I selected and saved it with that option off, but turned everything else on to show you that I still cannot get it to work with my setup for some odd reason. The user was checked several times if they are an adminstrator and they are not, and they belong under the "Faculty" group of groups of users. The SiteTree is from a regular user and of course the permissions is from a separate administrative user Here's updated screenshots:

Avatar
froog

Community Member, 43 Posts

27 February 2010 at 12:07pm

Hi HanginClowns.

Hmm, that is strange - I have turned on all Simplify permissions and they work for me (on a vanilla SS2.4 install).
Can you confirm what version you are using? The version is located on the bottom right of the CMS admin.

The reason I ask is I can't see either the Roles or the Simplify tab on your Group page screenshot - you should see something like what I've attached.

It doesn't matter if the user is an admin or not, that was a restriction of an earlier version of Simplify.

Also are you using any decorators (such as DataObjectDecorator or LeftAndMainDecorator)?

You may be onto something with the external auth - does Simplify work for you if you create a normal SS user and try to login?

Regards,
Dan

Attached Files
Avatar
HanginClowns

Community Member, 4 Posts

27 February 2010 at 1:14pm

Froog,

Thanks for taking the time to work this out with me. I don't know a whole lot about SilverStripe and I'm not the only person who has been working on this project. So if you can tell me where these decorators might be then I'd be sure to take a look for you. Otherwise, there is no tab and there is no version number in the lower right hand corner. I do remember it being there, before, just not sure why it's not showing? Cause I know I, personally, updated this to whatever was the latest stable release was, sometime last week.

Avatar
froog

Community Member, 43 Posts

2 March 2010 at 10:35am

HanginClowns,

The version can be found in /sapphire/silverstripe_version. The latest stable is 2.3.6.

It seems very strange that the version is not showing - does it reappear when you remove Simplify?

Any decorators should be applied in /mysite/_config.php
and will look like this:

DataObject::add_extension('Group', 'SimplifyGroupDecorator');
Object::add_extension('LeftAndMain', 'SimplifyLeftAndMainDecorator');

where the first param is the class to be decorated, and the second class is the decorator.

Avatar
HanginClowns

Community Member, 4 Posts

3 March 2010 at 6:21pm

Yeah, I found this before, that's why I said it was probably 2.4.0 beta: $URL: http://svn.silverstripe.com/open/modules/sapphire/tags/beta/2.4.0-beta1/silverstripe_version $

I don't see any decorators in here. Just looks like the defaults, besides I added in Director::set_environment_type to dev so I can read any error that come up.

Go to Top