search

openwebwork / webwork.maa.org

Information about the webwork.maa.org server
0 stars 0 forks source link

bugzilla configuration #36

Closed mgage closed 4 years ago

mgage commented 4 years ago

Bugzilla doesn't seem to be working with cookies. (I've tried with two browsers and done various combinations of emptying cache.

  1. login at https://bugs.webwork.maa.org/ . (the upper bar will register your email address and "logout"
  2. click home -- all data will have been forgotten.
  3. OR . click "all bugs" and you will be asked to login again. "bugzilla needs a legitimate login..." is anyone else experiencing this phenomenon?
drgrice1 commented 4 years ago

I see this too. I probably didn't reconfigure everything correctly when I changed from webwork.maa.org/bugs to bugs.webwork.maa.org.

drgrice1 commented 4 years ago

I believe this is fixed now. The file buzilla/data/params.json had the cookiepath set to "/bugzilla", but now the site is at the root of the domain. So it needed to be changed to "/".

mgage commented 4 years ago

This fixed it for my chrome browser but not for firefox — even after I shut down firefox and restarted it. (And also erased all cookies for bugs.webwork.maa.org http://bugs.webwork.maa.org/)

— Mike

On Mar 4, 2020, at 2:32 PM, Glenn Rice notifications@github.com wrote:

I believe this is fixed now. The file buzilla/data/params.json had the cookiepath set to "/bugzilla", but now the site is at the root of the domain. So it needed to be changed to "/".

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openwebwork_webwork.maa.org_issues_36-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAAJF27G2MFMFVPUE2IPXM23RF2UDFA5CNFSM4LBOYBVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENZZ4BQ-23issuecomment-2D594779654&d=DwMCaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=C6Pt5AGtImanmAdcooarL-JZO8M5dSFPfs3VweYXYkE&m=Pte4q00WWGhqqySI--8Lhf3hFXwHLq3MTufqA_CGEoo&s=50qiqUM0qmW-ZUnLUj_ROPTd4iFqRZ0rbCHwGjxVI30&e=, or unsubscribe https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAJF27DWJWIRUT4EEONHUPTRF2UDFANCNFSM4LBOYBVA&d=DwMCaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=C6Pt5AGtImanmAdcooarL-JZO8M5dSFPfs3VweYXYkE&m=Pte4q00WWGhqqySI--8Lhf3hFXwHLq3MTufqA_CGEoo&s=glpOBTcBVgP-cAVAC1FcmjwBstVSd2EccEu8KJed-A4&e=.

drgrice1 commented 4 years ago

That is odd. Firefox is the browser I tested this on.

mgage commented 4 years ago

the firefox browser on my home computer does fine so it must be some kind of cache on my work machine.