Textpattern Support Forum

> zem wrote:
> Should fix the non-ASCII URL bug (untested)

Confirmed. For me it works as expected now. Thank you, zem! :)

I have a weird behavior from this plugin. I’ve set up a new section & page type for errors. If you request a non-existent article id the plugin behaves fine & throws a 404 invisibly. But it you just put in nonsense after the domain (a non-existent section) then the plugin redirects you straight to the error page, not invisibly as an ErrorDocument should.

Edit: this isn’t referring to my personal site; it’s an internal site unfortunately not accessible from outside my work

Last edited by compooter (2004-09-28 22:42:06)

Hafnius,

You can (and should) handle that with a regular .htaccess ErrorDocument.

The plugin can’t do it because it has no way to intercept errors – it can only handle those generated by the plugin itself. (Which I think explains Compooter’s query above – the plugin can’t act as an ErrorDoc handler for things that occur outside of Texpattern, such as a missing section file)

zem – I think this plugin is redirecting http://station11.net/log/234/#comment to http://station11.net/log/234/photos-from-france. Has anyone else noticed this? I could just be misinterpreting the comments_invite function and passing it the wrong variables.

<code>[kjell@imac:~] % curl -I http://station11.net/log/234/#comment
HTTP/1.1 301 Moved Permanently
Date: Sun, 31 Oct 2004 03:54:04 GMT
Server: Apache
X-Powered-By: PHP/4.3.8, The blood, sweat and tears of the fine, fine TextDrive staff
Location: http://station11.net/log/234/photos-from-france
Vary: Accept-Encoding
Served-By: TextDrive
Connection: close
Content-Type: text/html; charset=UTF-8</code>

There’s the pages information, and here is how the part of my plugin which generates the comments link looks like: $comments = comments_invite($AnnotateInvite,$Section,$ID);. My fault or the plugins?

Last edited by misterk (2004-10-31 04:01:14)

I don’t think it is… it’s in the url, as an identifier. A 301 is returned, and php redirects the page to /title. I don’t see where anything is in a get, but when you load it in a browser you just get redirected just like curl says.