[Xerte-dev] Re: latest trunk - window size issues

Mon Nov 26 20:23:48 GMT 2012

Have committed the changes. 

Decided the extracted authentication options file should be called
auth_config.php hope everyone agrees?

Notes:

extracted the commented authentication options from config.php and added to
a required file named auth_config.php. This means when updating/upgrading
config.php can be overwritten without changing the authentication method
back to Guest. When updating/upgrading auth_config.php should be excluded or
re-edited after update. 

Updated the moodle_integration_readme.txt instructions to reflect this
change.

Not sure if there's an instruction needed anywhere else?

Ron

From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
Sent: 26 November 2012 16:34
To: For Xerte technical developers
Subject: [Xerte-dev] Re: latest trunk - window size issues

i'm dealing with bigger fish, what is suggested is the best fix for the
problem we have now

On Mon, Nov 26, 2012 at 4:31 PM, Ron Mitchell <ronm at mitchellmedia.co.uk>
wrote:

If Pat agrees?

I fear for the other cave dwellers...

From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
Sent: 26 November 2012 16:10
To: For Xerte technical developers
Subject: [Xerte-dev] Re: latest trunk - window size issues

Do you want to do that then Ron?

From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron Mitchell
Sent: 26 November 2012 16:10
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: latest trunk - window size issues

I'd suggest auth_method.txt or auth_method.php

The details for each method are in the various files inside
\library\Xerte\Authentication\

I suspect it's easier to include it as .php rather than txt so that a new
install automatically works with guest access as it does now. Then in the
README there's a note not to overwrite this file or to re-edit if you do.

From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
Sent: 26 November 2012 15:43
To: For Xerte technical developers
Subject: [Xerte-dev] Re: latest trunk - window size issues

I imagine config.php will continue to change. At the very least, I don't
think we can say it won't. SO separating out the auth_details into, say
auth_details.txt to be renamed auth_details.php after installation would
work?

From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron Mitchell
Sent: 26 November 2012 15:44
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: latest trunk - window size issues

Just to be clear I was suggesting separating out from line 175 onwards not
the changes you have made Pat.

It's only the authentication method lines that an admin needs to edit so
that seems a quick and easy fix to me if config.php needs to continue
changing.

From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
Sent: 26 November 2012 15:24
To: For Xerte technical developers
Subject: [Xerte-dev] Re: latest trunk - window size issues

I agree, you could take the new changes I made out of config and include
those, but I feel it is setting a precedent but having lots of work around
files in the root to allow for x and y and z

On Mon, Nov 26, 2012 at 3:16 PM, Julian Tenney
<Julian.Tenney at nottingham.ac.uk> wrote:

There is also an argument to say that what you need to do with config.php
isn't exactly complicated, and you at least ought to read a readme or
similar and take note of things it tells you, before updating a live site.

From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron Mitchell
Sent: 26 November 2012 14:58

To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: latest trunk - window size issues

I can see Pat's point about the chosen method should be in sitedetails but
that would require another database change/upgrade as well as additions to
the installer and management page etc.

Whereas separating just those authentication method lines into a separate
file would be a quick and easy change. Mainly thinking about people
upgrading live sites with minimum of hassle.

From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
Sent: 26 November 2012 14:42
To: For Xerte technical developers
Subject: [Xerte-dev] Re: latest trunk - window size issues

If it can easily be split, then it would seem sensible to?

From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
Sent: 26 November 2012 14:36
To: For Xerte technical developers
Subject: [Xerte-dev] Re: latest trunk - window size issues

Well that's not my call really, because

config.php isn't tied to the installer (AFAIK) and so the authentication
option has to be set manually, whereas it would make more sense to have it
in sitedetails (which would mean config.php can be mangled for fun)

On Mon, Nov 26, 2012 at 2:29 PM, Ron Mitchell <ronm at mitchellmedia.co.uk>
wrote:

Yep indeed - that fixed it - cheers!

But...

Can't help thinking there's something wrong with a process that when
upgrading by dropping new files over the top of an existing install renders
the selected authentication back to guest. That's why I didn't overwrite
config.php and Library. (the latter simply because it's easier to exclude
the parent than the specific authentication file)

Should those authentication options be a separate included/required file
e.g. authentication_method.php so that it's easier to protect those settings
when updating/upgrading?

Ron

From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
Sent: 26 November 2012 14:10
To: For Xerte technical developers
Subject: [Xerte-dev] Re: latest trunk - window size issues

Issues 1,2,3 and 4 are because you didn't update config.php

Fastest bug fix ever.

Pat

On Mon, Nov 26, 2012 at 12:49 PM, Ron Mitchell <ronm at mitchellmedia.co.uk>
wrote:

Hi all

decided it was worth starting a new thread but wasn't quite sure what
subject line to use here but anyway this is the first issues I've found.

Steps:

I checked out the lasted trunk and exported that to a new folder

Copied that exported copy over the top of an existing 1.8 localhost install
(omitting config.php and library because of local settings)

Issue 1

Click create to create a new XOT template project - the editor window is
tiny (about 270 x 186) and in IE can't be resized. IN Chrome opens the same
size but at least can be resized.

Issue 2

Not sure if this is unique to IE 9 but without refreshing the workspace in
the browser window I couldn't select a single project e.g. selecting a
different project to the one already selected just added that as an
additional selection rather than deselecting the previous project. Can't
reproduce this in Chrome and after refreshing the IE window can't reproduce
it in IE either but it did happen! ;-)

Issue 3

Not really an issue but clicking edit or preview in the workspace no longer
opens a Chromeless 800x600 window. Seems to open a new window the same size
as the current workspace window.

Issue 4

Again not really an issue but clicking play in the editor does still open a
Chromeless 800 x 600 window or rather 824x680 ish.

Issue 5

The changes to connectors whereby plain text connector, redirector connector
and tabbed nav connector have been removed means these pages are no longer
editable in existing projects. Should those page types be kept in the xwd
and just commented out new nodes? Or just support anyone who raises the
issue on one of the mailing list in what to do to fix any existing projects?

HTH

Ron

_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20121126/54ab1482/attachment-0001.html>