(For those who came here from google as me, also for myself in the future.)
Just add some params to forward cron output to specific files, eg.
php -d display_errors=1 bin/magento cron:run >> /path/to/cron.log 2>> /path/to/cron.error.log
This is intentional by design. Files stored in the var folder should not be publicly visible to the world to access as it also contains various Magento logs/reports/files that aren't meant for users to see in the browser.
It seems like you would want to access a file like that via SFTP. If you absolutely must have it accessible from the browser, you might ...
A few question from my end and my observations.
How does the call to the method getImage() take place? I want to look at the entire flow. I need to understand how the $product is passed to this.
What is the implementation of the method getProductId()?
What is the name of the third party module that you are working on?
On which page are you getting this ...
Ok, After reading the topic from Magento DOCS, best way is to create the custom module and whitelist the resources and domains that are not harmful for your system.
Create Your module as Namespace/Csp in app/code folder
register you module by creating app/code/Namespace/Csp/registration.php
This error showing because of Magento Content Security Policies. You can check detailed info about Magento Content Security Policies at the Magento Official link.
If you don't want to use this feature of Magento then you can simply disable this module by the ...
Please check the following reported issue: https://github.com/magento/magento2/issues/30540 looks like an issue with attributes of type 'decimal' which are set to be searchable. My advice is to track those down and apply a workaround until this is officially fixed. Or simply unset those attributes to be unsearchable.
The link provides both the lead to track ...
It will be done by using this link
Magento 2.3.5 - Large table scconnector_google_feed_cl
and also need to disable the module and then run
php bin/magento setup:upgrade and php bin/magento setup:di:compile
then it will solved the issue.
I don't think this has to do anything with your rest api call. There might be some triggers left from the Magento_GoogleShoppingAds module which now are set to action when you save the product from admin.
The module is now discontinued as of 28.04.2020 when it was removed from all Magento versions (Reference https://docs.magento.com/user-guide/sales-channels/...
Ask the Webkul support team to resolve it for you and also try to find and replace \Magento\Framework\Locale\ResolverInterface with \Magento\Store\Model\App\Emulation because it says that whatever class constructor you are extending (preference) passing required Emulation instead of ResolverInterface