White listing '/' seems to just white list the entirety of the website. Do you have an example of how to just white list the home page?

Thanks,

Reported issue:

In the admin backoffice: Store> Configuration > Advanced, the module is still shown as disable. Until I turn that one, I will not be able to see the Force Login Whitelist feature displayed as part of the menu. On the front end, it is working perfectly even if it is displayed as disabled in the admin backoffice.

Wouldn't it be great if a page/storefront can also be whitelisted based on Customer Group.
Any one planning to add this functionality?

The static strategy would be a good one to use in many simple cases, except that when trying it out I found that about half my links failed because a slash was appended. I should almost certainly canonicalise my links, but this still feels a little fragile.

Would it be better to allow an options slash on the end of links that do not have one, or perhaps you think that in this case we should be using regex (my solution here) or doubling every rule to match slashes.

I would like to also have the menu hidden when a customer is not logged in.

Description

The simplify the usage and writing of the whitelisting rules, the user should be able to specify how the given rule is to be interpreted. Not every user is custom to write regular expression, but want to add simple url rules. By allowing to select the way of interpreting the given rules, the normal user will have no trouble of adding simple static rules, and advanced users are able to create complex regex based rules to match their needs.

Tasks

• Add Matcher Strategies
  • Static (this should be default):
    Rule is used as a literal value and will be added onto the base url for matching.
  • RegEx-All (current behavior):
    Rule is based on regular expression, and will be used for looking up matching anywhere in the current Url.
• Let admin user decide which strategy to use

Extend the Travis build to run the Magento Extension Quality Program Coding Standard checks for every build.

A common use-case for this extension would be to have trade and direct to customer websites set up, possibly with multiple sites under each. I say this as we've had several clients over the years with this requirement.

To support this, the module just needs to have an enabled/disabled option in the system config. This can then be scoped by website/store without further effort.

I do see that the module was installed successfully because the homepage redirects to login, but when I attempt to sign into the admin backend it will only reload the login screen (without any error appearing).

I've cleared cache / cookies / etc. Sometimes when I've done that instead of the Login screen reappearing I see a "too many redirect loops" error, but that is intermittent.

I'm using the bitnami magento 2 AWS image. Is there a whitelist I need to add for the Admin side?

It seems in Magento 2.2 you cant start your module with a lowercase letter.

Hi,

I'm trying to add to the whitelist an entire site view, but it doesn't work. I tried to add "/" or "." or "", specifying the desired site view, nothing, it doesn't work. Could you help me?

I'm having a problem signing into a customer account with the module enabled on v2.0.0.

With the module enabled on a store view, I'm redirected to /customer/account/ which redirects me back to /customer/account/login/ and the loop continues.

This issue is resolved by whitelisting /customer/account/ which is not present in the default configuration.

I don't want customers to be able to create accounts in one of my websites/store views... so I'd like to similarly restrict access to this page... however, this is one of the "hardcoded" paths that I cannot delete from the Whitelist... is there a way to remove it?

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

I run composer require bitexpert/magento2-force-customer-login
in the directory of my website, however no menu is displayed

Composer, as I understand, shows it is installed

composer show bitexpert/magento2-force-customer-login
name : bitexpert/magento2-force-customer-login
descrip. : The Force Login module for Magento2 redirects a storefront visitor to the Magento2 Frontend login page, if the visitor is not logged in. It is possible to configure the whitelisted urls to add custom definitions.
keywords :
versions : * 1.2.4
type : magento2-module
license : Apache License 2.0 (Apache-2.0) (OSI approved) https://spdx.org/licenses/Apache-2.0.html#licenseText
source : [git] https://github.com/bitExpert/magento2-force-login.git 1ddcef1
dist : [zip] https://api.github.com/repos/bitExpert/magento2-force-login/zipball/1ddcef13021843478bfd453fabf66d80482e2f60 1ddcef1
names : bitexpert/magento2-force-customer-login

autoload
files
psr-4
bitExpert\ForceCustomerLogin\ => .

requires
magento/module-customer 100.1.*
php ~5.5.0|~5.6.0|~7.0.0

requires (dev)
phing/phing ^2.8.0
phpunit/phpunit ~5.0
squizlabs/php_codesniffer ^2.3

Tried to install on Magento 2.0.7, files loaded fine but the module isn't listing in Stores > Configuration > Advanced.

