Skip to main content

hide .php extension - htaccess



Possible Duplicate:

remove .php extension with .htaccess




Hey guys I'm trying to hide the .php file extension but for some reason can't get it to work, my latest attempt was the following




<IfModule mod_rewrite.c>
RewriteEngine on
RewriteRule ^folder/([a-zA-Z_\-0-9]+)/?$ /folder/$1.php
</IfModule>



I have tried many different variances of code I have found online but still no luck, the .htaccess file is placed within the root directory.



The site I am trying to get this to work on is http://www.ashleysark.com/



Thanks in advance Adam


Source: Tips4allCCNA FINAL EXAM

Comments

  1. I've used this:

    RewriteEngine On

    # Unless directory, remove trailing slash
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^([^/]+)/$ http://example.com/folder/$1 [R=301,L]

    # Redirect external .php requests to extensionless url
    RewriteCond %{THE_REQUEST} ^(.+)\.php([#?][^\ ]*)?\ HTTP/
    RewriteRule ^(.+)\.php$ http://example.com/folder/$1 [R=301,L]

    # Resolve .php file for extensionless php urls
    RewriteRule ^([^/.]+)$ $1.php [L]


    see also: this question

    ReplyDelete
  2. The other option for using PHP scripts sans extension is

    Options +MultiViews


    Or even just following in the directories .htaccess:

    DefaultType application/x-httpd-php


    The latter allows having all filenames without extension script being treated as PHP scripts. While MultiViews makes the webserver look for alternatives, when just the basename is provided (there's a performance hit with that however).

    ReplyDelete
  3. 1) Are you sure mod_rewrite module is enabled? Check phpinfo()

    2) Your above rule assumes the URL starts with "folder". Is this correct? Did you acutally want to have folder in the URL? This would match a URL like:

    /folder/thing -> /folder/thing.php


    If you actually want

    /thing -> /folder/thing.php


    You need to drop the folder from the match expression.

    I usually use this to route request to page without php (but yours should work which leads me to think that mod_rewrite may not be enabled):

    RewriteRule ^([^/\.]+)/?$ $1.php [L,QSA]


    3) Assuming you are declaring your rules in an .htaccess file, does your installation allow for setting Options (AllowOverride) overrides in .htaccess files? Some shared hosts do not.


    When the server finds an .htaccess file (as specified by
    AccessFileName) it needs to know which directives declared in that
    file can override earlier access information.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex