We released version 2.3 of our Force Login Module for Magento 2 which brings some requested features and fixes, here are the highlights of the current release:mehr lesen...
We released the new 2.2.0 version of the Force Login Module for Magento 2 providing support for Magento 2.2.
In one of our current Magento 2 projects we has the need to create a custom shipping method which thhat should not be selectable when there a product in our cart with a specific value selected in a custom attribute.
With the newest release of the Force Login module for Magento 2, you are now able to change the way to define your whitelist rules. For starters, you can choose between the already known regex-based interpreter strategy and the new static-based interpreter. The latter makes it now very easy to whitelist simple URLs without the requirement to know regex syntax. We also moved the configuration tab to "Customer > Customer Configuration" section.
Yesterday, we released the stable version 2.0 of our Force Login Module for Magento 2. To upgrade, you can get the latest release here, or update the dependency in your composer.json.
Last week we released version 1.2.0 of our Magento 2 Force Frontend Customer Login module which is compatible now with the latest 2.1 version of Magento. You can download the release on Github or require it via Composer:
Today, we release version 1.1.0 of our Magento 2 Force Frontend Customer Login module. Thanks to the feedback of some users, we could improve the module setup.
Here are some of the enhancements:
The administrative view of Magento 2 forces you to login, but in the website view the visitor can navigate as a guest through the pages. But if you do not wish to allow guest visitors to see your page without registration a valid login, Magento 2 leaves you on your own.
If you run the command:
The Magento 2 Transport Builder, responsible for preparing a mail message, wraps the mail component of the Zend Framework. Unfortunatly it is missing a method to add attachments. I submitted a Pull Request to Magento 2 to fix the issue but for now we need a work-a-round in our project. First we extend the Magento 2 Transport Builder like this: