Status of Premium Content extension for Firefox
What is the official status of the Firefox plugin for Premium Content? When I initially install it, it works. (Or if I remove it and then click "Undo" to reinstall it, it works then too.) But once I shutdown and restart the browser, the icon never goes green and no premium content access.
Comentários
-
Just in case this happens to be the issue, it does require log in to the Liahona WiFi each time you want to use it. And if you have auto-connect for Liahona turned on in your computer, that may be the problem. Turn off autoconnect and log in manually and see if that works (I'm assuming you're only trying to use it in a Church building where Liahona is installed and working of course - it won't work outside the building but some people still don't realize that).
The other thing I've found I need to do is click the puzzle piece (or greyed out dot - can't remember which one) and it will then prompt you to connect to the Premium browser extension. You'll need to click that as well as just logging into WiFi first.
--Chris
5 -
We have also experienced this inexplicable behavior with the Premium extension on Firefox. There appears to be no rhyme nor reason. In my experience, if you let the firefox browser "sit for awhile", it eventually works. Usually people are in a greater hurry, so the answer is to "use a different brand of browser".
0 -
For what it's worth, after spending several (!) unscheduled hours in our FSC yesterday with outstanding assistance from one of FamilySearch's two senior tech support people who went through all six of our computers, I also discussed the issue(s) of Firefox with him. Firefox is my own personally preferred browser due to security issues, and I do not use Chrome at home at all (for the same reason - security). However, his eventual comment was that FamilySearch is built around Chrome, and there will be less problems with it than Firefox even though Firefox is supposedly one of the acceptable browsers.
As a result yesterday, I finally gave up and we're now using just Chrome at the FSC. After all, people aren't authorized to do personal banking or other such internet "business" on FSC computers. so the issue of security is less significant with Chrome there than at home. I don't personally like using Chrome, but I decided to "get over it" yesterday and stop dealing with all the Firefox errors (including thinking Sophos is malware). Firefox is being deleted as an option on the desktop of all six computers.
Just one user's (also FSC leader's) 2¢....
--Chris
1 -
Thanks or the responses. It is helpful to know I'm not the only one with this issue. I've also heard that FamilySearch will usually just work better on Chrome, and have experienced the same thing myself.
The computers I'm working on are our hard-wired FSC computers, so the Liahona wireless is not involved. It feels like this issue is related to the network move and this new network's security (but I can't say exactly when this issue first started), and/or Sophos configuration changes for FSC computers.
Can this issue be passed onto the development team over the Firefox plugin? Or is this a network configuration issue that only affects Firefox, and it needs to go to network engineering?
0 -
Let's hope Elder Richins or one of the other tech support reps sees this and passes it along. It's not something the FamilySearch tech folks can resolve, from everything I've been able to discern. They do a great job for us, and have to deal with some of the same kinds of glitches that sometimes arise in a huge network system that is far bigger than just the FamilySearch portion of it.
Separately, even though my browser here at home is Firefox, it's obvious that it doesn't always play well with every network all the time. Remember that it's open source, and changes to it are happening all the time, which can be a challenge for networks to keep up with. I'm sticking with it and having to just accept that at times it's not going to properly open a page somewhere, one some website, even though most of the time it does a fine job.
And to keep this more or less on topic, I've experienced few problems once I figured out how to properly use the new browser extension to access the Premium content on FamilySearch. It's a bit quirky, but once I knew what is posted in my 20 May post above, I've had few problems accessing FamilySearch within a Church building via the Liahona WiFi. That's entirely separate from the problems involving Sophos on the FSC computers, apparently (at least I haven't experienced it via Liahona). I'm very happy to have left programming many years behind me - I'd hate to be trying to find all the programming glitches that exist between programs, sections of a huge network, etc., these days.
I started with punch cards (one card per line of computer code) and paper output (no such things as video monitors) using Fortran IV, LOL! Code wasn't even remotely as bloated as it is with today's modern languages. Whether Bill Gates really said it or not, his alleged rhetorical question as to "who would need more than 640K?" actually made some sense back in those days. Multi-megabyte or even gigabyte programs couldn't have even have been conceived of then (and we wonder why so much goes wrong these days).
--Chris
0 -
Ha, Ha Chris. The first programs I made were saved on ticker tape!!!!
0 -
LOL! We're ancient! 😄
--Chris
0
