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 funeral

April 22, 2012 10:11pm

Subscribe [3]
  • #1 / Apr 22, 2012 10:11pm

    Hi Guys,

    I recently bought ee2 for upgrading. I discovered basic stuff changed like
    - xxx_lang.php VERSUS lang.xxxxx.php
    - ?> at the end of language file VERSUS nothing
    - array named $lang VERSUS $L (Why??!!!)
    - PHP classes changed (due to OOP) I guess…
    - “Common” serialize bug, resolved here: http://ellislab.com/forums/viewthread/212060/#987639

    Some things need to change ok, but some don’t. It’s the first thing I expect from a CMS, easy upgrade.

    After 10 hours I finally solved these, when I realise that Photo gallery no longer exists and v2 should be avoided for the moment…..
    My customer site is based on that module. This should be written in red warnings when buying.

    ee is really good, still, I’m gonna all switch to Drupal, maybe I’ll feel the same about Drupal upgrade, but ya know…

    Bonne continuation à tous et un grand merci.

     

  • #2 / Apr 27, 2012 9:39am

    Man With A Peg

    124 posts

    As someone who has just upgraded a site from Drupal 6 to 7, I have to say that the upgrade process was not terribly smooth there either. In fact, part of the Drupal upgrade process involves disabling all of your third party modules.

    Go to Administer > Site building > Modules. Disable all modules that are not listed under “Core - required” or “Core - optional”. It is possible that some modules cannot be disabled, because others depend on them. Repeat this step until all non-core modules are disabled.

    Unlike EE, disabling them does not mean removing their settings. Their process still involves a lot of work. The theming interface and SQL querying have also changed. It took me several hours to straighten everything out with my custom theme and custom blocks. Oh, and I basically had to migrate all the nodes by hand. This made me really glad for Vim which sped up modifications to the database dump.

    Your comment about whether or not files end with ?>—it doesn’t really matter. The reasoning for the current EE choice is to avoid breaking HTML themes or HTTP header output when some developer puts (leaves?) extra whitespace at the end of the file.

    I can’t speak to the other things very well since my experience with EE 1.x is limited…

    Bon chance. 😊

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

ExpressionEngine News!

#eecms, #events, #releases