Please, i have tried to upgrade my module to make the xml changements functional. But, i have recognized that none changement has been done.
I think that the action of upgrading is not working.
Please who can hepl me
Restart your server and upgrade your module then it will work.
Related
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 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.
i have some error with my application symfony. one error is Unsupported declare 'strict_types'. Please help me to resolve that.
My php version is 7.0.12
My symphony version is 2.7.16
My Ocramius/proxy-manager version is 2.0.3
this is the link to my server : http://www.kossa.cm
I actually encounter the exact same issue and the only ugly fix I could find to just pass through (without fixing it) is to remove that vendor/ocramius/proxy-manager folder and do not run a composer update (that would install the proxy-manager back).
As I said, it is not a proper fix, I'm trying to solve it now.
If you found any kind of information about it, please share it with us ;)
--Edit-- Are you using wamp ?
to solve your problem, downgrade your php version to 5.6, because ocramius is not compatible for the momment with php 7.0 and above!
I am trying to upgrade Magento 1.3.2.4 to 1.7 using Magento Connect Manager via 'magento-core/Mage_All_Latest' extension key to install. But I found the following error and I don't know how to reslove it.
Error -
Exception caught:
Warning: include(/N91nq64igkwi8oxu.php): failed to open stream: No such file or directory in /var/www/projects/spacecenter/lib/Varien/Autoload.php on line 93
If anyone faced this kind of error, please help.
Thanks in Advance!
I strongly recommend this upgrade guide from Turnkey - worked perfectly for me.
Please don't expect that everything works or looks the same once you've upgraded to Magento 1.7. Depending on what features or extensions you use, quite a bit of work might be needed until you're done. So don't do this on your live system. Better duplicate it to a development environment and test the upgrade there.
Using the seach form in the shop outputs the "Whoops, our bad..." page.
I've seen similar questions but rebuilding the index is not solving the problem.
The search form sends to http://...//catalogsearch/result/?q=... and fails. But if I use the advanced search url http://...//catalogsearch/advanced/result/?name=... it works fine.
Any idea of what can be causing this behaviuor. The shop has recently been upgraded from magento 1.5.X to 1.6.0 and then to 1.6.1
thanks
Something similar happened to me and the problem was that the upgrade wasn't completed.
Make sure you've no dependencies problems or conflicts when upgrading.
If you get errors with dependencies, try uninstalling non core modules and then try to install magento latest again. Make sure the errors disappear.
Once the upgrade is correct you can re-install uninstalled modules, if they work in the latest magento version.
Just in case. Reindex from terminal. I had the same problem. Reindexing from the backoffice wouldn't work, but after reindexing from terminal, everything went back to normal.
php /path/to/magento/shell/indexer.php reindexall