Pirenko saidPage caching plugins create a static html version of the page which is served by the webserver directly using .htaccess rules, no php is involved in the process.
As far as I know sessions are created each time you open a website after a long period or after having closed and opened the browser application. So there’s no caching thing here. At least it seems to be like this to me
EugeneO saidyep, exactly. Device dependent server side code should never be used for this reason. I recall some caching plugins like wp super cache disabling cache for mobile devices but i don’t like this approach a bit because it hurts performances.
If you are using a caching plugin wouldn’t a visitor to your site see a cached version of the page whether they are on a device with a retina display or not.
This is the kind of stuff that should be handled client side only, we’ve been thinking about a possible solution which involves setting multiple “data-src” in imgs element and then using js to load the appropriate source for the detected device.
However, i’m still not sure whether this whole retina thing is worth the effort or not. Apps and games are fine but for websites on mobile devices, to serve bigger images doesn’t seem a good idea when you think most of them will be on slow/data limited 3g connections (no reliable way to detect available bandwidth).
didn’t have the time to check yet but i bet this was caused by latest url changes. To fix, it should be enough to edit the script header part where urls are listed.
Jordan_M saidThat’s clear to any existing members, the concern is about new potential buyers landed to TF. They know nothing about those differences and first thing they going to see is the “Web Design from $20” link bringing them to a whole different site.
It’s really important to keep in mind that what you get on Microlancer is fundamentally different to what you can get on the Marketplaces – we’re talking apples and oranges here.
RubenBristian saidIt does. You don’t drive new potential buyers away. They don’t find what they’re looking for, they don’t know TF != ML and therefore you could have just lost them.
It doesn’t matter if the banner drives buyers out if they won’t find what they’re looking for on ML.
We will not remove our custom post-format related metaboxes in 3.6 for a lot of reasons. I find the new UI pretty confusing to be honest. There’s a lot of discussion around this feature, some people think it should be moved to 3.7 and others propose to delay 3.6 until it gets better.
she’s beautiful J