Force Customer Login Module for Magento 2

Overview

Force Login Module for Magento® 2

Build Status Coverage Status

The Force Login Module for Magento® 2 allows you to restrict which pages a visitor is able to see. Visitors get redirected to the login page if the page is not marked visitable. The Force Login Module for Magento® 2 is especially useful for merchants serving only a specific group of users, e.g. enterprise related business partners and need to ensure that only those users are able to browse the the website or the product catalog.

Features:

  • Force your guest visitors to log in first (or register), before allowing them to visit your pages and catalog
  • Administration: Manage the whitelist rules by the GUI in the administration area
  • ACL: Restrict the administration of whitelist rules to certain backend user groups
  • Whitelisting: Define url rules as pattern to define which pages guest visitors can visit without logging in first
  • Multistore-Support: Define if whitelist rules either apply globally or for specific stores

Installation

The preferred way of installing bitexpert/magento2-force-customer-login is through Composer. Simply add bitexpert/magento2-force-customer-login as a dependency:

composer.phar require bitexpert/magento2-force-customer-login

Optional you can download the latest version here and install the decompressed code in your projects directory under app/code/BitExpert/ForceCustomerLogin.

Post-Install

After the installment of the module source code, the module has to be enabled by the Magento® 2 CLI.

bin/magento module:enable BitExpert_ForceCustomerLogin

System Upgrade

After enabling the module, the Magento® 2 system must be upgraded.

If the system mode is set to production, run the compile command first. This is not necessary for the developer mode.

bin/magento setup:di:compile

To upgrade the system, the upgrade command must be run.

bin/magento setup:upgrade

Clear Cache

At last, the Magento® 2 should be cleared by running the flush command.

bin/magento cache:flush

Sometimes, other cache systems or services must be restarted first, e.g. Apache Webserver and PHP FPM.

User Guide

Find the complete user guide here.

How to use

The usage of the Force Login Module for Magento® 2 is applied implicitly by redirecting visitors if the called URI does not match any configured whitelisted url rules.

Whitelisting

Whitelisting is based upon the usage of rules. The strategy selection defines how the rules are interpreted, details are listed below. By default, some static rules are already listed. The following example shows, how to add a whitelist entry for the homepage (startpage).

Navigate to the Overview Grid and use the Add Entry button.

  • Enter Homepage into the text field beside from the Label label.
  • Enter ^/?$ into the text field beside from the Url Rule label.
  • Select All Stores from the selection field beside from the Store label.

Use the Save button in the upper menu. After being redirected to the Overview Grid, the new entry should appear to the list and the systems homepage should be available for guest visitors.

How to configure

Administration

The Force Login Module for Magento® 2 allows you to enable or disable the module itself on the level of websites, stores and store views.

If the module is disabled, the whitelist ruling and the redirection are not applied. If the module is enabled based upon the configuration, the whitelist rules are process, which themselves are also configurable for all enabled stores or just specific ones.

After installing and enabling Force Login Module for Magento® 2 with the CLI, you must be able to navigate to Stores > Configuration > Force Login, where you are able to configure the availability of the module for each website, store and store view.

In the administration configuration, you are also able to setup the URL the redirecting is targeting to if not whitelist rule is matching.

alt text

Navigation

Navigating through the Magento® 2 backend menu by clicking onto Customers you must see a new menu entry Forced Login Whitelist.

Enter this menu entry.

alt text

Overview Grid

You can add new entries by clicking on the Add Entry button in the upper right corner ( 1 ), see below. The grid ( 2 ) contains all existing whitelisted Url Rules, for which the forced redirect to the Customer Login Page is omitted. The Url Rules ( 3 ) are part of a regular expression checking on the called Url and tries to match against the whitelist. Url Rules may be related to all stores or to a specific one ( 4 ). All rules except some mandatory ones are editable ( 5 ) and removeable ( 6 ).

alt text

Detail Form

You can return to the Overview Grid by using the Back button ( 1 ). The Label value has only declarative character and is for information purpose only ( 2 ). The Url Rule is an expression checking on the called Url and tries to match against the whitelist ( 3 ). Url Rules may be related to all stores or to a specific one ( 4 ). The strategy selection ( 5 ) defines how the Url Rule is interpreted, details are listed below. Persist the rule by using the Save button ( 6 ).

alt text

Strategies

Static

Rule is used as a literal value and will be added onto the base url for matching. This is default behaviour.

RegEx-All

Rule is based on regular expression, and will be used for looking up matching anywhere in the current Url.

RegEx-All Negation

Based on the RegEx-All strategy, but negates the result. Helpful if only a few pages should be restricted.

Tests

You can run the unit tests with the following command (requires dependency installation):

composer test

Contribution

Feel free to contribute to this module by reporting issues or create some pull requests for improvements.

License

The Force Login Module for Magento® 2 is released under the Apache 2.0 license.

