[CloIsed] Checklist of common misconfigurations?

  • Kenneth Boyd
  • Topic Author
  • Offline
  • New Member
  • New Member
More
14 years 8 months ago - 14 years 8 months ago #1 by Kenneth Boyd
... the Joomla URL in Moodle? [I.e., that particular message on the Health check panel.]

(Yes, different server. My prior post was about the server I use for testing and development. This one is more live.)

Context:
Joomla 1.7, Moodle 2.1.1., Joomdle 0.6 for Joomla 1.6.x . (This is the same between the test server, and the live server.)

The URL we're using works fine from a web browser, but it's detecting as misconfigured. The relative arrangement from the viewpoint of a web browser is (names changed but this is the behavior I'm observing):
* Joomla as web root: www.example.com/ (which redirects based on language preferences, it can end up as either www.example.com/en/ or www.example.com/fr/ )
* Moodle as subdirectory: www.example.com/moodle/

Yes, www.example.com/ will redirect to www.example.com/ before the internationalization redirect cuts in. The choice of https or http for the Moodle URL appears stable.

Both www.example.com/ and www.example.com/ are reported as misconfigured by the health check panel. I haven't tried any others yet.

Does this suggest anything? Likewise, is there anything I've omitted that would help in analyzing this?
Last edit: 14 years 8 months ago by Chris.

Please Log in or Create an account to join the conversation.

  • Kenneth Boyd
  • Topic Author
  • Offline
  • New Member
  • New Member
More
14 years 8 months ago #2 by Kenneth Boyd
Ok...found a way to turn the checkbox green : www.example.com/fr/ works. It seems the get_file_method approach actually needs content, which a redirect doesn't have.

Final login unification not solved yet, but all checkboxes an the health check are now green.

Please Log in or Create an account to join the conversation.

More
14 years 8 months ago #3 by Antonio Durán
Hi.

I don't fully understand your setup, so I am not sure of what the first problem was, and how you fixed it, so maybe that has something to do SSO not working...

Also, if you are using some plugin to redirect on login, it may conflict with Joomdle plugin for SSO. Try enabling redirect-less SSO in Joomdle, and make sure the joomdlehooks plugin is executed prior to the "redirect based on lang plugin" (if you are using something like that, that is)

Please Log in or Create an account to join the conversation.

  • Kenneth Boyd
  • Topic Author
  • Offline
  • New Member
  • New Member
More
14 years 8 months ago #4 by Kenneth Boyd
Frankly, I don't fully understand the setup yet (I'm fixing someone else's work). I'll schedule determining how the redirects work, and test out the plugin running sequence if that's what's going on.

Of course the docs indicate redirectless single signon (SSO) and file_get_method don't mix, but that's what I found initially configured. The Apache configuration's complicated, and the templates have been customized for branding purposes on both Joomla and Moodle so it's hard to tell what errors are from what.

Studying the error URLs led me to adjust the Joomla URL to www.example.com/fr (equally green-light on the health check panel, but keeps /fr// from appearing in the generated URLs for Joomla). After testing all three obvious valid options (file_get_method with redirecting SSO, cURL with redirecting SSO, cURL with redirectless SSO) I was told to park the live system in cURL with redirecting SSO. That actually both had working login (file_get_method with redirecting SSO fails this) and the login crosses over to Moodle (cURL with redirectless SSO fails this).

Please Log in or Create an account to join the conversation.

  • Kenneth Boyd
  • Topic Author
  • Offline
  • New Member
  • New Member
More
14 years 8 months ago #5 by Kenneth Boyd
The redirection is by Apache directives. I think I have a general solution strategy that doesn't involve patching Joomdle for stopping the HTTP errors on otherwise working links, it's just a question of how to implement it.

E.g., the generated logout link from Moodle,
www.example.com/fr/components/com_joomdl...s/wrapper/getout.php

triggers an HTTP error in spite of logging you out. The corresponding link
www.example.com/components/com_joomdle/views/wrapper/getout.php

both logs you out and doesn't HTTP-error. The easy fix for this,

AliasMatch ^/(.+?)/components/(.+) /home/example.com/components/$2

technically works within the VirtualHost defining www.exammple.com , but gets overwritten by the control panel.

The corresponding RewriteRule looks tempting, but I haven't figured out how to make it work yet.

Please Log in or Create an account to join the conversation.

  • Kenneth Boyd
  • Topic Author
  • Offline
  • New Member
  • New Member
More
14 years 8 months ago #6 by Kenneth Boyd
Solved; more of an Apache configuration problem than a Joomdle problem. All three HTTP-erroring links (Joomla login, Joomla logout, Moodle logout) were fixable with suitable RedirectMatches directives.

The remaining configuration errors appear to be covered well by the official documentation.

Please Log in or Create an account to join the conversation.

More
14 years 8 months ago #7 by Chris
Great thanks for letting us know.

Please Log in or Create an account to join the conversation.