Hal

Good timing … I was just going to ask if it were still under active development since there is no update in quite a while.

Glad to see someone is jumping in there to help with this! Thanks. I use both products and would love to see a full and proper integration.

I’ll mention one situation I noticed recently on a moderately busy site (using WPTouch Pro and WPSC 1.1). The two are mostly working very well together. With Wptouch, we have a separate front page defined, /mobile-home. WPSC creates this cached version properly. After a while a /index-mbile.html also gets created. Once this happens, the rightful /mobile-home/index-mobile.html is ignored, and all mobile traffic gets the wrong cached file. And, this one, while labeled index-mobile.html is not the mobile theme. I am guessing it is caused by a disconnect between the user agents between wpsc and wpt. Or, someone is switching to the desktop theme, and that gets cached and then served to all mobile devices.

Otherwise, it is working well for me. Next week I’ll try 1.2 and see if that helps things.

OK, this is cookie related. WordPress allows user definable cookie names for things like wordpress_logged_in_*. In this case, the user defined stuff was not agreeing with super cache.

I just realized that while I have the ‘don’t cache pages for known users’ option checked, I am still getting cached pages, judging by the output at the very bottom of the raw source, when logged in as an administrator. Maybe that’s an issue?

<!– Cached page generated by WP-Super-Cache on 2012-05-21 17:46:45 –>

Never really did. I finally decided I could do without ??

Never could get this to work correctly, so I went back to the old fashioned way and did my own pagination. Not sure if its because of the way I am doing the query or something else, but I never could get it to work at all. Nice idea, though.

As a follow up, if I set the mysql LIMIT to something like 0,10, then wp-paginate only sees 10 items, and doesn’t see a need to paginate, and doesn’t do anything, of course. And if I don’t use the LIMIT clause, I apparently get all posts. The pagination links are there, but they are fubar because all the posts are actually on the first page.

I can wrestle this to the ground, but was hoping somebody had already been here. Thanks.

Is it not possible to use the query_posts() function?

No.

If you do a custom query, you are going to have to make sure to set all of the internal WordPress values that WP-Paginate needs.

That’s what I am asking. I don’t see what those are. I assume I’ll need to do some LIMIT clause stuff with the query.

Thanks.