Comments
  • Password Reset not working

    Password Reset not working

    Preconditions

    Magento Version :CE 2.3.2

    Force Login Module Version :3.2.0

    Third party modules :

    Steps to reproduce

    1.Request a password reset, click on the password reset link xxx.com/it/customer/account/createPassword/?token=XXXXXXXXXXXX 2. 3.

    Expected result

    1. After clicking on the link, the reset page should appear xxx.com/it/customer/account/createpassword/

    Actual result

    1. The page remains on xxx.com/it/customer/account/createPassword/?token=XXXXXXXXXXXX and I give this error "This page does not redirect correctly" Immagine
    bug 
    opened by thelogh 21
  • Homepage Redirect After Login Leads To incorrect url

    Homepage Redirect After Login Leads To incorrect url

    When I have your plugin enabled using a store with force log in set, after I successfully login in it takes me to:

    "[store]/customer/section/load/?sections=cart&force_new_section_timestamp=false&_=1586875817856"

    instead of to the homepage.

    For stores without forced login enabled there is no problem and I am redirected to the homepage on login.

    Once I have logged in and it takes me to the wrong url, I can go to the homepage with no problem.

    Any ideas?

    Magento 2: 2.3.1 Plugin: 4.0.2

    Installed manually from github.

    opened by chackem 15
  • Customers get whoops.... after registering

    Customers get whoops.... after registering

    Has anyone had any issues with customers getting the "whoops, our bad..." page not found error after registering for a account? It seems like the redirect that is done by default from magento isnt executing when the extension is enabled. If I turn it off the registering works.

    Magento ver. 2.3.3 CE Force Login Module Version : 4.0.2 Third party modules : Magezon_PageBuilder Mageplaza_CustomerApproval

    Steps to reproduce

    1. Go to account register page and register
    2. click register

    Expected result

    1. To be redirected back to the customer login page ( customer/account/login )

    Actual result

    1. Get error "whoops, our bad" error page image
    opened by mastrip2 15
  • Redirect to homepage after entering wrong User password

    Redirect to homepage after entering wrong User password

    Hi guys

    Use case: Login to user account" /customer/account/login/ "After entering the wrong pw you get a redirect to the homepage and the default error message here

    Expected result: Stick on the same page (" /customer/account/login/) and get the error message here to retry.

    We have installed 2.2.4 on nginx server and default Whitelist rules only. Disable Module in Backend doesnt change anything. We have to disable the plugin via command line to get the usual expected result.

    Any ideas to solve it or what might cause the issue? Thanks Björn

    opened by Bmacuser1 14
  • Support for Magento 2.3

    Support for Magento 2.3

    Support for Magento 2.3

    Preconditions

    PHP version : 7.2.13 Magento Version : 2.3 CE Force Login Module Version : 3.1.0 Third party modules : None

    Steps to reproduce

    1. composer require bitexpert/magento2-force-customer-login

    Expected result

    1. It should install bitexpert/magento2-force-customer-login

    Actual result

    Your requirements could not be resolved to an installable set of packages.
    
      Problem 1
        - Installation request for magento/product-community-edition 2.3.0 -> satisfiable by magento/product-community-edition[2.3.0].
        - bitexpert/magento2-force-customer-login 3.1.0 requires magento/module-customer ~100.1|~101.0 -> satisfiable by magento/module-customer[100.1.0, 100.1.1, 100.1.2, 100.1.3, 100.1.4, 100.1.5, 100.1.6, 100.1.7, 100.1.8, 101.0.0, 101.0.1, 100.1.9, 100.1.10, 101.0.2, 100.1.11, 101.0.3, 100.1.12, 101.0.4, 101.0.5, 100.1.13, 100.1.14, 101.0.6, 100.1.15, 101.0.7].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.0].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.1].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.2].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.3].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.4].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.5].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.6].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.7].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.8].
        - Can only install one of: magento/module-customer[102.0.0, 101.0.0].
        - Can only install one of: magento/module-customer[102.0.0, 101.0.1].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.9].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.10].
        - Can only install one of: magento/module-customer[102.0.0, 101.0.2].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.11].
        - Can only install one of: magento/module-customer[102.0.0, 101.0.3].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.12].
        - Can only install one of: magento/module-customer[102.0.0, 101.0.4].
        - Can only install one of: magento/module-customer[102.0.0, 101.0.5].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.13].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.14].
        - Can only install one of: magento/module-customer[102.0.0, 101.0.6].
        - Can only install one of: magento/module-customer[102.0.0, 100.1.15].
        - Can only install one of: magento/module-customer[102.0.0, 101.0.7].
        - magento/product-community-edition 2.3.0 requires magento/module-customer 102.0.0 -> satisfiable by magento/module-customer[102.0.0].
        - Installation request for bitexpert/magento2-force-customer-login ^3.1 -> satisfiable by bitexpert/magento2-force-customer-login[3.1.0].
    
    opened by lracicot 13
  • Account Login Via API still redirects to customer force sign in page

    Account Login Via API still redirects to customer force sign in page

    I am logging in customers through a third party portal. It uses the Magento API. Without activating the force login plugin customers can login to the website via the portal fine and will auto login the customer to the magento login page. However when I activate the plugin and my customer's login through the portal, they are redirected to the website but are forced to the login page again. I looked at the whitelist rules and added all the urls I think would be e.g the link that should work is /companyaccount/api/login?email=name%40domain.com&&token=tokennumber so I added the following rules to the whitelist: /companyaccount /companyaccount/api /companyaccount/api/login even: /customer/account/login/referer

    but no luck,

    Im using magento 2.2.5

    does this plugin support the magento api for customers to login and if not how can we get this to work

    Thanks in advance

    opened by michaelfigg 12
  • Use with a SAML extention

    Use with a SAML extention

    This is not an issue. I'm trying to reach out to the developer about getting this to work with a saml module we are using. We seem to be able to login with SAML when the module is turned off, but when we enable the module we get an "Invalid Form Key" error on the login page. I assume there is a path i need to whitelist, and probably more customization than that to get this to work. Any help is appreciated.

    Magento Version : 2.3.1

    Force Login Module Version :3.0.4

    Third party modules :https://marketplace.magento.com/sixtomartin-onelogin-module-saml2.html

    We are happy to pay for custom dev.

    opened by oobehub 11
  • Invalid system.xml file

    Invalid system.xml file

    I installed module, run all post-installation commands and when I login to admin page and try to go to Stores-Configurations I get this error: 1 exception(s): Exception #0 (Magento\Framework\Exception\LocalizedException): Invalid XML in file /.../app/code/bitExpert/ForceCustomerLogin/etc/adminhtml/system.xml: Element 'resource': This element is not expected. Line: 7

    opened by jahicDario 11
  • Whitelist Backend not working upon fresh install

    Whitelist Backend not working upon fresh install

    After doing a manual install of this on my Magento 2.1.8 system, I get the following error with my marketplace plugin:

    Incorrect dependency in class Ced\CsMarketplace\Controller\Adminhtml\Vproducts\Vproductgrid in /opt/bitnami/apps/magento/htdocs/app/code/Ced/CsMarketplace/Controller/Adminhtml/Vproducts/Vproductgrid.php \Magento\Framework\App\Response\RedirectInterface already exists in context object Total Errors Count: 1 Interception cache generation... 7/7 [============================] 100% 3 mins 216.0 MiB Generated code and dependency injection configuration successfully.

    However, upon loading the Customers->Whitelist menu I get: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'bitnami_magento.bitexpert_forcelogin_whitelist' doesn't exist, query was: SELECT main_table.* FROM bitexpert_forcelogin_whitelist AS main_table

    Is that right? A full table was not generated during install?

    opened by mikemunevar 9
  • Conflict with extension https://amasty.com/improved-layered-navigation-for-magento-2.html

    Conflict with extension https://amasty.com/improved-layered-navigation-for-magento-2.html

    Hi,

    Can you help us resolved this issue:

    1 exception(s):
    Exception #0 (LogicException): Circular dependency: Magento\Catalog\Model\Layer\Category depends on Magento\Catalog\Model\Layer\Category\StateKey and vice versa.
    
    Exception #0 (LogicException): Circular dependency: Magento\Catalog\Model\Layer\Category depends on Magento\Catalog\Model\Layer\Category\StateKey and vice versa.
    #0 /vendor/magento/framework/ObjectManager/ObjectManager.php(57): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\\Catalog...', Array)
    #1 /vendor/magento/module-catalog/Model/Layer/Resolver.php(70): Magento\Framework\ObjectManager\ObjectManager->create('Magento\\Catalog...')
    #2 /app/code/Amasty/Shopby/Model/Resolver.php(38): Magento\Catalog\Model\Layer\Resolver->get()
    #3 /app/code/Amasty/Shopby/Plugin/RouteParamsResolverPlugin.php(30): Amasty\Shopby\Model\Resolver->get()
    #4 /vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(93): Amasty\Shopby\Plugin\RouteParamsResolverPlugin->__construct(Object(Magento\Catalog\Model\Layer\Resolver), Object(Amasty\Shopby\Model\Resolver), Object(Magento\Framework\Url\QueryParamsResolver), Object(Amasty\Shopby\Model\Request))
    #5 /vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(89): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('Amasty\\Shopby\\P...', Array)
    #6 /vendor/magento/framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Amasty\\Shopby\\P...')
    #7 /vendor/magento/framework/Interception/PluginList/PluginList.php(232): Magento\Framework\ObjectManager\ObjectManager->get('Amasty\\Shopby\\P...')
    #8 /vendor/magento/framework/Interception/Chain/Chain.php(65): Magento\Framework\Interception\PluginList\PluginList->getPlugin('Magento\\Framewo...', 'Amasty_Shopby::...')
    

    Thanks.

    question 
    opened by dungnv 9
  • Not compatible with Magento 2.4.0 Commerce

    Not compatible with Magento 2.4.0 Commerce

    Preconditions

    PHP Version : 7.3.10

    Magento Version : 2.4.0

    Force Login Module Version : v4.0.2

    Third party modules : not relevant for the problem

    Steps to reproduce

    1. update the Magento version in the composer.json to "magento/product-enterprise-edition": "2.4.0"
    2. composer update

    I think there is the same problem for the Magento 2.4.0 Open Source version

    Expected result

    1. no composer dependencies conflicts

    Actual result

    app@3f7cbd9d8cec:~/html/src$ composer update                                         
    Gathering patches for root package.
    Loading composer repositories with package information                                                                                                  Updating dependencies (including require-dev)         
    Your requirements could not be resolved to an installable set of packages.
    
      Problem 1
        - magento/module-store 101.0.0 requires php ~7.1.3||~7.2.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-store 101.0.1 requires php ~7.1.3||~7.2.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-store 101.0.2 requires php ~7.1.3||~7.2.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-store 101.0.2-p2 requires php ~7.1.3||~7.2.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.0 requires php ~5.6.0|7.0.2|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.1 requires php ~5.6.0|7.0.2|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.2 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.3 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.4 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.5 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.6 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.7 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.8 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.0 requires php 7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.1 requires php 7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.9 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.10 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.2 requires php 7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.11 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.3 requires php 7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.12 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.4 requires php 7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.5 requires php ~7.0.13|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.13 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.14 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.6 requires php ~7.0.13|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.15 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.7 requires php ~7.0.13|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 102.0.0 requires php ~7.1.3||~7.2.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.16 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 102.0.1 requires php ~7.1.3||~7.2.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.8 requires php ~7.0.13|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 102.0.2 requires php ~7.1.3||~7.2.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 100.1.17 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.9 requires php ~7.0.13|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.10 requires php ~7.0.13|~7.1.0|~7.2.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 102.0.2-p2 requires php ~7.1.3||~7.2.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - magento/module-customer 101.0.11 requires php ~7.0.13||~7.1.0||~7.2.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 3.2.0 requires magento/module-customer ~100.1|~101.0|~102.0 -> satisfiable by magento/module-customer[102.0.5, 102.0.5-p2, 102.0.4-p2, 102.0.4-p1, 102.0.3-p1, 102.0.4, 101.0.11, 102.0.2-p2, 101.0.10, 102.0.3, 101.0.9, 100.1.17, 102.0.2, 101.0.8, 102.0.1, 100.1.16, 102.0.0, 101.0.7, 100.1.15, 101.0.6, 100.1.14, 100.1.13, 101.0.5, 101.0.4, 100.1.12, 101.0.3, 100.1.11, 101.0.2, 100.1.10, 100.1.9, 101.0.1, 101.0.0, 100.1.8, 100.1.7, 100.1.6, 100.1.5, 100.1.4, 100.1.3, 100.1.2, 100.1.1, 100.1.0].
        - bitexpert/magento2-force-customer-login 3.2.0 requires magento/module-customer ~100.1|~101.0|~102.0 -> satisfiable by magento/module-customer[102.0.5, 102.0.5-p2, 102.0.4-p2, 102.0.4-p1, 102.0.3-p1, 102.0.4, 101.0.11, 102.0.2-p2, 101.0.10, 102.0.3, 101.0.9, 100.1.17, 102.0.2, 101.0.8, 102.0.1, 100.1.16, 102.0.0, 101.0.7, 100.1.15, 101.0.6, 100.1.14, 100.1.13, 101.0.5, 101.0.4, 100.1.12, 101.0.3, 100.1.11, 101.0.2, 100.1.10, 100.1.9, 101.0.1, 101.0.0, 100.1.8, 100.1.7, 100.1.6, 100.1.5, 100.1.4, 100.1.3, 100.1.2, 100.1.1, 100.1.0].
        - bitexpert/magento2-force-customer-login 3.2.0 requires magento/module-customer ~100.1|~101.0|~102.0 -> satisfiable by magento/module-customer[102.0.5, 102.0.5-p2, 102.0.4-p2, 102.0.4-p1, 102.0.3-p1, 102.0.4, 101.0.11, 102.0.2-p2, 101.0.10, 102.0.3, 101.0.9, 100.1.17, 102.0.2, 101.0.8, 102.0.1, 100.1.16, 102.0.0, 101.0.7, 100.1.15, 101.0.6, 100.1.14, 100.1.13, 101.0.5, 101.0.4, 100.1.12, 101.0.3, 100.1.11, 101.0.2, 100.1.10, 100.1.9, 101.0.1, 101.0.0, 100.1.8, 100.1.7, 100.1.6, 100.1.5, 100.1.4, 100.1.3, 100.1.2, 100.1.1, 100.1.0].
        - bitexpert/magento2-force-customer-login 4.0.0 requires magento/module-store ~101.0.0|~101.0.1|~101.0.3 -> satisfiable by magento/module-store[101.0.5, 101.0.4-p2, 101.0.4-p1, 101.0.3-p1, 101.0.4, 101.0.2-p2, 101.0.3, 101.0.2, 101.0.1, 101.0.0].
        - bitexpert/magento2-force-customer-login 4.0.2 requires magento/module-store ~101.0.0|~101.0.1|~101.0.3 -> satisfiable by magento/module-store[101.0.5, 101.0.4-p2, 101.0.4-p1, 101.0.3-p1, 101.0.4, 101.0.2-p2, 101.0.3, 101.0.2, 101.0.1, 101.0.0].
        - bitexpert/magento2-force-customer-login 4.0.0 requires magento/module-store ~101.0.0|~101.0.1|~101.0.3 -> satisfiable by magento/module-store[101.0.5, 101.0.4-p2, 101.0.4-p1, 101.0.3-p1, 101.0.4, 101.0.2-p2, 101.0.3, 101.0.2, 101.0.1, 101.0.0].
        - bitexpert/magento2-force-customer-login 4.0.2 requires magento/module-store ~101.0.0|~101.0.1|~101.0.3 -> satisfiable by magento/module-store[101.0.5, 101.0.4-p2, 101.0.4-p1, 101.0.3-p1, 101.0.4, 101.0.2-p2, 101.0.3, 101.0.2, 101.0.1, 101.0.0].
        - Can only install one of: magento/module-customer[102.0.5-p2, 103.0.0].
        - Can only install one of: magento/module-customer[102.0.4-p2, 103.0.0].
        - Can only install one of: magento/module-customer[102.0.5, 103.0.0].
        - Can only install one of: magento/module-customer[102.0.4-p1, 103.0.0].
        - Can only install one of: magento/module-customer[102.0.3-p1, 103.0.0].
        - Can only install one of: magento/module-customer[102.0.4, 103.0.0].
        - Can only install one of: magento/module-customer[102.0.3, 103.0.0].
        - Can only install one of: magento/module-customer[103.0.0, 102.0.5].
        - Can only install one of: magento/module-store[101.0.4-p2, 101.1.0].
        - Can only install one of: magento/module-store[101.0.5, 101.1.0].
        - Can only install one of: magento/module-store[101.0.4-p1, 101.1.0].
        - Can only install one of: magento/module-store[101.0.3-p1, 101.1.0].
        - Can only install one of: magento/module-store[101.0.4, 101.1.0].
        - Can only install one of: magento/module-store[101.0.3, 101.1.0].
        - Can only install one of: magento/module-store[101.1.0, 101.0.5].
        - magento/module-website-restriction 100.4.0 requires magento/module-customer 103.0.* -> satisfiable by magento/module-customer[103.0.0].
        - magento/module-website-restriction 100.4.0 requires magento/module-store 101.1.* -> satisfiable by magento/module-store[101.1.0].
        - magento/product-enterprise-edition 2.4.0 requires magento/module-website-restriction 100.4.0 -> satisfiable by magento/module-website-restriction[100.4.0].
        - bitexpert/magento2-force-customer-login 2.2.0 requires magento/module-customer ~101.0 -> satisfiable by magento/module-customer[101.0.11, 101.0.10, 101.0.9, 101.0.8, 101.0.7, 101.0.6, 101.0.5, 101.0.4, 101.0.3, 101.0.2, 101.0.1, 101.0.0].
        - bitexpert/magento2-force-customer-login 2.3.0 requires magento/module-customer ~101.0 -> satisfiable by magento/module-customer[101.0.11, 101.0.10, 101.0.9, 101.0.8, 101.0.7, 101.0.6, 101.0.5, 101.0.4, 101.0.3, 101.0.2, 101.0.1, 101.0.0].
        - bitexpert/magento2-force-customer-login v3.0.0 requires magento/module-customer ~101.0 -> satisfiable by magento/module-customer[101.0.11, 101.0.10, 101.0.9, 101.0.8, 101.0.7, 101.0.6, 101.0.5, 101.0.4, 101.0.3, 101.0.2, 101.0.1, 101.0.0].
        - bitexpert/magento2-force-customer-login 3.0.0 requires magento/module-customer ~101.0 -> satisfiable by magento/module-customer[101.0.11, 101.0.10, 101.0.9, 101.0.8, 101.0.7, 101.0.6, 101.0.5, 101.0.4, 101.0.3, 101.0.2, 101.0.1, 101.0.0].
        - bitexpert/magento2-force-customer-login 2.2.0 requires magento/module-customer ~101.0 -> satisfiable by magento/module-customer[101.0.11, 101.0.10, 101.0.9, 101.0.8, 101.0.7, 101.0.6, 101.0.5, 101.0.4, 101.0.3, 101.0.2, 101.0.1, 101.0.0].
        - bitexpert/magento2-force-customer-login 2.3.0 requires magento/module-customer ~101.0 -> satisfiable by magento/module-customer[101.0.11, 101.0.10, 101.0.9, 101.0.8, 101.0.7, 101.0.6, 101.0.5, 101.0.4, 101.0.3, 101.0.2, 101.0.1, 101.0.0].
        - bitexpert/magento2-force-customer-login 3.1.0 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 3.0.1 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 2.1.0 requires php ~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 2.0.2 requires php ~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 2.0.1 requires php ~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 2.0.0 requires php ~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.3.1 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.3.0 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.2.4 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.2.3 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.2.2 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.2.1 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.2.0 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.7 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.6 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.5 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.4 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.3 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.2 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.1 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.0 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.0.1 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.0.0 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 3.1.0 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 3.0.1 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 2.1.0 requires php ~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 2.0.2 requires php ~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 2.0.1 requires php ~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 2.0.0 requires php ~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.3.1 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.3.0 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.2.4 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.2.3 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.2.2 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.2.1 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.2.0 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.7 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.6 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.5 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.4 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.3 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.2 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.1 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.1.0 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.0.1 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - bitexpert/magento2-force-customer-login 1.0.0 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.3.10) does not satisfy that requirement.
        - Installation request for magento/product-enterprise-edition 2.4.0 -> satisfiable by magento/product-enterprise-edition[2.4.0].
        - Installation request for bitexpert/magento2-force-customer-login * -> satisfiable by bitexpert/magento2-force-customer-login[1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.3.0, 1.3.1, 2.0.0, 2.0.1, 2.0.2, 2.1.0, 2.2.0, 2.3.0, 3.0.1, 3.1.0, 3.2.0, 4.0.0, 4.0.2, 3.0.0].
    
    opened by bernarddelhez 8
  • Restore default whitelist all get static strategy

    Restore default whitelist all get static strategy

    When you remove the default whitelists in the admin and restore them with the restore button, all the whitelist will be added with the static strategy.

    Preconditions

    Remove some or all whitelists with the regex strategy.

    Magento Version : EE 2.4.5-p1

    Force Login Module Version : 5.1.0

    Steps to reproduce

    1. install force login module
    2. go to customers -> force customer login -> whitelist
    3. remove

    Expected result

    1. all removed default whitelist are added.
    2. all newly added whitelist will have the same strategy that were given when the module was first installed (in the patch file)

    Actual result

    1. all removed default whitelist are added.
    2. all newly added whitelist have the static strategy.
    opened by muuk-isaac 1
  • Exception #0 (Exception): Deprecated Functionality: strpos(): Non-string needles will be interpreted as strings in the future

    Exception #0 (Exception): Deprecated Functionality: strpos(): Non-string needles will be interpreted as strings in the future

    Preconditions

    Magento Version : Magento 2.4.4 EE

    Force Login Module Version : 5.0.1

    Third party modules : NO

    Steps to reproduce

    1. After Magento version upgrade from 2.3.7-p2 to 2.4.4 version.
    2. On the customer login page we are getting the below error.

    image

    Expected result

    1. It should show the customer login form and the login should be as expected.
    opened by manishgoswamig 0
  • Circular dependency: Magento\Customer\Model\Plugin\CustomerNotification depends on Magento\Customer\Model\Plugin\CustomerNotification and vice versa.

    Circular dependency: Magento\Customer\Model\Plugin\CustomerNotification depends on Magento\Customer\Model\Plugin\CustomerNotification and vice versa.

    Preconditions

    Magento Version : Magento 2.4.4 EE

    Force Login Module Version : 2.0.0

    Third party modules : NO

    Steps to reproduce

    1. After Magento version upgrade from 2.3.7-p2 to 2.4.4 version.
    2. On the customer login page we are getting the below error.

    image

    Expected result

    1. It should show the customer login form and the login should be as expected.
    opened by manishgoswamig 1
  • Problem with upgrade:  1061 Duplicate key name 'BITEXPERT_FORCELOGIN_WHITELIST_URL_RULE_STORE_ID'

    Problem with upgrade: 1061 Duplicate key name 'BITEXPERT_FORCELOGIN_WHITELIST_URL_RULE_STORE_ID'

    Preconditions

    1. Magento 2.4.3-p1
    2. "bitexpert/magento2-force-customer-login": "^v4.1"

    Steps to reproduce

    1. Upgrade Magento to 2.4.4
    2. Upgrade "bitexpert/magento2-force-customer-login": "^5.0.1"

    Expected result

    1. bin/magento setup:upgrade will be finished successfully

    Actual result

    1. bin/magento setup:upgrade fails with the following error:
    Updating modules:
    Cache cleared successfully
    Schema creation/updates:
    SQLSTATE[42000]: Syntax error or access violation: 1061 Duplicate key name 'BITEXPERT_FORCELOGIN_WHITELIST_URL_RULE_STORE_ID', query was: ALTER TABLE `bitexpert_forcelogin_whitelist` MODIFY COLUMN `strategy` text NULL COMMENT "strategy matcher identifier", ADD INDEX `BITEXPERT_FORCELOGIN_WHITELIST_URL_RULE_STORE_ID` (`url_rule`,`store_id`)
    

    Why it happened

    It happened because my bitexpert_forcelogin_whitelist table has index create index BITEXPERT_FORCELOGIN_WHITELIST_URL_RULE_STORE_ID on bitexpert_forcelogin_whitelist (url_rule);

    When I upgrade - it tries to create index with the same name but with additional column.

    opened by VladyslavSikailo 9
  • Password Reset Endless redirect

    Password Reset Endless redirect

    Preconditions

    Dev & Production, unrelated env's

    Magento Version : 2.4.3-p1

    Force Login Module Version : 4.1.0

    Third party modules : Yes, many

    Steps to reproduce

    1. Enable the plugin
    2. Password reset keeps redirecting to itself

    Expected result

    1. Password reset should work

    Actual result

    1. Endless redirect loop to the same page /customer/account/createpassword?token=XXX

    Disabling the plugin makes it work again

    Additionally, trying to update to version 5.X I got the version mismatch error in packagist/magento. Setting it to canonical did NOT work - I've seen hints that 5.X can fix my issues, will have to move it out of composer and in app/code directly. Will confirm ASAP if 5.X solved this issue

    opened by vandijkstef 4
  • [improve] Add field on CMS pages to authorize them to not force login

    [improve] Add field on CMS pages to authorize them to not force login

    For us, module is used to prevent catalog access (categories pages, products pages, searches, cart) for not logged in users. All pages allowed are :

    • homepage
    • account pages (login, passwordreset, create,...)
    • all cms pages

    But everytime we add a CMS page, we need to add its url in the whitelist. We have more than 100 pages in CMS pages and they are not having a specific word in their url. So we have to manually add them in the whitelist (and not forget to add them on creation process) It's time consuming and source for errors for contributors.

    We should have a field on cms page creation (boolean field) to authorize page to not force login.

    enhancement 
    opened by nelero 2
