magento-2 | PAYONE Payment Extension for Magento | Ecommerce library

We're running our site on Magento CE2.4.1. Currently, checkout fields have the following attributes:

I've installed the magento v2.4.1 by downloading and uploading the zip file content and apply simple commands to install the magento.

I'm new to magento and don't understand much, So please read through the below and I've tried my best to explain the issue.

Use the below command to install magento:

I need to change the product price in all the pages, for all the operations... on catalog (product listing), cart, etc... after all the catalog rules are applied. I've created a plugin for Magento\Catalog\Pricing\Price\FinalPrice on frontend/di.xml

I have been searching high and low for this answer, maybe it is a dead-end road I don't know. I am running Ubuntu 20.04 and I currently have this bash_profile:

I am new to Magento and am more used to scripting in PHP than doing Linux commands.

I tried setting up Cron Jobs for Magento as outlined here https://www.properhost.com/support/kb/41/How-to-Configure-Magento-2-Cron-Jobs but am getting an error email saying /bin/bash: php7: command not found

Ifound other articles that were leaving the version of PHP out of the command so it would be something like php -f /home//public_html/bin/magento cron:run | grep -v "Ran jobs by schedule" >> /home//public_html/var/log/magento.cron.log, this is not emailing me any errors so thought I might have gotten somewhere but my site is still not reindexing.

Any ideas what I should do in this case?

Thanks

It is the first time that I ask a question on this community that is literally saving my life everytime.

Now I get to the point, being that I have searched for this all over the internet with no result - so I hope this post will get useful for someone else in future.

I am using Magento 2.3 with the theme Porto in local 127.0.0.1, but when in Default and also Dev mode I run the prompt command php bin/magento setup:di:compile I instantly get this output:

C:\xampp\htdocs\magento2>php bin/magento setup:di:compile Compilation was started. Repositories code generation... 1/7 [====>-----------------------] 14% 2 secs 54.0 MiBPHP Fatal error: Declaration of Temando\Shipping\Model\ResourceModel\CollectionPoint\OrderCollectionPointRepository::save(Temando\Shipping\Api\Data\CollectionPoint\OrderCollectionPointInterface $collectionPoint) must be compatible with Temando\Shipping\Model\ResourceModel\Repository\OrderCollectionPointRepositoryInterface::save(Temando\Shipping\Api\Data\Delivery\OrderCollectionPointInterface $collectionPoint) in C:\xampp\htdocs\magento2\vendor\temando\module-shipping-m2\Model\ResourceModel\CollectionPoint\OrderCollectionPointRepository.php on line 24

Fatal error: Declaration of Temando\Shipping\Model\ResourceModel\CollectionPoint\OrderCollectionPointRepository::save(Temando\Shipping\Api\Data\CollectionPoint\OrderCollectionPointInterface $collectionPoint) must be compatible with Temando\Shipping\Model\ResourceModel\Repository\OrderCollectionPointRepositoryInterface::save(Temando\Shipping\Api\Data\Delivery\OrderCollectionPointInterface $collectionPoint) in C:\xampp\htdocs\magento2\vendor\temando\module-shipping-m2\Model\ResourceModel\CollectionPoint\OrderCollectionPointRepository.php on line 24

I have tried to disable the module, but nothing happens; I have tried to run via composer the MageFix downloaded from Github but it's not good for Magento 2.3 (I think).

Fix

According to the suggestion of TGR_dev, this is how works the complete fix to this error.

In Vendor folder, I have deleted the folder Temando, then I saw that Magento stopped working - it's normal;

I followed the "command line update" at this guide and reinstalled Magento: https://blog.magestore.com/upgrade-magento-2-3/#a3

Edit

Be sure to remove MageFix from the app/code folder if you uploaded it or it will give you error

Hope this will help!

I have a Magento 2 website with two stores. At the moment, I can edit the global website and his content is applied to both stores.

What I want to de is replace that behaviour in order to get one robot.txt file by store.

But I really have no idea how I should do that.

Currently, if I go to the back office Content > design > Configuration > (Store Edit) > Search Engine Robots

All the fields are disabled in the stores and can't be modified

But If I go on the global Content > design > Configuration > (Global Edit) > Search Engine Robots, of course, I can modify.

I also have 3 robots.txt files on my storage, but none of them seems to be matching the information saved in the global search engine robots configuration

• src/robots.txt
• src/app/design/frontend/theme1/jeunesse/robots.txt
• src/app/design/frontend/theme2/jeunesse/robots.txt

I found these two links...but none of them helped me : https://inchoo.net/online-marketing/editing-robots-txt-in-magento-2-admin/ and https://support.hypernode.com/knowledgebase/create-robots-txt-magento-2/

The first one tells me that If I have a robots.txt on my storage it should override the configurations...but looks like no considering I have robots file and they aren't showing when I go to website/robots.txt. I only find again the one in the global configuration.

The second one tells that saving the configuration should save the robots.txt file on the storage...but once again...that's not what is happening.

Thanks for your help, let me know if there is pieces of code I can show ? I really don't know which one at this point.

In Magento 2, I have a custom login form in Header.

If a customer is on the product page for eg :

http://www.testwebsite.com/catalog/product/view/id/10

and login from header form then customer should redirect to the same product page instead of Customer Dashboard.

I have tried plugin code from this link.

Below is my custom header form code -

I have tried to add the trust pilot extension following this guide.

However, when it comes to the readiness check in the extension manager, there is a failure on "Check Component Dependency" without any details on the conflict. The guide seems to indicate that the error would be shown but that's not the case (please see image below)

There does not appear to be anything in the exception log and I'm not sure where to check for the details regarding the conflict. Any recommendations on where to look would be really helpful.