Stefan Kalscheuer
Forum Replies Created
-
Forum: Plugins
In reply to: [Statify] aggregated info about resolution/browserNote that Statify does not aggregate on every hit. Each visit is stored in a single DB row and aggregated for visualization when accessing the dashboard.
With UserAgent (full string) and exact resolution one might recognize at least some visitors.
Second point: How to aggregate?
There are thousands of Browsers out there, think of all Chromium-based derivates… Major 10 + “others”, always last part of the String, …? Versions?
Even worse for resolution. width classes, height classes, pixel-count classes, what about DPI?I’m not sure if that kind of statistics really fits the scope of Statify. Could be an idea for a possible Extension Plugin though.
- This reply was modified 8 years ago by Stefan Kalscheuer.
Sure, that’s the obvious workaround. But as I said, I have a couple of older galleries with slashes (e.g. dates in form MM/YYYY) which have been converted to dashes (MM-YYYY) automatically. Seems this “feature” has been removed somewhen in the past.
I’d personally be fine with disallowing such characters on creation, favorite solution would be smart sanitization for the slug though.
Thanks for having a look into that!
Regards,
StefanForum: Plugins
In reply to: [Statify] Error: Failed to load resourceHi,
reason for that is most likely that you are using developer tools with your browser that try some JS mapping. So it’s not critical as no “normal” user will ever trigger such warning.
Nevertheless the maps are explicitly referenced in the pre-minified JS libs, so they could be added with the next update (or the corresponding reference removed).
Regards,
StefanSorry for that, you’re absolutely right. The site actually has a album called “gallery”, so I messed this up here..
What I was talking about is a Gallery with a slash in it’s name. So the attribute
<prefix>_ngg_gallery.slugstill contains the slash.
Hence the link to the gallery within the album (created via shortcode[ngg_images album_ids="...]leads to a blank page telling “no images found”.Forum: Plugins
In reply to: [Statify Filter] Seit Einsatz des Plugin werden Admin-Besuche mitgezähltDanke für’s Melden 😉 Sollte mit 1.3.1 behoben sein.
Forum: Plugins
In reply to: [Statify] Statify counting admin visits after theme changeIt was the plugin’s fault, mea culpa!
Using the filter hook and returningfalsemade Statify leaving the filter chain even if blacklist is disabled or not applied. In fact it’s not only admin visits, but every built-in filter has been skipped. Changed that behaviour in Blacklist 1.3.1 release a few minutes ago.I could confirm the bug with different WP instances, hence I can’t imagine any correlation with the change of theme. Maybe just noticed by closer observation afterwards.
Forum: Plugins
In reply to: [Statify Filter] Seit Einsatz des Plugin werden Admin-Besuche mitgezähltKann ich bestätigen (auf mehreren 4.6 und 4.7 Installationen mit selbstgebauten Themes). Offenbar beendet der Filter Hook in Statify selbst die Ausführung, wenn ein Plugin ein Ergebnis zurückliefert.
Ich evaluiere gerade, ob ich lieber den Rückgabewert im Plugin anpassen oder den Hook Filter Hook in Statify selbst anpassen sollte. Fix sollte in den nächsten Tagen kommen.
- This reply was modified 9 years, 5 months ago by Stefan Kalscheuer.