[Xerte-dev] Re: testing upgrade

[Ron Mitchell]

I think we're overcomplicating this - what's the problem with using guest2?
It what's been there for about 2 years as far as I can tell!

On the subject of installation documentation it needs updating anyway - I
could undertake to do that but I think it's your baby Pat - do you want to
do that?

-----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: 13 July 2012 10:16
To: For Xerte technical developers
Subject: [Xerte-dev] Re: testing upgrade

You could make a new XAMPP for 1.8, but that's new documentation

On Fri, Jul 13, 2012 at 10:13 AM, Julian Tenney
<Julian.Tenney at nottingham.ac.uk> wrote:
> Would it be easy to just do xampp install into /xertetoolkits18 and 
> create a
> xertetoolkits18 database? Then you'd end up with two installations for 
> the different versions, but nothing would screw up.
>
>
>
> From: xerte-dev-bounces at lists.nottingham.ac.uk
> [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron 
> Mitchell
> Sent: 13 July 2012 09:32
>
>
> To: 'For Xerte technical developers'
> Subject: [Xerte-dev] testing upgrade
>
>
>
> Hi
>
> I tested upgrading some older localhost xampp installations yesterday e.g.
> by dragging 1.8 code over the top of the earlier version and also 
> running upgrade.php
>
> As far as tests so far this seems to work fine but I did notice there 
> had been a change in demo.txt at some point which could cause problems 
> for those upgrading a xampp install. I guess this might be a question 
> for Pat and a judgement call as to what to use for the guest account
username....
>
>
>
> 1. At some point in demo.txt $_SESSION['toolkits_logon_username'] = 
> "guest"; was changed to $_SESSION['toolkits_logon_username'] = 
> "guest2"; and the current 1.7 zip download has 
> $_SESSION['toolkits_logon_username'] = "guest2";
>
>
>
> 2. The xot1.8 code in /library/Xerte/Authentication/Guest.php sets 
> guest as the username e.g.
>
> public function getUsername() {
>
>         return 'guest';
>
>     }
>
>
>
> 3. The reason this is relevant is that at the moment if someone 
> upgrades a xampp 1.7 install which is using demo.txt code rather than 
> switch.txt code they won't see their previous projects. Solution for 
> that would be to change Guest.php to use guest2 rather than guest. 
> However in older versions and I'm not sure exactly when the username 
> in demo.txt was guest rather than guest2 so upgrading these works fine.
>
>
>
> Questions:
>
> a) Should we change the 1.8 code to use guest2? e.g. will work ok for 
> more recent installs and perhaps add a note about changing this for 
> older installs
>
> b) Or should we leave 1.8 code as guest and add a note about changing 
> this for more recent installs?
>
> c) Or is there a way we can check for in the code and use guest or 
> guest2 accordingly?
>
>
>
> HTH
>
> Ron
>
>
> 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