HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
NEW: official docs, repo changes, site updates, and releases!
You probably saw we released 2.1 stable today and refreshed this site's theme.
Here's a few more things you might have missed in the last few days:
- At long last, the GitHub repo was renamed from
Garden
tovanilla
. Clarity! - We rewrote the README so it doesn't suck. Hello world!
- We launched docs.vanillaforums.com which is mapped to an official docs repo. Oh snap!
- The changelog is up-to-date for the first time since, I dunno, 2011? Yowza!
- Vanilla Porter hit 2.0 with new support for vBulletin 5 & IPB. Bam!
- After a long stint as "stealth" open source in our Addons repo, the Multilingual plugin was officially released in the directory. Ciao!
- This site got the cloud-exclusive new mobile theme Lithe for your browsing pleasure. ^5 @Kasper!
I hope today assuages any fears that we are less than serious about our open source project (and then some). We've stepped up our game, and the community has certainly stepped up theirs to match these last few months.
We couldn't be happier with all the testing, GitHub tickets, and pull requests we've been seeing, especially in the buildup to 2.1. Thanks for your continued support. Cheers, everyone!
9
Comments
Congrats...
party!
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Woot!
Time to update client installs.
@Kasper I am loving the new mobile theme! Where can I submit feedback?
Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.
Wow I think I am having palpitations !!
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
@hgtonight Glad you like it! You're more than welcome to submit feedback directly via email
Kasper Kronborg Isager (kasperisager) | Freelance Developer @Vanilla | Hit me up: Google Mail or Vanilla Mail | Find me on GitHub
@Kasper
the lithe mobile theme looks great. I really like the pop-to-side panel on left when clicking top left.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
and the most important thing missing in the (dealing with bonk errors).
http://docs.vanillaforums.com/
it is however in the old documentation.
http://vanillaforums.org/docs/errors
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
@peregrine that old page is deprecated by the simpler Debug=TRUE, which is the first step on the new troubleshooting page: http://docs.vanillaforums.com/developers/troubleshooting/
The docs repo has moved to: https://github.com/vanilla/vanilladocs
Updated the link above.
sadly, I think the original docs provided more information and was easier to navigate than the current docs and it really needs a big splashpage with links, like the wiki, that hbf has.
It could be just me adjusting. but
I still can't fathom at all why the vanilla crew - can't put a friendly link for the wiki that many have added to anywhere in the official documentation. Is having a friendly link to the wiki something that would cause vanilla to implode upon itself.
http://vanillawiki.homebrewforums.net/index.php/Main_Page
noticed a few typos - in docs like configuation
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
The URL for the community wiki isn't exactly business friendly (I like beer, but some might get turned off by homebrewforums.net).
Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.
yea I guess that is why the "homebrew" computer club never blossomed and no businesses started using pc's
http://en.wikipedia.org/wiki/Homebrew_Computer_Club
http://www.computerhistory.org/revolution/personal-computers/17/312
I suspect the url name has absolutely nothing to do with reason for not including wiki. if it does, then let it be said.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
It looks very nice. I am sure it is going to grow and possibly even include a wiki. How do I know this? The same way I knew there would be a version 2.0.18.11 before anyone else did.
Give it a few weeks I say. And we can provide the wiki link for as long as it is needed.
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
on this page
http://docs.vanillaforums.com/
link is broken here for "open source project"
Vanilla Forums Official Documentation
You can contribute to these docs via the GitHub repository.
Vanilla Forums consists of both an open source project and a cloud hosting solution. The documents cover five major areas:
it seems clicking on open source project should go here: https://github.com/vanilla/vanilla
not here as it does currently:
https://github.com/vanillaforums.com/vanilla
or I'm confused. where it is supposed to go... the current link does not work.
or maybe you haven't switched over to the new location. I'm a bit lost. bits of info all of over the place and hard to figure out which is the current state. I get confused easily, and i read the discussions daily, I imagine there's a few people who may be equally confused, if not more
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Thanks, just me typing too fast.
The docs have its own issue tracker: https://github.com/vanilla/vanilladocs/issues
well, at least now you know in case you want to make the simple change. good to know about the issues tracker on documentation.
just a thought: if the issues in the documentation were updated on a regular basis (weekly or monthly) and reviewed and changed on a regular basis (weekly or monthly) without a pull request (by just noting the issue or problem in a comment or issue., maybe more people could improve the documentation.
I know there are other fish to fry and more important things to do like fixing some of the plugins, so docs would take a bit of a backburner.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
I rewrote the main Framework page and these over the weekend: