Back Office too slow.

[rv01]

Prstashop 1.6.0.8, modules updated.

BO response time is between 10 and 20s even with Bozoom.

Thanks to help.

 

Edited September 1, 2014 by rv01 (see edit history)

[PrestaHeroes USA]

Well BoZoom is not your issue so I don't understand title.

 

Anyway trying to move forward.

 

When a shop owner is getting slow responses, the very first thing to do is to enable PrestaShop debug profiling:

 

The first thing a shop owner should do (and then repeat over time) is to profile their shop.

 

This is accomplished by enabling the built in PrestaShop Debug Profiling:

 

open file config/defines.inc.php

 

change this line to true

define('_PS_DEBUG_PROFILING_', false); //set to true too enable profiling

visit slow shop pages, collect the profiling data, analyze the data.

 

note: when enabled, all visitors will see this so turn off as soon as you collect the  data.

[rv01]

I changed the title, sorry Fred, my mistake.

 

For the profiling it works with the FO but does not show any info on the BO.

[rv01]

See now, I have activated the profiling for naturelore.com

 

The first thing the users see is

Redirection automatique dans 5 secondes

which is not nice of course...

[PrestaHeroes USA]

that is just part of debug profiling to show us redirects.

 

no luck  yet getting back office?  (your front office is very fast)

[PrestaHeroes USA]

turn on error reporting, what we are looking for in back office is not being able to write to 'certain' folders

 

http://www.prestashop.com/forums/topic/333695-solved-1606-back-office-slow/?p=1687307

 

so lets turn on error reporting look for any errors, also make sure to check your error log from hosting control panel.

 

note: if debug profiling is not showing detail in bo, turn off for now so visitors won't see it.

[rv01]

Ah, it's there, I had to logoff/login

From the BO, see attached

 

 

 

[PrestaHeroes USA]

turn on error reporting, what we are looking for in back office is not being able to write to 'certain' folders

 

http://www.prestashop.com/forums/topic/333695-solved-1606-back-office-slow/?p=1687307

 

so lets turn on error reporting look for any errors, also make sure to check your error log from hosting control panel.

 

note: if debug profiling is not showing detail in bo, turn off for now so visitors won't see it.

 

Make sure to follow up on error reporting.

 

Ah, it's there, I had to logoff/login

From the BO, see attached

 

yes, some progress...

[rv01]

I have this kind of errors when going to "modules", for "amazon", "authorizeaim" and "autoupgrade"

 

1. [autoupgrade] Erreur dans le fichier de configuration: Opening and ending tag mismatch: META line 1 and head
2. [autoupgrade] Erreur dans le fichier de configuration: Opening and ending tag mismatch: head line 1 and html
3. [autoupgrade] Erreur dans le fichier de configuration: Premature end of data in tag html line 1

[rv01]

whatever I do it's "initHeader" that takes several seconds

 

btw, the config/xml perms are all set to 0777.

[PrestaHeroes USA]

let's try this:

 

set to 'yes' the following two parms, (basically we are looking for a 'non' native module and/or override that is causing issue).

http://screencast.com/t/mFfHjDpnP

 

after setting to yes, then visit the slow pages in back office...

[rv01]

That's done, still same problems.

[rv01]

I have deleted the 3 modules with errors: "amazon", "authorizeaim" and "autoupgrade"

 

and now it's showing this:

1. [bankwire] Error found in config file: Opening and ending tag mismatch: META line 1 and head
2. [bankwire] Error found in config file: Opening and ending tag mismatch: head line 1 and html
3. [bankwire] Error found in config file: Premature end of data in tag html line 1

I cannot continue to delete the modules, I need this one

[PrestaHeroes USA]

is this issue on 'all' bo pages?

[rv01]

Yes this initHeader is taking 5 to 20s on every places

The errors with modules appear only in the "modules" page.

[PrestaHeroes USA]

from what I can tell initHeader is building the menu tabs, and I can not explain by looking at code where the issue could be.

 

see this post, it's possible and we must check all we can:

http://www.prestashop.com/forums/topic/342022-solved-slow-backoffice-admin-prestashop-1606/?p=1724746

 

also keep a close eye out for errors (use hosting php error log).

 

I'm running out of ideas, you may want to consider post in job offers if we don't make any progress on this, let one of the prestanerds look more deeply.

[rv01]

OK thanks. I reset the site into production.

Where to post this problem so that somebody from Prestashop can have a look?

[PrestaHeroes USA]

well, PrestaShop development would not look at this unless forge report:

http://forge.prestashop.com/

 

 

but most have very good experience by posting in

http://www.prestashop.com/forums/forum/235-job-offers/

 

there some really good prestanerds that work fast and for 'very' reasonable rate.

 

I wish there was more I can do but I think we hit the wall on this one.

 

make sure you have returned debugs to false, and enable non-prestashop modules and overrides.  Please post back here if you find resolution.

[rv01]

Hi Fred

I posted a bug in forge, we'll see.

 

Just an information: I use "Store Commander" and this is going very fast, hopefully. So I assume there is nothing wrong with the database or the server. This is saving my ass because PS BO is of no use for the time being.

 

My view is that it is for sure this "initHeader" thing messing after updating my Prestashop modules.

 

Thanks for trying.

Rene

[rv01]

Hello Fred,

Just to keep you informed.

No solution from the forge, although they tried: http://forge.prestashop.com/browse/PSCSX-3223

My hosting company senior technicians cannot find a solution either, they added PS IP's.

Seems too complicate or too simple, who knows.

I have posted a new subject, trying to find a solution:

http://www.prestashop.com/forums/topic/355784-prestashop-support-package-plans-effective-reviews-experience-advice/

 

In fact I MUST get out of this, even if I have to pay Prestashop to sort it out.

Cheers

Rene