Please I need some help with a Prestashop issue. I run a Prestashop 1.7 on an OVH shared hosting. Everything worked well until yesterday morning but then I couldn't access the backoffice anymore and got an error 500 instead. The frontoffice still works and I'm still receiving orders.
Informations :
I didn't upgrade anything, neither the website nor any module.
When I enable debug mode (define.inc.php), the backoffice works again but the frontoffice got an error : front office error. The error changed when I tried to regenerate the .htaccess from the backoffice.
On backoffice I got that error in debug mode :
Notice à la ligne 81 du fichier home/ateliertfy/www/app/cache/dev/smarty/compile/0a/c8/26/0ac82623c45234c79ace80cb79d62160793b16f3.file.list_content.tpl.php
[8] Undefined index: color".
I tried to clear the cache but I have no var/cache folder.
I tried to delete the app/cache/prod/smarty/cache and app/cache/prod/smarty/compile folders but that didn't change anything.
I tried to regenerate the .htaccess but it didn't change anything either.
When I checked on my OVH account, I noticed they turned my hosting into php 7.3 (beta) version without noticing me, a few days ago. I went back to the previous version (7.0) but it didn't change anything.
Any clue ?
Thanks in advance for your precious help.
Lyah
Based on your error it seems like template error.
You probably have some part of page that serves the products list.
In this list, you call the product color and if you have not assigned any color the site breaks.
Try to access the contact form for example (where there is no product) and let me know if you keep seeing the error.
Related
I have the following problem:
After trying to change the entry point to my website in the backend of my TYPO3 system (by using the site config), I cannot access neither my backend nor my frontend of the website anymore. Whenever I try to access the site it says "Oops, an error occurred! The parsedUri "https://" appears to be malformed".
What I have tried, is accessing the config.yaml on my webserver to change the baseURL inside of the config, but no matter what I change it to, it doesn't seem to work, as I always get the same error message even uploading the changed config file (what I mean by that is, that the text inside the error message doesn't change to reflect the new url but stays "https://").
I hope that someone who is more experienced in TYPO3 can help me solve this issue. I couldn't really find a working solution after extensively searching so far. Thanks a lot in advance.
After changing the yaml file of the site configuration, you need to clear all caches, either via the install tool (yourdomain.tld/typo3/install.php) or by deleting all files in the directories var/cache/code and var/cache/data.
I am starting the process of updating TYPO3 to higher versions (from the base 6.2.X version). The process of updating to version 7.6.X was ok. Being logged in 6.2 version, I switched to version 7.6 and updated elements in InstalTool, plugins etc. The problem appears when I log out. After entering my login address, I have a blank page - white page without any code. I can log into InstallTool but unfortunately not to BE.
The [FE] page works fine after the update. Any ideas what went wrong or where is the problem?
first: blank page normally means: there is an error but all error information was disabled.
If you just changed the source it might be a mismatch between cache and source: clear all caches in Install Tool.
Also your first step should be look into the server log.
If that does not give enough hints enable all debugging and error information in the Install Tool.
If that still gives no clue: disable all extensions (remove from PackageStates.php and don't forget to clear caches afterwards, maybe manually too)
I was fixing things on a not well-maintained typo3 installation and it resulted in blank pages of frontend, backend and install tool.
I wanted to fix extensions because the powermail-extension was not working anymore even after updating to latest compatible version (tried emptying cache and database compare).
I deactivated an extension "compatibility6" to see if it was interfering and since then all pages have been blank including Install Manager. I reactivated the extension via PackageStates.php, emptied the cache but it did not change anything. I was not able to see any error messages even though I set the parameter in LocalConfiguration.php which made it hard to try to find out what is wrong. Then I restored a backup using vmware. Still, backend and frontend are blank.
I am using Apache and Typo3 7.6.23.
I do not know what might be causing the problem and would like to know what else to look for?
It means you have a PHP error there. The first thing would be to examine logs. If you see anything like "class not found", then your next action would be composer dumpautoload --no-dev.
Long time ago I had an article about blank pages in TYPO3 FE. Not up to date but still can be helpful: https://www.dmitry-dulepov.com/2009/03/blank-empty-page-in-typo3.html
Dmitry already wrote it: you have an error.
In production environment nothing is shown for not revealing any information about your system.
So the only information about the error can be found in the error log of your webserver.
What can you do to get more information about your error?
Enter the install tool and switch to develop mode. This will also enable deprecation logging into a file. Try to avoid filling your system with deprecation warnings by disabling deprecation logging.
Disable the default exceptionhandler by adding this to your typoscript setup:
config.contentObjectExceptionHandler = 0
Now you should see a call stack instead of blank screens.
Be aware that this might reveal confidential information from your system.
because of this you should use a copy of the live-system.
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.
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!!.