Best Of
Re: Still getting this PHP error [RESOLVED]
Oh no, that's not too encouraging...
Vanilla 2.6 is here - includes security fixes
Vanilla 2.6 is now available. It requires PHP 7.0 or higher. This release brings a number of great enhancements to Vanilla, most notably the new "Category Following" feature that lets you filter the Recent Discussions page to only show discussions from select categories.
If you are not ready to upgrade to Vanilla 2.6 today, please install Vanilla 2.5.2 immediately (also released today). It maintains PHP 5.6 compatibility and provides important security updates to Vanilla 2.5.1 and lower.
Upgrading
- Vanilla 2.6 requires PHP 7.0 which is a change from earlier versions. We strongly recommend upgrading to PHP 7.2 as soon as possible. Many hosting plans allow a seamless transition via their control panel.
- Follow the normal upgrade process, including running /utility/update.
- Delete
plugins/Taggingandplugins/HtmLawed. They are now part of core and may conflict. - We strongly recommend deleting the contents of your
/cachefolder after upgrading, and again if you experience issues after the upgrade. - Test your plugin & theme compatibility in a safe place before upgrading your production forum.
Upgrading from Vanilla 2.3 or earlier, note this additional step: Manually delete /applications/vanilla/controllers/class.settingscontroller.php, then clear the cache folder.
Enabling Category Following
Category Following adds a menu to several pages. Therefore, it is OFF by default after upgrading. Please test your theme for compatibility before during it on in production. To turn it on, go to Dashboard -> Settings -> Categories and click the small control panel icon (next to the "Add Category" button). In the popup, toggle the feature 'ON' and click 'Save'.
Getting Help
IF YOU NEED ASSISTANCE, START A NEW DISCUSSION. If you are a developer and locate a reproducible issue, please file it on our GitHub tracker, noting your version as 2.6. We greatly appreciate the assistance.
Thanks
Thanks you everyone who contributed to Vanilla since the 2.5 release whether that was thru filing issues, submitting patches, participating in our HackerOne campaign, or helping folks on this forum. @R_J and @tflight contributed patches to 2.6.
Please upgrade to 2.6 as soon as possible!
Re: Prototyping custom themes for 2.5.x using XAMPP? [RESOLVED]
"key": "Godot", // Exactly the same as the resulting folder for the otherwise copied theme
I guess, that's just in your comment? Otherwise it would be invalid json.
Try clearing the addon cache. For development, I usually add this to a plugin so I don't have to clear it by hand every time I make changes to an addon.json:
public function settingscontroller_afterDisablePlugin_handler() {Gdn::addonManager()->clearCache();}
public function settingscontroller_afterEnablePlugin_handler() {Gdn::addonManager()->clearCache();}
public function settingscontroller_afterEnableTheme_handler() {Gdn::addonManager()->clearCache();}
Re: jsConnect and AutoConnect
It's posts like this one that go unanswered for two + days that reaffirm that I am in no hurry to upgrade my (delicate) SSO forums. That is my main complaint with vanilla forums.. piecemeal documentation and scattered forum responses.
Do NOT use this forum for HackerOne type activity.
Accounts using this forum to test Vanilla's vulnerabilities will be deleted on sight.
The terms make it clear you should NOT be using live sites.
Re: Transifex isn't updated
Any update on this? Still looks like the majority of locales are from November 2016.
Addon directory fixes
Hey guys,
The addon directory has some issues:
- If you go to an addon download page, the link to the author is broken (because the output of UserUrl is needlessly escaped again, even though userURL already sanatizes dangerous input).
- It completely ignores addon.json files in your zip file and it requires a PluginInfo array in your plugin file (even though that approach is deprecated). See this issue: https://github.com/vanilla/community/issues/135
- If your main class is class.Fancyplugin.php, it fails because it requires either class.FancyPlugin.plugin.php or default.php
- Plugins, applications and themes are now all addons. But there is no general addon type, so even if the addon directory would parse the addon.json file correctly, it wouldn't work because it has no type to file it under.
I think I fixed these various issues, but does someone have time to try out the fix / check the style requirements before I create a pull request?
https://github.com/Caylus/community
Re: Any plugin conversion tool available/necessary for Vanilla 2.5?
@Caylus said:
For my own use I've created this plugin:https://github.com/Caylus/PluginFixer/blob/master/class.PluginFixer.php
I'm strongly against running any automatic "fix" against the addon section though, since it's really hard to protect against all the exceptions to general rules, and odds are you break quite a few plugins by trying to fix them.
I just convert individual plugins, then I can at least test them individually to make sure they still work after my "fix".
I strongly agree that this is a better approach.
Here is my contribution for the addon.json update: https://github.com/R-J/addonjsonexporter
The plugins setting screen shows a dropdown with all available plugins and shows all internally stored plugin info keys in json format
Re: Any plugin conversion tool available/necessary for Vanilla 2.5?
For my own use I've created this plugin:
https://github.com/Caylus/PluginFixer/blob/master/class.PluginFixer.php
You download a zip file from the addon section, go to the settings page of this plugin, upload the zip file and download a "fixed" zip file.
It basically creates a addon.json file inside the zip file, and makes sure the classname is called KeyPlugin (older plugins sometimes only have a Key as name).
I'm strongly against running any automatic "fix" against the addon section though, since it's really hard to protect against all the exceptions to general rules, and odds are you break quite a few plugins by trying to fix them.
I just convert individual plugins, then I can at least test them individually to make sure they still work after my "fix".
Re: Official Feedback Thread
Of course it should be changed, but it should do by owner with update in repository.
