Attempt to install Magento 2 Stripe Payment module manually caused white screen - xampp

I followed the steps to install Stripe manually/with composer, found here:
Stripe Magento Module
After following all the steps, all that it has resulted in is a white screen, leaving me unable to access the backend to check if it's even installed properly.
My Magento 2.3.0 is installed on xampp, and checking through the file system, everything seems to have integrated properly, but I can't find a reason for it to have done this.

To debug what might be the issue you should enable developer mode via command line using below commands which might provide some hints about the issue
php bin/magento deploy:mode:set developer
Also you should enable php display errors in app/bootstrap.php by un-commenting below line
//ini_set('display_errors', 1);

Related

how can I avoid Package sebastian/resource-operations is abandoned, error while creating a new laravel application

I opened powershell and I run laravel new pp command to create a new application but I am unable to do so and this error occurs:
How can I solve it?
Make sure you have the latest Laravel installer installed, so see the documentation and install it again running composer global require laravel/installer as the documentation shows.
Edit
That is only a warning, it should not stop your Laravel build, and there is really nothing you can do about it (to hide it at least) as it is related to phpunit/phpunit, but it is just a warning.
Read this GitHub issue and you will see why it was abandoned and that it will be fixed when phpunit 10 is released (if you upgrade to it).

Windows 10 Magento 2.4 zip install on XAMPP has nowhere to agree to terms

I'm trying to get Magento 2.4 running using the production ready zip and I keep getting it to this point where I believe it's ready to start the setup process, but it's waiting for me to agree to the ToS. Unfortunately there's no agree button or instructions on if there's a file I need to edit. I just did a fresh install of XAMPP with PHP 7.4 and still have the same issue, and can't find a similar mention on google.
Is there supposed to be an agree button, do I need to edit a file?
Term & Agreement link leads here, still no agree button. Getting started link takes me to installation instructions for a Linux CLI
I saw I may still need to run the composer install command even on Windows, but I was under the impression the production ready zip already had the dependencies included. Where am I going wrong??
Update: I got composer running in windows terminal and it returns that there is nothing to install.
According to the official site docs, in a note at the top of the installation instructions for a CLI install of Magento 2.3:
"The Web Setup Wizard is being deprecated in Magento 2.3.6 and will be removed in Magento 2.4.0. After it is removed, you must use the command line to install or upgrade Magento."
So you cannot install Magento 2.4 without touching the command line.

Error "ionCube PHP Loader" after using composer. Magento 2 showing error. Please advise

I'm encountering this message:
"Site error: the ionCube PHP Loader needs to be installed. This is a widely used PHP extension for running ionCube protected PHP code, website security, and malware blocking.
Please visit get-loader.ioncube.com for install assistance"
I'm getting this message after using Composer/Magento commands (update, upgrade, compile, and deploy). I'm running a localhost install of Magento 2, which is now showing the following message.
"There has been an error processing your request
Exception printing is disabled by default for security reasons.
Error log record number: 629950493790"
I have looked for other solutions online but these solutions didn't fit. One solution seemed too risky, which was to change the name of my php.ini file to .php.ini (note the dot before). One solution advises to install a version of ionCube with the right PHP version, but since I'm working with PHP 7.0.* I'm not able to find that version of ionCube. I have also looked for the error that matches the error number I was given, but no luck.
I encountered these errors while trying to install a theme. I am new to Magento so I followed a guide that gave me a list of composed commands to go through. I selected the new theme through my admin's Configuration > Design, but noticed the design didn't really push through (cache or compile issue I think? I'm learning, if slowly.) I tried the command "composer update" but got my login credentials wrong.
My environment: Windows, XAMPP, PHP 7.0, Magento 2.2.8
If there are any resources that can help me, please let me know about them, incl. books. I really don't know how to proceed.
C:\xampp\htdocs\magento2> composer update
I want to be able to push the theme's visual changes, and safely and correctly clear the cache and update the files as needed.

Errors running Laravel Dusk

I just discovered Laravel Dusk, and I was excited to use it in my project. However, it can't seem to get it to work. I followed the Laravel Documentation to install Dusk. When I run php artisan dusk in the terminal, I get
[Symfony\Component\Process\Exception\RuntimeException]
TTY mode is not supported on Windows platform.
I found this (https://github.com/laravel/dusk/pull/13/files) which is supposed to fix it I think, but I still get the error.
Also, I attempted to run the Dusk tests through PhpStorm following the accepted answer here (https://laracasts.com/discuss/channels/testing/dusk-via-phpstorm), but I get a Class config does not exist error. Many people said that this caused by a space in the .env file, but that is not my issue.
Can anyone help me figure out what is going on with Laravel Dusk in my setup? My Laravel project is 5.4 and I'm using Laravel Dusk 1.0 and PhpStorm is 2017.2.1
You can install chromedriver into windows on your own, and try not to use the version that is shipped with laravel dusk. Remember that, your chromedriver version needs to match your currently installed Chrome version, and when Chrome gets updated, then you need to update/reinstall chromedriver manually again. Hopefully it does not happen too often, and when there are updates, you benefit from using latest versions, which I find really nice :)
Download it here.
After installing chromedriver, you need to start it from command line (just issue command in your download/install directory chromedriver) or add it as service (which I do not prefer, cause I want to have control of which service is running on 9515 port).
Finally you need to comment out // static::startChromeDriver(); in your DuskTestCase.php, which tries to start laravel dusk included chromedriver, cause in this case, you are already running one.
Run dusk tests again and all should be working fine.
I don't know what your system setup is, but I am using this workaround on windows 10 with Laravel 5.5, dusk 2.0, which still causes problems, when chrome gets updated.
BTW. Just to mention. This also works with CI workflows using docker. You can read more about it here

Undefined AITOC function at app/code/local/Aitoc/Aitoptionstemplate/Model/Observer.php on line 11

I copied the website files of a live magento website to my local machine. I try to open the home page and a blank white screen turns up.
In the apache2 error log, I find the following line:
PHP Fatal error: Call to undefined function kYESppcDEoBrEZyw() in .../httpdocs/app/code/local/Aitoc/Aitoptionstemplate/Model/Observer.php on line 11
The culprit line is:
if(Aitoc_Aitsys_Abstract_Service::initSource(__FILE__,'Aitoc_Aitoptionstemplate'))
{ kYESppcDEoBrEZyw('e71e3cbbed8235b2be55dfb8db045b91');
and the other bracket closes at the end of the file.
It seems there is an extension called Aitoc custom options template installed. That's fine but what is the purpose of the strangely named function? And how is it working on the live site?
Any leads will be appreciated.
We need to be careful here since the website uses 3rd party extensions and the extension protects its license - it doesn't allow using the extension without installing the license first and throws the above error.
So you'll need to install the license on the local/dev server first before starting work on the website. You can also disable the extension(for AITOC) and get the website working by following the instructions at:
http://www.aitoc.com/en/magentomods_custom_options_templates.html#docs
I did disable it and I am able to run the website on the dev server.
I had the same issue.One more extension was installed in my site "Custom Product Preview".
So some files were missing while installing the extension.
When we uploaded the same missing files.Then refreshed the admin section.It asked for the license information after providing license information everything worked fine.
So be careful while installing the extension.
Also install the license carefully.
For me "/app/code/local/Aitoc/Aitsys/etc/compilation.xml" was also missing.

Resources