I built a system with laravel-admin and guzzle. I send api requests to Shopify with Guzzle and everything works fine on my local environment. However, when I try to create a product in production , it gives me this error.
IDN conversion failed
I looked into it on Google, and it seems Guzzle is giving me this error because I get the error only when I try to create the kinds of products that I sync with Shopify with guzzle.
There is not much information about the error on Google, and I am lost as to why it is happening. Has anyone experienced the same issue?
Could you please add PHP and Guzzle versions to the question? I'm one of the authors of this feature, and (unfortunately) there were some issues related in specific cases. But to say something I need more details.
Generally, try to upgrade to the latest version. Things probably should be fine with the latest Guzzle 6.5.2.
I've also suddenly started running into this issue. I have PHP version 7.2.30 running on the server and cURL version 7.19.7.
It worked fine yesterday, and wasn't working properly this morning. Nothing has changed, other than I upgraded Laravel and all dependencies. However, I think the particular code in the Guzzle Utils.php file where this error is being triggered has been around for quite a while. I tried downgrading Laravel to versions from much earlier this year, and Guzzle stayed the same.
We recently updated our web server, but that didn't make a difference to the PHP version nor should it have affected configuration.
This error I'm getting right now is baffling and I have no idea how to troubleshoot it.
EDIT: I found a simple work around for this problem through server configuration. After digging through the codebase in Laravel I noticed that Symfony provides polyfils if the intl extension is not installed. As such, I just disabled the intl extension on the server, which caused it to use the polyfils, which resolved the problem for me.
I checked first to see what version of ICU the intl was using, and it was an older version and hence the reason I got the errors.
So if you are running Laravel or anything else Symfony based and are having this problem, this could be a simple solution if you can't upgrade to a newer version of PHP for whatever reason. We are running a Plesk-based server, so we are dependent on them providing PHP and all the various extensions and we can't control their upgrade timing.
If you don't have that problem, then your other option would be to upgrade your PHP yourself and ensure the intl extension is up to date and compiled against a more current version of ICU.
Related
I have a Laravel 5.1 install that I am upgrading. I meticulously followed the instructions available at https://laravel.com/docs/5.3/upgrade#upgrade-5.2.0 for the upgrade, including removing Illuminate\Foundation\Providers\ArtisanServiceProvider and Illuminate\Routing\ControllerServiceProvider from the config/app.php file (I am stressing this point, as googling for this issue has suggested this in every response).
Despite this, I am still getting this error when I run composer cache:clear
[Symfony\Component\Debug\Exception\FatalThrowableError]
Class 'Illuminate\Routing\ControllerServiceProvider' not found error
and see this error in my browser:
FatalThrowableError in ProviderRepository.php line 146:
Class 'Illuminate\Routing\ControllerServiceProvider' not found
Thinking that perhaps references to these classes were being cached, I checked bootstrap/cache/services.json and removed the references from there as well and then ran composer dump-autoload but I am still getting this error.
I also made sure to copy over example config/app.php from Laravel 5.2 clean install example here: https://raw.githubusercontent.com/ziyed/Laravel-5.2/master/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php
I have read through the similar threads on StackOverflow and Laracast and tried tried to use the advice contained inside, but nothing seems to work.
Any help would be greatly appreciated. For reference, my dev setup is running on a local XAMPP stack under a Windows 10 OS. The other environments are remote, using a traditional LAMP stack with Amazon Linux 2. I was trying to do the upgrade locally.
Illuminate\Routing\ControllerServiceProvider is not present anymore.
When I recently had to upgrade the same versions as you, I had to run composer update before and after removing Illuminate\Routing\ControllerServiceProvider::class and Illuminate\Foundation\Providers\ArtisanServiceProvider::class to make it work. Also worth to mention you need to clear bootstrap/cache. It worked for me.
Edit: i noticed now you tried the last step partially as well. You can remove all php files from cache.
I am closing this question, not because I found an answer, but because continuing down this path just didn't pass a cost/benefit analysis. After upgrading to 5.2, the next upgrade would be 5.3, and the breaking changes between 5.2 to 5.3 is a lot higher than between 5.1 to 5.2. After some thought, it was obvious that the better approach would be a fresh install on my target version, and then start porting over each module in my project by copying over the views, updating the routing, and making changes to the controllers and middleware as needed.
Or just using Laravel Shift.
Thank you to everyone who chimed in with suggestions!
I want configure elasticsearch(ES) with Drupal
to integrate ES in Drupal following this tutorial
In order to install ES followed steps mentioned on this link
Drupal-8.8.4
search api version-8.x-1.15
Elasticsearch drupal connector-8.x-6.x,also tried 8.x-7.x but no success
After added modules can see this below screenshot
But when I want enable added modules as mentioned in steps,got below error
the website encountered an unexpected error. please try again later.
Referred this stack question
Is it due to compability issue or how to resolve issue
any leads will be appreciated?
Adding this answer to support community.
Yes, indeed it was version incompatibility issue between drupal, elastic-search and drupal-elasticsearch connector and search api..
Tried number of combinations by installing modules manually but keep getting below error.
the website encountered an unexpected error. please try again later.
Used composer tool to install modules which work exactly like maven in java project.
composer require 'drupal/search_api:^add version accordingly'
composer require 'drupal/elasticsearch_connector:^add version accordingly'
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.
I had a simple query but don't know how to work on it, I am working on two Different Project one is in Laravel 5.6 and other is in Magento 2.1. Now my problem comes when i am trying to install both on the same server because my Laravel support PHP 7.1 and i am using a theme Magento(Porto) which support 7.0.
I want to know how to install both on my server. I have already a built side of Laravel. I had to check some google it gives me multiple PHP version related help. but how to implement it.
Thanks
I am not sure which development server you are using at your local machine. However, you can have more than one PHP version.
You can switch between versions. Refer below.
Perhaps, this may help you.
Multiple PHP versions in Wamp under Windows 7
If you are using Ubuntu try below,
https://www.tecmint.com/install-different-php-versions-in-ubuntu/
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