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.

EE 2.1 update process questions (mostly relating to add-ons)

August 25, 2010 6:18pm

Subscribe [2]
  • #1 / Aug 25, 2010 6:18pm

    xlawdog

    62 posts

    I am getting ready to update a client site from 1.6.8 to 2.1. We use a number of add-ons on the site, and I understand, I think, that after I make sure they’re compatible with 2.1, I need to update the add-ons first. Is that correct?

    Assuming that is correct, after doing an inventory of the add-ons that we’re using on the site, I have some additional questions to which I haven’t been able to find answers:

    1. Is it necessary or advisable to update from 1.6.8 to 1.6.9 before going to 2.1?

    2. What do I do with a couple of first-party plugins that I think were included in EE1 but do not seem to be available for EE2—specifically, Magpie RSS Parser, XML Encode, and HTML Stripper? I’m surprised that I can’t find EE2 versions—are they maybe “baked in” to EE2? And if so, do I have to make changes to the templates that use them?

    3. For other first-party plugins (e.g., Word Limiter, Character Limiter, Randomizer), there are new separate downloads for EE2, rather than updated versions. Is it OK to install these in 1.6x before doing the update to 2.1?

    4. How is the installation of third-party add-ons handled, since the file location has now changed? Should the new ones be installed alongside the existing old ones, do I have to change the file locations after the update, or ... something else?

    5. Since FieldFrame is no longer necessary in EE2 for adding custom fieldtypes, what happens to the 1.6x fieldtypes that were dependent on FieldFrame, such as FF Select and nGen File Field? Are they automatically converted to something new, or do I have to manually replace them with something else?

    Sorry about the number of questions. If answers are already available somewhere, I haven’t been able to find them.

  • #2 / Aug 26, 2010 9:21am

    xlawdog

    62 posts

    Can anyone help with any of these questions? “A Note about Add-ons” in the updating instructions doesn’t address these specifics, nor could I find answers elsewhere in the forum. Thanks.

  • #3 / Aug 26, 2010 4:51pm

    xlawdog

    62 posts

    OK, one partial answer to question 2: I now see that Magpie RSS Parser and XML Encode are built in to EE 2.1.

    Any other answers out there?

  • #4 / Aug 26, 2010 5:06pm

    Ingmar

    29245 posts

    1. Is it necessary or advisable to update from 1.6.8 to 1.6.9 before going to 2.1?

    You can but it’s normally not required. Going to 2.1 you’ll pass this stage, of course.

    2. What do I do with a couple of first-party plugins that I think were included in EE1 but do not seem to be available for EE2—specifically, Magpie RSS Parser, XML Encode, and HTML Stripper? I’m surprised that I can’t find EE2 versions—are they maybe “baked in” to EE2? And if so, do I have to make changes to the templates that use them?

    There are some stripping alternatives, I think.

    3. For other first-party plugins (e.g., Word Limiter, Character Limiter, Randomizer), there are new separate downloads for EE2, rather than updated versions. Is it OK to install these in 1.6x before doing the update to 2.1?

    No, the code is incompatible. Also note that the location of the plugin has changed as well.

    4. How is the installation of third-party add-ons handled, since the file location has now changed? Should the new ones be installed alongside the existing old ones, do I have to change the file locations after the update, or ... something else?

    Basically every add-on has its own folder now. Check out the docs for details.

    5. Since FieldFrame is no longer necessary in EE2 for adding custom fieldtypes, what happens to the 1.6x fieldtypes that were dependent on FieldFrame, such as FF Select and nGen File Field? Are they automatically converted to something new, or do I have to manually replace them with something else?

    Yes, you should disable them before upgrading and replace them with compatible versions.

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

ExpressionEngine News!

#eecms, #events, #releases