You can set this value to No in Configuration > Customers > Customer Configuration > Login Options
and the expected result is that after login the user should be returned to the original page they were on, but with this plugin enabled it seems to always send them to the My Account page after login.

Please increment the module.xml version for 1.3.0

Just a note - we noticed that after installing this plugin that successful Authorize.net charges would result in an error being shown upon checkout. All the orders were still entered into Magento (v2.2.2) and the charges were successful at Authorize.net. However, the error "Attention: Something went wrong, please contact the seller" would appear after a bit of a pause.

To correct this, we added "/authorizenet" as a whitelisted directory - and it now works fine.

Just wanted to share this for others who may encounter the same problem.

I tried entering / as a whitelist to allow the home page to match.

But this seems to match all pages. I think the regex needs to match the specified page and no more. For the start this could just match the part of the request that Magento considers the path, and at the end ignore any query string.

Reported Issue:
Registering a new address for the Force Login Whitelist has failed to add a new address. Please see the attached image.

After I activate the module in the backend I'm redirected to the frontend login. The events.xml file should be placed in the frontend directory to fix the issue.

Dear Author,

How to add only home page in whitelist ?

Thanks.

It's great that we now have the ability to enable/disable by scope, but system admin is getting unusable with every developer putting in another top level tab.

Any chance that the very small number of config options could be put in as a group under the Customer system config tab?

Hi,

After installing and adding the home page on the whitelist, the navigation bar with the categories completely disappeared. Any clue what might have caused that?

When creating a fresh install from a composer.json file with Magento & modules in and after running setup:install, when running setup:upgrade after this we're getting the following error:

Module 'bitExpert_ForceCustomerLogin':
Upgrading data... 

                                                                                                                                                                                                                                                                                                                                                                                                       
  [Zend_Db_Statement_Exception]                                                                                                                                                                                                                                                                                                                                                                        
  SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Rest API' for key 'BITEXPERT_FORCELOGIN_WHITELIST_LABEL', query was: INSERT INTO `bitexpert_forcelogin_whitelist` (`store_id`,`label`,`url_rule`,`editable`) VALUES (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?)  
                                                                                                                                                                                                                                                                                                                                                                                                       




                                                                                                                                   
  [PDOException]                                                                                                                   
  SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Rest API' for key 'BITEXPERT_FORCELOGIN_WHITELIST_LABEL'  
                                                                                                                                   


setup:upgrade [--keep-generated] [--magento-init-params="..."]

In the Setup the installSchema and installData is missing where there is the upgradeSchema and upgradeData.

Without the schema install to create the Table it gives the error as
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'gp.bitexpert_forcelogin_whitelist' doesn't exist, query was: SELECT main_table.* FROM bitexpert_forcelogin_whitelist AS main_table WHERE (store_id IN(0, 1))

@websharp we're seeing an error in developer mode on Magento CE 2.1.6 (not sure if this is present on earlier versions).

When trying to access a Store's configuration in the admin side the following error is getting thrown:

Invalid XML in file {...}/bitexpert/magento2-force-customer-login/etc/adminhtml/system.xml:
Element 'resource': [facet 'pattern'] The value 'bitExpert::ForceCustomerLogin' is not accepted by the pattern '([A-Z]+[a-zA-Z0-9]{1,}){1,}_[A-Z]+[A-Z0-9a-z]{1,}::[A-Za-z_0-9]{1,}'. Line: 11
Element 'resource': 'bitExpert::ForceCustomerLogin' is not a valid value of the atomic type 'typeAclResourceId'. Line: 11

The regex for resources expects the module's vendor name to begin with an uppercase letter, using bitExpert causes it to throw the above error.

@chedaroo has submitted a PR for this here: #63

Hi,

the composer.json ("magento/module-customer": "100.0.*") is not compatible with Magento 2.1.

Is there a future release that will be compatible with Magento 2.1 soon ?

Thanks.

After login every time redirecting to my account page when i click home page.
We have configured varnish cache.
Some times if i delete browser cache & refresh varnish it seems working fine.

Hello,

i have installed the module on a plain 2.2

1 exception(s):
Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'block', attribute 'class': [facet 'pattern'] The value 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Manage\Create' is not accepted by the pattern '[A-Z][a-zA-Z\d](\[A-Z][a-zA-Z\d])*'.
Line: 124

