Best Of
Re: NEW critical security update: Vanilla 2.6.3
@R_J said:
That version as of now will crash your dashboard
Fixing now. Version 2.6.3 incoming.
It's never a good sign when I wake up in the morning and there's actually comments on the release discussion!
Re: Moving to domain.com/subdirectory from another forum.domain.net
@zonmo2 said:
When I create a new account in WHM no subfolder for domain.com is created. This makes quite a mess when you add numerous addon domains, especially when you use something like WordPress on the main account domain, as it's full with WordPress folders AND addon domain folders, eg:
Sorry, but what has that to do with Vanilla Forums? Shouldn't that be posted in either the cPanel forums or WordPress Forums?
Since it is not a WP issue, I suggest you complain about that on the cPanel forums
Re: Critical security update: Vanilla 2.6.1 is here
For those still running PHP 5.6, we've now released Vanilla 2.5.3 - now 2.5.4 with a patch for the disclosed vulnerability and a few other security patches.
If you are able to run PHP 7.0+ we strong recommend you do so immediately and upgrade to 2.6.1 (above).
Critical security update: Vanilla 2.6.1 is here
All installations must be upgraded to Vanilla 2.6.1 immediately. Please follow the upgrade instructions in the README.
Full release notes will follow shortly. This release contains multiple security patches, including a critical exploit that was publicly disclosed today. There are no new features or backwards-incompatible changes.
A security-only update to the 2.5 branch of Vanilla will also follow, in this same discussion.
Re: How do I install Italian locale?? 2.6.1
Thank you...thats the answer I was looking for!
Apologies to everyone in Vanilla community
I have been bombarding this forum!!! didn’t mean to be a pain in the you know what.... but anyway thank you to everyone who has helped me get started.
Re: Embedded tweets in post - error
Gah I'm getting out of touch.
Re: How to add a description to theme options?
Simply add a Description to the options! 
$ThemeInfo['jeongwee'] = [
...
'Options' => [
'Description' => 'If you like this theme, please consider giving me all your money',
'Styles' => [
'day' => '%s_light',
'night' => '%s_dark'
],
'Text' => [
'FunnyQuote' => [
'Description' => 'Some text which will be displayed somewhere',
'Type' => 'textbox'
]
]
]
];
Re: Vanilla 2.5 Articles
@rbrahmson said:
I repeat my preference of using a new discussion type rather than an entirety separate application. I believe it will better integrate with all the other plugins, be more compatible and in the long run simpler to maintain.
I'm revisiting this discussion type concept. The main advantages would be immediate support for Vanilla discussion features, such as bookmarks, notifications, permissions system, and moderation. Additionally, addons that modify discussions, such as Yaga, would work without any modification. Articles can show up in discussion indexes, increasing visibility of new comments and promoting more discussion. Furthermore, it may be cleaner just to use the built-in Media model for thumbnails and so on.
Adding a new discussion type has some quirks, but I hope we can make it work.
- When adding a custom discussion type, it is enabled on all categories by default. In order to limit the types of new discussions a category can take, you have to go edit the category and then toggle the custom permissions to see a list of types to select. Assumption: admins would likely have "article contributors/authors" be opt-in by role, so we should somehow disable this default behavior on all categories. Would an admin find it inconvenient if we just let it stay auto-enabled and having to go to set custom permissions for each category? This is how Vanilla implemented their custom discussion types system.
- A visitor of your website will browse articles and experience them as being abstractly different from discussions: (1) the articles index would look different than the discussions index, of course, with thumbnail images, excerpts and large headers, (2) sidebar would show only categories that allow the article type, (3) links within the article view and article categories module would link to a custom category controller action that shows a view like the articles index. Handling proper display and separation of categories from the articles controller and discussions controller all the way to user profile indexes should be approached with attention to detail because I think articles should be separated from discussions in some places.
- When I first created the Articles app, I was still learning the ways of Vanilla and copied a lot of code from the forum components. In this discussion type concept, there would still be some code borrowed over from Vanilla, such as index logic and views since there just aren't enough events to hook into or something has to be modified in the middle, but the rest of it requires the same code, etc.
- Special case: users may want to hide articles from all discussion indexes and only show it on the articles index. Probably don't need this, but it can be added in as a config option toggle and a where clause to DiscussionModel if there are sufficient events to inject code.
This project would introduce "breaking changes" and proper instructions on upgrading would need to be written and carefully followed by admins. An export/import script would probably have to be made.
Re: Polish polish needed
@sparrowhawk66 said:
In the docs it says:To add this to your theme, use this module: {module name="FlatCategoryModule" categoryID=00}
@R_J Would it be difficult to implement in an existing theme? None of the recent themes seem to have the feature.
Trivial: just create your custom theme and add it anywhere to the default.master.tpl of your theme. You might have to style it, depending on the place where you like to see it and the theme you are using. If it should be just one anyway in the Panel, just like any other module, you should insert it with some lines of code in your themes theme hook file.
I haven't looked at flat categories by now, so I cannot give you any answers, sorry.
When I said "you can write plugins", I meant "a developer can write plugins and that will be either you, someone you pay or someone that you convince to write it for you because it is such an outstanding idea"
