While submitting an extension compatible with Magento 2.x, it failed the Technical review, and the test reports show this error:
Command:
Varnish PageCache Test
Output:
Cannot update product price.
Response:
{\"messages\":{\"error\":[{\"code\":500,\"message\":\"Server internal error. See details in report api\\/1143348353039\"}]}}
From the above message, if am not wrong, am supposed to check in var/report/1143348353039 file but it's Magento's server, not sure how to get more details about the bug.
Have been on this for some time now, had posted on Magento forums without much avail. This particular error is a result of the command "Varnish PageCache Test".
Inorder to reproduce the error at my end, tried installing and configuring varnish, but I don't see any tools which use such a command which leads me to believe its a user-defined one.
Any inputs on how to debug/solve this, leading to a successful extension submission, will be appreciated, thanks in advance!
Update:
Finally got a response for the ticket raised in Magento MarketPlace - They sent the error stack - was pretty straight forward from there. Had missed exception handling at a point :/
Related
I'm getting this error:
Warning: Event xstate.after(1000)#waitingMachine.batchingNodeMutations"
was sent to stopped service "waitingMachine". This service has already reached
What can I try? Also I'm getting eslint errors:
import/no-extraneous-dependencies", "import/no-absolute-path" & "global-require" are giving errors since an update last week....
I was also getting this error. There are two open issues for it on the Gatsby github:
Browser won't hot reload re-compiled sources, broken after gatsby#2.24.9
Warning: Event "xstate.after(1000)#waitingMachine.batchingNodeMutations
It looks like the problem was introduced with PR #25815. Rolling back to Gatsby 2.24.9 fixed the problem for me and looks like it fixes it for most others, but your mileage may vary.
Latest update gatsby#2.24.57 should fix it!
I am using php-cs-fixer for code formatting in Netbeans 8.2. When I try to format one file, it shows the error
Files that were not fixed due to errors reported during linting after fixing:
I searched for the fix in many websites, but couldn't get this fixed. Is there any way to fix this? I tried with both php-cs-fixer 1 and php-cs-fixer 2.
The error message means that PHP CS Fixer loaded some files from drive, apply changes on them, and then realised that files are not valid anymore (invalid PHP syntax) after those changes, thus it decided to not save it. That's one of the safety mechanism of PHP CS Fixer to not break your project.
This means that you have found an issue in PHP CS Fixer itself.
Please, verify you are using newest release, maybe the bug was already fixed!
If not, please consider to expose your configuration file (if any) and content of files you got listed at https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/new !
There is also an option to see what happen in progress.
$ ./vendor/bin/php-cs-fixer fix src/ErrorFile.php -vvv
The --verbose option will show the applied rules. When using the txt format it will also display progress notifications.
NOTE: if there is an error like "errors reported during linting after fixing", you can use this to be even more verbose for debugging purpose
-v: verbose
-vv: very verbose
-vvv: debug
I am getting below error in magento 2 local system:
We're sorry, an error has occurred while generating this email.
It is not showing me the sample data installed in catalog. Please help me out to get solution of this problem.
Regards,
Rakesh Kumar
The first thing you need to do is go to your .htaccess file. Uncomment
SetEnv MAGE_MODE developer
The error message is 90% of the time misleading and most likely you have an xml parsing issue. Either way turning on the developer environment and clearing the cache will pull the error.
Without seeing your error log it'd be hard to give an exact diagnosis. Some users will say sendmail will fix this error but generally this is because the error is trying to be emailed to you and that is because you are not in the correct developing environment to debug the issue. This could be because you are in default or production mode which is not ideal for fixing issue.
The sendmail module is meant to allow a site to operate and if any issues do occur with the site then the developer can be notified and hopefully the error hasn't caused a full site rendering issue. This way a site can still operate unbeknown to users and the issue can be resolved by a qualified developer behind the scenes.
This error is quite misleading. In my case an error in MySql query was causing this.
You should enable developer mode the get the exact error.
php ./bin/magento deploy:mode:set developer
In My case issue get solved by giving permissions to directory pub/media/catalog/product/
Enable developer mode using command line php bin/magento deploy:mode:set developer
Clear cache using command line php bin/magento cache:flush
Reload the frontend page
After reloading the page the message will change to
Error filtering template: Unable to write file into directory \C:/xampp/htdocs/Magento/pub/media/catalog/product\cache\f073062f50e48eb0f0998593e568d857/m/b. Access forbidden.
Follow this link to fix Magento 2: Unable to write file into directory. Access forbidden
Clear cache
Reload the frontend page again
If you see another message after enabling developer mode you can search for it
In my case it was missing php-gd extension on my machine.
This was on my exception log (magento_root/var/log/exception.log):
main.CRITICAL: exception 'Exception' with message 'Required PHP extension 'gd' was not loaded.' in /var/www/html/magento2/vendor/magento/framework/Image/Adapter/Gd2.php:620
Solved by installing php-gd library on my Ubuntu machine with the following command:
sudo apt-get install php-gd
If you want to install for php5.6 then you may run:
sudo apt-get install php5.6-gd
This can be for any error occurred in the page. The notice is different. The notice is given when system tries to send error email to administrator and failed while in Production mode.
For actual error one should enable developer mode and enable display error in app/bootstrap.php and checking error logs. It can be any error like php or mysql.
ini_set('display_errors', 1);
Thanks
Please check your /var/log/exception.log
This is issue raised because your product does not upload. so check your database or upload your sample database again .Let me know what error in exception.log
I installed the Redmine-Mylyn-Connector in Eclipse and had our admin install the Mylyn-Plugin for Redmine. The connection to Server seems to work:
When I try to add a query, I receive a Server Error:. Unfortunately no more details are available.
What are potential reasons for this error, and how can I solve the problem?
There might be useful details in the Error Log. Open the Error Log view (Alt+Shift+Q then L, or use Window > Show View...). I would clear the log first (using the red X button in its toolbar), then reproduce the error. You should see error details in the Error Log which might point you to the source of the problem.
Like the header says I am getting an error when trying to work with Umbraco(6.2.1) back office
This is the error:
I already talked with goDaddy support, they says everything is OK from their side.
I flowed every "tutorial" I could find regarding this.
This is an error I am seeing in Goggle Chrome Console:
I am now clueless about what to do next.
*every help will be much appreciated.
This is the config folder:
This is the -- file -- it self
The error says you have an incorrect TinyMCE configuration. It will be a problem with that component and not the host. There is a [Umbraco support ticket] which suggested this may be fixed in release 6.2, but also a [forum post] where its said this could happen in all versions, when a style-sheet which is registered in the database is deleted.
Are you sure all the files are present in the deployed /config/ folder? Check that there is a /config/tinyMceConfig.config file present.