{"id":347411,"date":"2026-08-01T08:05:48","date_gmt":"2026-08-01T08:05:48","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/user-restrict\/"},"modified":"2026-08-01T10:46:43","modified_gmt":"2026-08-01T10:46:43","slug":"easeora-content-access","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/easeora-content-access\/","author":23540385,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.4.2","stable_tag":"1.4.2","tested":"7.0.2","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"Easeora Content Access","header_author":"Md Rifat Hasan","header_description":"Restrict selected pages and posts to logged-in users with a lightweight, secure admin interface.","assets_banners_color":"69768e","last_updated":"2026-08-01 10:46:43","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/wordpress.org\/plugins\/easeora-content-access\/","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":60,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.3.0":{"tag":"1.3.0","author":"rifathasanbd","date":"2026-08-01 08:05:33"},"1.4.0":{"tag":"1.4.0","author":"rifathasanbd","date":"2026-08-01 08:56:39"},"1.4.1":{"tag":"1.4.1","author":"rifathasanbd","date":"2026-08-01 10:29:26"},"1.4.2":{"tag":"1.4.2","author":"rifathasanbd","date":"2026-08-01 10:46:43"}},"upgrade_notice":{"1.4.2":"<p>Improves the restriction manager pagination with five visible page numbers, clear Previous and Next controls, and left-aligned responsive styling.<\/p>","1.4.1":"<p>Fixes the central restriction manager pagination layout and keeps the controls responsive in WordPress admin.<\/p>","1.4.0":"<p>Adds configurable WordPress admin menu placement without changing existing restrictions or visitor settings.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3630762,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3630762,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3630730,"resolution":"1544x500","location":"assets","locale":"","width":2172,"height":724},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3630730,"resolution":"772x250","location":"assets","locale":"","width":2172,"height":724}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.3.0","1.4.0","1.4.1","1.4.2"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Central page and post restriction manager.","2":"Restriction checkbox in the WordPress editor.","3":"General options for the restriction title, message, and login form.","4":"Restricted-content message displayed to a logged-out visitor."}},"plugin_section":[],"plugin_tags":[1912,16114,602,19898,17992],"plugin_category":[38],"plugin_contributors":[274123],"plugin_business_model":[],"class_list":["post-347411","plugin","type-plugin","status-publish","hentry","plugin_tags-access-control","plugin_tags-content-restriction","plugin_tags-login","plugin_tags-members-only","plugin_tags-private-content","plugin_category-authentication","plugin_contributors-rifathasanbd","plugin_committers-rifathasanbd"],"banners":{"banner":"https:\/\/ps.w.org\/easeora-content-access\/assets\/banner-772x250.png?rev=3630730","banner_2x":"https:\/\/ps.w.org\/easeora-content-access\/assets\/banner-1544x500.png?rev=3630730","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/easeora-content-access\/assets\/icon-128x128.png?rev=3630762","icon_2x":"https:\/\/ps.w.org\/easeora-content-access\/assets\/icon-256x256.png?rev=3630762","generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>Easeora Content Access provides focused access control for WordPress websites that need selected pages or posts to be available only to logged-in users.<\/p>\n\n<p>It adds a simple checkbox to each page and post editor, plus a central management screen for applying or removing restrictions in bulk. Logged-out visitors see a configurable message and can be returned to the requested page after signing in.<\/p>\n\n<h4>Core features<\/h4>\n\n<ul>\n<li>Restrict individual pages and posts with one checkbox.<\/li>\n<li>Manage restrictions centrally with search, filters, pagination, bulk controls, and alphabetical ordering.<\/li>\n<li>Customise the restriction title and message with the WordPress editor.<\/li>\n<li>Display an optional WordPress login form.<\/li>\n<li>Return users to the requested page after login.<\/li>\n<li>Exclude restricted content from public search, archives, feeds, comments, REST collections, and supported XML sitemaps.<\/li>\n<li>Add search-engine privacy directives to restricted URLs for logged-out visitors.<\/li>\n<li>Use native WordPress post metadata without custom database tables.<\/li>\n<li>Run without frontend JavaScript, external API calls, cron jobs, or bundled third-party libraries.<\/li>\n<li>Import page and post restrictions from the older Page Restrict plugin when its data is available.<\/li>\n<li>Choose whether the plugin appears as a main dashboard menu or under <strong>Settings &gt; Easeora Content Access<\/strong>.<\/li>\n<\/ul>\n\n<h4>Default visitor message<\/h4>\n\n<pre><code>You are required to login to view this page.\n<\/code><\/pre>\n\n<p>The login link uses the standard WordPress login screen and returns the user to the original page after successful authentication.<\/p>\n\n<h4>Supported placeholders<\/h4>\n\n<ul>\n<li><code>%login_url%<\/code> - the login URL for the requested page.<\/li>\n<li><code>%login%<\/code> - a complete clickable login link.<\/li>\n<li><code>%title%<\/code> - the original page or post title.<\/li>\n<\/ul>\n\n<h4>Privacy<\/h4>\n\n<p>Easeora Content Access does not contact external services, set tracking cookies, collect analytics, or transmit personal data. WordPress handles authentication and the optional login form.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the <code>easeora-content-access<\/code> folder to <code>\/wp-content\/plugins\/<\/code>, or install the plugin through <strong>Plugins &gt; Add New<\/strong>.<\/li>\n<li>Activate <strong>Easeora Content Access<\/strong>.<\/li>\n<li>Edit a page or post and select <strong>Restrict this content to logged-in users<\/strong>.<\/li>\n<li>For bulk management, open <strong>Easeora Content Access &gt; Restricted Content<\/strong>.<\/li>\n<li>Configure the visitor message under <strong>Easeora Content Access &gt; General Options<\/strong>.<\/li>\n<li>Clear any page, server, or CDN cache after changing restrictions.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"who%20can%20view%20restricted%20content%3F\"><h3>Who can view restricted content?<\/h3><\/dt>\n<dd><p>Any authenticated WordPress user can view content marked as restricted. Logged-out visitors receive the configured restriction message.<\/p><\/dd>\n<dt id=\"can%20i%20restrict%20several%20pages%20at%20once%3F\"><h3>Can I restrict several pages at once?<\/h3><\/dt>\n<dd><p>Yes. Open <strong>Easeora Content Access &gt; Restricted Content<\/strong>, select the required pages or posts, and save the visible restrictions.<\/p><\/dd>\n<dt id=\"can%20i%20customise%20the%20login%20message%3F\"><h3>Can I customise the login message?<\/h3><\/dt>\n<dd><p>Yes. The restriction title, rich-text message, and optional login form can be configured under <strong>Easeora Content Access &gt; General Options<\/strong>.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20redirect%20users%20back%20after%20login%3F\"><h3>Does the plugin redirect users back after login?<\/h3><\/dt>\n<dd><p>Yes. Login links and the optional login form can return visitors to the restricted page they originally requested.<\/p><\/dd>\n<dt id=\"does%20this%20plugin%20create%20custom%20database%20tables%3F\"><h3>Does this plugin create custom database tables?<\/h3><\/dt>\n<dd><p>No. Restrictions are stored with native WordPress post metadata and plugin options.<\/p><\/dd>\n<dt id=\"does%20it%20load%20javascript%20on%20the%20frontend%3F\"><h3>Does it load JavaScript on the frontend?<\/h3><\/dt>\n<dd><p>No. Easeora Content Access does not enqueue frontend JavaScript or contact external APIs.<\/p><\/dd>\n<dt id=\"what%20happens%20if%20i%20deactivate%20the%20plugin%3F\"><h3>What happens if I deactivate the plugin?<\/h3><\/dt>\n<dd><p>The restriction logic stops running, so the content becomes publicly accessible. Existing plugin settings and restriction metadata remain stored unless the plugin is uninstalled.<\/p><\/dd>\n<dt id=\"can%20i%20import%20settings%20from%20page%20restrict%3F\"><h3>Can I import settings from Page Restrict?<\/h3><\/dt>\n<dd><p>When compatible Page Restrict data is detected, use <strong>Easeora Content Access &gt; Tools &gt; Import old restrictions<\/strong>. Test the import on a staging website before removing the old plugin.<\/p><\/dd>\n<dt id=\"will%20already%20indexed%20pages%20disappear%20from%20search%20immediately%3F\"><h3>Will already indexed pages disappear from search immediately?<\/h3><\/dt>\n<dd><p>Search engines must recrawl a URL before processing updated directives. Existing search results may remain temporarily. Use the search engine's webmaster tools when urgent removal is required.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.4.2<\/h4>\n\n<ul>\n<li>Redesigned the restriction manager pagination with a clear left-aligned WordPress-style layout.<\/li>\n<li>Shows a five-page navigation window with Previous and Next controls.<\/li>\n<li>Added a page summary and improved keyboard and screen-reader accessibility.<\/li>\n<\/ul>\n\n<h4>1.4.1<\/h4>\n\n<ul>\n<li>Fixed pagination links displaying vertically on the central restriction manager.<\/li>\n<li>Added responsive, scoped administration pagination styling.<\/li>\n<li>Improved pagination markup and accessibility labels.<\/li>\n<\/ul>\n\n<h4>1.4.0<\/h4>\n\n<ul>\n<li>Added the <code>easeora_menu_location<\/code> setting.<\/li>\n<li>Added a General Options control to place the plugin in the main dashboard menu or under WordPress Settings.<\/li>\n<li>Added shared navigation so all plugin screens remain accessible in either location.<\/li>\n<\/ul>\n\n<h4>1.3.0<\/h4>\n\n<ul>\n<li>Renamed the plugin to Easeora Content Access with the new easeora-content-access slug and text domain.<\/li>\n<li>Added migration from previous User Restrict and Boardwalk identifiers.<\/li>\n<li>Escaped the replacement title returned by the title filter.<\/li>\n<li>Retained the existing access, search, REST, sitemap, cache, and bulk-management protections.<\/li>\n<\/ul>\n\n<h4>1.2.1<\/h4>\n\n<ul>\n<li>Added translator comments for placeholder strings.<\/li>\n<li>Removed the discouraged manual translation loader for WordPress.org hosting.<\/li>\n<li>Documented justified cached post exclusions for Plugin Check.<\/li>\n<\/ul>\n\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>Prepared the plugin metadata and readme for WordPress.org submission.<\/li>\n<li>Added current compatibility information for WordPress 7.0.<\/li>\n<li>Added clearer installation, privacy, FAQ, and usage documentation.<\/li>\n<li>Updated the public author name.<\/li>\n<li>Retained the existing security, migration, performance, REST, search, feed, and sitemap protections.<\/li>\n<\/ul>\n\n<h4>1.1.1<\/h4>\n\n<ul>\n<li>Renamed the plugin folder, main file, classes, hooks, options, metadata keys, CSS identifiers, and text domain to Easeora Content Access naming.<\/li>\n<li>Added a one-time migration for settings and restrictions stored under the previous internal identifiers.<\/li>\n<\/ul>\n\n<h4>1.0.6<\/h4>\n\n<ul>\n<li>Added configurable restriction title, rich-text message, optional login form, placeholders, and alphabetical content ordering.<\/li>\n<\/ul>\n\n<h4>1.0.5<\/h4>\n\n<ul>\n<li>Removed metadata query parameters from the restriction-index rebuild and used normal paginated WordPress queries.<\/li>\n<\/ul>\n\n<h4>1.0.4<\/h4>\n\n<ul>\n<li>Removed direct database queries and strengthened direct-file-access protection.<\/li>\n<\/ul>\n\n<h4>1.0.3<\/h4>\n\n<ul>\n<li>Restored WordPress default object-cache priming in the administration manager.<\/li>\n<\/ul>\n\n<h4>1.0.2<\/h4>\n\n<ul>\n<li>Added uninstall cleanup, licensing, translation loading, accessible labels, request validation, and a cached restriction index.<\/li>\n<\/ul>\n\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>Added search-engine privacy headers, generic restricted titles, and supported SEO schema filtering.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release.<\/li>\n<\/ul>","raw_excerpt":"Restrict selected pages and posts to logged-in users with a lightweight central manager, custom login message, and search-safe protection.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/347411","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=347411"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/rifathasanbd"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=347411"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=347411"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=347411"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=347411"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=347411"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=347411"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}