oOMF!

<p>oOMF! Access gives WordPress sites a better front door: a polished login page, guided account flows, passwordless magic links, social sign-in, safe redirects, CAPTCHA, hide-admin controls, honeypots, throttling, and lockout protection.</p>
<p>It is built for agencies, membership sites, product teams, and site owners who want a professional sign-in experience without hand-rolling templates, OAuth plumbing, redirect rules, and abuse controls for every project.</p>
<h4>Why teams use it</h4>
<ul>
<li><strong>A login page worth sharing</strong> – replace the default WordPress screen with a branded page powered by <code>[oomf_access_form]</code>, theme-aware styling, logo controls, custom copy, gradients, and live admin previews.</li>
<li><strong>One flow for every access moment</strong> – keep login, registration, lost password, password reset, logged-in states, and magic-link requests inside the same consistent interface.</li>
<li><strong>Passwordless and social sign-in</strong> – offer email magic links plus Google, Apple, GitHub, Microsoft, and Facebook providers with provider-specific setup hints.</li>
<li><strong>Redirects you can trust</strong> – send people to the right page after login/logout while validating <code>redirect_to</code> values and exposing filters for approved external hosts.</li>
<li><strong>Layered anti-abuse controls</strong> – enable reCAPTCHA, hCaptcha, honeypots, soft throttling, lockouts, secret login paths, and emergency bypass flows from wp-admin.</li>
<li><strong>Developer-friendly internals</strong> – focused hooks and filters let you customize destinations, CAPTCHA behavior, provider handling, inline CSS, and allowed redirect hosts.</li>
</ul>
<h4>Built for the real WordPress admin</h4>
<p>The settings screen includes a live preview, grouped controls for content/appearance/behavior/security, provider previews, and setup copy for external services. Frontend and admin assets load only where needed and are versioned with <code>filemtime()</code>.</p>
<h3>Privacy</h3>
<p>oOMF! Access does not send data to oOMF! services. CAPTCHA and social login features connect only when you enable them and provide your own third-party credentials. Removing the plugin deletes its settings, and the generated login page can also be removed via the <code>oomf_access/delete_page_on_uninstall</code> filter.</p>
<h3>External services</h3>
<p>oOMF! Access connects to outside services only when the related feature is enabled.</p>
<h4>Google reCAPTCHA (v2/v3)</h4>
<ul>
<li>Purpose: spam and abuse protection for access forms.</li>
<li>Endpoints: <code>https://www.google.com/recaptcha/api.js</code> and <code>https://www.google.com/recaptcha/api/siteverify</code>.</li>
<li>Data sent: site key/secret, visitor response token, action name, and optionally visitor IP.</li>
<li>Terms: https://policies.google.com/terms</li>
<li>Privacy: https://policies.google.com/privacy</li>
</ul>
<h4>hCaptcha</h4>
<ul>
<li>Purpose: CAPTCHA validation.</li>
<li>Endpoints: <code>https://js.hcaptcha.com</code> and <code>https://hcaptcha.com/siteverify</code>.</li>
<li>Data sent: site key/secret, response token, action name, and optionally visitor IP.</li>
<li>Terms: https://www.hcaptcha.com/terms</li>
<li>Privacy: https://www.hcaptcha.com/privacy</li>
</ul>
<h4>Google OAuth</h4>
<ul>
<li>Purpose: sign in with Google.</li>
<li>Endpoints: <code>accounts.google.com/o/oauth2/v2/auth</code>, <code>oauth2.googleapis.com/token</code>, and <code>openidconnect.googleapis.com/v1/userinfo</code>.</li>
<li>Data sent: authorization code, code verifier, redirect URI, client credentials, and selected scopes. Returned data can include name, verified email, avatar, and locale.</li>
<li>Terms: https://policies.google.com/terms</li>
<li>Privacy: https://policies.google.com/privacy</li>
</ul>
<h4>Apple Sign In</h4>
<ul>
<li>Purpose: sign in with Apple.</li>
<li>Endpoints: <code>appleid.apple.com/auth/authorize</code> and <code>appleid.apple.com/auth/token</code>.</li>
<li>Data sent: authorization code, client ID, redirect URI, and signed JWT assertions generated from your Apple key. Returned data can include name and email.</li>
<li>Terms: https://www.apple.com/legal/internet-services/terms/site.html</li>
<li>Privacy: https://www.apple.com/legal/privacy/</li>
</ul>
<h4>GitHub OAuth</h4>
<ul>
<li>Purpose: sign in with GitHub.</li>
<li>Endpoints: <code>github.com/login/oauth/authorize</code>, <code>github.com/login/oauth/access_token</code>, <code>api.github.com/user</code>, and <code>api.github.com/user/emails</code>.</li>
<li>Data sent: authorization code, client credentials, redirect URI, and scopes. Returned data can include ID, email, name, and avatar.</li>
<li>Terms: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service</li>
<li>Privacy: https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement</li>
</ul>
<h4>Microsoft OAuth</h4>
<ul>
<li>Purpose: sign in with Microsoft.</li>
<li>Endpoints: <code>login.microsoftonline.com/common/oauth2/v2.0/authorize</code>, <code>login.microsoftonline.com/common/oauth2/v2.0/token</code>, and <code>graph.microsoft.com/v1.0/me</code>.</li>
<li>Data sent: authorization code, client credentials, redirect URI, and scopes. Returned data can include ID, email, name, and locale.</li>
<li>Terms: https://www.microsoft.com/licensing/terms/productoffering/MicrosoftOnlineServices/MOSPT</li>
<li>Privacy: https://privacy.microsoft.com/privacystatement</li>
</ul>
<h4>Facebook Login</h4>
<ul>
<li>Purpose: sign in with Facebook.</li>
<li>Endpoints: <code>facebook.com/v18.0/dialog/oauth</code>, <code>graph.facebook.com/v18.0/oauth/access_token</code>, and <code>graph.facebook.com/v18.0/me</code>.</li>
<li>Data sent: authorization code, app credentials, redirect URI, and scopes. Returned data can include ID, email, name, and avatar.</li>
<li>Terms: https://www.facebook.com/legal/terms</li>
<li>Privacy: https://www.facebook.com/policy.php</li>
</ul>
<h3>Hooks & Extension Points</h3>
<ul>
<li><code>oomf_access_redirect_destination</code> – override the final destination after login.</li>
<li><code>oomf-access/allowed_redirect_hosts</code> – allow approved external redirect hosts.</li>
<li><code>oomf-access/captcha/allow_external</code> – control whether CAPTCHA network calls are allowed.</li>
<li><code>oomf_access_captcha_is_required</code> – decide whether CAPTCHA is required for a request.</li>
<li><code>oomf_access_captcha_validate_result</code> – customize CAPTCHA validation results.</li>
<li><code>oomf-access/inline_css</code> – inject extra CSS into the admin preview and frontend.</li>
</ul>


