                                                                                                                                                                                                                                                                
Received-SPF: pass (google.com: domain of pasa...@gmail.com designates 74.125.92.24 as permitted sender) client-ip=74.125.92.24;
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=Em/bZn48H9cLaeuxMsUIDGyOPG9yb4sGKEwAzJrhOXhy7u7JVRV0l2J6NgNsb/IVyc
         9OgEyAhKbgMKcgfPPJe+0gJgfJnci1UmxNvrfyKtb2bSAr6up8nQnME77l5kx8A8/R8Y
         kg7vYxgW1CeZ+ocHbHiwV4Ki4+Cq+2sPKACzU=
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <0FD2779F-39D8-46E2-AE7A-BDD68B889...@gmail.com>
References: <712ca724-6387-4675-a9ea-14a9bb50e...@o36g2000vbl.googlegroups.com>
	 <4A9B9706.2070...@googlemail.com>
	 <df48dd45-e8e2-4f3d-ae14-389e5da5f...@33g2000vbe.googlegroups.com>
	 <4A9C299B.2030...@googlemail.com>
	 <0FD2779F-39D8-46E2-AE7A-BDD68B889...@gmail.com>
Date: Tue, 1 Sep 2009 22:33:27 +1000
Message-ID: <b3371ae50909010533i4047a6f9w9ef9a4c68ed24...@mail.gmail.com>
Subject: Re: Migrator script for Joomla 1.6
From: Sam Moffatt <pasa...@gmail.com>
To: joomla-dev-cms@googlegroups.com

The hope is eventually we'll get the JED automatically building the
XML files required for the update. Extension wise there isn't much
that is changed, if you have an extension that updates now, it'll
still work. There is support for using a class instead however the
legacy com_install/com_uninstall functions are still there.

XML Update Samples: http://jsitepoint.com/update/update.xml (follow
the referenced uris)
Sample component:
http://joomlacode.org/svn/joomla/testing/trunk/installer_samples/components=
/com_alpha/

All that is really being added is support to have a slightly improved
UI for updates integrated into a single point.

Sam Moffatt
http://pasamio.id.au



On Tue, Sep 1, 2009 at 7:16 AM, Mike Hamanaka<haman...@gmail.com> wrote:
>
> Hi J1.6
>
> Hannes, You mentioned that the extension upgrade to 1.6 is the 3rd
> party developers job.
>
> Obviously the community thrives on added functionality.
>
> Could all people here offer transparency on any available
> documentation on j1.6 extension update manager that Sam is involvled
> with.
>
> I feel that the easy accessiblility of this information could motivate
> extension devs and the extension community to have greater
> organization in regards to the delivery of communication for ext
> upgrades both major and minor.
>
> Just the usual subscription the the 3rd party dev's RSS feed is not
> good enough anymore.
>
> Mike Hamanaka
> Website Production
> Vertualize.com
>
> On Aug 31, 2009, at 12:50 PM, Hannes Papenberg
> <hackwa...@googlemail.com> wrote:
>
>>
>> I would say that the component should only care for Joomla. Upgrading
>> their extensions to something compatible for 1.6 is the third party
>> developers job. Since we are not going to a completely new encoding
>> scheme like from 1.0 to 1.5, we don't need to export the complete
>> database, install a new Joomla 1.6 and then import the old database.
>> "Just" replacing the changed files and applying the necessary
>> changes to
>> the database would be enough. But that would only be the case when we
>> really go the way of an installable update component.
>>
>> Hannes
>>
>> Matias Aguirre schrieb:
>>> Hannes,
>>>
>>> The component will include 3rd party extensions or only contents,
>>> categories, modules and stories images?
>>>
>>> -Matias
>>>
>>> On Aug 31, 6:25 am, Hannes Papenberg <hackwa...@googlemail.com>
>>> wrote:
>>>
>>>> Hi Matias,
>>>> thanks for your offer. At this moment, its not really decided how
>>>> to do
>>>> this. I would prefer that people would not have to delete all their
>>>> files, install 1.6 and then migrate data over from 1.5. My dream
>>>> for the
>>>> update process from 1.5 to 1.6 would be an updater-component. That
>>>> component would ship with all the files from 1.6 and after
>>>> installation,
>>>> you just select it from the component menu and it starts the update
>>>> process. So it has to move around a lot of files, delete the
>>>> obsolete
>>>> ones and do table updates. This will trigger the max_execution
>>>> limit, so
>>>> this has to happen with a bunch of ajax requests and several page
>>>> loads.
>>>> But thats just me dreaming. ;-)
>>>>
>>>> If you have good ideas for a migration path, write them down and
>>>> present
>>>> them to the list here and you can start work on this. :-)
>>>>
>>>> Hannes
>>>>
>>>> Matias Aguirre schrieb:
>>>>
>>>>
>>>>> Hi all,
>>>>>
>>>>> I see in the Joomla Development Status that is planned to include a
>>>>> migrator script into the Joomla 1.6 core.
>>>>>
>>>>> What is the plan of this? Make a migrator script as component or
>>>>> external script?
>>>>>
>>>>> I think that i can help with this, so if any have some info or
>>>>> ideas
>>>>> please tell me.
>>>>>
>>>>> Take care
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>> >
>
> >
>