[Xerte-dev] Re: Upgrading to 1.8

Thu Jul 5 15:18:09 BST 2012

So just don't overwrite it

On Thu, Jul 5, 2012 at 3:02 PM, Julian Tenney
<Julian.Tenney at nottingham.ac.uk> wrote:
> No, I wasn't going to.
>
> -----Original Message-----
> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
> Sent: 05 July 2012 15:02
> To: For Xerte technical developers
> Subject: [Xerte-dev] Re: Upgrading to 1.8
>
> you aren't going run setup again though? Don't do that.
>
> On Thu, Jul 5, 2012 at 2:58 PM, Julian Tenney
> <Julian.Tenney at nottingham.ac.uk> wrote:
>> Shouldn't have to worry about database.php cos it's made by setup?
>>
>> -----Original Message-----
>> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
>> Sent: 05 July 2012 14:11
>> To: For Xerte technical developers
>> Subject: [Xerte-dev] Re: Upgrading to 1.8
>>
>> OK.
>>
>> Being a 'just do it' kind of guy, I am thinking about right now just copying the new files over the top. Having the site_details site_location thing makes it difficult to ape the install on ltdev without creating a new database.
>>
>> If I backup the dir first, I can go back very quickly.
>>
>> Right?
>>
>> -----Original Message-----
>> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
>> Sent: 05 July 2012 14:05
>> To: For Xerte technical developers
>> Subject: [Xerte-dev] Re: Upgrading to 1.8
>>
>> yep, and at some point you might need to create it
>>
>> On Thu, Jul 5, 2012 at 2:01 PM, Julian Tenney
>> <Julian.Tenney at nottingham.ac.uk> wrote:
>>> Ah, OK.
>>>
>>> So that needs adding in to the svn then?
>>>
>>> -----Original Message-----
>>> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
>>> Sent: 05 July 2012 14:01
>>> To: For Xerte technical developers
>>> Subject: [Xerte-dev] Re: Upgrading to 1.8
>>>
>>> when you set up XOT, is uses an SQL file in /setup/basic.sql to create
>>> all the tables (not a problem if you already have a database).
>>>
>>> If the update script uses a database table called config, then at
>>> present, the installer doesn't contain an instruction to make a table
>>> called config.
>>>
>>> So it shouldn't be a problem for you to swap code.
>>>
>>> On Thu, Jul 5, 2012 at 1:57 PM, Julian Tenney
>>> <Julian.Tenney at nottingham.ac.uk> wrote:
>>>> What did this mean?
>>>> "(but see early q about where the config table is?)"
>>>>
>>>> -----Original Message-----
>>>> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
>>>> Sent: 05 July 2012 11:19
>>>> To: For Xerte technical developers
>>>> Subject: [Xerte-dev] Re: Upgrading to 1.8
>>>>
>>>> Speaking as Chief of Legacy code for XOT at Nottingham - don't forget
>>>> all the crazy curveball settings for people who left, people without
>>>> accounts, people with odd names stuck in the code. (mostly in
>>>> index.php)
>>>> I'd do a test version on LTDEV first for 1.8
>>>>
>>>> (but see early q about where the config table is?)
>>>>
>>>> As a suggestion.
>>>>
>>>> Get Unix bod to alter time stamps on all the files outside user-files.
>>>> Then drop over the top. All files with the old date are spurious. Then
>>>> delete those.
>>>>
>>>> On Thu, Jul 5, 2012 at 11:14 AM, Julian Tenney
>>>> <Julian.Tenney at nottingham.ac.uk> wrote:
>>>>> I'd like to move our setup to 1.8 here: we've implemented some local changes
>>>>> whilst development's been going on in the trunk, and things are getting a
>>>>> bit out of synch, and I'm going to end up getting in a mess if I try and
>>>>> bring all the various things into line bit by bit.
>>>>>
>>>>>
>>>>>
>>>>> We'll also have a working and reasonably busy install running 1.8 and any
>>>>> outstanding issues will quickly surface...
>>>>>
>>>>>
>>>>>
>>>>> So, $64m question: I can upgrade going over the top. I'd quite like to make
>>>>> a clean set of files, i.e. backup the existing files; delete the files from
>>>>> the folder on the web server, drop in the new files, and then go, so I'm not
>>>>> left with a load of old files lying around that I'm not sure what to do
>>>>> with: but I need to keep our config files etc.
>>>>>
>>>>>
>>>>>
>>>>> How best to proceed? We should also write this up so others can follow a
>>>>> simple set of instructions.
>>>>>
>>>>>
>>>>>
>>>>> I should probably wait until a  quiet ish time of the week to do this, and
>>>>> it would be good if you guys were around for help, should I need it...
>>>>>
>>>>>
>>>>> This message and any attachment are intended solely for the addressee and
>>>>> may contain confidential information. If you have received this message in
>>>>> error, please send it back to me, and immediately delete it. Please do not
>>>>> use, copy or disclose the information contained in this message or in any
>>>>> attachment. Any views or opinions expressed by the author of this email do
>>>>> not necessarily reflect the views of the University of Nottingham.
>>>>>
>>>>> This message has been checked for viruses but the contents of an attachment
>>>>> may still contain software viruses which could damage your computer system:
>>>>> you are advised to perform your own checks. Email communications with the
>>>>> University of Nottingham may be monitored as permitted by UK legislation.
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Xerte-dev mailing list
>>>>> Xerte-dev at lists.nottingham.ac.uk
>>>>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>>>>>
>>>>> This message and any attachment are intended solely for the addressee and
>>>>> may contain confidential information. If you have received this message in
>>>>> error, please send it back to me, and immediately delete it.   Please do not
>>>>> use, copy or disclose the information contained in this message or in any
>>>>> attachment.  Any views or opinions expressed by the author of this email do
>>>>> not necessarily reflect the views of the University of Nottingham.
>>>>>
>>>>> This message has been checked for viruses but the contents of an attachment
>>>>> may still contain software viruses which could damage your computer system:
>>>>> you are advised to perform your own checks. Email communications with the
>>>>> University of Nottingham may be monitored as permitted by UK legislation.
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Xerte-dev mailing list
>>>> Xerte-dev at lists.nottingham.ac.uk
>>>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>>>>
>>>> _______________________________________________
>>>> Xerte-dev mailing list
>>>> Xerte-dev at lists.nottingham.ac.uk
>>>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>>>
>>> _______________________________________________
>>> Xerte-dev mailing list
>>> Xerte-dev at lists.nottingham.ac.uk
>>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>>>
>>> _______________________________________________
>>> Xerte-dev mailing list
>>> Xerte-dev at lists.nottingham.ac.uk
>>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>>
>> _______________________________________________
>> Xerte-dev mailing list
>> Xerte-dev at lists.nottingham.ac.uk
>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>>
>> _______________________________________________
>> Xerte-dev mailing list
>> Xerte-dev at lists.nottingham.ac.uk
>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>>
>> _______________________________________________
>> Xerte-dev mailing list
>> Xerte-dev at lists.nottingham.ac.uk
>> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev