All the extension does is replace the {ee:} tags with your pages and templates. The default settings are only a guide and will change from site to site.
The first thing I suggest is to get the “include method” working without the extension and then use your .htaccess as a base for the extension settings
This really should be handled by the EE admin. It is nuts that we have to go in and do these hacks to make the URL strings more usable. Are there plans to include this in the Admin of a coming release?
or better yet, EE should remove index.php from the URL by default. Is there even anyone who uses EE that prefers to have index.php in the middle of the URL?
I for one love taking out the index.php bit as I just like my URLs to be that little bit shorter wherever possible. Having said this though this is not something that ExpressionEngine will probably ever do as standard and definitely not something that I think the developers would ever support.
The problem is that whilst on most servers it is a pretty simple thing to do there are a few different server environments that make it slightly more difficult to get to work and whilst this is definitely something which is a server environment issue and not directly related to ExpressionEngine then I feel the developers have taken the correct path here on this one.
If your host can’t help you get this set up properly then I for one don’t really see why the ExpressionEngine developers should have to? That said they do help out with these kinds of requests all the time but do let you know that it isn’t supported. The point here being that ExpressionEngine works fine with index.php in the URL and as this is a server environment setting then I doubt it will ever be supported directly.
I’m sure one of the developers will be able to pop in on this one though and flesh out what I have said but really this is akin to saying that because ExpressionEngine can spit out images in my template then the developers should help me get my images looking really professional
That all makes sense what you say, but there are prominent open source solutions out there which use the same sever environment (i am only familiar first hand with Drupal, Zenphoto, and Wordpress) and have no problem with modifying how URL’s are generated.
omg!! this did the trick for me!! thank you!!! I’ve been struggling with this for months also and now it is working!
spindigg - 09 August 2008 02:45 PM
Using the default recommended rewrite rules using .htaccess on Apache didn’t work for me. I found a forum post with the following recommendations which did the trick.
First, I think it’s silly that a $250 CMS like EE doesn’t actually have the native ability to remove the /index.php/ in there. That’s just dumb. Sorry, but it is. I can’t think of one other CMS with that issue, and most of the ones I’m thinking of are free and open source.
Second, the wiki page is wrong, and doesn’t seem to work for anyone. Plenty of fixes have been suggested in these comments, which DO work for me. However, since I haven’t quite posted 100 messages yet, I cannot edit the wiki page. This also is frustrating.
Can someone with permission simply edit the wiki page to mention that you want a ? after index.php or it won’t work for most folks?!?
I am sorry that you are frustrated, but $0, $250, or $250,000 - this is a server-side change. I know that some of the open source systems *include* the .htaccess with their distribution; that doesn’t make it any less of a server-side trick.
Many more people use those wiki tricks with no problems - remember, people without problems don’t post to support forums; what you see here is the subset of people that need assistance, it is not representative of the entire community. Furthermore - the wiki has no 100 post limit; that is only for the comments on the documentation. So you can, indeed, change the wiki article if appropriate.
Thank you again for your feedback and I hope you did manage to get this working after all.
I’m having a problem using the include method. My template groups contain dashes (-) and thus the rewrite rules aren’t being properly applied to them. For example:
Did you ever get this worked out? I don’t seem to be having the same problem with dashes in my RewriteCond. Maybe try replacing the dashes with dots (single char)?
idfive - 14 April 2009 03:47 PM
I’m having a problem using the include method. My template groups contain dashes (-) and thus the rewrite rules aren’t being properly applied to them. For example:
I’m having a problem using the include method. My template groups contain dashes (-) and thus the rewrite rules aren’t being properly applied to them. For example:
In regular expressions dashes and dots need to be escaped. (this also crops up for things like favicon.ico and robots.txt that are typically in the root. They need to be written as favicon\.ico and robots\.txt for those that are using the exclude method)
On the whole the site is working fine. The only problem is member logouts. When a member logs out, the system doesn’t seem to register the logout properly, and the member doesn’t seem to be “really” logged out. The weird thing is logging in works fine, logging out causes the page to display as if the member is still logged in.
I’ve tried adding the rule explained here that is supposed to fix paths with the ?ACT=X query string in them, but no luck.
I can give a bunch more info, but any ideas where I should be looking to solve this?
Nik
although manually removing the pipe didn’t fix it.
