Seqouia 15.6.1 breaks FOEX extension
HI, After upgrade to Seqouia 15.6.1 an extension for developing Oracle APEX applications breaks Firefox. It is the only extension I have installed. Console information is not really that helpful. Maybe you can make some head and tails about it.
被選擇的解決方法
Hi Paul,
We found the issue. The FOEX. Plug-in/extension has a setting "Run on sites with restrictions" , option Allow/ Don’t Allow. (Don't Allow is the default) You have to set this to Allow. (was Don’t Allow)
Now what I don’t understand why this worked before upgrade to 15.6.1 MacOS as I did not change anything on this config. However our development server is running HTTP with Tomcat. So maybe because it is HTTP it stops that traffic until you set it to Allow. Same version on Windows 11 with setting (default) “Don’t Allow” is working fine, no problem.
Interesting issue, 3 days to figure out what was going on.
Anyway thank you for your help.
從原來的回覆中察看解決方案 👍 0所有回覆 (5)
Hi Raymond
Is this an add-in you have installed and it is breaking Firefox? If so, what us the name of the add-on?
If it is another piece of software you have installed on your computer, what is it called?
This add-in has been working without any problems until I upgraded to Sequoia 15.6.1 I also run Parallels on my Mac (M1) with Windows 11. So I tried running Firefox with that extension/add-in only too. I am getting the same error as on Mac. So maybe there is something underlying on MacOS which cause the problem.
What is the name of this add-on for Firefox that you have installed?
The name is FOEX and is supplied by Oracle. You can't download it through the standard extension "shop". I can email you a copy as I can't upload it here
選擇的解決方法
Hi Paul,
We found the issue. The FOEX. Plug-in/extension has a setting "Run on sites with restrictions" , option Allow/ Don’t Allow. (Don't Allow is the default) You have to set this to Allow. (was Don’t Allow)
Now what I don’t understand why this worked before upgrade to 15.6.1 MacOS as I did not change anything on this config. However our development server is running HTTP with Tomcat. So maybe because it is HTTP it stops that traffic until you set it to Allow. Same version on Windows 11 with setting (default) “Don’t Allow” is working fine, no problem.
Interesting issue, 3 days to figure out what was going on.
Anyway thank you for your help.