Download the PHP package nofrixion/magento2-payments-module without Composer
On this page you can find all versions of the php package nofrixion/magento2-payments-module. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download nofrixion/magento2-payments-module
More information about nofrixion/magento2-payments-module
Files in nofrixion/magento2-payments-module
Package magento2-payments-module
Short Description Nofrixion online payments for Magento 2
License MIT
Informations about the package magento2-payments-module
Magento 2 Module for Nofrixion Payments
NoFrixion.com online payments for your Magento 2 store.
System Requirements
The NoFrixion payments module is designed to be compatible Magento 2.4.4 onwards (note, support for the 2.4.0-2.4.3 release line ended on November 28, 2022).
For the underlying Magento dependencies, please refer to the Magento system requirements.
Installation, Updates & Removal
It is recommended to use the composer
PHP package manager for production magento deployments. composer
can be used to install, update and remove the NoFrixion magento 2 module.
Installation
Install the NoFrixion payments module using composer by running the following commands:
* it is also possible to install the module by downloading the ZIP file from github and extracting it to {magento-install-directory/app/code/Nofrixion/Payments
. Then run the last four commands in the sequence above to enable the plugin. This method is NOT recommended for production environments.
Note, there are several third-party caching products that may be deployed in your Magento environment and prevent the payments module from appearing in the Magento administration interface. If the Nofrixion Payments module is not visible after following the above steps, most third party caches will be cleared by restarting the apache server.
Updates
If you have installed the payments module using the composer command specified above, you can update the plugin using composer. From a shell session on your magento server, run:
If you are updating a production environment, we recommend placing the store in maintenance mode first.
Removal
To remove the payment module:
- Login to the Magento storefront administration panel and:
- Disable the module in the
Stores -> Configuration -> Sales -> Payment Methods
section. - Go to the cache management page and refresh any caches with a status of 'invalidated'.
- Disable the module in the
- Open a shell to your Magento server and:
- Disable the module at server level by running
php bin/magento module:disable Nofrixion_Payments
. - Run
composer remove nofrixion/magento2-payments-module
. - Apply database updates by running
php bin/magento setup:upgrade
(for production, also add the parameter--keep-generated
or you will need to runphp bin/magento setup:di:compile
again.)
- Disable the module at server level by running
- Depending on how caching services are configured on your Magento server it may be necessary to restart the application stack at this point.
Configuration
See the NoFrixion guide on configuring the magento2-payments-module
Known Issues
There is a known issue where PayPal buttons render over the tooltip. This has not been directly fixed in the plugin as it would would involve applying styles to another vendor's module. Affected merchants can resolve this issue by applying the following style to the header section of the Magento storefront theme via Content -> Design -> Configuration
.
Troubleshooting
If something goes wrong during installation or during deployment, just follow the typical Magento 2 module installation steps. The NoFrixion Payments module follows all Magento 2 standards and should not be any different.
- Switch or make sure you are in developer mode
- Remove all temporary files to make sure your latest changes are being applied. This is done by emptying the cache (typically in
MAGENTO_ROOT/var/cache
or your cache server, like Redis) and the files generated inMAGENTO_ROOT/generated
andMAGENTO_ROOT/var/view_preprocessed
. - Try again
- If this is a production server, make sure you switch back to production mode