Element 'block', attribute 'class': 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Manage\Create' is not a valid value of the atomic type 'blockClassType'.
Line: 124

Element 'block', attribute 'class': [facet 'pattern'] The value 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Manage\Create\Submit' is not accepted by the pattern '[A-Z][a-zA-Z\d](\[A-Z][a-zA-Z\d])*'.
Line: 125

Element 'block', attribute 'class': 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Manage\Create\Submit' is not a valid value of the atomic type 'blockClassType'.
Line: 125

Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'block', attribute 'class': [facet 'pattern'] The value 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Manage\Create' is not accepted by the pattern '[A-Z][a-zA-Z\d](\[A-Z][a-zA-Z\d])*'.
Line: 124

Element 'block', attribute 'class': 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Manage\Create' is not a valid value of the atomic type 'blockClassType'.
Line: 124

Element 'block', attribute 'class': [facet 'pattern'] The value 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Manage\Create\Submit' is not accepted by the pattern '[A-Z][a-zA-Z\d](\[A-Z][a-zA-Z\d])*'.
Line: 125

Element 'block', attribute 'class': 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Manage\Create\Submit' is not a valid value of the atomic type 'blockClassType'.
Line: 125

We found conflicting component dependencies. Hide detail

Command "update" failed: 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

• bitexpert/magento2-force-customer-login 2.0.0 requires magento/module-customer ~100.0 -> satisfiable by magento/module-customer[100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.1.0, 100.0.7, 100.0.8, 100.1.1, 100.0.9, 100.1.2, 100.1.3, 100.0.10, 100.1.4, 100.1.5, 100.0.11, 100.1.6, 100.0.12, 100.1.7, 100.1.8, 100.0.13, 100.0.14, 100.1.9].
• bitexpert/magento2-force-customer-login 2.0.0 requires magento/module-customer ~100.0 -> satisfiable by magento/module-customer[100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.1.0, 100.0.7, 100.0.8, 100.1.1, 100.0.9, 100.1.2, 100.1.3, 100.0.10, 100.1.4, 100.1.5, 100.0.11, 100.1.6, 100.0.12, 100.1.7, 100.1.8, 100.0.13, 100.0.14, 100.1.9].
• Can only install one of: magento/module-customer[101.0.0, 100.0.2].
• Can only install one of: magento/module-customer[101.0.0, 100.0.3].
• Can only install one of: magento/module-customer[101.0.0, 100.0.4].
• Can only install one of: magento/module-customer[101.0.0, 100.0.5].
• Can only install one of: magento/module-customer[101.0.0, 100.0.6].
• Can only install one of: magento/module-customer[101.0.0, 100.1.0].
• Can only install one of: magento/module-customer[101.0.0, 100.0.7].
• Can only install one of: magento/module-customer[101.0.0, 100.0.8].
• Can only install one of: magento/module-customer[101.0.0, 100.1.1].
• Can only install one of: magento/module-customer[101.0.0, 100.0.9].
• Can only install one of: magento/module-customer[101.0.0, 100.1.2].
• Can only install one of: magento/module-customer[101.0.0, 100.1.3].
• Can only install one of: magento/module-customer[101.0.0, 100.0.10].
• Can only install one of: magento/module-customer[101.0.0, 100.1.4].
• Can only install one of: magento/module-customer[101.0.0, 100.1.5].
• Can only install one of: magento/module-customer[101.0.0, 100.0.11].
• Can only install one of: magento/module-customer[101.0.0, 100.1.6].
• Can only install one of: magento/module-customer[101.0.0, 100.0.12].
• Can only install one of: magento/module-customer[101.0.0, 100.1.7].
• Can only install one of: magento/module-customer[101.0.0, 100.1.8].
• Can only install one of: magento/module-customer[101.0.0, 100.0.13].
• Can only install one of: magento/module-customer[100.0.14, 101.0.0].
• Can only install one of: magento/module-customer[100.1.9, 101.0.0].
• magento/product-community-edition 2.2.0 requires magento/module-customer 101.0.0 -> satisfiable by magento/module-customer[101.0.0].
• Installation request for magento/product-community-edition 2.2.0 -> satisfiable by magento/product-community-edition[2.2.0].
• Installation request for bitexpert/magento2-force-customer-login 2.0.0 -> satisfiable by bitexpert/magento2-force-customer-login[2.0.0].

