|
eDee Bruns
|
October 17, 2013 at 10:36 am
So here’s a question you probably don’t get every day ….
We’re not going to offer our staff members some of the options in the Event Overview. Things like “make this event a post” will need to be removed, even though it’s set to not allow a staff member to do so, it still shows up in the Event Overview options.
So when we purchase the software, what php page am I going to need to edit to comment out the options we’re not going to offer?
Thanks.
|
|
Jonathan Wilson
|
October 17, 2013 at 12:48 pm
Hi eDee,
Are you testing this by logging into an account with the Role set to “Event Manager”? It will still show for anyone with Admin rights, even if you set that option to No.
|
|
Sidney Harrell
|
October 17, 2013 at 1:31 pm
Thanks, I’ve created a bug ticket, found the fix for it, added the fix to your demoee.org site, and submitted the fix onto the ticket for the 3.1.37 release. For the 3.1.36 release, you can add it manually by opening the file includes/admin-files/event-management/new_event_post.php and adding the following to the top of the file:
<?php
if (function_exists('espresso_member_data')) {
global $espresso_manager;
$is_admin = (espresso_member_data('role') == "administrator" || espresso_member_data('role') =='espresso_event_admin')? true:false;
if ($espresso_manager['event_manager_create_post'] == 'N' && $is_admin == false){
return;
}
}
?>
Note: if copy and pasting from here, be careful because the forum software will include the line numbers above in your paste. You’ll have to manually remove them after you paste, or copy and paste one line at a time. Thanks.
|
|
eDee Bruns
|
October 21, 2013 at 10:08 am
Thank you, very much appreciate it. I will attempt that now on our demo site.
However there are other options we’ll need to remove:
Member Options
Event Promotions
Event meta
Groupon Options
Event Questions for additional attendees
event questions for primary attendees
Featured image
Event media
Even though Staff Members are not allowed those permissions or roles, won’t those still appear? I need to know which .php page I’ll need to comment those out. We may use them in the future, but for now we want it a bit more simplified.
Thanks again
|
|
eDee Bruns
|
October 21, 2013 at 10:12 am
I don’t think I can change it because I’m running a test drive through your sever. I don’t have access to those files.
I was thinking I could edit through the plugin editor, but I’m not sure you want me to.
|
|
Dean
|
October 22, 2013 at 12:17 am
Hi,
Ideally, we would prefer it if the core files were not modified 🙂
The two files that would contain most of the boxes are event-espresso/includes/event-management/add_new_event.php and edit_event.php
|
|
eDee Bruns
|
October 22, 2013 at 8:28 am
Hey Dean,
I agree with you completely, but commenting out the code is easier for me than playing with the css.
However, if you have a suggestion for a wiz-bang plugin (lol) and tips to make it easier to edit the css I’m all ears.
I have about 3 weeks to make sure this is going to work and roll it out so time is of the essence.
Thank you for all your help. I think this plugin is going to work for us, I may just need to recode a bit of it for a while.
|
|
Dean
|
October 23, 2013 at 12:40 am
Yes sometimes it is necessary to tweak the code, while we try to be as flexible as possible we can never meet every need.
The templates are aimed to keep core edits reduced, but if you need edits like changing the admin side of things, they may be needed. If I find a way to do it without core edits, i’ll let you know.
I like to use the My Custom CSS plugin for over riding the CSS, it keeps it separate so updates dont affect it.
|
|
Seth Shoultes
|
November 5, 2013 at 10:27 am
Another option would be to create hooks and/or filters for the sections or settings that are not to be seen by your users. Then you can send us the code to for review for addition into a later version.
|
