New answers tagged

0

Another way this error can happen for homemade admin modules is when frontName in your routes.xml doesn't match the <add action"someFrontName/someAction" /> in your menu.xml. This causes the key you see in the link when trying to open the module to be different than expected.


0

You have to Unlock an administrator account sometimes Use this command to unlock the account of an administrator that was locked, typically because of multiple incorrect login attempts. bin/magento admin:user:unlock {username} You must specify the administrator’s username. Example: bin/magento admin:user:unlock admin The user account "admin" has been ...


1

I think it might issue at code. The data for the welcome message section coming from customer-data.In order to understand it, you have to check how Private content worked on Magento 2. Study the links: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/cache/page-caching/private-content.html https://webkul.com/blog/sections-magento-2/ The data ...


1

You can achieve the requirement by creating a module with following steps: Step 1: Create registration.php under app/code/STech/LoginProduct/registration.php with below content: <?php \Magento\Framework\Component\ComponentRegistrar::register( \Magento\Framework\Component\ComponentRegistrar::MODULE, 'STech_LoginProduct', __DIR__ ); Step ...


2

Create events.xml file app/code/Vendor/Module/etc/events.xml <?xml version="1.0"?> <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:ObjectManager/etc/config.xsd"> <event name="controller_action_predispatch"> <observer name="...


0

Override the layout catalog_product_view.xml and add a new custom block and phtml file. Create a custom block file and add code for getting customer sessions, if the session exists continue otherwise redirect from it. For adding custom block check that reference Add custom block and for getting customer session check reference Customer Session.


0

Wow, still relevant in 2020. Only thing that works for me is to leave cookie domains blank on both domain.com and dev.domain.com (I use non-www same as OP) and then set different backend admin urls via Custom Admin Path setting in admin. Obviously you have to do this via database if you can't access directly. Anyone comment on the dangers of leaving cookie ...


0

After a long debug and review migrated database I found the reason During migration I found that some of custom attributes were not there in migrated DB ( I don't know, Why !). Another important point is we should check the options for the select type attributes( options had not been migrated in my case). These 2 can be the possible reasons for the error.


Top 50 recent answers are included