How to deploy your Magento 2.x in AWS LightSail
Clone from your repository, importing your database and setting up to go live Creating a new vanilla Magento 2.3 instance in AWS LightSail is pretty easy and straightforward, with just…
Then let me think about it and come back to you with a proposal. I’ll do my best to offer you a solution which will suit your needs, fit your budget, make use of the best technologies and provide optimal results.
Until then, take a look at how others benefited from my services, in my portfolio.
Clone from your repository, importing your database and setting up to go live Creating a new vanilla Magento 2.3 instance in AWS LightSail is pretty easy and straightforward, with just…
Quick solution to move website on new host and keep email on old host Do you want to move your website to a new host, but keep email on the…
One reason for this, other than the ones already mentioned in the numerous stackexchange posts, can be having an incorrectly referenced resource loading on the current page, which causes the…
After Porto theme removal (which includes Smartwave Megamenu), when accessing Categories page in the backend, you get an error report which contains: This is because the extension added new category…
Debug tools DPCIManager https://github.com/MuntashirAkon/DPCIManager/releases Piker-Alpha ssdtPRgen.sh Look at the forks graph if you’re looking for the latest additions: https://github.com/Piker-Alpha/ssdtPRGen.sh/network
Magento 1.x custom customer attribute not visible in REST API2 Attributes ACL, while custom customer address attribute is visible. To debug why attribute does not show up on the ACL…
Insert attribute option and return option id in Magento 1.x This article presents three methods to add attribute options in a loop and return the inserted option_id correctly. If you…
The Hardware Recommendations Macbook Pro 15″ Anything between 2012-2015 will perform good with a Quad Core CPU (i7) and 16GB of RAM. Regarding the latest 2016 model, you can find…
This error message is caused by a Magento 1.x bug that has always been there (at least up to current 1.9.3.1 version), but few gave it attention or observed it.…