[wp-hackers] AjaxWp enhancement

[Stephen Rider]

On Nov 19, 2008, at 2:50 AM, Dan Gayle wrote:

> There was a page that Gianni Milanesi had that explained his  
> rationale and process in creating AjaxWp, recreated here:
>
> http://ajaxwp.com/ajaxifing-wordpress-the-making-of-ajaxwp/
>
> In that page, he talks about Ajax' inability to bookmark/navigate  
> history and how he fixed that issue, in the process making really  
> ugly permalinks.
>
> On Nov 19, 2008, at 12:38 AM, Alex Hempton-Smith wrote:
>
>> Just a note about my first point, although copying that generated  
>> URL and
>> pasting it does work, it's certainly not pretty, and almost defies  
>> the
>> object of having pretty permalinks (which I sort of live off :P)
>>
>> On Wed, Nov 19, 2008 at 8:36 AM, Alex Hempton-Smith wrote:
>>
>>> Some enhancements before I would even think about using this on my  
>>> sites;
>>> *  Better URL's, the 'real' URL of the page would be needed  
>>> because many
>>> people copy/paste this


A quick note on pretty permalinks and Ajax --

If putting the Ajax state in the URL, you should (in my opinion)  
_avoid_ making it part of the URL "directories".  In pre-2.6 WP I use  
a Paged Comments plugin, and it sets up each posts comments in pages  
like so:

example.com/blog/post1/comment-page-1/
example.com/blog/post1/comment-page-2/
example.com/blog/post1/comment-page-3/

This is a BAD thing, because (among other things) it messes with site  
stats.  The popularity of that page is distorted in stats because that  
is seen as three different pages, when really it isn't.  It is also  
probably doing the same with Google stats, since that is three pages  
with substantially the same content (only different comments).

I would much rather have:

example.com/blog/post1/?comments-page=1
example.com/blog/post1/?comments-page=2
example.com/blog/post1/?comments-page=3

What WP 2.7 does with paged comments is beside the point, because I'm  
not really talking about paged comments specifically -- I'm simply  
saying that when putting such things (Ajax state is very similar) into  
the URL, it's better to put them into a GET then make them into fake  
"directories".

Just my two bits.

Sincerely,
Stephen Rider