Hi,
I’m working on a login page, that ideally, will display additional content like a what's new listing.
Somewhere along the line, the Login functionality is changing the charset.
This results in undesirable characters being presented in the news listing, instead of apostrophes and quotes etc.
Some background info…
The charset that I need iso-8859-1 but by default it seems to use UTF-8.
I tried adding the required charset to a meta tag in the head, but the response header is returning the incorrect charset.
I can view the news listing without the login design applied and everything looks fine.
Nesting the what's new into a frontend design (with exactly the same content but updated design_area) will also display fine.
One thing that I've noticed is that the page returns a 403 Forbidden status. Is this related? Can the charset that 403's use be updated?
Is there anyway around this without becoming a headache to maintain? We don't specifically want to change the charset for specific URLs.
Any help appreciated.
Cheers
Cam