I have installed the moduel(v2.3.0-RC1) on Magento 2.2.0, after I enable the module and test it on frontend, it works. great.
My php version is 7.0.22.

However, when I try to access Backend -> Customer -> Whitelist, I got error Message:

1 exception(s):
Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'block', attribute 'class': [facet 'pattern'] The value 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Settings\Whitelist' is not accepted by the pattern '[A-Z][a-zA-Z\d](\[A-Z][a-zA-Z\d])*'.
Line: 132

Element 'block', attribute 'class': 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Settings\Whitelist' is not a valid value of the atomic type 'blockClassType'.
Line: 132

Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'block', attribute 'class': [facet 'pattern'] The value 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Settings\Whitelist' is not accepted by the pattern '[A-Z][a-zA-Z\d](\[A-Z][a-zA-Z\d])*'.
Line: 132

Element 'block', attribute 'class': 'bitExpert\ForceCustomerLogin\Block\Adminhtml\Settings\Whitelist' is not a valid value of the atomic type 'blockClassType'.
Line: 132

#0 /var/www/html/aaron/vendor/magento/framework/Config/Dom.php(115): Magento\Framework\Config\Dom->_initDom('<layout xmlns:x...')
#1 /var/www/html/aaron/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(111): Magento\Framework\Config\Dom->__construct('<layout xmlns:x...', Object(Magento\Framework\App\Arguments\ValidationState), Array, NULL, '/var/www/html/a...', '%message%\nLine:...')
#2 /var/www/html/aaron/vendor/magento/framework/ObjectManager/Factory/Compiled.php(108): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('Magento\Framewo...', Array)
#3 /var/www/html/aaron/vendor/magento/framework/ObjectManager/ObjectManager.php(56): Magento\Framework\ObjectManager\Factory\Compiled->create('Magento\Framewo...', Array)
#4 /var/www/html/aaron/vendor/magento/framework/Config/DomFactory.php(42): Magento\Framework\ObjectManager\ObjectManager->create('Magento\Framewo...', Array)
#5 /var/www/html/aaron/vendor/magento/framework/View/Model/Layout/Update/Validator.php(125): Magento\Framework\Config\DomFactory->createDom(Array)
#6 /var/www/html/aaron/vendor/magento/framework/View/Model/Layout/Merge.php(461): Magento\Framework\View\Model\Layout\Update\Validator->isValid('<layout xmlns:x...', 'layout_merged', false)
#7 /var/www/html/aaron/vendor/magento/framework/View/Model/Layout/Merge.php(442): Magento\Framework\View\Model\Layout\Merge->_validateMergedLayout('LAYOUT_adminhtm...', '\n <css ...')
#8 /var/www/html/aaron/vendor/magento/framework/View/Layout/Builder.php(86): Magento\Framework\View\Model\Layout\Merge->load()
#9 /var/www/html/aaron/vendor/magento/framework/View/Layout/Builder.php(63): Magento\Framework\View\Layout\Builder->loadLayoutUpdates()
#10 /var/www/html/aaron/vendor/magento/framework/View/Page/Config.php(197): Magento\Framework\View\Layout\Builder->build()
#11 /var/www/html/aaron/vendor/magento/framework/View/Page/Config.php(207): Magento\Framework\View\Page\Config->build()
#12 /var/www/html/aaron/vendor/magento/framework/App/View.php(170): Magento\Framework\View\Page\Config->publicBuild()
#13 /var/www/html/aaron/vendor/magento/framework/App/View.php(114): Magento\Framework\App\View->loadLayoutUpdates()
#14 /var/www/html/aaron/app/code/bitExpert/ForceCustomerLogin/Controller/Adminhtml/Manage/Index.php(26): Magento\Framework\App\View->loadLayout()
#15 /var/www/html/aaron/vendor/magento/framework/App/Action/Action.php(107): bitExpert\ForceCustomerLogin\Controller\Adminhtml\Manage\Index->execute()
#16 /var/www/html/aaron/vendor/magento/module-backend/App/AbstractAction.php(229): Magento\Framework\App\Action\Action->dispatch(Object(Magento\Framework\App\Request\Http))
#17 /var/www/html/aaron/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Backend\App\AbstractAction->dispatch(Object(Magento\Framework\App\Request\Http))
#18 /var/www/html/aaron/vendor/magento/framework/Interception/Interceptor.php(138): bitExpert\ForceCustomerLogin\Controller\Adminhtml\Manage\Index\Interceptor->___callParent('dispatch', Array)
#19 /var/www/html/aaron/vendor/magento/module-backend/App/Action/Plugin/Authentication.php(143): bitExpert\ForceCustomerLogin\Controller\Adminhtml\Manage\Index\Interceptor->Magento\Framework\Interception{closure}(Object(Magento\Framework\App\Request\Http))
#20 /var/www/html/aaron/vendor/magento/framework/Interception/Interceptor.php(135): Magento\Backend\App\Action\Plugin\Authentication->aroundDispatch(Object(bitExpert\ForceCustomerLogin\Controller\Adminhtml\Manage\Index\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
#21 /var/www/html/aaron/vendor/magento/framework/Interception/Interceptor.php(153): bitExpert\ForceCustomerLogin\Controller\Adminhtml\Manage\Index\Interceptor->Magento\Framework\Interception{closure}(Object(Magento\Framework\App\Request\Http))
#22 /var/www/html/aaron/generated/code/bitExpert/ForceCustomerLogin/Controller/Adminhtml/Manage/Index/Interceptor.php(26): bitExpert\ForceCustomerLogin\Controller\Adminhtml\Manage\Index\Interceptor->___callPlugins('dispatch', Array, NULL)
#23 /var/www/html/aaron/vendor/magento/framework/App/FrontController.php(55): bitExpert\ForceCustomerLogin\Controller\Adminhtml\Manage\Index\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
#24 /var/www/html/aaron/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Framework\App\FrontController->dispatch(Object(Magento\Framework\App\Request\Http))
#25 /var/www/html/aaron/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\App\FrontController\Interceptor->___callParent('dispatch', Array)
#26 /var/www/html/aaron/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception{closure}(Object(Magento\Framework\App\Request\Http))
#27 /var/www/html/aaron/generated/code/Magento/Framework/App/FrontController/Interceptor.php(26): Magento\Framework\App\FrontController\Interceptor->___callPlugins('dispatch', Array, Array)
#28 /var/www/html/aaron/vendor/magento/framework/App/Http.php(135): Magento\Framework\App\FrontController\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
#29 /var/www/html/aaron/vendor/magento/framework/App/Bootstrap.php(256): Magento\Framework\App\Http->launch()
#30 /var/www/html/aaron/index.php(39): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http))

