-
Posts
2,086 -
Joined
-
Last visited
-
Days Won
51
Everything posted by wbmnfktr
-
Awesome! As always.
- 1 reply
-
- 1
-
- sitebuilder
- builder
-
(and 4 more)
Tagged with:
-
User Activity module AJAX forbidden due to updated apache
wbmnfktr replied to adrian's topic in General Support
Oh, no... sorry. Don't have that. ? -
User Activity module AJAX forbidden due to updated apache
wbmnfktr replied to adrian's topic in General Support
What Pro module is this or where do I would get it? -
Isn't this the most modern way of doing it? html, body { height: 100%; } body { min-height: 100vh; // those who don't know min-height: 100svh; // those who know margin: 0; }
-
Module: Most Viewed Pages Tracker (UpdMostViewed)
wbmnfktr replied to update AG's topic in Modules/Plugins
I bet it does but not on the homepage. I skipped through your website and the only page that is cached by ProCache, is the homepage. At least that's the only one I found. Pretty sure as ProCache bypasses all PHP. Just checked it with this. public function init() { if ($this->user->isLoggedIn()) return; // necessary as the backend would trigger this as well $this->wire->log->save('debug', "from init"); } public function ready() { if ($this->user->isLoggedIn()) return; // necessary as the backend would trigger this as well $this->wire->log->save('debug', "from ready"); } I don't know the details about cache maintenance in ProCache but it's more than the init/ready methods. It absolutely is. And yes... you could prioritize hooks but that wouldn't help in this case - I guess: https://processwire.com/docs/modules/hooks/#hook-priority -
Module: Most Viewed Pages Tracker (UpdMostViewed)
wbmnfktr replied to update AG's topic in Modules/Plugins
What's your cache's lifespan? I use 604800=1 week for almost everything. Homepage cleares after an hour, RSS isn't cached at all. Both are the only ones that receive any counts at all. That only triggers when ProcessWire/the module actually boots up. So on first uncached page load. After that neither ProcessWire, nore the module know anything about page loads due to ProCache magic accessing the cached versions. In conclusion you might receive more counts but probably have a way lower lifespan set in ProCache or parts of your page's cache are more often invalidated. I most often publish in chunks once a week so there isn't much happening in terms of deleting the cache. Was my first thought as well! -
Module: Most Viewed Pages Tracker (UpdMostViewed)
wbmnfktr replied to update AG's topic in Modules/Plugins
So... yet another short update here. 2 sites - almost identical in terms of ProcessWire and overall setup - both have issues, only one uses HTMX for preload/prefetch, both use aggressive ProCache settings (cache lifetime 1week+). I'll rule out that HTMX as the issue here. I deleted the MostViewed-log file on both sites, after putting all pages in cache, only un-cached pages were registered anywhere. Can you please double-check and verify on your own site that it still works on pages that are cached in ProCache. A few hours later... [Sponge Bob - sequence voice] -
[SOLVED] Update to TracyDebugger 4.26.33 throws error
wbmnfktr replied to wbmnfktr's topic in Tracy Debugger
My Tracy is from a few days ago without any configs changed. Anyway... version 4.26.34 works perfectly fine! -
Just updated to the latest TracyDebugger version (4.26.33) via Upgrades (ProcessWireUpgrade) module and run into the error above. ProcessWire 3.0.240 PHP 8.2
-
Module: Most Viewed Pages Tracker (UpdMostViewed)
wbmnfktr replied to update AG's topic in Modules/Plugins
I looked into the stats once in a while and tried to figure out whats happening but still have no clue. Just for yesterday (2024-07-10) the overall numbers are this: MostViewed logs: 19-28 views tracked (only 3 detected bots and therefore no tracking) MostViewed overview: 20 views listed Google Search Console: 79 clicks Analytics: 132 page views (107 unique visitors) MostViewed's numbers are fine within itself. The 24 hour range is a bit blurry in the logs so I would say this is ok. Looking into the 79 registered clicks in Google Search Console and comparing those with 107 unique visitors in my analytics does make absolute sense when looking into the sources/details which show 83 hits from Google overall and some other sources. So it's not that the module catches too many bots or that the numbers are just slightly off. The views don't even reach the module. I thought about ProCache as an issue but you already cleared that. Cloudflare CDN shouldn't be a problem as well - that would filter out absolutely everything. Here comes the fun part: MostViewed tracks my RSS feed, which isn't tracked/listed/shown in Google Search Console or web analytics and that number is 100% on point. That RSS feed is not cached by ProCache, just standard cache for 1 hour, it's not linked anywhere in the frontend, it's just plain PHP and some RSS/XML output and it doesn't use any templating engine. There are two last things that I can think of that might cause this: HTMX Preload Plugin - some weird AJAX content switching voodoo ProCache - still, as it bypasses almost everything and goes straight to static files -
Just to clarify a few things... is this the overall structure you have/want to accomplish? ├── Homepage ├── Houses (template: houses) │ ├── Small House (template: house) │ ├── Medium House (template: house) │ ├── Big Mamas House (template: house) │ │ └── ref_floors: (page reference field: "parent=floors, template=floor") │ │ ├── Basement │ │ ├── 1st Floor │ │ ├── 2nd Floor │ │ └── 3rd Floor │ ├── ... │ └── Super Large House (template: house) ├── Floors (template: floors) │ ├── Cellar (template: floor) │ ├── Basement (template: floor) │ ├── 1st Floor (template: floor) │ ├── 2nd Floor (template: floor) │ ├── ... │ └── Attic (template: floor) └── ... If so... could you mark and add more details where you need some kind of logic/automation, please. And those additional fields where you want to add custom content if and where needed.
- 11 replies
-
- 1
-
- page reference field
- field
-
(and 1 more)
Tagged with:
-
Now I am curious how you solved that. Can you post a snippet of your solution, please.
-
That's awesome! Side note: Perplexity does such a great job with tasks and questions like this.
-
Looking for an AI assistant for code? Consider Supermaven
wbmnfktr replied to gornycreative's topic in Dev Talk
I am still on the free plan for now - might get the pro for Claude Sonnet 3.5 support in the chat as that models is a true banger. Whatever nonsense I throw at it, it gets the gist and gives me at least a solid foundation to work on - sometimes even a completely fine working solution. -
Looking for an AI assistant for code? Consider Supermaven
wbmnfktr replied to gornycreative's topic in Dev Talk
Out of curiosity, I installed Supermaven yesterday, even though I was quite happy with Codeium, and started playing around with it since then. For now, I am super impressed by its speed, accuracy, and knowledge. While Codeium is more on the PHP side of things, Supermaven seems to know more about or even understands ProcessWire. -
Weekly update and new blog post – 28 June 2024
wbmnfktr replied to ryan's topic in News & Announcements
Haven't played with it yet, but I already love it - and I would pay for it when it solves the issues I face in a project right now, to be honest. A recipe collection with only 200 recipes in 20 categories/cuisines/styles is already hard to manage. I have ProLister but THIS here... is a real game changer. Update: It works as I imagined. Those Kategorien (categories) now list all those recipes (from Low Carb Rezepte) that were assigned by a page reference field. It's great/awesome/I love it! Update 2: One disadvantage of using this module is that you are reminded of how bad your data structure really is. And that even sideprojects should be build with a bit of thinking. I could cry (for joy). ?? What a total chaos. Every line and therefore template and fields to exactly the same. -
Interim status: About almost 2 weeks in on Manjaro... in a VM (on the main machine but as a daily, beside e-mails, yes performance is not an issue) and on real hardware... outside of home on a Thinkpad X260 (still no performance issues, maybe even better). NOPE. Not for me. Don't like it. Doesn't feel right. It's off. A bit. Don't know if it's Manjaro, as I had troubles with it in the past, or the fact that I had to download about 2GB of updates since installing it already or the keyring issue I had (probably from AUR package - didn't look deeper into it). Nothing I have seen or had issues with on Ubuntu 23.10 since installing. There was a reason I moved to Debian Stable quite a whille ago just to have less updates just because my internet speed here was about 0.5 Mbit in total (DON'T LAUGH! I live in Germany. That's fast internet on the countryside here ?). It's faster now, still... downloading such big updates feels weird to me. Especially in that time period and there was no major Manjaro release since then. I will try it for another two weeks just to ... either feel more at home and give Manjaro a bigger chance to convince me. remove my bias towards Manjaro don't give up too fast (again on a distro) But to be honest, even though everything works, I don't feel at home. Even less at home than on Fedora, which feels like walking on raw eggs for some kind. I have my i3 and Gnome, my keyboard shortcuts from sxhkd, my overall settings from my dotfiles, but still... Did you guys ever felt NOT AT HOME on a distro and if so WHY?
-
Could it be that you acutally use a multi-image field aka an image field that allows multiple images? If so that image part needs to be in a foreach() or you need to use $image->first() and go from there. // probably easier to use first() here as you only want to show one picture $image = $content->$block->cover_img; // Access the block property dynamically if ($image) { $cover_image = $image->first()->size(0, 2000); echo "<a href='{$content->url}'><img src='{$cover_image->first()->url}' alt='{$cover_image->first()->description}'></a>"; }
-
Module: Most Viewed Pages Tracker (UpdMostViewed)
wbmnfktr replied to update AG's topic in Modules/Plugins
Sure, of course. https://drive.google.com/file/d/13hkrLH-SGI4zLxVDIjlHVHPAiFZPU0iI/view?usp=drivesdk https://drive.google.com/file/d/1n__9Fsj14CO_l8EyapjvzftqKl-mR8gU/view?usp=drivesdk -
I have read this 10 or more times now and I am still not sure if my understanding is correct, so therefore the following is a bit of a deep-dive here: You have pages around in your site, that are somewhat special beneath/below other pages or at least need to be treated like they are special/or somewhat. I imagine it like something like this: Spain ... France Eiffel Tower (this is the special one) Germany ... And now you need to know if this... referring page (France) is referring to Eiffel Tower or/and the referring page (France) was accessed and you need to know this in the referred page. see below... Case 1: When you are in need to know if a page or any page uses a reference (PageReference field) to point to a specific page (Paris -> Eiffel Tower), there is a selector for that. <?php namespace ProcessWire; // find pages that reference to a POI by POI-field // field: this_is_a_poi = page reference field to select POI pages // used in that template of target page (Eiffel Tower in this case) $who_links_to_me = $pages->findMany("this_is_a_poi=$page, parent=$page->parent") You could put that into place for your POI pages to see what other pages reference it. Case 2: Oh... and there is this $page->links() method in which you can find out which (HTML) field links to that one specific page. Case 3: In case you want to track access to referring pages we first of all need to know what kind of tracking you use, but at least PageHitCounter could be triggered via JS in case a referring page was accessed. Sure there is a bit more needed for this, but I don't know if this is the case, and won't look for a solution that deep. Sorry. ? My understanding for this: poi = POI = Point of Interest And yes... every snippet is untested. Oh... and btw. ... Welcome to the ProcessWire Forums with your first post.
-
There must be something in either the error or exception log of ProcessWire itself.