oOMF! Access

Turn the default WordPress login into a branded, passwordless, social-ready access hub with redirects and layered anti-abuse controls.

Sami Ahmed Siddiqui

Aliya Yasir

<p><strong>Permalinks Customizer</strong> helps you to set the different permalink structure for different PostTypes and Taxonomies which are publicly available.</p>
<p>You can use the tags which are defined by the WordPress as mentioned <a href="https://github.com/yasglobal/permalinks-customizer#default-tags-for-posttypes" rel="nofollow ugc">here</a>. Also, you can use the tags which are customily defined by this plugin for <a href="https://github.com/yasglobal/permalinks-customizer#custom-tags-for-posttypes" rel="nofollow ugc">PostTypes</a> and <a href="https://github.com/yasglobal/permalinks-customizer#custom-tags-for-taxonomies" rel="nofollow ugc">Taxonomies</a>. You can also find these tags in Permalinks Customizer menu on WordPress Dashboard (if the plugin is installed).</p>
<h3>How to set the Permalinks for different PostTypes</h3>
<p>Let’s assume that you have 6 <strong>PostTypes</strong> and you like to apply differnet <strong>permalink</strong> structure for them. Like:</p>
<ol>
<li><strong>Blog :</strong> For this post type you want to create a <strong>permalink</strong> which looks like this: http://www.example.com/blog/year-month-date-postname/</li>
<li><strong>Customers :</strong> For this post type you want to create a <strong>permalink</strong> which looks like this: http://www.example.com/customers/postname/</li>
<li><strong>Events :</strong> For this post type you want to create a <strong>permalink</strong> which looks like this: http://www.example.com/events/year-month-date-postname/</li>
<li><strong>Press :</strong> For this post type you want to create a <strong>permalink</strong> which looks like this: http://www.example.com/press/category/year/postname/</li>
<li><strong>News :</strong> For this post type you want to create a <strong>permalink</strong> which looks like this: http://www.example.com/news/year/postname/</li>
<li><strong>Sponsors :</strong> For this post type you want to create a <strong>permalink</strong> which looks like this: http://www.example.com/company/sponsor/post_title/</li>
</ol>
<p>This plugin allows you to do this very easily. You just need to go on <strong>Permalinks Customizer</strong> Settings Page. Where text fields are shown with PostType name. You can define your permalinks you want to create for each post type.</p>
<p>If you leave any PostType field empty, <strong>Permalinks Customizer</strong> will create a permalink for that PostType by using the default <strong>permalink</strong> settings.</p>
<h3>How to Configure Permalinks Customizer</h3>
<p>You can configure the plugin by navigating to the <code>Permalinks Customizer</code> menu from the WordPress Dashboard</p>
<h3>Structure Tags</h3>
<p>You can find all the tags which are currently supported by the <code>Permalinks Customizer</code>.</p>
<h3>Default Tags for PostTypes</h3>
<p>Below mentioned tags are provided by the <code>WordPress</code>. These tags can be used on Default <code>WordPress Permalink</code> Settings Page as well as <code>Permalinks Customizer</code> Settings page.</p>
<ol>
<li><code>%year%</code>:  The year of the post, four digits, for example 2019</li>
<li><code>%monthnum%</code>: Month of the year, for example 01</li>
<li><code>%day%</code>: Day of the month, for example 02</li>
<li><code>%hour%</code>: Hour of the day, for example 15</li>
<li><code>%minute%</code>: Minute of the hour, for example 43</li>
<li><code>%second%</code>: Second of the minute, for example 33</li>
<li><code>%post_id%</code>: The unique ID of the post, for example 123</li>
<li><code>%postname%</code>: A sanitized version of the title of the post (post slug field on Edit Post/Page panel). So “This Is A Great Post!” becomes this-is-a-great-post in the URI.</li>
<li><code>%category%</code>: A sanitized version of the category name (category slug field on New/Edit Category panel). Nested sub-categories appear as nested directories in the URI.</li>
<li><code>%author%</code>: A sanitized version of the author name.</li>
</ol>
<h3>Custom Tags for PostTypes</h3>
<p>Below mentioned tags are provided by the <code>Permalinks Customizer</code> for PostTypes. These tags can not be used on the Default <code>WordPress Permalink</code> Settings Page.</p>
<ol>
<li><code>%title%</code>: Title of the post. let’s say the title is “This Is A Great Post!” so, it becomes this-is-a-great-post in the URI.</li>
<li><code>%parent_title%</code>: This tag is similar as <code>%title%</code>.<br />Only the difference is that it appends the immediate <strong>Parent Page Title</strong> in the URI if any parent page is selected.</li>
<li><code>%all_parents_title%</code>: This tag is similar as <code>%title%</code>.<br />Only the difference is that it appends all the <strong>Parents Page Title</strong> in the URI if any parent page is selected.</li>
<li><code>%parent_postname%</code>: This tag is similar as <code>%postname%</code>.<br />Only difference is that it appends the immediate <strong>Parent Page Slug</strong> if any parent page is selected.</li>
<li><code>%all_parents_postname%</code>: This tag is similar as <code>%postname%</code>.<br />Only the difference is that it appends all the <strong>Parents Page Slug</strong> in the URI if any parent page is selected.</li>
<li><code>%child-category%</code>: A sanitized version of the category name (category slug field on New/Edit Category panel).</li>
<li><code>%product_cat%</code>: A sanitized version of the product category name (category slug field on New/Edit Category panel). Nested sub-categories appear as nested directories in the URI.
<p> <em>This <code>tag</code> is specially used in WooCommerce Products.</em></li>
<li><code><%ctax_custom_taxonomy%></code>: A sanitized version of the custom taxonomy where the taxonomy name is <code>custom_taxonomy</code>. Replace the <code>custom_taxonomy</code> with your appropriate created taxonomy name.
<p> If you want to provide the default slug which is used when the category/taxonomy doesn’t be selected so, make sure to provide default name/slug which looks like this: <code><%ctax_custom_taxonomy??sales%></code>. Value which is written between the <code>??</code> and <code>%></code> is used as default slug.</li>
<li><code><%ctaxparents_custom_taxonomy%></code>: This tag is similar as <code><%ctax_custom_taxonomy%></code>.<br />Only the difference is that it appends all the <strong>Parents Slug</strong> in the URI if any parent Term/Category is selected.</li>
<li><code>%author_firstname%</code>: A sanitized version of the author first name. If author first name is not available then it uses the author’s username.</li>
<li><code>%author_lastname%</code>: A sanitized version of the author last name. If author last name is not available then it uses the author’s username.</li>
</ol>
<p><strong>Note</strong>: <code>%title%</code> is similar as <code>%postname%</code> tag but the difference is that <code>%postname%</code> can only be set once by WordPress whereas <code>%title%</code> can be changed by user at multiple times. let’s say the title is “This Is A Great Post!” so, it becomes “this-is-a-great-post” in the URI(At the first time, <code>%postname%</code> and <code>%title%</code> works same) but if you edit and change title let’s say “This Is A WordPress Post!” so, <code>%postname%</code> in the URI remains same “this-is-a-great-post” whereas <code>%title%</code> in the URI becomes “this-is-a-wordpress-post”</p>
<h3>Custom Tags for Taxonomies</h3>
<p>Below mentioned tags are provided by the <code>Permalinks Customizer</code> for Taxonomies. These can not be used on the Default <code>WordPress Permalink</code> Settings Page.</p>
<ol>
<li><code>%name%</code>: Name of the Term/Category. let’s say the name is “External API” so, it becomes external-api in the URI.</li>
<li><code>%term_id%</code>: The unique ID # of the Term/Category, for example 423</li>
<li><code>%slug%</code>: A sanitized version of the name of the Term/Category. So “External API” becomes external-api in the URI.</li>
<li><code>%parent_slug%</code>: This tag is similar as <code>%slug%</code>.
<p> Only the difference is that it appends the immediate <strong>Parent Term/Category Slug</strong> in the URI if any parent Term/Category is selected.</li>
<li><code>%all_parents_slug%</code>: This tag is similar as <code>%slug%</code>.
<p> Only the difference is that it appends all the <strong>Parent Terms/Category Slugs</strong> in the URI if any parent Term/Category is selected.</li>
</ol>
<h3>Filters</h3>
<p>You can find all the filters below which are provided by <code>Permalinks Customizer</code> plugin. These filters can be used as per your Website requirement.</p>
<h3>Exclude Permalinks</h3>
<p>If you want to exclude some Permalink to processed with the plugin so, just add the filter looks like this:</p>
<pre><code>function yasglobal_exclude_url( $permalink ) {
  if ( false !== strpos( $permalink, '/contact-us/' ) ) {
    return '__true';
  }
  return;
}
add_filter( 'permalinks_customizer_exclude_request', 'yasglobal_exclude_url' );
</code></pre>
<h3>Show Relative Permalink/URL</h3>
<p>To show relative permalink/url in Edit Post, add this filter in your themes <code>functions.php</code>.s</p>
<pre><code>add_filter( 'permalinks_customizer_remove_home_url', '__return_true' );
</code></pre>
<h3>Exclude PostType from the Plugin</h3>
<p>To exclude the plugin to be worked on any PostType. Add this filter in your themes <code>functions.php</code>.</p>
<pre><code>function yasglobal_exclude_post_types( $post_type ) {
  if ( $post_type == 'page' ) {
    return '__true';
  }
  return '__false';
}
add_filter( 'permalinks_customizer_exclude_post_type', 'yasglobal_exclude_post_types');
</code></pre>
<p><strong>Note</strong>: Plugin stops working on the backend. <em>No more permalinks</em> would be generated by the plugin but the permalink which are already created will remains in work.</p>
<h3>Disable automatically create redirects</h3>
<p>To disable automatically create redirects feature on creating and updating the post/pages/categories, add this filter in your themes functions.php.</p>
<pre><code>add_filter( 'permalinks_customizer_auto_created_redirects', '__return_false');
</code></pre>
<p>This filter stops to be creating new redirects but existed redirects keeps working. To stop existed redirects, add <code>permalinks_customizer_disable_redirects</code> filter.</p>
<h3>Disable Redirects</h3>
<p>To disable redirects to be applied , add this filter in your themes functions.php.</p>
<pre><code>add_filter( 'permalinks_customizer_disable_redirects', '__return_false');
</code></pre>
<p>This filter only stop redirects to be work but the automatically create redirects still works. To stop automatically create redirects feature add <code>permalinks_customizer_auto_created_redirects</code> filter.</p>
<h3>Bug reports</h3>
<p>Bug reports for Permalinks Customizer are <a href="https://github.com/yasglobal/permalinks-customizer" rel="nofollow ugc">welcomed on GitHub</a>. Please note GitHub is not a support forum, and issues that aren’t properly qualified as bugs will be closed.</p>


Permalinks Customizer

Does not work

This plugin should be on top and deserves more downloads than the plugins which do not work for WooCommerce Taxonomies/Categories.

Thanks!

The only free plugin which works

Permalinks Customizer helps you to set the different permalink structure for different PostTypes and Taxonomies which are publicly available.

oOMF! Access vs Permalinks Customizer