Problems with mofuse and W3 Total Cache

  • stitchkingdom

    (@stitchkingdom)


    14 years, 4 months ago

    First of all, thanks for the plug-in. I absolutely love it. I switched over from Super Cache and was using mobilepress, but that had it’s occasional issues. since mobilepress appears to not even be an option with Total, I took some advice in another thread and checked out mofuse which is actually pretty neat.

    I just have two issues with mofuse, one I don’t expect there to be any cure for, but one I’m hoping something can be done about.

    if you go to http://www.stitchkingdom.com on a mobile and go into an article with a photo and then click that photo, it’s trying to show the original size back on stitchkingdom.com. The problem is that the plug-in is blocking the request for the original file (jpg/gif/png/whatever) and re-directing back to the mofuse homepage. So is there a way to prevent the plug-in for doing the redirect if the request is for an image?

    My other issue which I don’t really expect a resolve to since mobi is effectively just an RSS reader is that if I post a direct link to an article somewhere, it’ll go to the homepage on a mobile. I’m assuming the only way around that is just to find a mobile theme that will work well enough with Total.

    Thank you

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter stitchkingdom

    (@stitchkingdom)

    14 years, 4 months ago

    Also, since this is still unaddressed, is there a way to limit direction so it only affects wordpress posts? my WP is at my root and if I go to subdirectories directly on a mobile, I get bumped to the mobile site which I’d rather not have happen.

    Frederick Townes

    (@fredericktownes)

    14 years, 2 months ago

    Please upgrade to the current release if you have not already. Then use the rejected user agents box on the various active caching tabs, to specify the mobile user agents you want to be handled with mobilepress, mofuse etc. So doing this will prevent W3TC from trying to cache the request and become confused about which user agent needs which cached file. If you’re using an origin pull CDN, you do not need to add rejected users agents on that tab.

    There are some rather elegant mobile features coming that I’ve yet to see any plugins address as yet, so for now the above should suit you fine.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Problems with mofuse and W3 Total Cache’ is closed to new replies.