Composer does this build process as well. It's how we're now handling dependencies, which each get their own repo.
It would be great if we had a documented function list rather than searching for them in the core and then researching each to e…
First, I think distributing a "generic functions" plugin is a very bad route. Generic functions go in core, that's the point. No one wants to maintain extra plugins - neither the author nor the end user. I'd take this off the table.
Second, I wou…
Also note there is an "Email" permission that you can revoke from a role to prevent them from receiving any email. That is perhaps the easiest solution to "deactivate": just stick them in a restricted role.
A controller is definitely the best way to go about this. It's straightforward, clear, and less prone to future issues. @Bleistivt is correct: applications will one day be folded into plugins. There is precious little difference between them at this…
I really thought it was used at some point.
My feeling is it should be removed to avoid security complacency. I've heard folks confuse it for the only needed permission check on that page, and that worries me.
Official means only that it is official, it does not imply that it works or that it is updated, sometimes the addons are abandoned in the add-on section and switched to github. Official implies nothing.
That's straight-up fa…
@Andrew4848 I apologize for the digressions. I've filed an issue to resolve the problem in the WordPress plugin. I hope to have a new version released in late August. The suggestions above won't hurt in the meantime if you cannot wait that long.
It won't help me , I have not been able to do it correctly
There are links to our repo from:
* The Vanilla download page
* The sidebar of EVERY page in th…
Ha, yeah, I guess it wouldn't get along with Markdown so well in its default form. I guess there has always been a strong correlation between folks who use Civil Tongue and folks who use WYSIWYG formatting. Personally I've never been a fan of either…
We've filed the Facebook deprecation as an issue to resolve: https://github.com/vanilla/vanilla/issues/4129
I didn't realize the deadline was so close, however. I moved up the milestone to be completed this month.
I frequently get responses from people who tell me about issues that have been around "years" because someone talked about it on the forum and never actually raised it up for the developers to look at formally.
Suggesting hacks to individuals mea…
I wasn't involved in it really so I don't have any great insights here, sorry.
I was however having a idle thought about maybe skipping 2.4 and jumping us straight to 3.0 this winter tho. Depends how things go with API v2.