17 April 2010, 16:05

I just upgraded to 1.2.4 on 2 sites and both have the same problem.

I click on the little blue question marks and all that is displayed is "An error occurred trying to retrive the help page". The url on the buttons is "http://selfdesignhigh.org/maharatest/artefact/internal/".

Is there a path to help files setting somewhere?

Paul

 

04 May 2010, 20:25

I just upgraded to 1.2.4 on 2 sites and both have the same problem.

I click on the little blue question marks and all that is displayed is "An error occurred trying to retrive the help page". The url on the buttons is "http://xxxxxxx.org/maharatest/artefact/internal/".

Is there a path to help files setting somewhere?

23 September 2010, 9:07

Hi, I've just noticed this on an upgrade to 1.3.1. Maybe it was a problem earlier, too, that I hadn't noticed.

On Account settings pages only, I'm getting the same (misspelt!) phrase "An error occurred trying to retrive the help page", which links to https://portfolios.xxxxxx.ac.uk/account/

This seems to be because we're using https on the Account settings pages (login is via LDAP so we really have to secure it). Is there a way around this?

Thank you
Joss

23 September 2010, 9:45

Joss,

The help pages are actually loaded using javascript and an ajax call to /json/help.php.

There's no reason that this shouldn't work using https that I'm aware of - The only thing that I can think of is that your wwwroot may perhaps be incorrect. I've just verified this on my local setup and it works exactly as expected.

I'd suggest breaking out a debugging tool such as the google chrome inspector, or FireBug to see why it's failing.

Andrew

24 September 2010, 4:45

Here's my config details. It seems to work fine for everything else.


$cfg->wwwroot = 'http://portfolios.xxxx.ac.uk/';

// SSL stuff
$cfg->httpswwwroot = 'https://portfolios.xxxx.ac.uk';

// dataroot - uploaded files are stored here
// must be writable by the webserver and outside document root.
// Mahara will NOT RUN if this is inside your document root, because
// this is a big security hole.
$cfg->dataroot = '/var/www/mahara_uploads';

Looking at the source code for a page where the problem occurs, it looks like a href="" is empty when it shouldn't be:

<span class="help"><a href="" onclick="contextualHelp(&quot;accountprefs&quot;,&quot;friendscontrol&quot;,&quot;core&quot;,&quot;account&quot;,&quot;&quot;,&quot;&quot;,this); return false;"><img src="http://portfolios.xxxx.ac.uk/theme/raw/static/images/icon_help.png" alt="Help" title="Help"></a></span>

24 September 2010, 5:15

Hi Joss,

The clarification from your config.php helps... I think I know what's going on here.

I'm having a look into it some more. Thanks for reporting the issue.

Andrew 

23 September 2010, 11:03

I've bugged (https://bugs.launchpad.net/mahara/+bug/646075) and corrected the spelling error - I would imagine that it should make it to 1.3.2.

Andrew

24 September 2010, 8:01

I am also having this problem.

It appears that if you have https enabled for logins ($cfg->httpswwwroot='https://www.somestie.com'), it breaks the help links. 

Setting the entire site to HTTPS ($cfg->wwwroot = 'https://...) and commenting out the $cfg->httpswwwroot config line resolves the problem. This makes all pages served after login https. I don't see a problem with this, so it is an acceptable workaround until the bug is fixed.

 

 

 

 

 

 

 

 

 

24 September 2010, 9:56

Thanks, Melinda. The problem with your solution is that users that login via the http URL of the site do not login over SSL.

With my current config, login from http:// passes via https (I can see from my ssl_access logs). With your changes, logins from http:// do not go via https:// as can be seen from my logs.

I wonder if one of the developers can explain how SSL works in Mahara 1.3.1?

Thanks!

24 September 2010, 10:19

Hi Joss,

I'm looking into this one and having a look with other developers.

Essentially though, if you specify:

$cfg->httpswwwroot = 'https://foo.ac.uk';
$cfg->wwwroot = $cfg->httpswwwroot;

Or just:

$cfg->wwwroot = 'https://foo.ac.uk';

Then this should work. All traffic will be sent over SSL. From what I recall, there's no specific requirement to specify the httpswwwroot if it's the same as the wwwroot. There are some potential bugs I'm trying to track down with use of the httpswwwroot.

Is there any reason you don't want all traffic using your secure connection?

Andrew