[ww-devel] The library browser not updating problem

[Jason Aubrey]

Hi John,

On Mon, Aug 25, 2014 at 3:16 PM, John Jones <jj at asu.edu> wrote:

> This is a problem which has appeared many times before.  There are long
> discussion threads on the wiki as well.  Unfortunately, there are multiple
> things which can cause it.
>
> The menus not updating, or the add buttons not working are all signs of
> the same thing -- webwork is making an ajax call
> through instructorXMLHandler.pm and the webservice, and it is failing.
>
> One cause is if $server_root_url is not set correctly in site.conf.  There
> was a bug report just earlier today where the site was redirecting to https
> with apache, but did not have $server_root_url set to https.  A second
> cause (maybe now fixed) arises when using a local authentication (not
> webwork's internal one).  In that case, the authentication step of the ajax
> call fails.  A third cause is mis-matched perl modules.
>
> You should hope you set $server_root_url incorrectly, because that is the
> easiest to track down and fix.
>

I saw that bug report earlier and did check that - I"m running over ssl and
server root is https://... so that doesn't seem to be the problem.  There
do seem to be different ways to do the redirect, and it could be that some
of them interfere with this and some don't. On the other hand, I don't see
how that would explain the JSON unexpected character error I'm seeing in
the web console.


> Next check authentication.  For starters, is it ok if you set things to
> webwork's internal password authentication?  If so, that is probably the
> culprit and you might need to alter the particular authentication module
> you want to use so that it will not be confused by instructorXMLHandler.
>
>
Right now we're only using webwork's internal authentication.


> For both authentication and the last one, it might help to look at the
> apache error.log.  Even then, you may need to modify webwork to show errors
> instead of just reporting "there were lots of errors".  That's how we
> tracked down a mismatched perl module problem.
>

I am seeing this in the error logs:

[Mon Aug 25 14:32:07 2014] [error] [client 128.196.225.25]
[/webwork2/instructorXMLHandler] Can't call method "result" on an undefined
value at /opt/webwork/webwork2/lib/WebworkClient.pm line 164.\n * in
WebworkClient::xmlrpcCall called at line 318 of
/opt/webwork/webwork2/lib/WeBWorK/ContentGenerator/instructorXMLHandler.pm\n
* in WeBWorK::ContentGenerator::instructorXMLHandler::pre_header_initialize
called at line 183 of
/opt/webwork/webwork2/lib/WeBWorK/ContentGenerator.pm\n * in
WeBWorK::ContentGenerator::go called at line 380 of
/opt/webwork/webwork2/lib/WeBWorK.pm, referer:
https://webwork.math.arizona.edu/webwork2/UA_Math_505C-910_FS14/instructor/setmaker/?effectiveUser=admin&user=admin&key=Z9yGTNl7Ov8fTSwnv4uBhMzUHUHCbVo8
Use of uninitialized value $_[0] in uc at (eval 2278) line 60.



>
> Sorry to not have a simple fix.  If someone has a more robust solution to
> the ajax authentication issue, that would be the best.
>
> If worst comes to worst, you can re-enable the non-javascript version of
> setmaker.  It now has fewer features, but it should be immune to the ajax
> problem.
>
> By the way, does the webwork3 interface work for you?
>

Actually, the ww3 library browser seems to work - at least I can go through
the menus and display problems. I hadn't tested it before you asked because
I ran into some problems with the Problem Sets Manager. (Which I am
recording Peter).

Thanks,
Jason


> John
>
>
>
>
> On Mon, Aug 25, 2014 at 2:29 PM, Jason Aubrey <aubreyja at gmail.com> wrote:
>
>> Nope, no luck. Still the same error on master, develop and ww3.
>>
>>
>> On Mon, Aug 25, 2014 at 12:43 PM, Paul Pearson <paultpearson at gmail.com>
>> wrote:
>>
>>> Hi Jason,
>>>
>>> Does a git pull and OPL-update fix this problem?  (I am responsible for
>>> an OPL tagging bug that lasted a short while last weekend, but it should
>>> now be fixed.)
>>>
>>> ##############
>>>
>>> cd /opt/library/webwork-open-problem-library/OpenProblemLibrary
>>>
>>> git pull
>>>
>>>
>>> /opt/webwork/webwork2/bin/OPL-update
>>>
>>> ###############
>>>
>>>
>>> Best regards,
>>>
>>>
>>> Paul
>>>
>>>
>>>
>>> On Mon, Aug 25, 2014 at 3:30 PM, Jason Aubrey <aubreyja at gmail.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> A number of people have reported a problem where after an install of
>>>> ww2.9 the library browser (2) doesn't update or display problems when the
>>>> subject is changed.  I'm having this problem on the ww3 branch too.  My web
>>>> console says
>>>>
>>>> SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the
>>>> JSON data
>>>>
>>>> Is there a known solution to this problem yet?
>>>>
>>>> Thanks,
>>>> Jason
>>>>
>>>>
>>>> _______________________________________________
>>>> webwork-devel mailing list
>>>> webwork-devel at webwork.maa.org
>>>> http://webwork.maa.org/mailman/listinfo/webwork-devel
>>>>
>>>>
>>>
>>> _______________________________________________
>>> webwork-devel mailing list
>>> webwork-devel at webwork.maa.org
>>> http://webwork.maa.org/mailman/listinfo/webwork-devel
>>>
>>>
>>
>> _______________________________________________
>> webwork-devel mailing list
>> webwork-devel at webwork.maa.org
>> http://webwork.maa.org/mailman/listinfo/webwork-devel
>>
>>
>
> _______________________________________________
> webwork-devel mailing list
> webwork-devel at webwork.maa.org
> http://webwork.maa.org/mailman/listinfo/webwork-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://webwork.maa.org/pipermail/webwork-devel/attachments/20140825/7028e64f/attachment.html>