Quick fix for WordPress white screen of death

WordPress / Kirjoittaja /

Don’t you just hate it if you needed one simple answer and then you’ll have to read loads of text to get your answer or watch 10 minute video? Me too! So here is one of solutions how to fix white screen of death in WordPress sites. This really happens a lot also to me, too. There’s no need to remember everything. Just find solution for it very quick.

You need access to your file system. Find wp_config.php file from WordPress document root and edit it.

Insert this code to after a line that says:
/* Add any custom values between this line and the ”stop editing” line. */
(around line 84)

Insert next code:
define( ’WP_MEMORY_LIMIT’, ’256M’ );
Then save your file.
Problem should be solved! If not, you need to continue searching for another solution.

Can’t login as admin to Prestashop 1.7.8.6

Prestashop / Kirjoittaja /

First of all, it is very important to keep you shop engine up to date exept if there are serious vulnerabilities in that version what you are going to upgrade into. When you reach the version that is stable, maybe it’s better to wait couple of versions before upgrading to newest version, just in case. This way you’ll know if new versions have any problems before you upgrade your online shop. It might save you from lot of trouble. I’m glad I have just done that, because one of the Prestashop versions was vulnerable to malicious injection. This Prestashop version was 1.7.8.6.

I run WHM controlled server and I get messages (tweaks) if something strange is happening in the server files. There is great plugin installed called Imunify what detects malware and viruses from server files. What a great thing! And this morning I had one of those messages in my mailbox waiting when I woke up. Message said something about malicious activity on some server, so I checked it out as soon as I could. (NOTE: not anything that was online)

Imunify is great because it shows what files are infected. And it really was one Prestashop version which is not online. I had upgraded it a while ago. It still got infected. Very strange. Even when the shop is not online anymore. So I just entered file system and checked these files.

It was not hard to detect malicious code that was injected into the file. It looked like this:

(Injected code in red highlighted area)

Malware code was located at the end of the file and I just deleted it and saved the file. What this code does is that it hijacks your shop. Meaning that admins can’t log into the Back Office, not even superadmin. Originally there were a lot more infected files than this. Luckily all infected files were found and there was also newer version available. Upgrading to new version overwrited (replaced) all infected files. Luckily next versions of Prestashop did not have that ”feature” and for now all shops are safe from this malware. At this point, newest version of Prestashop 1.7. is 1.7.8.8.

If you are merchant and you don’t have access to shop file system or WHM, you need to ask your technical support to upgrade your Prestashop and that will repair your shop. It will help.

Miksi et pääse kirjautumaan Prestashop 1.7.8.6 kauppiaspaneliin?

Ensinnäkin on erittäin tärkeää, että kauppaohjelmisto on ajan tasalla, jollei tiedossa ole haavoittuvaisuutta uusien versioiden kohdalla. Kun asennettuna on stabiili versio, on ehkäpä hyvä pysyä siinä hetken aikaa ennen kuin päivittää käynnissä olevan verkkokaupan uusimpaan versioon, jota ei ole välttämättä testattu uhkilta. Odottamalla hetken, ainakin uhkat tulevat ilmi, ja saatat välttyä niiltä.

Onneksi olin tehnyt näin, koska yhdessä Prestashopin versiossa oli suuremman luokan ongelma, nimittäin kaupan adminit eivät päässeet kirjautumaan kauppiaspaneeliin sisälle. Prestashoppiin oli asentunut jostakin malware joka kaappasi kaupan haltuunsa. Tämä haavoittuvainen versio oli Prestashop 1.7.8.6.

Pidä aina testikauppaa jossa voit testata vaikkapa uusia moduleita ja kokeilla kaikkia pikku muokkauksia.

Artikkelin kirjoittaja | Article writer

Minna Laamanen

How to enable Prestashop DEV mode from file system (FTP)

Prestashop / Kirjoittaja /

Prestashop version: 1.7.7.0-1.7.8.8.

This is about Prestashop ecommerce solution if you need debugging.

DEV mode shows errors that might occur in your shop. It is also recomended that php setting show errors. (File in root of the shop directory php.ini). Only Prestashop site admins are able to see errors when logged in into the shop.

display_errors = On

Open server files and go to:
/shop_directory/config/defines.inc.php
replace false with true
define(’PS_MODE_DEV’, true);
Save file

I had this situation that I upgraded my Prestashop from 1.7.8.5 to 1.7.8.8. Of course I upgraded one version forward at the time. But one of these versions did something to my shop and I couldn’t log in as admin to my shop. This is where I wanted to see if DEV mode would help. But I couldn’t log in. So I found this file in server where you can manually turn DEV mode on or off.

Artikkelin kirjoittaja | Article writer

Minna Laamanen

Weird translation locations in Prestashop 1.7.

Prestashop / Kirjoittaja /

Myself or my customers use Finnish as Prestashop language and I have struggled with some translations as long as I remember using Prestashop. Right now I am using version 1.7.8.8 and after ugrading to this latest version, all previously modified translations were overwritten. This gives me headache everytime when upgrading Prestashop. So, I start writing down here in my blog where all these configurations are located at in server or in Prestashop Back Office. It saves me time when I run into these situations again. Just find answers here…

Suomennosten outoja paikkoja

Itselläni ja asiakkaillani on käytössä Prestashop suomeksi, ja olen usein törmännyt todella outoihin kielikäännöksiin. Joskus niiden selvittelyyn kuluu todella paljon aikaa, ja haluankin nyt kirjoittaa tänne omaan blogiini niistä muokkauksista, joita itse olen joutunut tekemään aikojen saatossa. Viimeeksi tänään (24.4.2023) jouduin etsimään serverin tiedostoista mistä ohjelmistopäivityksen jälkeen footeriin ilmestynyt epämääräinen otsikko suomennetaan.

Prestashop-yhteisön keskustelufoorumista ei yleensä löydä yhtään mitään kun ilmoitusten laittajat eivät ymmärrä ilmoittaa otsikoissaan ja tägeissä mistä Prestashop-versiosta on kyse. Siinä tulee sitten selattua turhaan kaikkia viestiketjuja ja menetettyä viimeisetkin hermonsäikeet. Kun kysytään jostain asiasta, niin vastauksen saa ihan eri versioon. Ei sellainen voi toimia, tai se on vähintäänkin turhauttavaa.

How to change or translate VALIKKO_MÄÄRITYKSET teksti footer | Contact info Prestashop 1.7.8.8.

This is in footer ps_contactinfo

Found this location in server files where this translations could be:
/store_path/app/Resources/translations/fi-FI/ModulesContactinfoShop.fi-FI.xlf
I also changed source language ”en” to ”en_US” which is the default language code and deleted translation files in template (which in my case was Classic Child). After saving the file, I cleared cache and forced compilation in BO.

These in my belief are core files. Most translations can be modified in BO where most translation strings are. But for some reason not all are there. One thing must be checked also, that max_input_vars in php.ini and user.ini are set up as high as possible. My value in both of these settings is 7000. Translations stop saving into database from BO if this value is set up too low. Php version in my shop is 7.4.33.

Click to enlarge
Click to enlarge

I also modified other translations in this same file. We don’t use Fax anymore, or I don’t, so I replaced Fax with VAT number. I don’t understand why it is not visible anywhere in the shop by the default. In Finland it needs to be visible by the law. You can see moderated translation in previous picture.

Artikkelin kirjoittaja | Article writer

Minna Laamanen

Scroll to Top