TOPIC:

Hi
we have followed with great care and attention the installation instructions of version 3 on to web server.

Integrated with moodle installation has caused usage issues
tested the install as per instructions in moodle integration read me txt document
step 1. ok
step 2 ok
step 3 ok
step 4 ok
Can log in and see the xerte home screen ..

Post integration issues

1. Project templates can not be created ( partially works in IE with "Only secure content is displayed" warning message ? I can add a title but fails to work at all in FF or Chrome)

2. Management screen all buttons at top are there but no content below ?

3. Can not log out of xerte ?


Any suggestions or ideas welcome ?

So in step 1 everything worked? e.g. creating and viewing projects as the guest user?

After step 4 creating and viewing doesn't work but you do get prompted to login to Moodle and then redirected back to xerte and then see your first name and last name at the top of the Xerte workspace?

around line 43 of the xerte config.php change $development = true; and see if that provides any useful error messages?

Your reference to "only secure content..." did you install Xerte using a https:// address or did you change that after install? The url in sitedetails or via the management page needs to match what you are using to access the install.

HTH
Ron

yes is installed on a https server.
I will try the config line 43 change and reply ..

Thanks Ron,

All OK now it was https and http issues...

now for the roll out to staff - exacting and exciting times ahead then joy !

Hi Ian
Glad it's sorted!
Remember to reset development to false if you haven't already.
Likewise don't forget to register your installation if you haven't already and watch out for a survey we hope to send out before the end of the year to capture stories, reflections and examples from the ever-growing Xerte community.
Ron

I have seen quite a few occasions now of problems regarding http vs https where xerte does not 'work' properly when the wrong protocol is used. I have had this problem too.
Is it possible to change the install script that this issue won't occur anymore? Like forcing to use the correct protocol?