Releases(v5.1.0)
  • v5.1.0(Oct 31, 2022)

    Added

    • #224 Make module compatible with Magento 2.4.5
    • #218 Upgrade PHPStan to version 1.7
    • #217 Update readme, add composer error instructions

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #223 Add db_schema_whitelist.json to fix issue
    Source code(tar.gz)
    Source code(zip)
  • v5.0.1(May 14, 2022)

  • v5.0.0(May 13, 2022)

    Added

    • #211 M2.4.4 compability
    • #197 Allow the store column to be sorted in the grid view
    • #188 Paypal Ipn

    Deprecated

    • #202 Only support M2.4.x

    Removed

    • Nothing.

    Fixed

    • #212 Allow Magento admin to log in as customer
    • #209 Fix bug for wrong redirect on customer login and account confirmation
    • #206 Homepage Redirect After Login Leads To incorrect url
    • #198 Fix undefined method call
    Source code(tar.gz)
    Source code(zip)
  • v4.1.0(Oct 19, 2020)

    4.1.0

    Added

    • #191 Added support for Magento 2.4
    • #187 Skip dynamic asset request
    • #186 Fixed registration redirect

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #192 force login in store redirects to default login
    • #180 Customers get whoops.... after registering
    • #179 Improve menu placement: fix compatibility with B2B
    • #161 After login in shows css page
    Source code(tar.gz)
    Source code(zip)
  • v4.0.2(Dec 27, 2019)

  • v4.0.1(Dec 16, 2019)

    Added

    • Nothing.

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #167 Password Reset not working

    Thank you @mischabraam, @websharp & @daniel-ifrim for tackling this issue!

    Source code(tar.gz)
    Source code(zip)
  • v4.0.0(Nov 2, 2019)

    Added

    • #172 Add PHP7.3 and Magento 2.3.3 version requirements
    • #165 Added /stores/store/switch and /stores/store/redirect to the whitelist
    • #155 Add varnish ESI url to whitelist
    • #154 Add option to configure to force https redirect

    Deprecated

    • Nothing.

    Removed

    • #160 Drop Magento 2.1 & 2.2 compatibility

    Fixed

    • Nothing.

    Thank you @viniqueiroz, @philippsander & @mirsch for your contribution!

    Source code(tar.gz)
    Source code(zip)
  • v3.2.0(Feb 7, 2019)

  • v3.1.0(Nov 17, 2018)

    Added

    • #134 Fixed an issue where GET query parameters get stripped
    • #123 Fixes for multiple stores with store name in path
    • #118 Add path /customer/account/resetpasswordpost to the default setup
    • #108 Add Magento EQP tool in Travis build
    • #105 Add coveralls.io support in Travis build

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • Nothing.
    Source code(tar.gz)
    Source code(zip)
  • v3.0.1(Dec 26, 2017)

  • 3.0.0(Dec 25, 2017)

    Added

    • Nothing.

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #98 Convert "bitExpert" namespace to "BitExpert" to fix the Magento 2.2 XSD issue
    • #99 Don't store AJAX requests as after login url
    • #100 Apply fixes sugested by the EQP tool
    • #101 Update docs to fix typos and reflect latest changes
    • #102 Rename button "delete"

    Thank you @wexo-team for your contribution!

    Source code(tar.gz)
    Source code(zip)
  • v2.3.0(Oct 31, 2017)

    2.3.0

    Added

    • #88 Migrated from using observers to hook into router chain
    • #89 Enabled edition of default whitelist routes
    • #92 Fixed syntax issue in layout xml, invalid block definition

    Deprecated

    • Nothing.

    Removed

    • #88 Usage of observers (LoginRequiredOnCustomerSessionInitObserver, LoginRequiredOnVisitorInitObserver) and event hooks (customer_session_init, visitor_init) have been removed

    Fixed

    • #83 404 pages do not show when logged out
    • #84 Disable registration isn't possible
    • #91 Whitelist is Not works for Magento 2.2.0
    Source code(tar.gz)
    Source code(zip)
  • v2.3.0-RC2(Oct 26, 2017)

    2.3.0

    Added

    • #88 Migrated from using observers to hook into router chain
    • #89 Enabled edition of default whitelist routes
    • #92 Fixed syntax issue in layout xml, invalid block definition

    Deprecated

    • Nothing.

    Removed

    • #88 Usage of observers (LoginRequiredOnCustomerSessionInitObserver, LoginRequiredOnVisitorInitObserver) and event hooks (customer_session_init, visitor_init) have been removed

    Fixed

    • #83 404 pages do not show when logged out
    • #84 Disable registration isn't possible
    • #91 Whitelist is Not works for Magento 2.2.0
    Source code(tar.gz)
    Source code(zip)
  • v2.3.0-RC1(Oct 25, 2017)

    2.3.0

    Added

    • #88 Migrated from using observers to hook into router chain
    • #89 Enabled edition of default whitelist routes

    Deprecated

    • Nothing.

    Removed

    • #88 Usage of observers (LoginRequiredOnCustomerSessionInitObserver, LoginRequiredOnVisitorInitObserver) and event hooks (customer_session_init, visitor_init) have been removed

    Fixed

    • #83 404 pages do not show when logged out
    • #84 Disable registration isn't possible
    Source code(tar.gz)
    Source code(zip)
  • v2.2.0(Oct 4, 2017)

  • v2.1.0(Aug 4, 2017)

    2.1.0

    Added

    • #82 Fixed invalid position of tag resource in system.xml
    • #78 Move backend configuration to customer > customer configuration section
    • #77 Provides backwards compatibility by set strategy for existing rules to regex matcher instead of static
    • #76 Static matcher now canonicalizes url and rule to omit differences of trailing slashes
    • #60 Behavior Setting for Matcher

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #81 Error in admin pages due to invalid XML
    • #79 Invalid system.xml file
    • #75 Static matching strategy could ignore ending slash
    • #74 Upgrade to 2.1 RC2 from 2 breaks backward compatibility of rules
    • #73 Force login top level system config tab is overkill
    • #72 Fixes on class resolution
    Source code(tar.gz)
    Source code(zip)
  • v2.1.0-RC4(Aug 3, 2017)

    2.1.0

    Added

    • #82 Fixed invalid position of tag resource in system.xml
    • #78 Move backend configuration to customer > customer configuration section
    • #77 Provides backwards compatibility by set strategy for existing rules to regex matcher instead of static
    • #76 Static matcher now canonicalizes url and rule to omit differences of trailing slashes
    • #60 Behavior Setting for Matcher

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #81 Error in admin pages due to invalid XML
    • #79 Invalid system.xml file
    • #75 Static matching strategy could ignore ending slash
    • #74 Upgrade to 2.1 RC2 from 2 breaks backward compatibility of rules
    • #73 Force login top level system config tab is overkill
    • #72 Fixes on class resolution
    Source code(tar.gz)
    Source code(zip)
  • v2.1.0-RC3(Jul 11, 2017)

    2.1.0

    Added

    • #78 Move backend configuration to customer > customer configuration section
    • #77 Provides backwards compatibility by set strategy for existing rules to regex matcher instead of static
    • #76 Static matcher now canonicalizes url and rule to omit differences of trailing slashes
    • #60 Behavior Setting for Matcher

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #75 Static matching strategy could ignore ending slash
    • #74 Upgrade to 2.1 RC2 from 2 breaks backward compatibility of rules
    • #73 Force login top level system config tab is overkill
    • #72 Fixes on class resolution
    Source code(tar.gz)
    Source code(zip)
  • v2.1.0-RC2(Jul 5, 2017)

  • v2.1.0-RC1(Jul 5, 2017)

  • v2.0.2(Jun 12, 2017)

    Changelog

    2.0.2

    Added

    • #71 Moved events.xml to frontend/events.xml

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #68 Activating the module also blocks the backend
    Source code(tar.gz)
    Source code(zip)
  • v2.0.1(Apr 24, 2017)

    Changelog

    2.0.1

    Added

    • #67 Resolve redirect loop from login to customer dashboard

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #66 Redirect loop
    Source code(tar.gz)
    Source code(zip)
  • v2.0.0(Apr 19, 2017)

    Changelog

    2.0.0

    Added

    • Changed type namings in DI to match best practice.
    • Respect configured login option behavior.
    • Added own session handler.
    • #63 Updated resource ACL
    • #62 Move UpgradeSchema to InstallSchema
    • #54 Added configuration to enabled or disabled the module
    • #43 Added additional default rules for sitemap.xml and robots.txt
    • #26 Added cache control to redirecting
    • #24 Added configuration to set target url

    Deprecated

    • Nothing.

    Removed

    • Removed full qualification of namespace representation type name to match best practice.

    Fixed

    • Refactored code structure.
    • #64 ACL error when accessing Store Configuration
    • #61 Setup install then upgrade fails
    • #35 Redirection after logging in
    Source code(tar.gz)
    Source code(zip)
  • v2.0.0-RC3(Apr 15, 2017)

  • v2.0.0-RC2(Apr 10, 2017)

  • v2.0.0-RC1(Mar 23, 2017)

Owner
bitExpert AG
Our pulse is cross-technology software development that beats with every line of code.
bitExpert AG
Magento 2 Module that adds Donation Product Type. Enables the customer to add a donation (product) of a preferred amount to the cart.

Magento 2 Module Experius DonationProduct (RC1.0) Demo website: https://donationproduct.experius.nl Magento Marketplace: https://marketplace.magento.c

Experius 23 Apr 1, 2022
This Magento extension provides a Real Full Page Caching for Magento powered by Varnish with support of Session-Based information caching (Cart, Customer Accounts, ...) via ESI includes

This Magento extension provides a Real Full Page Caching (FPC) for Magento powered by Varnish with support of Session-Based information caching (Cart, Customer Accounts, ...) via ESI includes

Hugues Alary 95 Feb 11, 2022
Akaunting module to use employee as a customer

Associate Employee to customer App for Akaunting to associate employee to customer. With this app contacts with the employee type can be used as custo

LibreCode coop 2 Sep 21, 2022
implementation of a simple Brute-force attack in python

Brute-force-attack-python implementation of a simple Brute-force attack in python using requests library who involved in this project: Python side : A

ali sharifi 5 Nov 25, 2022
Extends the customer functionality of Magento.

FireGento_Customer This extension extends the core functionality of the customer module of Magento. It is possible to temporarily lock the user accoun

