Hello everyone,

Recently I have been getting fatal errors on my site. I am honestly uncertain if it is related to my new expression engine setup but thought I would bounce it off you guys and girls to see if there was perhaps some solutions.

Fatal error: Maximum execution time of 10 seconds exceeded in /home/www/faeaa941e32262c9df46d45cfc94e5e8/web/system/core/core.functions.php on line 2774

That is the error we are getting and it is quite often. I notice core is in the line… now I used to use the core version but now am on full edition, perhaps this is related?

Any information I can get on this issue would be of the greatest help. Thanks in advance.

Kind regards,
David

Hi, David.

The error is found in the file core.functions.php - in this case core main functions.

It looks like there are some speed issues in doing various tasks.

Can you reliably cause the error?

Which version/build of EE are you using?

Hi Sue,

Thanks for the reply. The error is quite systematic when clicking a certain page. I get the error about 50% of the time and it does occur to other people too.

I am currently using ExpressionEngine 1.6.3 with the build:  20080421

A few more questions:

What settings do you have in Output and Debugging Preferences?

Are you on a Windows or Linux hosting?

Who is your host?

How much memory is allocated to EE? (You can find that out from inside of Admin ›  Utilities ›  PHP Info

Sure of course, here are the settings:

__

Generate HTTP Page Headers?    Yes

When enabled, your site will be shown in a compressed format for faster page loading     No

This is a safety mechanism for servers that do not support the PATH_INFO variable.    Yes

Redirection Method     Location(faster)

Enables the display of error messages, which are valuable during site development     2PHP/SQL errors shown to everyone   (this may be it to at least not show the error?)

Display SQL Queries?    No

Display Template Debugging?    No

__

My host is infomaniak.ch and they use Linux.

For the memory on the php info, memory_limits local value 48M and master value of 16M

Do you require index.php? for your links to work properly? You could try setting on Gzipping, and see if that makes a difference.

Yes the site uses index.php, it is also in every url. It would be great to no longer have that but that was how it was coded for me. I will enquire about gzipping

To be honest, it looks just like a restriction set by your host “Maximum execution time of 10 seconds”. Apparently your template is so complex that it takes PHP longer than that? So, here’s my advice: 1) Ask your host about any such limits, and whether they can be lifted or expanded. 2) Make sure that your templates are as efficient as possible. This wiki article should get you started.

I contacted the host and their policy does not allow for more than 10 seconds execution time, because it works on most sites. I have done my best to make the pages more efficient now but its still not brilliant.

Perhaps making the site work is a task I could request on the job offer section of the site. Is it a realistic request?

Thanks

dache, it just depends on your templates and your hosting. There are some hosts that overload their servers. You could have someone look at your templates and help you modify them to work with your current host. I’d probably find another host.

But that’s my personal opinion.

dache, while we can’t help you optimize your templates as that is beyond standard support; it should not take 10 seconds either.  Can you zip up your template and attach it here, please?  I’d like to have a quick look and see if there’s anything obvious there.

A link to the site would help a great deal as well.

I am enquiring about better hosting. Thanks Sue

Sure no problem Lisa. I have attached the index template and the portfolio template to this post.

Thanks

You will definitely need someone to work with you on that template.  I think you have over 20 weblog entries tags on one page, and an absolutely ton of conditionals?  You might try simplifying and allow yourself to use more than one template rather than all of those conditionals.  That is a pretty heavy template from the looks of it; you could turn on Template Debugging and see exactly what is going on there.

You also have some syntax errors in there, like:

which should be:

Honestly, if it were me, I’d sit down and think about what you really want from this template, and how best to achieve that while broadening your horizon to consider using more templates than just the one.

Your portfolio template has ~25 exp:weblog:entries tags, none of which are using the disable= parameter...

You should rethink your setup, but that change alone would probably bring significance performance gains.

It would seem Im a bit over my head with the technicalities on this one. I think it best to outsource for the rest.

Thanks ever so much, I really appreciate the input.

dache, as Lisa suggested, you should probably rework your templates as they really are quite heavy. Still, as an intermediate fix, by all means try using the disable parameter.

So, are we ready to close this thread? Any unresolved technical issues?

I think I have all the info I need to fix it or have it fixed, thanks Ingmar - it can be closed

Sure thing.