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
Related
I got to work on a Typo3 page and I have to say I'm at the very beginning if it comes to TYPO3.
So I wanted to fix a bug and updated the plugin "fluidpages" from version 4.1.0 (I guess) to 4.3. That cause the "Oops, an error occurred!" in the backend and frontend, so I dont have access from that side. I still have the FTP login for the website. The version of TYPO3 is 8.7.18.
The errorcode I get is that one:
Could not analyse class:
"FluidTYPO3\Flux\Configuration\ConfigurationManager" maybe not loaded
or no autoloader?
Class FluidTYPO3\Flux\Configuration\ConfigurationManager does not exist
So does anyone know what I need to do?
From my research I think I need to update another plugins to make it back to work? And can I update them just by uploading them through FTP?
Thanks in advance!
Edit: After I tried to get the old version of the plugin running, I'm getting this error code from the log file:
Mon, 17 Feb 2020 22:59:56 +0100 [ALERT] request="fec23f8baf6dc" component="TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler": Oops, an error occurred! Code: 2020021722595594039a4d - {"exception":"TYPO3\CMS\Extbase\Mvc\Exception: The default controller for extension \"Flux\" and plugin \"Page\" can not be determined. Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php.
You can enter the Install Tool via https://example.org/typo3/install.php and start with Check for broken extensions. If that doesn't yield the extension in question, you can always manually change the PackageStates.php file and remove the extension you want to unload. Afterwards you should flush all caches through the Install Tool.
In the long term you should consider a few things:
Use a local development environment which mirrors your production environment. You can safely perform all steps without any risk here before deploying.
Use a deployment strategy/tool which allows for rollbacks. This allows you to quickly revert to a working version of your instance in case all other checks have failed. A simple but flexible solution is Deployer, you'll need SSH for this though.
Have you tried dumping autoload from Install Tool? Generally, it would help for the class not loaded problem. Otherwise, you may want to check the log at typo3/temp/var/log/ and find the errors in code.
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 :/
I'm working on win 7 and trying to get Zend Eclipse to run properly for a CakePHP project. But when try to access the plugin list via the welcome page I get this error:
A problem occurred while accessing the update site.
RemoteBundleDiscoveryStrategy failed with an error
Unable to read repository at http://downloads.zend.com/studio-eclipse/updates-extra/10_0/pdt_directory.xml.
Connect timed out
I've tried severalt solutions I found on the net but nothing worked. My proxy settings are fine since I can access all sites via the internal browser of eclipse. My guess is, that there is some restriction in the Windows administration that is keeping me from getting the plugin list.
When I try to update Eclipse the update window tries half an hour to contact the software site and after that I get this error message:
Some sites could not be found. See the error log for more detail.
Communication with repository at http://downloads.zend.com/studio-eclipse/updates/10_0 failed.
Connect timed out
Finally!!
The problem was that is were actually two problems. First one was that Eclipse wasn't saving the username and password for the proxy settings. After finally finding the eclipse error log in
"{eclipse-workspace}/.metadata/.log"
(there seems to be no way to view the file in zend-eclipse itself) I found out that Eclipse was trying to save the password-file into the Administrator's user directory but had no access. (Oh what a surprise)
Putting this into the "zend-eclipse-php.ini" worked for me:
-eclipse.keyring C:\eclipse\keyring.txt
After this was done I could finally save username and password for the proxy but still no connection. When I took another look into the error log I found this error:
"!MESSAGE System property http.proxyHost is not set but should be {proxyname}
!MESSAGE System property http.proxyPort is not set but should be {proxyport}"
and 4 more for https and socks. After googling this error I came upon a fixed bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=281472
where it states that maybe the proxy refuses SOCKS. So I cleared the settings for SOCKS and tried again and IT WORKED! Finally!
Hope this description can anyone else with these problems.
In conjunction with the failed installation of an extension (yag), the install tool is no longer available with the following error message:
PHP Fatal error: Class '\\tx_install_session' not found in /var/typo3_src-6.0.2/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4158
Any suggestions are welcome.
Ok, I'm one step further.
Assuming the backend login works, it helps to clear the cache via the flash button.
Which leads me to the question: Is there a way to do this in the shell in case the BE login is broken?
Remove/comment the bad extension in the LocalConfiguration.php file and then remove content of /typo3temp/Cache/ directory.
It will allow you restore to the state before the malformed installation.
I've created an Zend Application on a local machine, with Zend Server Installed on it.
However I am now looking to migrate it to a live host - Shared hosting with Parallel Plesk 8.4.0
I've moved everything up and at one point I was just getting a blank screen when loading the public folder.
I tweaked the public/index.php file to include Error_Reporting(E_ALL|E_STRICT)
So I am now getting an error from the script. The error I am getting is...
Fatal error: Uncaught exception 'Zend_Config_Exception' with message 'Error parsing /var/www/vhosts/eekonomics.co.uk/httpdocs/application/configs/application.ini on line 4
Theres more to the error. But alot of it seems irrelevant, If required I can post the rest.
Has anyone any ideas how I can get this setup and working, Its slowing me down big style :-(
Any help appreciated...
Changing the application.ini file from APPLICATION_PATH to the absolute path of the files seems to have fixed this.
I've got another error associated with PDO Adapter not being installed, but that is down to a server install issue rather than Zend / PHP.