FireGento e. V. 23 Apr 1, 2022
Magento extension which makes it impossible for a customer to log in until the account has been activated by the administrator.

This Magento 1 extension is orphaned, unsupported and no longer maintained. If you use it, you are effectively adopting the code for your own project.

Vinai Kopp 120 Oct 10, 2022
Set a customer password with bin/magento.

Set a customer password Since Magento 2 no longer provides facilities to set a customers password, this command can come in handy during development w

Vinai Kopp 25 Mar 8, 2022
Magento 2 custom extension to add custom attributes(longitude, latitude) to customer address

Magento 2 custom extension to add custom attributes(longitude, latitude) to customer address. Then save them to quote model and copy them from quote address to order address on bakend, frontend, rest api

MageArab 2 Jul 14, 2022
Laravel Nova integration for justbetter/laravel-magento-customer-prices

Laravel Magento Customer Prices Nova Laravel Nova integration for justbetter/laravel-magento-customer-prices. Installation Install the package. compos

JustBetter 13 Nov 4, 2022
Package to send customer specific prices to Magento from a Laravel application using a configurable source.

Laravel Magento Customer Prices This package provides a way to add customer specific prices to Magento from a Laravel app. By default, it uses the Mag

JustBetter 14 Nov 4, 2022
Magento 2 Module Experius Page Not Found 404. This module saves all 404 url to a database table

