Blank WebPage

[Bobcat22]

I have no idea where you can turn on error reporting.

[vekia]

I have no idea where you can turn on error reporting.

 

check this thread: http://www.prestashop.com/forums/topic/224525-how-to-get-debug-information-for-500-error-or-blank-page/

[Bobcat22]

Thank you. I get: "Warning: strpos() [function.strpos]: Empty delimiter in /mysite.com/classes/Tools.php on line 1893"

 

This was the result of deleting a group and seller.

Edited August 6, 2013 by Bobcat22 (see edit history)

[vekia]

it's only warning (not error). Warnings shouldn't affect website

[Bobcat22]

Well my site is completely blank. Did my check bounce? I see the admin area but with no template. Seems as though the theme got trashed.

 

Within the log folder I see: *ERROR* 2013/08/05 - 17:02:05: Property HomeSlide->position is empty at line 837 in file classes/ObjectModel.php

Edited August 6, 2013 by Bobcat22 (see edit history)

[Bobcat22]

Is there available help for this problem?

[vekia]

try to remove the homeslider module from the /modules/ directory

(make a backup of this addon before you remove it)

[Bobcat22]

Hi Vekia

 

I renamed the "homeslider" module, that did not have any impact. I also then renamed the modules folder, and still no change. I still see a blank page when viewing the front end. Looks like the CSS references for pages of the admin and front end are missing

 

Could this be a Htaccess issue? htaccess for the CSS folder reads,

<IfModule mod_rewrite.c>

RewriteEngine on

RewriteCond %{REQUEST_FILENAME} !-f

RewriteRule "(.*)\.css$" retro-compat.css.php?file=$1.css [QSA,L]

</IfModule>

Edited August 7, 2013 by Bobcat22 (see edit history)

[tomerg3]

Was this working correctly at any point?

What exactly started this issue?

Did you make any file changes?

What's the URL for the site?

Can you check the main server error log (usually available from cpanel)

[Bobcat22]

Hi Tomerg3,

 

All was working fine until I started adding modules and added categories. What I then did was to rename the modules folder to modulesX, then tried again thinking perhaps I had an out of date module(s) that may be breaking the site. There was no impact. Then I renamed the prestashop to prestashopX then re-installed prestashop using the same database. It was like the previous, no theme for either the admin or front end. When I used a new index for the same database, all works. I am wondering if this build or in general, is Prestashop fragile when adding or uninstalling modules?

Edited August 8, 2013 by Bobcat22 (see edit history)

[El Patron]

do you have file cache active in your shop?

 

if so turn it off while debugging this issue.

 

honestly...you should have opened a new post bobcat...trying to figure out who responded to whose post...really makes it more difficult to help...so please in the future, don't assume your problem is exactly like someone else's and post on their thread.

[vekia]

@Bobcat22 I moved whole discussion related to your problem to seaprate topic, im conviced that it will be more visible right now.

 

let's clarify several things.

 

1) you changed name of the /modules/ directory to /modulesx/

2) then you changed the prestashop root dir name to /prestashopX/

3) you said, that then you installed prestashop again - the question is - in what directory? the same?

4) you said also that you used the same database, so i suppose that you just used different prefix for new installation?

 

everything sounds like you're starting from scratch, is there possibility to remove whole files, database and to install prestashop again? with fresh database and clean directory?

[Bobcat22]

I do appreciate your attention to this matter. For archival sake, I thought this was relevant to the pre-existing post of getting a blank page after the install was successful and then modifying elements within the admin with special regards to modules.

 

Using the same name folder:

 

/pretashopX - renamed - no CSS/Theme for admin and frontend

/prestashop - current and successful

 

Rather than deleting the broken install, I left if so I could possibly find out what happen and the solution.

 

I did reinstall Prestashop and try to use the pre-existing database with the same db prefix. The results was the same, blank pages for the frontend, no theme for the admin. Using another database prefix on the same database the site is back to good.

 

Conclusion: manipulating/sitting up clickable options within the admin, can break your PrestaShop install.

Edited August 8, 2013 by Bobcat22 (see edit history)

[benjamin utterback]

Hi Bobcat22,

 

We are here to help.

Whenever you need to install PrestaShop again you should drop the database and install again from scratch with a new database.

 

Your original database changes as you install or remove modules and make other changes.

 

That's why when you installed PrestaShop again on the same database, it did not work the way you wanted.

 

Would you be open to installing PrestaShop again using a clean database?

[tomerg3]

This would be much easier to resolve if you could check the apache error log (also known as server log from cpanel).

 

It would show the actual error, instead of this guessing game.

[Bobcat22]

Please note, the same database using a different newly created db prefix works. The first install using the first created db prefix provides the same results - no impact. The newly created db prefix = success. This is not a db setup issue it is something that changed the database while clicking on options within the admin. This can very well happen again.

 

"This would be much easier to resolve if you could check the apache error log (also known as server log from cpanel)"

 

Let me try getting that log.

Edited August 8, 2013 by Bobcat22 (see edit history)

[Bobcat22]

The Apache error log file is not available for anything that happened a few days ago

[benjamin utterback]

Hi Bobcat22, do you have any idea what may have caused this issue? Do you remember what modules you were installing/deleting.

 

Did you make any code changes? Did the blank page happen after/before renaming modules and/or folders.

[Bobcat22]

I don't remember exactly what I did, but I will try to replicate it on a test site.