Hi Nicolaas,

This has helped.

I only get a warning about the form not being secure and a JS warning 
about getPreventDefault() being obsolete.

Thanks,
J-F

On 20/01/2014 15:12, Nicolaas Matthijs wrote:
> Hi Jean-Francois,
>
> Apologies if this has already been tried, but can you try to clear your cache 
> and reload the page just to make sure that it's not a caching issue?
>
> The 404s are interesting because none of those files are supposed to be 
> loaded on the global administration tenant. Would you mind sending a copy of 
> your nginx config file?
>
> Thanks,
> Nicolaas
>
>
> On 20 Jan 2014, at 14:04, Jean-Francois Leveque 
> <jean-francois.leve...@upmc.fr> wrote:
>
>> After some filtering, I have 404s for:
>> /ui/css/oae.index.css
>> /node_modules/oae-core/topnavigation/css/topnavigation.css
>> /node_modules/oae-core/footer/css/footer.css
>> /ui/js/index.js
>> /node_modules/oae-core/topnavigation/js/topnavigation.js
>> /node_modules/oae-core/footer/js/footer.js
>>
>> I also get:
>> Error: Script error
>> http://requirejs.org/docs/errors.html#scripterror twice for
>> /shared/vendor/js/requirejs/require-jquery.js
>>
>> And:
>> L'utilisation de « getPreventDefault() » est obsolète. Utiliser «
>> defaultPrevented » à la place.
>>
>> Thanks,
>>
>> J-F
>>
>> On 20/01/2014 14:46, Branden Visser wrote:
>>> Thanks, for deployment issues on your local machine though I think we
>>> can probably stick to list.
>>>
>>> Do you have any errors in your browser console when using it from
>>> Firefox 26? Looks like it may be a local deployment issue.
>>>
>>> Thanks,
>>> Branden
>>>
>>> On Mon, Jan 20, 2014 at 8:41 AM, Jean-Francois Leveque
>>> <jean-francois.leve...@upmc.fr> wrote:
>>>> Your QA server is fine once the cert is accepted.
>>>>
>>>> I've nevertheless reported the issue.
>>>>
>>>> Thanks,
>>>> J-F
>>>>
>>>>
>>>> On 20/01/2014 14:28, Branden Visser wrote:
>>>>>
>>>>> That's great to hear! About not working with Firefox 26, can you give
>>>>> it a try on our QA server [1] and let us know if it fails there too?
>>>>> If so feel free to create a bug in our github issue tracker [2].
>>>>> You'll need to accept a self-signed cert, though.
>>>>>
>>>>> Thanks,
>>>>> Branden
>>>>>
>>>>> [1] https://admin.oae-qa0.oaeproject.org
>>>>> [2] https://github.com/oaeproject/Hilary/issues?state=open
>>>>>
>>>>> On Mon, Jan 20, 2014 at 8:24 AM, Jean-Francois Leveque
>>>>> <jean-francois.leve...@upmc.fr> wrote:
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> I've reached the "Global administration UI".
>>>>>>
>>>>>> BTW, it does not seem to work with Firefox 26.0, but is fine with
>>>>>> Chromium
>>>>>> 31.0.
>>>>>>
>>>>>> J-F
>>>>>>
>>>>>>
>>>>>> On 20/01/2014 12:04, Branden Visser wrote:
>>>>>>>
>>>>>>>
>>>>>>> Yes I think so. Appears it was built with a different version of
>>>>>>> node.js then you are trying to run it with another version. You may be
>>>>>>> better off deleting all modules in node_modules that **don't** begin
>>>>>>> with "oae-" and then run "npm install -d"
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Branden
>>>>>>>
>>>>>>> On Mon, Jan 20, 2014 at 5:36 AM, Jean-Francois Leveque
>>>>>>> <jean-francois.leve...@upmc.fr> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> I now get another error:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [2014-01-20T10:33:28.358Z] ERROR: oae/7771 on SakaiLaRochelle: An
>>>>>>>>> uncaught
>>>>>>>>> exception was raised to the application.
>>>>>>>>>        Error: Module version mismatch. Expected 11, got 1.
>>>>>>>>>
>>>>>>>>>            at Module.load (module.js:356:32)
>>>>>>>>>            at Function.Module._load (module.js:312:12)
>>>>>>>>>            at Module.require (module.js:364:17)
>>>>>>>>>            at require (module.js:380:17)
>>>>>>>>>            at Object.<anonymous>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> (/home/leveque/OAE/Hilary/node_modules/passport-ldapauth/node_modules/ldapauth-fork/node_modules/ldapjs/node_modules/buffertools/buffertools.js:1:77)
>>>>>>>>>
>>>>>>>>>            at Module._compile (module.js:456:26)
>>>>>>>>>            at Object.Module._extensions..js (module.js:474:10)
>>>>>>>>>            at Module.load (module.js:356:32)
>>>>>>>>>            at Function.Module._load (module.js:312:12)
>>>>>>>>>            at Module.require (module.js:364:17)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Should I clean node_modules/passport-ldapauth too?
>>>>>>>>
>>>>>>>>
>>>>>>>> On 20/01/2014 11:09, Branden Visser wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Jean-Francois, just to confirm, you have run npm install -d in the
>>>>>>>>> Hilary directory?
>>>>>>>>>
>>>>>>>>> There might be some lingering issues with the npm issues you had
>>>>>>>>> earlier (e.g., a partially installed "connect" module), resulting in
>>>>>>>>> NPM not retrying to install some of the nested modules. You could try
>>>>>>>>> deleting the connect module that is showing this issue: rm -rf
>>>>>>>>> node_modules/connect and then trying to run "npm install -d" from the
>>>>>>>>> root of hilary again.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Branden
>>>>>>>>>
>>>>>>>>> On Mon, Jan 20, 2014 at 4:57 AM, Jean-Francois Leveque
>>>>>>>>> <jean-francois.leve...@upmc.fr> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I get an error:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> module.js:340
>>>>>>>>>>>         throw err;
>>>>>>>>>>>               ^
>>>>>>>>>>> Error: Cannot find module 'cookie-signature'
>>>>>>>>>>>         at Function.Module._resolveFilename (module.js:338:15)
>>>>>>>>>>>         at Function.Module._load (module.js:280:25)
>>>>>>>>>>>         at Module.require (module.js:364:17)
>>>>>>>>>>>         at require (module.js:380:17)
>>>>>>>>>>>         at Object.<anonymous>
>>>>>>>>>>> (/home/leveque/OAE/Hilary/node_modules/connect/lib/utils.js:17:17)
>>>>>>>>>>>         at Module._compile (module.js:456:26)
>>>>>>>>>>>         at Object.Module._extensions..js (module.js:474:10)
>>>>>>>>>>>         at Module.load (module.js:356:32)
>>>>>>>>>>>         at Function.Module._load (module.js:312:12)
>>>>>>>>>>>         at Module.require (module.js:364:17)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> It seems I have the latest Hilary:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> OAE/Hilary $ git pull
>>>>>>>>>>> Already up-to-date.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Any idea?
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> J-F
>>>>>>>>>> _______________________________________________
>>>>>>>>>> oae-dev mailing list
>>>>>>>>>> oae-dev@collab.sakaiproject.org
>>>>>>>>>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
_______________________________________________
oae-dev mailing list
oae-dev@collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/oae-dev

Reply via email to