Magento 2 Module Experius Page Not Found 404 This module saves all 404 urls to a database table. Adds an admin grid with 404s It includes a count so y

Experius 28 Dec 9, 2022
Automatically load the next page of products in Magento. Easy to install and configure, this module works 100% out of the box with vanilla Magento 1.9.x and earlier.

Automatically load the next page of products in Magento. Easy to install and configure, this module works 100% out of the box with vanilla Magento 1.9.x and earlier.

Strategery 123 Nov 20, 2021
SuiteCRM is the award-winning open-source, enterprise-ready Customer Relationship Management (CRM) software application.

SuiteCRM is the award-winning open-source, enterprise-ready Customer Relationship Management (CRM) software application.

SalesAgility 111 Dec 21, 2022
Guest to Customer for Magento2 - Quickly and easily convert existing guest checkout customers to registered customers.

Guest to Customer for Magento 2.0 For Magento 2.0.x, 2.1.x, 2.2.x, 2.3.x and 2.4.x In general E-commerce, shoppers do not like to create an account du

MagePal :: Magento Extensions 66 Oct 7, 2022
The Laravel eCommerce Accept Payment Gateway allows the customer to make use of Accept payment gateway in the Bagisto eCommerce website.

Introduction Bagisto WeAccept add-on allow customers to pay for others using WeAccept payment gateway. Requirements: Bagisto: 1.3.2 Installation with

Bagisto 2 May 31, 2022
A tool that allows to quickly export data from Magento 1 and Magento 2 store and import it back into Magento 2

Simple Import / Export tool A tool that allows to quickly export data from Magento 1 and Magento 2 store and import it back into Magento 2. Table data

EcomDev B.V. 51 Dec 5, 2022
The swiss army knife for Magento developers, sysadmins and devops. The tool provides a huge set of well tested command line commands which save hours of work time. All commands are extendable by a module API.

netz98 magerun CLI tools for Magento 2 The n98 magerun cli tools provides some handy tools to work with Magento from command line. Build Status Latest

netz98 758 Dec 28, 2022