Symphony.

Hello everyone.

I got a strange error on my client's server. The same exact Ensemble works perfectly on my localhost (OS X, PHP 5.3.15) and on my own server (hostpoint.ch).

Some links:

my client's server install: http://provaweb.eina.cat

kanduvisla's check.php script: http://provaweb.eina.cat/check.php
mod_rewrite works ok, I checked bypassing the error.

phpinfo if you want to look further: http://provaweb.eina.cat/test.php

it, working on my server: http://eina.8302.net
(you can switch languages)

and the master.xsl: https://gist.github.com/3905900

I discovered the error is caused by two things, related all with the Frontend Localisation extension.

One is whenever I use the fl:__() function, from line 68 in master.xsl:

<xsl:copy-of select="fl:__('navigation/estudis')"/> 

The other is on a snippet I wrote for language selection (on line 114)

<xsl:for-each select="data/fl-languages/supported-languages/item[not($lang-code=./@handle)]">
<xsl:if test="position()!=1"> / </xsl:if>
<a href="{$root}/{./@handle}/{substring($current-path,5)}">
<xsl:value-of select="substring(., 1, 3)" />
</a>
</xsl:for-each>

If I comment out those two bits of code then it works.
FL namespace is declared, remember it works local and on another server. I have no .shtml files anywhere.

Thanks a lot for your help! Highly appreciated.

/

I started asking for help on another discussion (on the Frontend Localisation extension) thinking that it would be the problem. Some of you kindly recommended solutions that didn't work. Here's a link if you want to check it out:

http://getsymphony.com/discuss/thread/82249/2/#position-26

Please don't open another thread for a question you've already asked about.

From your other thread it's clear that the problem is server related and not to do with Symphony, which you've proven by installing exactly the same files on two servers, working on one and not the other.

Please ask your host to look into this as it isn't Symphony related. You will ned to figure out what the differences between your working server and the shared host are to figure this out.

@designermonkey

Please don't open another thread for a question you've already asked about.

I asked whether or not I should open another thread on the other thread befone opening this one, and I was told to do it. But it's ok, I will be more careful next time.

Please ask your host to look into this as it isn't Symphony related.

Ok. Now it's clear. Thanks a lot.

I was only hoping for some tips from any Symphony pros related to the error, in order to help me spot the issue on the server.

As they said this is a server issue. Your server tries to use a default 500 error which would be your 500.shtml since this file is probably deleted by yourself... the file is returning a not-found error which is presumably being handled by symphony.

You have to check with your host why it is looking for 500.shtml + you should look at those logs and see why you are having the 500 in the first place.

It's either an Apache or PHP configuration difference that the shared host has implemented.

Check whether they have prevented access to any specific PHP functions, or have any preventative steps in place in the Apache setup for your domain.

PS, I didn't realise someone had said to open another issue, sorry if I came across brash there.

I stopped using Symphony on shared hosting as I too have run into all sorts of issues like this, and it wasn't worth my time to try and diagnose the problem. Using VPS isn't a solution for everyone though I know, but it needs to be sorted with the host.

Dependant on what they respond to you, we will be glad to help out with more info, but the first port of call is definitely the host, They do all sorts of weird things to PHP and Apache thinking they are securing it for shared environments.

@gunglien

You have to check with your host why it is looking for 500.shtml + you should look at those logs and see why you are having the 500 in the first place.

I will use this to first approach the host. Symphony is just reacting with a 404 to a strange 500.shtml response from the server. I wasn't sure about this, now I am. Thanks.

@designermonkey

They do all sorts of weird things to PHP and Apache thinking they are securing it for shared environments.

Definitely agree with you. Sometimes you cannot control what crappy server the client needs/wants to use for non-sense reasons.

PS, I didn't realise someone had said to open another issue, sorry if I came across brash there.

No problem :-) Thank you for your time and for sharing your experience.

I will get back with information and results in case I can fix this.