[Xerte-dev] Re: Export Code

Ron Mitchell ronm at mitchellmedia.co.uk
Wed May 2 10:09:42 BST 2012


Could it be that inside xot config.php require_once fo the integration
config needs to be changed to require? e.g.

if ($row['integration_config_path'] != "") {
        require_once($row['integration_config_path']);
    }

if ($row['integration_config_path'] != "") {
        require($row['integration_config_path']);
    }

If that is the case the question still arises is there any benefit in using
the database for this given that xot config.php needs editing anyway?

Ron 

-----Original Message-----
From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron Mitchell
Sent: 02 May 2012 10:03
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: Export Code

Been testing and have a temporary or possibly permanent fix in place in the
install....

One key change from the previous method was adding the require path to
moodle config.php to the db (integration_path) instead of coded into XOT
config.php

Manually adding the require path back to the top of xot config.php resolves
the problem. To be honest given that whoever installs has to edit the xot
config.php anyway to choose which auth method they wish to use I wonder if
it's not better to keep the require path hard coded too? 

Alternatively I guess somehow the require path from the db isn't being
picked up in config.php?

Cheers
Ron

-----Original Message-----
From: xerte-dev-bounces at lists.nottingham.ac.uk
[mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of David Goodwin
Sent: 02 May 2012 09:48
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Export Code


On 2 May 2012, at 09:28, Ron Mitchell wrote:

> <bug>
> spoke to soon re the moodle integration! :-(
> 
> Opening, editing, publishing existing projects seems to work fine but 
> when creating a new project all seems fine until closing the editor.
> The workspace appears empty until refresh when all the existing 
> projects then re-appear but not the newly created project. However 
> this is being created in the user-files directory so I'm guessing it's 
> not being added to the database but will check that next. Even so not 
> sure why the workspace appears empty on closing the editor until 
> refresh. Here's a quick screencast showing all this 
> http://dl.dropbox.com/u/1388941/xot18_beta_moodle_integration_problem.
> mp4
> 
> David - can you advise?




Err. no (I can't provide any useful insight yet). 

Your session should be setup by the time you are able to create new LOs so
I'm a little perplexed as to why :

a) the workspace appears empty

and

b) you're not able to see the thing you've just created

Thanks for the .mp4


David.

Pale Purple Ltd.  (Company No: 5580814)
'Business Web Application Development and Training in PHP'

http://www.palepurple.co.uk   
Office: 0845 0046746     Mobile: 07792380669 

Follow us on Twitter: @PalePurpleLtd


_______________________________________________
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




More information about the Xerte-dev mailing list