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.
Related
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'm in the middle of moving a site to a new server. All files and database contents have already been transferred. The pages I've Googled about moving a Joomla site to a new server have all said that all I'd need to do after the move is make sure that configuration.php was using the new database's connection details. I've done all of this but for some reason, Joomla can't seem to detect my components. I can't even log in to the administrator site because logging in just throws an error (specifically: "mod_fcgid: stderr: PHP Fatal error: Call to undefined method stdClass::onAuthenticate()").
Are there any other settings or configuration files I can check to fix this? Thanks.
I'm trying to install the Zend skeleton application and when I run the command "php composer.phar create-project --repository-url="http://packages.zendframework.com" zendframework/skeleton-application path/to/install" I get an error about magic_quotes being deprecated. I'm using GoDaddy servers and I turned magic_quotes off in my php.ini file. Any ideas what could be causing the problem?
Based on the error it looks like my the file in /web/conf/php5.ini has magic_quotes On for some reason. It's a read only file that I can't change. Shouldn't the file in the root of my server be changing the setting in it?
When I run phpinfo it shows magic_quotes_gpc and the other magic_quotes all as Off. What could be causing this error message in ssh?
Could it be because my GoDaddy hosting account is running PHP 5.3.24? The minimum on the Zend site says 5.3.3
I installed LAMP on Ubuntu 12.0.4 LTE. Then I installed phpmyadmin. Everything was good. I used phpadmin to do lots of DB administration....
Then I installed Zend CE server. Now, phpmyadmin throws a blank page. No login screen.
So, I reinstalled my VPS in the same sequence again. No luck. Same behavior.
This time, I installed Apache, Mysql, PHP and Zend server in that order. Then I installed phpmyadmin....Unfortunately, still blank page on phpmyadmin.
Any help?...Thanks in advance.
First, for all those that posted their suggestions to my above issue, thanks!.
Of course, I had to dig deeper into forums and threads to find the specific root cause and solution for this issue.....and after spending few hours...finally, I resolved it!. Thanks to the following bug discussion link on php.net.
https://bugs.php.net/bug.php?id=25876
I tired many suggested fixes there but they didn't help. The suggestion that finally fixed the problem was pasted below ( so that let the credit go to the right owner):
[2011-03-03 12:18 UTC] comments at htmlcompressor dot com
If you are gettin the following error:
"Fatal error: session_start(): Failed to initialize storage module: files (path: ) in...."
Make sure that you have setup the session save path in your php.ini:
session.save_path = "/tmp"
which seems to be disabled by default.
I swear using Open Source software is tough!. I have spent whole day on this issue alone. My goal was to build some software and I have yet to get to it!!.
There is a problem that I can't resolve. I am developing a project and test on my computer which runs as expected. But when I move the project to testing server, which also has Zend Server CE, it gives blank page. Display errors function is ON and I put try catch at the very begining, but it still shows a blank page. When ever I write "exit;" command at the end of related view script, page works normally!
What can couse this problem ?
Thanks
My first guess would be a problem with your include path. That's a very common issue when deploying from one server to another.
But clearly it's some kind of fatal error. I haven't used Zend Server, but in Apache I'd look in the error_log, since any fatal error output ends up there. Does Zend Server have something similar?
...aha, Zend Server seems to have a log, accessed through Monitor > Logs in the admin interface. Try looking in the PHP Error Log for reports of fatal errors.