Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • treybraid Friend
    #144530

    will we just be able to overwrite the old file’s version 1.2 with this version? any idea what has been changed— ive already modified the template.css pretty heavily…

    wondering

    thanks
    trey

    Arvind Chauhan Moderator
    #318315

    Dear treybraid,

    Wait for the release of 1.3 and lets see whats in the changelog and may be then we can comment something on this. I think css edit should not be of much problem as the update would be much more in the php codes (hope so).

    Arvind

    cgc0202 Friend
    #318324

    <em>@treybraid 145931 wrote:</em><blockquote>will we just be able to overwrite the old file’s version 1.2 with this version? any idea what has been changed— ive already modified the template.css pretty heavily…

    wondering

    thanks
    trey</blockquote>

    trey,

    If Joomlart identifies the specific files that are affected, as well as the changes done, then it is a simple case of overwriting the old files with the changed files. More than likely from v1.2 to v1.3 less than a dozen to a few dozen at most of the several thousand Joomlart added files would be affected. I hope also that Joomlart would state any specific CSS tags specifications were modified, if any.

    The “overwrite” approach is how Joomla itself updates its very complex software. It is also the safest way of updating an existing working site, and the easiest to do if you have already extensively modified your site. The overwrite approach is less time consuming and more safe than the “uninstall and delete the old extension (or template) and install the revised extension (or template).

    I have been advocating since last year for Joomlart to provide members with sufficient information so that those who prefer the “overwrite approach” may do so. But so far, Joomlart has been reluctant to provide the required information.

    I do hope more members will rally to petition Joomlart to provide this information.

    Cornelio

    *******************

    Consider these hypotheticals:

    Collective time (effort) spent by members

    1000 Teline III users @ 0.5-5hours to perform “reinstall-install” process => 500-5000 hours

    1000 Teline III users @ 0.1-1hour to perform “overwrite” process => 100-1000 hours

    The higher end are assumed times required by members who have extensively revised sites. The collective time would be somewhere in between.

    If there are more actual Joomlart users, then the total amount of time would even be more. For the record, there are already more than 2,700 downloads of the Teline III. Even with just a single installation for members, there are possibly about 1500-2000 “upgrades” with respect to the beta version, from early users of Teline III. Expect these numbers to go up, as Teline III is upgraded and more users adopt the Teline III template.

    The issue becomes: how long would it take a Joomlart staff — actually involved in the revision of Teline III — to provide the detailed information requested above?

    1. Ten hours?
    2. Two days?
    3. One week?

    However long it would take, it would still be much much less compared to the amount of time that would be spent collectively by all members. And, more important, the “overwrite” process would minimize potential upgrades that may go awry. These would save the amount of time and aggravation lost posting problems and amount of time spent by members and moderators and staff trying to help members encountering these upgrade problems.

    I know for a fact that there were members who were reluctant to upgrade their prior Teline II sites, simply because they dread the possibility of something going awry during the upgrade.

    Edit: (20091003) Since this response was posted, Joomlart has finallly came up with the detailed changelog list from version 1.2 to version 1.3:

    UPDATED!! Teline iii 1.3 List of changed files & Upgrade Steps

    http://www.joomlart.com/forums/topic/updated-teline-iii-1-3-list-of-changed-files-upgrade-steps/

    it is still being updated, and the complete “patch” update was removed, for now. One a complete patch is ready, it should be possible to use the overwrite approach to update an existing file. Be very careful however if you have a highly customized site. Make sure to keep of copy of the configuration.php, the database, revised files, including revised CSS. I usually oerform the update in a Sanbox before I try it on my site.

Viewing 3 posts - 1 through 3 (of 3 total)

This topic contains 3 replies, has 3 voices, and was last updated by  cgc0202 15 years, 2 months ago.

We moved to new unified forum. Please post all new support queries in our New Forum