Any suggest?

This is in Magento 2.1.7.
When visiting pages like a cart rule, I get the following error:

1 exception(s):
Exception #0 (Magento\Framework\Exception\LocalizedException): Invalid XML in file /Volumes/Sites/SomeSite/vendor/bitexpert/magento2-force-customer-login/etc/adminhtml/system.xml:
Element 'resource': This element is not expected.
Line: 7


Exception #0 (Magento\Framework\Exception\LocalizedException): Invalid XML in file /Volumes/Sites/SomeSite/vendor/bitexpert/magento2-force-customer-login/etc/adminhtml/system.xml:
Element 'resource': This element is not expected.
Line: 7

#0 /Volumes/Sites/SomeSite/vendor/magento/framework/Config/Reader/Filesystem.php(127): Magento\Config\Model\Config\Structure\Reader->_readFiles(Object(Magento\Framework\Config\FileIterator))
#1 /Volumes/Sites/SomeSite/vendor/magento/framework/Config/Data/Scoped.php(103): Magento\Framework\Config\Reader\Filesystem->read('adminhtml')
#2 /Volumes/Sites/SomeSite/vendor/magento/framework/Config/Data/Scoped.php(81): Magento\Framework\Config\Data\Scoped->_loadScopedData()
#3 /Volumes/Sites/SomeSite/vendor/magento/module-config/Model/Config/Structure.php(73): Magento\Framework\Config\Data\Scoped->get()
etc.

It looks like the node should be removed from system.xml?

My 404 pages are working fine when a user is logged in but are white screening when logged out. I've disabled this plugin and the 404 pages work fine again.

• Is this something that I need to whitelist?
• Is there any way to serve a different 404 page to users who are logged in Vs those who aren't (even just with a class on the body/CSS)?

