![]() |
![]() |
![]() | |
![]() |
Main sidebar
|
PITS /
01000: ?action=crypt fails with CleanUrls enabled Summary: ?action=crypt fails with CleanUrls enabled
Created: 2008-01-05 16:17
Status: Closed
Category: Bug
From: JL
Assigned:
Priority: 4
Version: 2.2.0-beta65
OS: Linux / Apache2 / PHP Version 5.2.5
Description: ?action=crypt fails with CleanUrls enabled. There is a '/' missing in crypt.php . <form action='{\ This already was an issue some time ago. http://www.pmichaud.com/pipermail/pmwiki-users/2004-December/008722.html Version 2.0.beta14 (28-Dec-2004) should have fixed this bug but it is still there. Changing it as suggested may break the form on sites with CleanUrls/PathInfo disabled. Also, I couldn't reproduce this bug. PmWiki.org uses CleanUrls and the ?action=crypt form works. On my CleanUrls site it works too. Maybe you need a fix with your Sometimes there seems to be some kind of magic. It seems to work like it should on my linux server and on my host server. I close this bug. JL May 09, 2009 I had the exact same problem. After some experimentation I found a likely solution. The problem lies in a combination of the configuration required for CleanUrl and what's in the .htaccess file. This is also assuming you have an index.php wrapper set up from the install instructions. First of all, if you have # Use mod_rewrite to enable "Clean URLs" for a PmWiki installation. RewriteEngine On # Define the rewrite base. RewriteBase /wiki # Send requests without parameters to index.php. RewriteRule ^$ index.php [L] # Send requests to pmwiki.php, appending the query string part. RewriteRule ^([A-Z0-9\xa0-\xff].*)$ index.php?n=$1 [QSA,L] This will ensure that all requests go to the index.php file, which will, on its own, send all requests to pmwiki.php, thus preserving all your clean urls akin to http://www.example.com/wiki/Main/WelcomePage. this rewrite solution still isn't working, with getting 301 Moved Permanently answer to POST query |
Page last modified on June 01, 2018, at 08:47 PM |
Powered by PmWiki pmwiki-2.5.2 |