Thread

Hello

I changed my hoster. Everything seemst to work more or less fine except that with my EE installation only the index page can be displayed, instead you receive a classical 404 not found. I found a wrong theme folder path in the “General Configuration”. Since I corrected that the Templates for the CP works again but no other.

Is there an other configuration where I have to correct the path. I tought about path.php but saw that there the field is empty….

Thank you in advance for your help.

I remarked a second problem: If I write a new posting with Umlauts, the won’t be rendered correctly. Somebody any idea what i have to change :-(

It sounds like the new host may not support the path_info server variable and you’ll need to use query strings in your urls.  Check this Kblog entry for the details.  See if that does the trick.

As to the Umlauts- do the old entries with high ascii characters show up fine?  It’s only when you make new ones it borks?

[quote author=;Robin Sowell” date=“1183313328”]It sounds like the new host may not support the path_info server variable and you’ll need to use query strings in your urls.  Check this Kblog entry for the details.  See if that does the trick.

I tried that - doesn’t change anything

As to the Umlauts- do the old entries with high ascii characters show up fine?  It’s only when you make new ones it borks?

It is exactly like that

It is possible to link to the site in question?

sure, sorry
http://www.rouge.ch/blog
http://www.rouge.ch

OK- sometimes you have to actually edit a file when using the ‘force query string’ method.  But that doesn’t appear to be the case here.  With the ? in the url- the pages work correctly.
member page:
http://www.rouge.ch/blog/index.php?/member/register/
comment page:
http://www.rouge.ch/blog/index.php?/vr/comments/alinghi_like/#comment-5253

HOWEVER- it looks like some of your links aren’t automatically adding the ? like they should.  For example- on the main page here: http://www.rouge.ch/blog  the latest comments links don’t have the ? added in.

So- looks like it should work as setup, but some of your links are being generated in a manner that doesn’t include the ? .  We need to track those down and change them.  Double check in your template- any EE autogenerated link should have the ? in it.  But is it possible you haven’t changed the links in some of the settings- such as on a per weblog basis, for links to the comments/search/etc pages?  If we fix any hard coded links to include the ?, your pages look like they’ll show correctly.

Now- as to the funky character issue- if I force latin-1 encoding, all displays fine.  Actually, looks like IE defaults to that- and displays fine.  FF is defaulting to utf-8 and thus buggered code.  And looks like the server is sending utf-8 according to the live headers.  You aren’t specifying the character encoding in your meta tags- so it’s taking the server default.  Well, FF is.  IE is being IE.

I’d have gone with utf-8 myself, but what’s your encoding setting?  If you specify in a metatag a la:

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">

Does all show as desired?

For the path_info history: I remarked that the server needs a while to react to the changes. After a while everything worked fine. But as described in the user guide it’s better to do it with active info_path a asked my hoster and he showed me how to activate path_info. So everything is fine for that issue and I thank you for your help. (Its true that the main page is not adding the “?” automatically because its a hardcoded redirect. Don’t I want the main page to point on the gallery module.

For the funky character issue: This is a issue that I’m not strong at all. The DB is also latin-1 and i changed the xml langaugage also tu utf-8. No changes so far. Or does the XML encoding only impacte the rss templates?
Update: I see it does impact the rendering of the page: Now, the Umlauts in the templates are also wrong

Now I need realy some help with the Umlaute issue. The point is now, that all the comments made by the frontend, the umlauts are working fine. But they are displayed wrong in the cp. All the umlauts which are made in the cp are displayed fine in the cp but not at the front end?!

All clear! I found the problem and anything works fine now. Thank you once again for your help!

regards from Switzerland

LOL- sorry iRouge.  I just checked back in- and very glad you figured it out.  I was starting to get confused in the above!  Yea- I think the fix was simply specifying the correct character encoding in the metatag on the frontend.  The example code above should have worked for that- and then EE has a {charset} global that could be used- it will pick up the encoding based on your settings.  I just figured it was going to be easier to test hard coding it.

In short- glad you’re squared away!