New Extension: Entry Permissions

Boo to bugs. Thanks for reporting. I’m pretty busy with other projects right now, so I’m not sure when I’ll be able to fix these.

I can understand being busy. (I’m glad I am!)

Just a little feature request, if you ever get around to it…it would be really cool to be able to lock a member group out from editing the url_title in a weblog (a whole weblog or individual posts), which you can sort of do now with taking that default field out of the Publish page, and I do, but editors can still edit the url_title in the Edit section if they check off one or more and hit “Edit” in the dropdown selection box at the bottom of the list.

I often use url_title instead of entry_id for hardcoded links to single-entry pages because they look better in the browser. Clients complain when they see “www.mydomain.com/index.php/site/page/45” or whatever. Stupid, but I get it all the time! But, if someone edits the url_title for a given entry, my hardcoded link dies…not good.

I’m mostly not much scared that a editor will even find the url_title once I remove it from the publish page, let alone that they would know what to do with it, but you never know. :D That would really dumb-proof one’s workflow if one needed it…

Another bug…

When I go to the Extensions panel in the CP, I get this at the top of the screen:

Warning: Utilities::include(/opt/home2/jccacweb/public_html/systemfolder33/extensions/ext.entry_permissions.php) [function.Utilities-include]: failed to open stream: Permission denied in /opt/home2/jccacweb/public_html/systemfolder33/cp/cp.utilities.php on line 147

Warning: Utilities::include() [function.include]: Failed opening ‘/opt/home2/jccacweb/public_html/systemfolder33/extensions/ext.entry_permissions.php’ for inclusion (include_path=’.:/usr/share/pear’) in /opt/home2/jccacweb/public_html/systemfolder33/cp/cp.utilities.php on line 147

…and it doesn’t show up in the extensions list, so I can’t even enable the extension. All I did was upload the extension and the language file. Seems like a core system conflict rather than a conflict with any other extension / plugin?

Nick

Sounds like a permission problem, not an issue with the extension itself. Make sure you set correct permissions on the file and the extensions folder.

Nick, what version of EE are you using? I think a ‘failed to open stream’ means the file just wasn’t found for inclusion. Are you sure it’s in the proper directory?

Side note, I just found another bug where if an entry was given permission to multiple groups to edit, it wouldn’t be editable for any of them. Should have this fixed very soon.

I just updated to version 0.3, download it in my first post.

LynneL - I’m using Gypsy with the project I developed this for, and my field is a Gypsy field too and used in multiple weblogs, but I’ve never gotten an error like you’ve described.

I did fix the issue with TinyMCE, which wasn’t related to TinyMCE directly (it was a conflict with the hook).

Also fixed the rather large bug I previously mentioned where you can’t assign multiple groups to edit the entry.

OK testing it out again (I had deactivated that unworking bit a while back) and then of course will update to the new version as well.

This still doesn’t prevent people from deleting an entry, right?

…OK, nope, still getting the same problem…even after updating to .03…

I have a Gypsy group of fields, which is where I am storing the Gypsy field for the Member Group field I want. Then when I check off the member group I want to have access, I get

MySQL ERROR:

Error Number: 1054

Description: Unknown column 'field_id_28_0' in 'field list'

Query: UPDATE `exp_weblog_data` SET `weblog_id` = '2', `field_id_13` = 'b4faec5b8962ba57c0a5fcd634cd60d7.gif\n\n\n\n\n\n\n\n\n\r', `field_id_14` = 'Yes', `field_ft_14` = 'none', `field_id_10` = '

And it totally destroys the View Entry page that happens after you update an entry, blows up the CP, LOL.

On the other hand, when I put the Gypsy field into the field group that holds the rest of the regular fields, specify the one weblog I want it to show up, I still have a problem…

As superadmin, I go into the entry, check off the member group, then log in as someone from that member group. I go to edit the entry I should theoretically have access to, but I get “You are not authorized to access this page” error instead. What’s more, I get that same “You are not authorized” message when that member group tries to edit one of the other weblogs that this Gypsy field is NOT supposed to be part of!

EDIT: I am going to try deactivating extensions to see if there’s a conflict with something other than Gypsy.

EDIT II: Nope, no go..still not working, even wiht everything deactivated except Entry Permissions

Nick, what version of EE are you using? I think a ‘failed to open stream’ means the file just wasn’t found for inclusion. Are you sure it’s in the proper directory? Side note, I just found another bug where if an entry was given permission to multiple groups to edit, it wouldn’t be editable for any of them. Should have this fixed very soon.

I’m on EE 1.6.7 build 20090211. I’m pretty sure the extension was in the correct directory (lang file too). What permissions should the extensions directory be? Mine is 755.

Nick

Ug, I’m so sad! This isn’t working at all for me…

Again, I have a field group that is assigned to three different weblogs. Even when I shut off Gypsy, nothing is working right.

I have given the ember group in question edit/publish access to these weblogs.

Then I give permission for an entry in one of those weblogs to the Member Group.

Then log in with a user account under that Member Group and try to edit. “You are not authorized to access this page”

That also happens when that user account creates a new entry, then tries to edit that! I get the same “You are not authorized to access this page.”

:( Halp?

Oh, and on build 20090320, here.

I wish I could simulate the bugs you’re having. I wish I had time to look into it further, but I made this extension for a paying client, so I have to update it in my free time. My client did report a bug with the Preview and Quick Save buttons though… apparently you’d get a big fat MySQL error if you clicked either of these two. I never use those two buttons so I never saw the error. Anyway, I’ve fixed that bug and will be uploading a new file soon. Maybe that’ll fix the bug you’re having?

I don’t think so…for one thing, I never use those buttons either! For another, the bug is mostly on the “I gave member group permission to edit this post and those members are not able to, nor add new ones.”

It’s possible it’s just a simple thing I did wrong, like missing one permission or something on the member group, but I already went thru it with a fine tooth comb…

I might very well be very interested in sending some moderate scratch your way to fix this, if that’ll motivate you. 😊 Also, I can give you access to the install I’m building to help me debug (again, I don’t expect you to do this for free, though I don’t have a LOT of spare money…but since this plugin appears to do EXACTly what I need for multiple projects, and will be very useful to me, I’m willing to pay!).

I’ll send you an email, if you have an hour or two to start with, I can afford at least that!

Attached to the first post is version 0.4

The old version was storing the IDs in a string separated by an “\n”, which is how how off Mark Huot’s extensions works (as I mentioned I recycled some code from various plug-ins while I was learning how to make one). You might need to manually reset all the permissions in the entries you assigned editing privileges to because I changed it to save the ID separator to a space.

This look like a very useful extension and may solve some of our permissioning problems. Just one minor issue; the extension settings will not save when I submit. Any ideas as to what I may have missed? Thanks.

I attached version 1.1 to the first post. If you were using 0.4 then hopefully your issue should be fixed. If not let me know.