Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only works for Admins / Editors #40

Closed
nexjsystems opened this issue Jul 14, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@nexjsystems
Copy link

commented Jul 14, 2016

Afternoon,

Using this plugin for front end code display (used with bbpress). Everything works fine except today I received an email from a user that the code tabs (css, js, java etc.) do not show up within the TextHTML section of the comments. These buttons display for myself and other admins / editors but not website participants / members.

Is this intentional or is there a fix?

Cheers,
Andrew

@AndiDittrich

This comment has been minimized.

Copy link
Member

commented Jul 15, 2016

Dear Andrew,

currently, this behaviour is intended, because there are too much buttons added which is very confusing for end-users. therefore the quicktag-buttons are limited to editors/contributors.

i can add an option to the next release to enable the quicktags for all kind of users.
additionally, a "code insert dialog" is projected for the Text-Editor (via single Quicktag Button) - this will avoid the long list of buttons in the future.

best regards, Andi

@AndiDittrich

This comment has been minimized.

Copy link
Member

commented Aug 9, 2016

Dear Andrew,

i've just added the filter enlighter_frontend_editing on request #44 - this also allows you to enable the frontend editing functions for all kind of users

FILTER::enlighter_frontend_editing

Description: Forced enabling/disabling of the frontend editing functions. The default value is created by the condition USER_LOGGED_IN AND (CAN_EDIT_POSTS OR CAN_EDIT_PAGES). Useful to bind editing capabilities to special users/groups

Example 2 - Allow all users to use the editing extensions

function mm_ejs_frontend_editing($allowed){
      return is_user_logged_in();
}

// add filter
add_filter('enlighter_frontend_editing', 'mm_ejs_frontend_editing');
@nexjsystems

This comment has been minimized.

Copy link
Author

commented Aug 9, 2016

You are the man!!

Thanks much.

Andrew

From: Andi Dittrich [mailto:notifications@github.com]
Sent: August-09-16 8:25 AM
To: AndiDittrich/WordPress.Enlighter
Cc: Andrew Penley; Author
Subject: Re: [AndiDittrich/WordPress.Enlighter] Only works for Admins / Editors (#40)

Dear Andrew,

i've just added the filter enlighter_frontend_editing on request #44#44 - this also allows you to enable the frontend editing functions for all kind of users

FILTER::enlighter_frontend_editing

Description: Forced enabling/disabling of the frontend editing functions. The default value is created by the condition USER_LOGGED_IN AND (CAN_EDIT_POSTS OR CAN_EDIT_PAGES). Useful to bind editing capabilities to special users/groups

Example 2 - Allow all users to use the editing extensions

function mm_ejs_frontend_editing($allowed){

  return is_user_logged_in();

}

// add filter

add_filter('enlighter_frontend_editing', 'mm_ejs_frontend_editing');


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/40#issuecomment-238536927, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIRTPfvQlLxck_Tz921ke0jOFI6XaDRRks5qeHGfgaJpZM4JMr48.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.