I installed this extension:
http://leevigraham.com/cms-customisation/expressionengine/lg-htaccess-generator/

which worked fine, then I removed the index.php from URLs:
Control Panel Home › Admin › System Preferences › General Configuration

This works as I want.

However, it has mucked up my css links.

Here is the code I use:

and this is the html is generates:

That url does not exist. However if I remove the ? from after the domain name, it works fine. So how do I fix this? Do I have to hardcode my css links? I’d rather not do that.

Thanks!

I have the “?” in my css link and it still works.  I’m guessing the code to take out the index.php from the URL isn’t working totally right.  I’m using the same extension, but I remember I had to tweak it a bit to get it to work.  Here’s what I’m using in that particular section of the htaccess file:

Try that and let me know if it works.

Hi no luck with that, in fact, it meant I couldn’t access any of my pages.

Tom I am having the same problem.  Any fix?

Found the problem using LG HTaccess:

For the section of the code that removes index.php you have to remove the | before “members” on the next to last line.  I actually looked at my htaccess after using this to regenerate the file and saw || in the list of template groups and pages.  From some previous experiences I knew immediately this was the issue.  So change this:

To this:

And your problem might go away.

Nice one, I’ll give that a go. Although at the moment, I upload my css via ftp and hard code the link. I prefer this actually, rather than editing the css inside the EE templates.

Thanks Chad.  This solved my CSS issue after installing the lg.htacccess extension.

Paul B - 19 February 2009 06:06 AM

Thanks Chad.  This solved my CSS issue after installing the lg.htacccess extension.

Yes, it also solved my similar CSS problem (stylesheets not being applied). The double “pipe” character is a definite problem.

Somewhere in this thread, Leevi was talking about updating LG .htaccess Generator to fix this by doing something like this:

That would be great, but it won’t work. I tried it and it produces a 500 internal server error for both front and back ends. That’s because the EE “if” tags are not parsed correctly (or at all), and they end up as literals, with curly braces, in the generated .htaccess file, and that takes your site right down.

So… if you don’t use the Pages module, and know you never will, you can leave the “ee:pages” tag in there with no pipe character, or you can just remove the “ee:pages” tag (and the extra pipe) altogether. However, if you ever do use the Pages module, your site will break if the tag is in there with no pipe, or if you don’t use the tag at all, you won’t get automatic generation of those pages by the LG extension.

Unless Leevi comes up with a way to parse “if” tags in this extension, you’ll have to make a note to yourself somewhere to add the tag if you ever use the Pages module.

Leevi, thanks for a great extension that allowed me to stop apologizing for “index.php” in EE URLs. That, plus adopting a templating structure that consists of a template group for every site section with only an index in each one (plus a template group of embeds), and I finally have what I’ve long wanted for URLs:

Yay.