Thanks for your help,

I'm having trouble accessing protected pages after logging in when using 2.0.1 and Magento CE 2.1.6.

If I try to access homepage root on / I'm getting redirected to /customer/account/login, I can login then get redirected to /customer/account/, the customer dashboard.

Once logged in and trying to access the homepage again, I get a 302 redirect to /customer/account/login which 302 directs me back to /customer/account/.

I thought this may be down to the customer/startup/redirect_dashboard (Redirect Customer to Account Dashboard after Logging in) configuration being set to 1 however setting it to 0 has no change in behaviour at all.

Does anyone have any ideas what could be causing this?

Hi guys,

It would be great if robots.txt and sitemap.xml are default added to the whitelist.
Now you'll get redirect to the customer login page when you go to http://www.example.com/robots.txt.
Google will not be able to index the site since robots.txt is not allowed to visit.
Thank you in advance.

Kind regards,
Mike

I have tested it on magento 2.2 . After installing, it shows blank page. Do we have new version of it which compatible with magento 2.2 ?

Hello,

I have mulitwebsite, I have to set this module for another website. but when i add the / to whitelist the homepage it is allowing me to access all pages.

For example.
http://test-2.com should be allowed to visit.
http://test-2.com/site should be allowed to visit , here shop is store name.

but / is allowing to access all pages.
when i try to check the #^.%s/?.$#i into regular expression checker they are saying the expression have errors.

Can you help me in that if i want to allow only homepage no other pages.

Thank you.

I tried to install both through composer and manually.

Magento ver. 2.1.0

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.

Removing the whitelist to "/customer/account/create/" have no effect.

It's still possible to create an account even though it's not whitelisted.

I would like to disable possibility to register new user(for B2B shop).
I removed /customer/account/create from whitelist but registration is still possible because default rule Customer Account Dashboard (/customer/account) is also match for registration url.

There was an error message occurred when I was trying to install the module to Magento 2.0.10

sudo composer require bitexpert/magento2-force-customer-login

Do not run Composer as root/super user! See https://getcomposer.org/root for details
Using version ^1.2 for bitexpert/magento2-force-customer-login
./composer.json has been updated
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
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.4
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.3
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.2
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.1
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.0
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.4
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.3
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.2
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.1
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.0|remove magento/framework 100.0.12
- Conclusion: don't install bitexpert/magento2-force-customer-login 1.2.0|don't install magento/framework 100.0.12
- Installation request for bitexpert/magento2-force-customer-login ^1.2 -> satisfiable by bitexpert/magento2-force-customer-login[1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4].
- bitexpert/magento2-force-customer-login 1.2.0 requires magento/module-customer 100.1.* -> satisfiable by magento/module-customer[100.1.0, 100.1.0-rc1, 100.1.0-rc2, 100.1.0-rc3, 100.1.1, 100.1.2].
- magento/module-customer 100.1.0 requires magento/framework 100.1.* -> satisfiable by magento/framework[100.1.0, 100.1.0-rc1, 100.1.0-rc2, 100.1.0-rc3, 100.1.1, 100.1.2].
- magento/module-customer 100.1.0-rc1 requires magento/framework 100.1.* -> satisfiable by magento/framework[100.1.0, 100.1.0-rc1, 100.1.0-rc2, 100.1.0-rc3, 100.1.1, 100.1.2].
- magento/module-customer 100.1.0-rc2 requires magento/framework 100.1.* -> satisfiable by magento/framework[100.1.0, 100.1.0-rc1, 100.1.0-rc2, 100.1.0-rc3, 100.1.1, 100.1.2].
- magento/module-customer 100.1.0-rc3 requires magento/framework 100.1.* -> satisfiable by magento/framework[100.1.0, 100.1.0-rc1, 100.1.0-rc2, 100.1.0-rc3, 100.1.1, 100.1.2].
- magento/module-customer 100.1.1 requires magento/framework 100.1.* -> satisfiable by magento/framework[100.1.0, 100.1.0-rc1, 100.1.0-rc2, 100.1.0-rc3, 100.1.1, 100.1.2].
- magento/module-customer 100.1.2 requires magento/framework 100.1.* -> satisfiable by magento/framework[100.1.0, 100.1.0-rc1, 100.1.0-rc2, 100.1.0-rc3, 100.1.1, 100.1.2].
- Can only install one of: magento/framework[100.0.12, 100.1.0].
- Can only install one of: magento/framework[100.0.12, 100.1.0-rc1].
- Can only install one of: magento/framework[100.0.12, 100.1.0-rc2].
- Can only install one of: magento/framework[100.0.12, 100.1.0-rc3].
- Can only install one of: magento/framework[100.0.12, 100.1.1].
- Can only install one of: magento/framework[100.0.12, 100.1.2].
- Installation request for magento/framework (locked at 100.0.12) -> satisfiable by magento/framework[100.0.12].

