Yes in our case this was the fact. There were two web servers, Apache 2 in our case, and one PHP. The php.ini file was in /etc/ as usual. Everything seemed to be perfect. But however some directives in php.ini does not worked for one of the server.

Why the second server does not read php.ini?

Well actually when you load the php.ini for the first server it loads correctly with everthing declared in it. However when you start the second server, of course on a different port than the first one, you get all the php.ini values as if they are default.

Why?

That’s some feature of PHP we didn’t know. I still don’t have an explanation about it. But of cource there’s a …

Workaround

You can put everything for the second server in the .htaccess file, so this will act as second php.ini for the second web server

Well it may look strange to want to do that exaclty. Who wants to have a <a> tag in another. It really looks semanticaly incorrect, but however, every normal A grade browser’s displaing it correctly, except .. IE6.

The Case

The Microsoft team may be too much semanticaly involved in that problem, I should guess, but that’s really impossible.

The Workaround

The workaround is trivial. You just put the <a> tags one after another and adjust them with relative position and margin with negative values.

… and The Example

<a href=”#”>link here</a>

<a href=”#” style=”margin:-10px 0 0; position : relative;”>link there</a>