giellalt / bugzilla-dummy

0 stars 0 forks source link

Muter.oahpa.no and sanat.oahpa.no not working; two separate behavior patterns (Bugzilla Bug 1891) #1985

Closed albbas closed 10 years ago

albbas commented 10 years ago

This issue was created automatically with bugzilla2github

Bugzilla Bug 1891

Date: 2014-09-17T09:45:00+02:00 From: Jack Rueter <> To: Ryan Johnson <> CC: berit.nystad.eskonsipo, ciprian.gerstenberger, lene.antonsen, trond.trosterud

Last updated: 2014-10-24T21:23:21+02:00

albbas commented 10 years ago

Comment 9585

Date: 2014-09-17 09:45:00 +0200 From: Jack Rueter <>

Using Firefox 31.0 on Mac maveric

muter.oapha.no language pair can be selected on http://mrj.wikipedia.org/wiki/%D0%A2%D3%B9%D0%BD%D0%B3_%D3%B9%D0%BB%D3%B9%D1%88%D1%82%D3%93%D1%88

but no connection is found

Visible wheel in upper right corner appears

Error! Could not connect to dictionary server (host: http://muter.oahpa.no). Close.

The sanat.oahpa.no Allows language pair selection. On: http://omamua.rkperiodika.ru/

No spinning wheel appears, no reaction whatsoever.

albbas commented 10 years ago

Comment 9591

Date: 2014-09-18 19:54:36 +0200 From: Jack Rueter <>

More specifically The tool bar behavior for muter.oahpa.no

Visiting the main page for the Hill Mari Wikipedia: http://mrj.wikipedia.org/wiki/%D0%A2%D3%B9%D0%BD%D0%B3_%D3%B9%D0%BB%D3%B9%D1%88%D1%82%D3%93%D1%88

muter.oahpa.no/mhr/fin muter.oahpa.no/fin/mrj both are functional, but since they do not necessarily identify the word forms of the wrong language. They are useless.

muter.oahpa.no/mrj/fin Does not function! Error! Could not connect to dictionary server (host: http://muter.oahpa.no).

So the complaint about MUTER lies in the muter.oahpa.no/mrj/fin transducer facilitation

albbas commented 10 years ago

Comment 9593

Date: 2014-09-18 22:08:12 +0200 From: Ryan Johnson <>

Interesting, I can confirm it. I'll keep you posted, should have it fixed today. :)

albbas commented 10 years ago

Comment 9594

Date: 2014-09-18 23:00:17 +0200 From: Ryan Johnson <>

So, separate problems as well:

Sanat revealed that the structure to some configuration options that are read from the server when the plugin is loaded, and are stored for convenience, are actually inconveniently stored when the structure to the configs changes. Normally I'd say "clear the cache and try again", but I realized that maybe this is a situation where not everyone would be aware to clear their cache. The easiest solution is to just read the new settings each time. This should save us some trouble down the line, as the plugin should now behave as expected.
Muter revealed that i had made some internal changes but, forgot to be consistent with them. ;)

And also, sorry-- I seem to have missed your messages earlier on Gtalk. My phone was signed in but I was not around.

I'll have the changes available in a little bit.

albbas commented 10 years ago

Comment 9692

Date: 2014-10-24 21:23:21 +0200 From: Ryan Johnson <>

Also fixed.