Installation failed, reverting ./composer.json to its original content.

Could anyone help me resolving this issue?
Thank you

I am tried to setup this module in my magento 2.1.5 v. its enabled prefect but when i am try to open it its disable label display .also the admin confiuration getting exception error the system.xml file format is not proper can you help me .
Thanks

Before 2.1 the assumption was that all rules were regex.
In 2.1 the default is that all rules are static, and seems to apply to all the existing rules.

Therefore in upgrading my current functionality breaks. Can I suggest that even if your default becomes static, all existing rules on upgrade are set to regex to maintain backwards compatibility?

Running cli command setup:di:compile fails for the Controller\LoginCheck dependencies due to internal dependency reference duplication.

Not reproducable with Magento2 v2.0.4.

Confirm error occurance on older magento2 installments.

In Chrome > Inspect > I see error "Failed to load resource: the server responded with a status of 500 (Internal Server Error)" and link to https://www.armota.lt/setup/index.php/componentGrid/components, after oppening which I see:
An error occurred during execution; please try again later.

Additional information:

RuntimeException

File:
/var/www/armota/setup/src/Magento/Setup/Model/PackagesData.php:88
Message:
Couldn't get available versions for package bitexpert/magento2-force-customer-login
Stack trace:
#0 /var/www/armota/setup/src/Magento/Setup/Controller/ComponentGrid.php(98): Magento\Setup\Model\PackagesData->syncPackagesData()
#1 /var/www/armota/vendor/zendframework/zend-mvc/src/Controller/AbstractActionController.php(82): Magento\Setup\Controller\ComponentGrid->componentsAction()
#2 [internal function]: Zend\Mvc\Controller\AbstractActionController->onDispatch(Object(Zend\Mvc\MvcEvent))
#3 /var/www/armota/vendor/zendframework/zend-eventmanager/src/EventManager.php(444): call_user_func(Array, Object(Zend\Mvc\MvcEvent))
#4 /var/www/armota/vendor/zendframework/zend-eventmanager/src/EventManager.php(205): Zend\EventManager\EventManager->triggerListeners('dispatch', Object(Zend\Mvc\MvcEvent), Object(Closure))
#5 /var/www/armota/vendor/zendframework/zend-mvc/src/Controller/AbstractController.php(118): Zend\EventManager\EventManager->trigger('dispatch', Object(Zend\Mvc\MvcEvent), Object(Closure))
#6 /var/www/armota/vendor/zendframework/zend-mvc/src/DispatchListener.php(93): Zend\Mvc\Controller\AbstractController->dispatch(Object(Zend\Http\PhpEnvironment\Request), Object(Zend\Http\PhpEnvironment\Response))
#7 [internal function]: Zend\Mvc\DispatchListener->onDispatch(Object(Zend\Mvc\MvcEvent))
#8 /var/www/armota/vendor/zendframework/zend-eventmanager/src/EventManager.php(444): call_user_func(Array, Object(Zend\Mvc\MvcEvent))
#9 /var/www/armota/vendor/zendframework/zend-eventmanager/src/EventManager.php(205): Zend\EventManager\EventManager->triggerListeners('dispatch', Object(Zend\Mvc\MvcEvent), Object(Closure))
#10 /var/www/armota/vendor/zendframework/zend-mvc/src/Application.php(314): Zend\EventManager\EventManager->trigger('dispatch', Object(Zend\Mvc\MvcEvent), Object(Closure))
#11 /var/www/armota/setup/index.php(31): Zend\Mvc\Application->run()
#12 {main}

Marketplace submissions will be checked in regard to problems with Varnish. This should not affect the current development as we fixed some issues in the past.