Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Try Vanilla Forums Cloud product
Vanilla 2.6 is here! It includes security fixes and requires PHP 7.0. We have therefore ALSO released Vanilla 2.5.2 with security patches if you are still on PHP 5.6 to give you additional time to upgrade.

Vanilla 2.1b2 released

LincLinc Director of DevelopmentDetroit Vanilla Staff
edited September 2013 in Releases

I'm pleased to announce the release of Vanilla 2.1 beta 2. Since this is not the final release you will have to download it from it's direct link here.

Technical skills required!

This beta release is here so that the community can help us get Vanilla ready to release 2.1. Please keep this in mind when downloading it. Please do not download this release if you do not have some experience using Vanilla. You may have the best intentions, but you will be hindering, not helping the testing process.

Report issues on GitHub

We really want you to report issues on our GitHub issues page. If you don't have a GitHub account please get one. Specify your version (2.1b2) in all issues.

Configuration notes

Turning debug on will really help with testing. To do this add the following to your config.php file:

$Configuration['Debug'] = TRUE;

Vanilla 2.1 has new feature that will combine your css files into one file and minify them. This is potentially a great feature that will give a real speed boost to a lot of communities. This feature is somewhat experimental though so we've made it an opt-in feature. To turn on this feature add the following to your config.php file:

$Configuration['Garden']['CombineAssets'] = TRUE;

This release cycle is really long

We know. Please assist us by 1) testing the heck out of this release under many different environments and scenarios and 2) submitting pull requests (against the 2.1 branch) for issues tagged for the milestone '2.1'. We have no ETA for final release or moving to RC. I would expect to have a beta 3.

Thanks!

TamaUnderDogR_JphreakaglioeolioMasterOnelifeisfoohgtonightEathuisShadowdareilovetechDragstarKistlakm_hmt
«1

Comments

  • hgtonighthgtonight ∞ · New Moderator
    edited September 2013

    @Lincoln said:

    • 2013-08-24 Remove 200 header when testing an add-on. Fixes issue #1561.
    • 2013-08-24 Kill 'Remove' plugin button and all related functionality

    So stoked for these fixes!

    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.

    Akron
  • Dr_SommerDr_Sommer Dr. of tender Programing ;) ✭✭

    For first time Users, the Versioning is a bit confusing. So please correct me if I'm Wrong:
    The 2.1.x branch is the Community Edition ant the 2.2.x branch in Github is the Commercial edition?
    Is that correct?

    If YES, this AND the differences between them should be pointed out (in the FIRST Post!) because i think every potential new Vanilla User will have this Problem... like me.. ;)

    Thanks in advance.. ;)

    Cheers,

    Dr. Sommer

  • 1+ well done guys

    grep is your friend.

  • @Dr_Sommer said:
    For first time Users, the Versioning is a bit confusing. So please correct me if I'm Wrong:
    The 2.1.x branch is the Community Edition ant the 2.2.x branch in Github is the Commercial edition?
    Is that correct?

    Not understand like you but may be, you 're right but ;) even if my f**king English understanding is very bad, it's not so easy

    http://vanillawiki.homebrewforums.net/index.php/Github_Access

  • LincLinc Director of Development Detroit Vanilla Staff
    edited September 2013

    @Dr_Sommer said:
    For first time Users, the Versioning is a bit confusing. So please correct me if I'm Wrong:
    The 2.1.x branch is the Community Edition ant the 2.2.x branch in Github is the Commercial edition?
    Is that correct?

    No, the 2.2 branch is simply not tested for stability on multiple platforms yet. As far as you guys are concerned, it is "alpha" quality. Calling it "commercial" is misleading because everything in 2.2 will be in the next release cycle after 2.1. Our release cycles are just lagging a bit.

    PamelaUnderDog
  • Dr_SommerDr_Sommer Dr. of tender Programing ;) ✭✭
    edited September 2013

    Ah, ok.... Thanks for clarification... ;)
    I red many postings about the Verions and got all confused... ;)

    So to round it up:

    • 2.0.x Version is THE STABLE Version of Vanilla

    • 2.1.x is the BETA Version (Next updated stable Version)

    • 2.2.x Is an early ALPHA version

    USE the 2.0. Version in productive systems

    USE the 2.1. BETA for testing ONLY and post errors in Github

    Don't have an "USE" for 2.2.... :D :D :D

    Thanks.. ;)

    UnderDog
  • Hi, I installed this but when I want to visit the site, I get this error:

    _Something has gone wrong.

    We've run into a problem and are unable to handle this request right now.
    Please check back in a little while._

    Using Linux PC with WAMP.

  • vrijvlindervrijvlinder Papillon-Sauvage MVP

    @DogHam:

    Technical skills required!

    This beta release is here so that the community can help us get Vanilla ready to release 2.1. Please keep this in mind when downloading it. Please do not download this release if you do not have some experience using Vanilla. You may have the best intentions, but you will be hindering, not helping the testing process.

    Report issues on GitHub

    We really want you to report issues on our GitHub issues page. If you don't have a GitHub account please get one. Specify your version (2.1b2) in all issues.

    Turning debug on will really help with testing. To do this add the following to your config.php file:

    $Configuration['Debug'] = TRUE;

    DogHamUnderDog
  • ShadowdareShadowdare π Moderator
    edited October 2013

    Good job, Vanilla team. I recommend everyone using 2.1b1 to update to 2.1b2 if possible. Remember to avoid modifying the core files as much as possible and use plugins and themes instead, so that updates to Vanilla will be simple.

    Add Pages to Vanilla with the Basic Pages app | Publish articles with the Articles app

    UnderDog
  • ilovetechilovetech Vanilla 2.1 ✭✭

    @vrijvlinder @Lincoln What does $Configuration['Debug'] = TRUE; do?

    UnderDog
  • ShadowdareShadowdare π Moderator
    edited October 2013

    @ilovetech said:
    What does $Configuration['Debug'] = TRUE; do?

    The boolean value of the $Configuration['Debug'] config setting determines the error reporting level Vanilla will set for PHP during initialization.

    When this config setting is set to TRUE, more PHP errors will be shown for development and testing purposes and the PHP setting display_errors is enabled.

    When set to FALSE, only PHP errors appropriate for production websites will be shown and the display of errors depends on the web server's php.ini config setting.

    When the config setting isn't set or assigned to NULL by the admin, the error reporting settings in the web server's php.ini config file will be used.

    Add Pages to Vanilla with the Basic Pages app | Publish articles with the Articles app

    UnderDog
  • ilovetechilovetech Vanilla 2.1 ✭✭

    @Shadowdare said:
    The boolean value of the $Configuration['Debug'] config setting determines the error reporting level > Vanilla will set for PHP during initialization.

    When this config setting is set to TRUE, more PHP errors will be shown for development and testing > purposes and the PHP setting display_errors is enabled.

    When set to FALSE, only PHP errors appropriate for production websites will be shown and the > > > > display of errors depends on the web server's php.ini config setting.

    When the config setting isn't set or assigned to NULL by the admin, the error reporting settings in the > web server's php.ini config file will be used.

    Woah! Then that thing has more work to do then me in a 1 hour chicken buffet!

  • ilovetechilovetech Vanilla 2.1 ✭✭

    @Lincoln @Mark I'm loving the work you guys did on Vanilla 2.1b2! It's really efficient and really pretty! If I find anyone interested in hosting a forum or using a forum hosting service OR using another forum hosting software, I will definitely point them to vanillaforums.org or vanillaforums.com for dedicated paid hosting!

  • LincLinc Director of Development Detroit Vanilla Staff

    @ilovetech Thanks. Mark hasn't been working on the project for quite a while. Todd is the product lead so you'll find many of the improvements trace back to him, and Tim contributes regularly too.

    hgtonightUnderDogilovetechalkol
  • ilovetechilovetech Vanilla 2.1 ✭✭

    Well then

    @Lincoln @Mark @Tim @Todd @VanillaStaff I'm loving the work you guys did on Vanilla 2.1b2! It's really efficient and really pretty! If I find anyone interested in hosting a forum or using a forum hosting service OR using another forum hosting software, I will definitely point them to vanillaforums.org or vanillaforums.com for dedicated paid hosting!

  • jens1seojens1seo
    edited October 2013

    I installed v2.1b and im not a programer by any means. Am I heading down a blind alley? should I uninstall 2.1b? Tama is strongly recommending 2.1b for a theme he's working on. If I leave it I'd be happy to add the code to help with the beta

  • ShadowdareShadowdare π Moderator

    @jens1seo, I am sure you have got Vanilla 2.1b2 working just fine. Please don't fret about not being a programmer as it is good to receive feedback about Vanilla from non-programmers as well. :)

    Add Pages to Vanilla with the Basic Pages app | Publish articles with the Articles app

    UnderDog
  • jackjitsujackjitsu ✭✭
    edited November 2013

    Are there upgrade instructions somewhere?

    Or do you treat this like a full fresh install again and use the import tool?

  • whu606whu606 I'm not a SuperHero; I just like wearing tights... Moderator
    edited November 2013

    @jackjitsu

    Bear in mind this is a beta release and, whilst many people are using it successfully, it is not yet released for production sites.

    If you are at all unsure, you should stick with the latest stable release.

    If you still want to have a go, this thread may be of use:

    http://vanillaforums.org/discussion/24793/yet-another-vanilla-upgrade-and-duplication-tutorial#latest

    If you do use it, please be prepared to report issues you find on Github, to help the team to improve it further.

    UnderDograjlaksh
  • Im a techie.... new to vanilla though.... and some of additional abilities are critical to me, so im ready to go to prod with it (but with a rollback plan)

  • jens1seojens1seo
    edited November 2013

    @jackjitsu said:
    Are there upgrade instructions somewhere?

    Or do you treat this like a full fresh install again and use the import tool?

    >

    I did a full fresh install. Worked good for me

  • @Lincoln said:

    We know. Please assist us by 1) testing the heck out of this release under many different environments and scenarios and 2) submitting pull requests (against the 2.1 branch) for issues tagged for the milestone '2.1'. We have no ETA for final release or moving to RC. I would expect to have a beta 3.

    Thanks!

    Instead of making lot of features for next version, which is actually forcing for beta3, how about releasing versions with constant interval with less features?

    It will be easier to debug and test.

  • @mahesh said:
    Instead of making lot of features for next version, which is actually forcing for beta3, how about releasing versions with constant interval with less features?

    >

    t will be easier to debug and test.

    Most of those are fixes, not features.

    There a constant interval it is called alpha testing. Beta testing, you put together in a semi stable release.

    The time between 2.1b1 and 2.1b2 was short.

    It they had 10 different betas being tested a the same time it wouldn't make it easier for them.

    grep is your friend.

    UnderDog
  • peregrineperegrine MVP
    edited December 2013

    when upgrading to vanilla 2.1b2 from vanilla 2.0.1.18

    beware the mobile theme has a mobile/views/discussions/helper.php in vanilla 2.0.18.8

    whereas the mobile theme does not have a mobile/views/discussions/helper.php in vanilla 2.1b2

    this can lead to different things happening depending on whether your are installing a new version in a new folder vs. installing over the existing vanilla 2.0.18.8 folder.

    there may be other instances of this.

    just one more reason - not to have views or helper_functions in your themes. because when you change versions things will go awry. (default.master.tpl with themehooks is the way to go.)

    see item #2 in comment
    http://vanillaforums.org/discussion/comment/197539/#Comment_197539

    I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.

    UnderDogAdrianphreak
  • YoJoeYoJoe New
    edited December 2013

    [Split Please] Hello
    I've got couple questions in regards of v2.1b.
    Be aware that I've spent about 3-4 hours searching for solutions and answers, and all this for nothing :(

    1. Canonical url in page's sourcecode contain :80 port. How can I get rid of it ?
      I tried cutting returned $Result with str_replace() but it has to stay in more than 1 controller file.

    2. Was overall SEO (friendly urls) improved in any way ? I'd like to achieve something like domain/category/ID/topic_title (no matter what's the order). None of solutions posted in existing threads worked as well as plugins.
      At least getting rid (changing) /discussion/ in URI path to anything else (I suppose it's hardcoded in controller) would be great.
      Same goes to administration, changing domain/settings to own directory is like a basic intrusion prevention for me

    3. Statistics seem not to work.

    4. Since recaptcha doesn't force to have API key anymore, will it be upgraded ?

    5. I'm a bit confused when it goes to approving new content. Am I able in v2.1 to set first post/thread of user to be approved by moderator ?

    I'll have couple more questions about 2.1
    Above mentioned are most important as for now.

  • Not sure of your hosting setup, but I have friendly URLs through my nginx configuration. Probably something similar can be done with other http servers as well.

  • @openletter said:
    Not sure of your hosting setup, but I have friendly URLs through my nginx configuration. Probably something similar can be done with other http servers as well.

    Mostly apache 2.x on dev server/account.
    I'm not doing things locally (no wamp/mamp).
    There's no problem with rewriting urls with mod_rewrite
    But script's controller isn't going to magically generate proper urls in menus, categories and so on.
    There's only one rewrite in .htaccess, which is responsible for removing /index.php from url.
    That's all :(

  • peregrineperegrine MVP
    edited December 2013

    @peregrine said:
    when upgrading to vanilla 2.1b2 from vanilla 2.0.1.18

    beware the mobile theme has a mobile/views/discussions/helper.php in vanilla 2.0.18.8

    whereas the mobile theme does not have a mobile/views/discussions/helper.php in vanilla 2.1b2

    this can lead to different things happening depending on whether your are installing a new version in a new folder vs. installing over the existing vanilla 2.0.18.8 folder.

    there may be other instances of this.

    just one more reason - not to have views or helper_functions in your themes. because when you change versions things will go awry. (default.master.tpl with themehooks is the way to go.)

    see item #2 in comment
    http://vanillaforums.org/discussion/comment/197539/#Comment_197539

    I just noticed the vanilla team is already on top of this as of one year ago... :)

    http://vanillaforums.org/discussion/comment/170761/#Comment_170761

    and I quote for the people who don;t like clicking links

    lincoln said:
    Going from 2.0.18 to 2.1 successfully has a few more tricks than the usual copy/paste unfortunately.

    Before you ask, here's a couple I can think of off the top of my head: Any folders under the mobile theme's views, and the /applications/dashboard/views/default.master.php file should be deleted from your server; notice they aren't in the new version. Also, if you overwrote the forum's CSS entirely to make your 2.0.18 theme (by adding a style.css file to it), you'll want to start over using an additive custom.css file instead based on the large number of markup and style changes.

    something to take heed of.

    I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.

    R_J
«1
Sign In or Register to comment.