ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

The End (of Beta) is Near: What You Need to Know

June 18, 2010 6:25pm

Subscribe [36]
  • #31 / Jun 22, 2010 9:02am

    Leonard M

    24 posts

    What will happen to the EE 1.6 documentation (currently at http://expressionengine.com/docs). Will they be replaced by the EE2 documentation (currently at http://expressionengine.com/public_beta/docs)? Or will they both be available at different URLs for a while longer after 2.1? (I imagine the EE2 docs can’t stay at ‘public_beta’ after 2.1…)

  • #32 / Jun 22, 2010 9:20am

    Ingmar

    29245 posts

    Coinciding with EE 2.1’s release, ExpressionEngine.com will be undergoing a refresh that includes replacing EE 1.x documentation and support resources with resources focused on EE 2. We will do our best to keep current URLs intact or redirected. If something breaks we’ll do our best to restore it quickly.

  • #33 / Jun 22, 2010 11:10am

    James Likeness

    10 posts

    Will there be some kind of discount on the 2.1 license for users who have very recently purchased 1.6.9?

  • #34 / Jun 22, 2010 11:19am

    Ingmar

    29245 posts

    They will be able to upgrade to the EE 2 branch for the difference in purchase prices, ie ~50$ if I recall.

  • #35 / Jun 22, 2010 12:02pm

    TrevorNet

    30 posts

    Will there be an upgrade path to the licensing model? I would like to wrap my head around EE2 at the freelance license level (I can’t get the trial version to install on *anything*) and then upgrade it a commercial license when a future client arises. (possibly answered above)

  • #36 / Jun 22, 2010 12:11pm

    Matt Weinberg

    489 posts

    I second the question about 1.6 documentation. Ingmar, I saw your answer before, but that’s not 100% clear if the 1.6 documentation will still be up somewhere, or if all the old URLs will get replaced with 2.x docs (but still work). Will 1.x docs be *somewhere*, even if the URLs changed?

  • #37 / Jun 22, 2010 12:33pm

    Leslie Camacho

    1340 posts

    What will happen to the EE 1.6 documentation (currently at http://expressionengine.com/docs). Will they be replaced by the EE2 documentation (currently at http://expressionengine.com/public_beta/docs)? Or will they both be available at different URLs for a while longer after 2.1? (I imagine the EE2 docs can’t stay at ‘public_beta’ after 2.1…)

    In addition to what Ingmar quoted, just want to make clear that the EE 1.x User Guide will be available online as long as we offer official support for it.

  • #38 / Jun 22, 2010 12:38pm

    Leslie Camacho

    1340 posts

    Will there be some kind of discount on the 2.1 license for users who have very recently purchased 1.6.9?

    Will there be an upgrade path to the licensing model? I would like to wrap my head around EE2 at the freelance license level (I can’t get the trial version to install on *anything*) and then upgrade it a commercial license when a future client arises. (possibly answered above)

    Going from EE 1.x to EE 2.1 will the be the same, pricing/upgrade wise, as going from EE 1.x to EE 2.0PB. You’ll be able to upgrade for just the price difference between the two. In other words, you won’t be penalized if you purchase EE 1.x today and then upgrade to EE 2.1 when its released.

    Yes, you can upgrade from The Freelancer to the Commercial or Non-profit licenses for just the price difference (again, no penalty).

    And finally, just to be thorough, EE 2.0 to EE 2.1 is a free upgrade.

  • #39 / Jun 22, 2010 7:45pm

    jayf

    41 posts

    Thanks Leslie, for your post and for answering questions in this thread.

    I want to voice some concern about EE 1.x being no longer available for purchase as of 1/1/11:

    First, let me say that we appreciate having months of warning, and now are shooting to transition to EE 2 before December this year. That’s an OK enough target, at this point.

    My concern is, however, that we’re in a pickle if we can’t make that target.

    What this transition, from EE 1.x to 2.x, is asking of us is that we budget additional time for R & D (making our processes work with EE 2.x) vs production (building sites in EE 1.x). Our time is already pretty booked-up into the Fall. And, we have a lot of things our clients like us to do for them, that we know exactly how to do in EE 1.x, that are going to take an unknown amount of time to work out in EE 2.x.

    While your post signals to us that we need to go forward with working out those things in EE 2, we really don’t know if we can make that transition 100% before the new year. For example, if it’s going to take us 120 work hours, we don’t know if we’re going to be able to actually budget 120 work hours between now and then.

    So, I hope that concern is clear, and that you will keep open the possibility of extending EE 1.x availability into 2011. I hope that we ourselves don’t need EE 1.x next year—and I hope that EE 2.x plus add-ons can do what we need. But, I am concerned enough to ask for the extended availability for EE 1.x into 2011.

    Finally, let me note that, from our perspective, the EE 2 beta has not been something we could work with in a way that allowed us to start this transition. So, we’ve been waiting for the release of the non-beta 2.1, to start a serious transition process. From the non-beta release date, we would ask for at least 6 months of continued availability of EE 1.x.

  • #40 / Jun 22, 2010 7:53pm

    Leslie Camacho

    1340 posts

    I want to voice some concern about EE 1.x being no longer available for purchase as of 1/1/11

    These are excellent points Jayf, much appreciated. These are the decisions as they stand today. But our foremost mandate is to help people, most notably web professionals, succeed. If 1/1/2011 rolls around and this causes major issues for people we will certainly try to work out a solution that makes the transition easier.

    And just to clarify, we are not removing download access for existing EE 1.x license holders. You will still have access to EE 1.x for as long as we support it, which will be long after 1/1/2011. What we’re talking about specifically refers to the ability to acquire new EE 1.x licenses.

  • #41 / Jun 22, 2010 10:31pm

    Ibn Saeed

    98 posts

  • #42 / Jun 25, 2010 1:11pm

    the_crimsonrooster

    264 posts

    I for one IS ready for the change!!  I have a couple sites on 1.6x, but I’m tired of waiting for 2.0. It’s been a LOOONNNNG time coming!! 

    So EL pull the plug already, and let’s go forward. No more conferences, or talks, or promotions. Enough!  Huddle up, close the doors, do some “super-sessions” and get the REAL GOLD product out there!! Your faithful audience is chomping at the bit, but our faith is starting to waver….

    Get the product out and EL just be ready for some “hotfixes!”

    GO TEAM!!

  • #43 / Jun 25, 2010 8:24pm

    nathanpitman

    531 posts

    We’ve attempted to migrate to development with EE2 but our efforts have been hampered by the lack of extension hooks available in EE2. Will 2.1 reinstate all of the ‘existing’ hooks which we have in 1.6.9?

  • #44 / Jun 25, 2010 10:56pm

    Derek Jones

    7561 posts

    We’ve attempted to migrate to development with EE2 but our efforts have been hampered by the lack of extension hooks available in EE2. Will 2.1 reinstate all of the ‘existing’ hooks which we have in 1.6.9?

    Nathan, all old extension hooks are in place that make sense within the architecture of 2.1’s code.  What specifically are you missing?  I can check our discussions from the developer preview, but I’m assuming that you must have something new in mind since that time.

  • #45 / Jun 26, 2010 10:03am

    nathanpitman

    531 posts

    So are the hooks documented in the current online docs as per 2.1? Specifically I didn’t see an equivalent of ‘edit_entries_additional_tableheader’ from 1.6.9. I’d really like to port my ‘Show Categories’ extension (http://ellislab.com/forums/viewthread/112543/) to EE2 but I don’t see any way to do it at present. :/

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases