Recently Browsing 0 members
No registered users viewing this page.
while developing a sideproject which is completly build with ProcessModules i suddenly had the urge to measure the performance of some modules 😉 as a result, say welcome to the FlowtiAppPerformance module.
It comes bundled with a small helper module called FlowtiModuleProfiler. In the first release, even though you could select other modules, it will track the execution of selected Site/ProcessModules.
This will give you the ability to gain insights how your Application behaves.
The Main Module itself will come with 2 Logging Options, Database or PW Logs. Select Database for Charts and Logs...well If you just want your profiles as a simple log file in PW.
You also could choose to dump the request profile into TracyDebugger as shown here:
Dont wonder about my avg_sysload, somehow my laptop cant handle multiple VMs that good 😄
again, dont look at the sysload 😄
I will update the Module in the future to give some filter options and aggregation, but for now it satisfies my needs.
I hope it is helpfull for some.
Module is submited to the directory and hosted at github
Any suggestions, wishes etc. are much appreciated.
I want to allow full text search on my site. There is a very nice solution that comes right out of the box:
$selector = "title|body~=$q, limit=50"; This works, but to make it even better I would want to give higher weight to pages where the search term occurs in the title, than if it just occurs in the body. After all, a page with the title "Wine from France" is probably the best match for the search "france wine". How do I accomplish this in ProcessWire?
I can see three possible paths, but I am not very fond of any of them:
Do a direct SQL query, circumventing the API, along these lines. But I would prefer to abstract away the database layout if at all possible. Use something like ElasticSearch, but to be honest that would be to complicated to set up and maintain in the long run. Make multiple lookups, first for matches in the title, then for matches in the body, and merge and sort in PHP. My suspicion is that this would get complicated quite quickly. For instance, how do you deal with a page that has two of the three search terms in the title and the third in the body? Is there a magic option four I should look into? Or are any of the above options better than the others? Any input is welcome!
This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory
I am using ProCache v3.1.8 on ProcessWire 3.0.96.
Everything worked fine in the past, but today I noticed that the css file serverd by procache gives a 410 error.
The file is there, I checked.
I deleted the cached files, I deleted the css file, I looked into the .htaccess file looking for some clues about this problem but nothing worked.
The only way i can see my website correctly again is disabling ProCache.
Has anyone any clue on what could be the cause of the problem or on what should I do to fix it?
Hy Processwire community,
There are some problem in fileCompiler cache.
when i change under the directory \site\templates\ it must change under the directory /site/assets/cache/FileCompiler/site/templates/
but it does not update and functionality working with /site/assets/cache/FileCompiler/site/templates/ directory.
In this case please suggest me how i clear fileCompiler cache?
what i have to clear it manually?