Super Restricted Entries

Developer

Amici Infotech

3rd Party (Commercial)
Current Version: 1.0.2
Minimum EE Version: 4.0.0
Release Date: Oct 25, 2019

Timed License

Duration: 1 year
Renewal Price: $10
What's this?

License Agreement

Buy Now!

$29.00
Qty:

EE Version Support

  • ExpressionEngine 4
  • ExpressionEngine 5

Compatibility

If an item is crossed out, it might be untested, not applicable or incompatible. Contact the developer to be sure.

  • Updater
  • Multi Site Manager
  • Stand Alone Entry Form
  • Low Variables
  • Content Elements
  • Better Workflow
  • Matrix
  • Grid
  • Webservice
  • Publisher

Requirements

  • jQuery for the Control Panel

Add-On Type(s)

Extension, Module

Tags

Super restricted entries is created to allow admin to restrict members or member groups to access entries. You can select whom you want to allow to see the entry in create/edit entries page. You can either allow specific members or member groups to access entries or leave that settings empty to allow everyone to access that entry. There is frontend tags to check access entry wise. You can also pass a parameter in exp:channel:entries loop to rid all entries from list that user not have access to view.

User Links

To get all the entries member is allowed to view, You can just pass a parameter in exp:channel:entries tag. (apply_super_restricted_entries=“yes”). Without adding this parameter, We will not search weather user is allowed to access entries comes with the channel loop or not. If you want to check all the entries in site for member access, You can either pass this parameter to each channel:entries tag or you can just set a config variable in “system > users > config > config.php” file. Variable is:

$config['apply_super_restricted_entries'] = 'y';

Same way if you want to enable all the relationships tags to show only member access entries, You can set a config variable:

$config['apply_super_restricted_entries_relationships'] = 'y';

In similar manner, If you have pass the config variable (that will remove all entries that user has no access to view from exp:channel:entries loop) and want to disable any exp:channel:entries loop to do that, You can do this by passing a same parameter in loop. (apply_super_restricted_entries=“no”)

Template Tags:

1. exp:super_restricted_entries:check

  • Parameters:
    1. entry_id (Example: entry_id=”{entry_id}”)
Example 1: (Check if granted)
{exp:channel:entries channel="blog" url_title="{last_segment}" require_entry="yes"}
    {exp:super_restricted_entries:check entry_id="{entry_id}"}
    {if super_restricted_entries:granted}
        <p> <strong>Granted: </strong>{title}<br></p>
    {/if}
    {/exp:super_restricted_entries:check}
{/exp:channel:entries}
Example 2: (Check for not granted)
{exp:channel:entries channel="blog" url_title="{last_segment}" require_entry="yes"}
    {exp:super_restricted_entries:check entry_id="{entry_id}"}
    {if ! super_restricted_entries:granted}
        {redirect="404"}
    {/if}
    {/exp:super_restricted_entries:check}
{/exp:channel:entries}
Example 3: Mix example for granted and not granted:
{exp:channel:entries channel="blog" dynamic="no"}
    {exp:super_restricted_entries:check entry_id="{entry_id}"}
    {if super_restricted_entries:granted}
        <p> <strong>Granted: </strong>{title}<br></p>
    {if:else}
        <p> <strong>NOT Granted: </strong>{title}<br></p>
    {/if}
    {/exp:super_restricted_entries:check}
{/exp:channel:entries}

Paramter in {exp:channel:entries}

As described above, If you have not set config variable to search for each channel entries loop for member access and you want only entries that member has access to show, You have to pass a parameter like in given example below:

{exp:channel:entries channel="blog" dynamic="no" limit="10" apply_super_restricted_entries="yes"}
    <p>{title}</p>
    {paginate}{pagination_links}{/paginate}
{/exp:channel:entries}

If you have set a config variable and want all entries even if user is not allowed to view that, You have to pass the same parameter (with different value) like in given example below:

{exp:channel:entries channel="blog" dynamic="no" limit="10" apply_super_restricted_entries="no"}
    <p>{title}</p>
    {paginate}{pagination_links}{/paginate}
{/exp:channel:entries}

Working with Relationships

If you have not set a config variable to show only member access entries, You can do that by passing a parameter in channel:entries loop. (parameter not in relationships.)

Example 1
{exp:channel:entries url_title="{last_segment}" apply_super_restricted_entries_relationships="yes"}
    {relationships}
        <p>{relationships:title}</p>
    {/relationships}
{/exp:channel:entries}

Same way, If you have set a config variable and want all relationships entries, You can set that variable to “no”

Example2
{exp:channel:entries url_title="{last_segment}" apply_super_restricted_entries_relationships="no"}
    {relationships}
        <p>{relationships:title}</p>
    {/relationships}
{/exp:channel:entries}

Hooks Used

If the add-on is an extension, and ties into ExpressionEngine's core files, it will use ExpressionEngine hooks. We are listing any hooks the add-on uses for developers to have an easier time locating other add-ons that they can reference for their own work.

  1. channel_entries_query_result

This entry was created July 1, 2019, 2:57 am.
This entry was last updated October 25, 2019, 5:52 am.

Disclaimer: Information about ExpressionEngine add-ons is provided as a service to you, the user, and every member of the ExpressionEngine community. devot:ee is not responsible if you hose, mangle, wreck, or otherwise destroy your EE website by installing an add-on that you found out about at this site, regardless of its rating, Favorites status, commercial or free status, or general popularity. Caveat EEmptor!

Returns: devot:ee has a 30-day return policy on all commercial add-ons sold through devot-ee.com. If you need to return an add-on, do not go to the developer or the developer's site, but rather visit our returns page at https://devot-ee.com/returns to initiate your return. If you have questions, email support@devot-ee.com.

1 Review:

pixi 10.28.19

Rating - {addon_rating_average}

Very usefull and simple to settle in add-on. The support is very quick, efficient and kind. I’m glad to use Super Restricted Entries.