Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter drlonniejonespfmp

    (@drlonniejonespfmp)

    Before I would manually create different roles but I found the plugin User Role Editor to be better. I haven’t had an opportunity to try User Role Editor with custom actions though. In this case, I have different types of editors like operations editor, marketing editor, or community content author and then different content consumers like employee, manager, and trainer. The content editors are allowed to modify their custom post types. Then the consumers have different levels of access based on their role.

    Side note: I have been messing around with the idea with nested groups which hold multiple roles;however, logistically it will get complicated with vertical and horizontal roles.

    Thread Starter drlonniejonespfmp

    (@drlonniejonespfmp)

    Sooner is better. Arsdehnel, how long do you think it would take?

    The only workaround I’ve figured out to do in the mean time is to remove the title then place an h1 inside eyes only. Not my most elegant solution, but it works as a temp solution. Downside is that sorting by title is pretty much worthless.

    I tried Access Control, but I ran into an issue with custom post types showing when it is on the page. The expected behavior would be to hide the post regardless of the page.

    Thread Starter drlonniejonespfmp

    (@drlonniejonespfmp)

    I’ve been looking high and low for one. What would you recommend? I’m looking for something that will hide a custom post type title based on the user role for specific posts. So, a non-contributor should not be able to view a post related to a new blogging policy. This is a list of plugins I’ve looked at:

    • Toolset Access
    • WP-Members
    • Members
    • User Role Editor
    • Hide Title
    • WordPress Access Control
    • Adminimize
    • Advanced Access Manager
    • Groups

    I know this is a bit old, but I thought it should be answered. You need to select a formID and fieldID for separate field conditions. Your day > 0 return will work.

    Your code should look something like this:

    <script>
    gform.addFilter( 'gform_datepicker_options_pre_init', function( optionsObj, formId, fieldId ) {
    if ( formId == 10 && fieldId == 9 ) {
    //Block Here for first calendar
    }
    return optionsObj;
    
    if ( formId == 10 && fieldId == 25 ) {
    //Block Here for second calendar
    }
    return optionsObj;
    </script>

    You can find additional details about about similar examples here:
    https://www.gravityhelp.com/documentation/article/gform_datepicker_options_pre_init/
    https://api.jqueryui.com/datepicker/

    This is my sample for only allowing mondays and tuesdays for form 4 on field 6 (a calendar).

    <script>
    gform.addFilter( 'gform_datepicker_options_pre_init', function( optionsObj, formId, fieldId ) {
        if ( formId == 4 && fieldId == 6 ) {
            optionsObj.firstDay = 1;
            optionsObj.beforeShowDay = function(date) {
                var day = date.getDay();
                return [(day == 1 || day == 2)];
            };
        }
        return optionsObj;
    });
    </script>

    +1
    If whitelisting an IP address is not available within an enterprise environment, work flow stops to a grinding halt. I wish there would be a way to just lock the account and not IP.

Viewing 5 replies - 1 through 5 (of 5 total)