Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
ShortStat 1.3
This discussion has been closed.
Comments
(forum is my subdir, you could have something different)
This post had the solution. Oh and that config thing should indeed be 'extension/'. Hope this fixes it for others as well that use the rewriterules for nice urls.
Actually found out about the htaccess changes while trying to get your polls extension to work. Unfortunately that problem isn't fixed with this solution. At least the stats work now, looks great. Thanks for this addon!
Just for the Vanilla devs: I just installed vanilla recently, and I think those small bugs like that config setting and the htaccess rewriterules should be updated in the vanilla download. Weird problems out of the box scare new users away...
When ShortStat is disabled, the setting PERMISSION_VIEW_SHORTSTAT still shows up in the role form settings. It has no dictionary so its labeled from the $Configuration array key.
This setting is "dead", you can't change it, it's just populating the form.
It took me time to figure out how this setting is added to the form until I found that it is an "automatic feature for configuration setting named PERMISSION_*. Jazzman : how did you find this?
I'm not sure if it can be qualified for a ShortStat problem or a core one. I'll start an separate thread pointing on this one to be sure Mark have a glance.
What I don't get, parsing the source, is why the Role form is unable to toggle it. It stays in the last state set when the extension was active.
I though it might be a clue showing a way to hide inactive settings.
BTW, the fact that no definition is associated with it could be a filter?
Mark, do you encourage using PERMISSION_ and CUSTOMIZATION_ special prefixes to get automatic insertion of settings?
Or are they reminiscent/obsolete?
As they are undocumented, I'm wondering.
The query that updates the table seems to be setting the count on every record, not just the one being updated. I'd fix it, but it uses the Lussumo database classes, which I don't understand one bit.
Notice: Undefined index: p in /home/public_html/sitename/extensions/ShortStat/default.php on line 171
Is this a bug or sth that can be fixed?