Jump to content

Search the Community

Showing results for tags 'cache'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

  1. Hello, I was having some trouble installing modules (they weren't showing up in the module manager) and so I deleted the contents of the folder site > assets > cache in the hope of fixing this problem. However, having done this any page I try to navigate to on the site (including the root /index.php) throws up a 500 Internal Sever Error. Does anyone have any idea about what might have gone wrong here? It's slightly worrying... Many thanks in advance for any help. b
  2. Hi there, If I do some conditional output, for example if($config->ajax) { echo 'something'; } else { echo 'somtething else'; } And then switch on cache for this particular page. I guess the first hit will determine what gets stored in the cache? The second hit will get the same results regardless. So that means I cant really have conditional output and caching at the same time, right? If I use ProCache, it's cached by URL instead, right? So then there can be multiple versions of the same page, depending on the URL? For example if I use #!, then the ?_escaped_fragment= version of the page would be cached separately, I suppose? Just trying to see If I understand how it works correctly thanks, J *edit: procache question
  3. Hello everyone, I have a question to Ryan and the PW experts here: in the upcoming PHP release 5.5.0 we are going to see Zend OPCache, a caching mechanism similar to APC. How does it compare to Cache Pro? Will Cache Pro still be needed if OPCache is used? Just a side note: I am buying CP as soon as my web project goes into production simply because I love PW and want to contribute. But will it decrease the page loading time any more than it will be possible with OPCache? Thank you.
  4. I have activated the Cache module and then configured the cache in Setup -> Templates -> Cache, where I have set the expiration to 3600 seconds for all my templates. When I run ApacheBench to stress the server, I am seeing exceptionally high load. My throughput is only ~10 requests/s despite the page being cached, and I can see high MySQL traffic, even though cache is supposedly activated. Is this expected behaviour? Are there any high-performance cache options available? (That preferrably don't query the DB at all when a cached page is requested.)
  5. Hi, I have a couple of restricted templates using the "Redirect to another URL" if the user doesn't have access. I redirect to a custom login page with the {id} tag. On successful login the user then gets redirected to the page he/she was trying to access in the first place (if the user in question has access to the page). You probably get the point. I now have a user who gets the "too many redirects" browser issue. I haven't been able to reproduce this so it's too early to draw any conclusions. Anyone else having similar issues? Also pw seems to always redirect with a HTTP 301 internally, i.e. the "Redirect to another URL" functionality, and these are cacheable in the browser (http://en.wikipedia.org/wiki/HTTP_301). PHP does however by default add headers that should make the browser not use cache: the no-store, no-cache, expires etc. This would effectively make the 301 (permanent redirect) behave like a 302 (temporary redirect), however the browsers have as far as I know have not been particularly good at following the recommendations regarding cache headers. Is there a reason for always using 301, in the pw core?
×
×
  • Create New...