Log on:
Powered by Elgg

LWPS development :: Blog :: Installation of Elgg 0.8.1 on LWPS

February 07, 2007

  1. List of problems with the upgrade
  2. Timeline for upgrading LIVE LWPS with Elgg 0.8.1
  3. List of changes that need to made after install to complete the LWPS 0.8.1 Upgrade

Billing log posts for Jeffrey and Diana.

Return to LWPS Dev. T.O.C. or Planning considerations ...

Keywords: 20%, 2008, 2Q08, 4/13, 60%, contractor, Diana, enhancements, hph, Installation of Elgg 0.8.1 on LWPS, Jeffrey, LWPS 0.8.1, LWPS test system, lwpsdevelop

Posted by Pete Hubbard (LWPS Founder) @ LWPS development


Comments

  1. I think that the issue of "Release Candidates" is a sure sign that a final 0.7 release is imminent.



    As for the conversations, I am happy to continue them here, but I don't necessarily know when you have responded, or when you are expecting a response from me, so if you'd like to be certain of a timely response, please continue to send me email.





    Thank you,

    Jeffrey

    user iconJeffrey Froman on Wednesday, 28 February 2007, 12:30 EST # |

  2. Whoops, I figured out why my posts are repeating. I have been reloading the page to see if any new comments are present, but the reload causes my previous comment to be resubmitted. (The application can prevent this by issuing a redirect after any successful form submission, but apparently this version of Elgg does not ensure this.)



    Jeffrey

    user iconJeffrey Froman on Wednesday, 28 February 2007, 13:26 EST # |

  3. I have downloaded the new Elgg files, created the new database, and briefly reviewed the installation process. I may not have a chance to the initial install until this weekend.



    As we discussed on the phone, the first installation will be a clean and shiny Elgg-0.7. If that looks good, we'll try an installation over the current 0.4 version, keeping all previous data intact.



    Jeffrey

    user iconJeffrey Froman on Friday, 16 March 2007, 13:26 EDT # |

  4. Excellent!

    user iconPete Hubbard on Friday, 16 March 2007, 13:36 EDT # |

  5. Hi Pete,



    A clean installation of Elgg-0.7 is installed at http://dev.lifeworkps.com. To begin adding accounts, log in as:



    username: news

    password: 9eriKA@txm



    In theory, you can also edit options for the Elgg installation itself, for example the tagline "Community Learning Space", by visiting the URL http://dev.lifeworkps.com/_elggadmin/ and log in as:



    username: administrator

    password: boliastrepurious



    However, I don't seem to be able to get this interface to save any changes. So for now, it should be considered a read-only interface. Any changes we want to make can be performed by editing the config.php file directly.



    Please give this clean installation a little shakedown, and let me know if it looks OK to start the next phase of the site upgrade.





    Thank you,

    Jeffrey

    user iconJeffrey Froman on Saturday, 17 March 2007, 19:41 EDT # |

  6. The missing tag cloud, uneditable elggadmin screen, lack of recent activity, and installation of plugins are all best investigated by someone better versed in PHP than I am. These issues are all likely to be PHP based, and I would be fumbling in the dark where someone more knowledgeable might complete the investigation more efficiently. I recommend passing these tasks to CMagic. (Your guess as to the nature of the problem with the tag cloud does sound reasonable -- it may just require more data to work with.)



    The next step is to copy the current lifework data over to the new site location, and attempt to install the new Elgg over the old data. The database *should* take care of itself (cross your fingers), but any files that have been previously uploaded will be a bit trickier to move over. It may take a few tries to get those uploaded files into the correct new locations. The capital 'W' and visual editor can be easily added during this second phase.



    When all the issues have been worked out with Phase2, we will essentially repeat the Phase2 installation process on the live site at a pre-appointed time. During this Phase3 installation, LWPS will be at least partially inaccessible. Phase3 shouldn't take very long, because in theory we will have worked out all of the problems already during Phase2.



    It sounds like we are ready for Phase2, and I will move ahead upon hearing confirmation from you.



    Thanks,

    Jeffrey

    user iconJeffrey Froman on Tuesday, 20 March 2007, 11:12 EDT # |

  7. Phase2 is complete, and most features appear to be working. Some problems I still notice:



    1. User images are missing. The directory structure and filenaming scheme for user images appears to have changed too drastically to properly migrate the images to the new version. Elias may have better luck figuring out how to migrate the images than I have. If not, the simplest (albeit a bit awkward) solution may be to ask users to re-upload their images.



    2. Procedures for escaping quotes and HTML are different, and this is causing some posts to be formatted incorrectly. Wrongly escaped quotes come out with a backslash preceeding each quote character, like: Click \\"Personal blog\\". These cases can be corrected by choosing to "edit" the post, and re-saving it as is.



    The solution to the HTML escaping is less obvious to me. HTML that was previously being properly formatted is now being escaped, causing the raw HTML to be displayed. Take a look at the first blog post for "news" as an example. This may also be something that Elias can fix, but in the end it may require re-writing those posts in order to satisfy all program requirements.



    (Note: I misplaced the original password for "LWPS news", and so I had to change it in order to test the account. The new password for "news" is 9eriKA5txm.)



    Please ask Elias to inform me of any and all changes made, so that I can incorporate those changes into the final updated version of the site.





    Thank you,

    Jeffrey

    user iconJeffrey Froman on Thursday, 22 March 2007, 12:37 EDT # |

You must be logged in to post a comment.