stiadmin

Send private message

You must be logged in to send a private message.

Friends

No friends yet.

Group membership

Activity

  • stiadmin replied on the discussion topic Upgrade Woes from 1.12.13 to 2.X
    Thanks for the suggestions! I will give it a try tonight and let you know if I have been successful or not. view reply
  • stiadmin replied on the discussion topic Upgrade Woes from 1.12.13 to 2.X
    Here is a pic of that the site looks like after the upgrades.   http://pasteboard.co/dQzVZCgO7.png view reply
  • stiadmin added a new discussion topic Upgrade Woes from 1.12.13 to 2.X in the group Elgg Technical Support
    Hi Elgg Community, I am really struggling here. I have a 1.12.13 instance of Elgg. I cannot seem to get the upgrade to work. I have followed the official Ellg Instructions (http://learn.elgg.org/en/2.0/admin/upgrading.html) but have not been...
    • I think the only thing you forgot was to update .htaccess with the new version that comes with Elgg 2 (template file is in vendor/elgg/elgg/install/config).

      I can't follow the upgrade instructions given by RvR. The instructions about how to handle the mod directory seem quite complicated - and maybe even too complicated.

      My suggestion: prepare the upgrade by creating a working directory (outside the document root directory) on your server where you upload to and/or extract the new Elgg version. You can also already add any 3rd party plugins you want to use to the mod folder of the Elgg installation in this working directory (of course the new versions of the plugins if there are new versions necessary for Elgg 2).

      Then add settings.php to the elgg-config directory (use vendor/elgg/elgg/elgg-config/settings.example.php as template and edit your database credentials and other changes you might have made into it). Also add a .htaccess in the working directory (again using the template included in the new Elgg version and merging any changes from your old .htaccess you made on your own).

      Of course, you could also prepare (and test) the new Elgg installation locally and uploading it to a working directory when you are ready. The advantage of preparing everything in a working directory is that you can move the content of the work directory (that wll be the new Elgg install directory) quite fast on the server as opposed to upload everything directly to the install folder.

      When you have finished the preparations of the install folder, backup your install folder + data directory + database. Never be too lazy for backups at this point!

      It's not necessary to disable all plugins before upgrading. But you should disable at least any plugins that are no longer part of Elgg core in Elgg 2 (don't know at the moment if any bundled plugins were dropped but I think this was done for 1 or 2).

      Disable Elgg's caching option is a good idea at this point.

      With a full backup made and the working directory ready you can now do the upgrade

      • just delete everything including all subfolders in your Elgg install directory (only install directory NOT data directory),
      • move the content of the working directory into your Elgg install folder,
      • either call yoursite.url/upgrade.php in your browser or log in and click on the "Upgrade" button on the admin dashboard page,
      • enable the caching options again.
      • done.

       

    • Thanks for the suggestions! I will give it a try tonight and let you know if I have been successful or not.

    • @iionly  Awesome! But I tried it in practice.