Once logged in under the mapped domain URL it should keep it for that domain.Īnother option is available for some. But domain mapped blogs might be a problem with some browsers or some browser security settings. Logging in to WordPress.COM at your admin dashboard should work (does for me on Firefox) for posting comments on WordPress.COM blogs. Some browsers do try to isolate cookies in ways that can impact login status, which also uses cookies. The mechanism of login might be a problem. This is to prevent others from making comments and falsely attributing them to you (by way of your email address that will get your Gravatar image). Like it or not.A security/privacy feature of WordPress.COM is that if a comment is being made using an email address that is registered already, it is necessary to prove you are the owner of that email address. I have workarounds in place for whatever eventuality prevails. We will all just have to use what is currently available and wait it out and see what comes. Or you maybe forced to just upgrade and run your Mac from a newer OS version, if your older Mac supports it or look into purchasing new or newer (used) Mac computer that can run the new and current Mac OS systems. One older OS X for our older work software and email and workflows and another one just to be able to surf the internet from, if you stil have older software that works, but cannot afford to update or like the older software better than newer versions. You may be able to get by an older version web browser for awhile after April 2017 (there are still many legacy OS X users running mostly running OS X 10.6.8 Snow Leopard who continue to use the very out of date and unsecure version of Safari on that version of OS X), but unless some other web browser developer pIcks up the gauntlet thrown down by the Mozilla Firefox group or SeaMonkey group, we may end up having to run two OS X versions (new up to date and older legacy ) and boot two operating systems, eventually. I am hoping another new web browser developer will rise to the challenge of developing a new web browser for legacy, obsolete OS X systems. WIthout another web browser developer to support older legacy systems (like what the developers of TenFourFox did for older Apple PowerMac, PowerPC users still running OS X 10.4.11 and OS X 10.5.8), we will be without an updated and secure web browser for 10.6-10.8 by end of April 2017. Waterfox maybe the only option left to us by the time April 2017 comes along. I am hoping that the lone developer of Waterfox will maintain its support for older OS X versions. It's all over for older legacy OS X secure web browsers, unless. So what will happen in April 2017? Will we have no supported browser to use? I have downloaded the ESR version of Firefox. Thank you MichelPM, you are very knowledgeable. Those of us that are forever tied to older OS X versions will need to to be flexible in our web browser use as, currently, we have really few to no alternatives for web browsers to securely and functionally access the Internet for the foreseeable future. If this ESR 45.x version of Mozilla Firefox disables any FF plugins and extensions you were using, or any plugins you were using with your older Safari,I whole heartedly recommend that you use the two versions of Firefox together, but only use the plugins functional one only when you need to use it. You can use this version now OR you'll have to switch to the ESR version before the end of Dec 2016 as Mozilla won't offer this version after Dec 2016. The ESR version 45 of Mozilla Firefox is still completely secure. Mozilla will issues ESR (security) updates to OS X10.6-10.8 for the version 45 of Firefox, but will not get ANY new web browser functionality feature updates. Mozilla will keep issuing security updates for Firefox in the form of their Firefox ESR web browser (Extended Security Release web browser program, vers. Ignore all the enteprise and educational info. Can also switch, before end of 2016, to Firefox ESR 45.6 version here.
0 Comments
Leave a Reply. |