I cannot find this file
You can also change in 5.* the 4.0 value of maxVersion of the install.rdf file in coFFPlgn folder, the same value of maxVersion of the install.rdf file in IPSFFPlgn folder: it would work with the next FF upgrades...
FILE IPSFFlgn:
<!-- Firefox -->
<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<!-- firefox -->
<em:minVersion>2.0</em:minVersion>
<em:maxVersion>5.*</em:maxVersion>
</Description>
</em:targetApplication>
</Description>
</RDF>
FILE coFFPlgn:
<!-- Firefox -->
<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<!-- firefox -->
<em:minVersion>3.0</em:minVersion>
<em:maxVersion>4.0</em:maxVersion>
</Description>
</em:targetApplication>
</Description>
</RDF>
so what should we do now ???
Anyway I think it would be better to wait for the official Norton hotfix.... Few days only, I hope.
Works like a champ!
Tony,
I "assume" that you work for Symantec....If not...SORRY! if I just insulted you.
Continuing on the assumption you are an employee I have to ask: Do you bosses understand how irate many of your customers are getting with your company?
I've been using Symantec and Norton products since I bought my first DOS/Windows based PC in the late 80s/early 90s (when Peter Norton's picture was still on the boxes) and I am not a "happy camper". They really need to make some adjustments if they don't want to lose what I suspect is a large segment of the customer base.
Symantec:
Your customers are stating that this problem can be resolved simply by changing the value of the maxversion parameter from 4.0 to 4.0.1 in the install.rdf file !!!!
If the fix is truly that simple, then (1) shame on you for missing this trivial detail and (2) you need to update push out the install.rdf file IMMEDIATELY.
If the fix is not that simple, then please explain why your customers are reporting that making such a trivial change appears to fix the problem, and explain why making this trivial change does not actually fix the problem.
As long as you make tools that work within browsers, then you will need to stay on top of browser updates. While you might not have anticipated the Firefox 4.0.1 update, you would have to be living in a cave to have missed the Firefox 4.0 upgrade .... and yet when Firefox 4.0 came out .... it appeared to have taken you by surprise and broke the Norton Toolbar. No excuse for that!
Please fix this current incompatibility problem ASAP (i.e., TODAY).
I still don't get it
SGFC wrote:
Tony_Weiss wrote:I recommend that you hold off on upgrading to 4.0.1.
So Firefox puts out a security update and you recommend against it?
To be fair, that's a paraphrase of my original message:
For now, if you want to continue using the Norton Toolbar with Firefox, I recommend that you hold off on upgrading to 4.0.1.
We want you to be secure when you're online. My point was to give customers options.
I'm surprised more people aren't concerned with the security concerns involved in manually modifying their Norton product. That's a very risky operation, with serious security issues.
Tony,
I used drminer's suggestion because I wanted the FF 4.0.1 security updates without losing Norton's toolbar. I understood the risk in modifying Norton's files, but I decided it was worth taking.
I have a question about the "install.rdf" file that I changed. Why does Norton require the max version number to be so exact?
I changed the value just like drminor did and it works perfectly also. I don't think there's any risk because you're just changing the mozilla version number.
Updating to Firefox 4.0.1 has been deemed Critical by Mozilla - TRUE
The Norton Toolbar v5.5 is not compatible with this version yet - TRUE
My solution?
Save all your passwords mentally (or on a piece of paper which is in a place only you go if you cannot) like I have done and update to Firefox 4.0.1 and wait for Symantec to fix the issue (and they are already aware of it). People are saying "I see no risk as blahdeblahdeblah" but did the captain of the Titanic see the risk in running his ship close to an iceberg? And we all know how that ended up....
Although the risk may not become immediately obvious, it does not mean that there is no risk
Kind Regards,
Dazza-N360
noghere....
I found that the maxversion of the "install.rdf file in IPSFFPlgn folder" was already set to "5.*". However, the maxversion of the "install.rdf file in the coFFPlgn folder" was set to "4.0".This is the file that deals with the Toolbar, see below.... my highlight.
<?xml version="1.0" encoding="UTF-8"?>
<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:em="http://www.mozilla.org/2004/em-rdf#">
<Description about="urn:mozilla:install-manifest">
<em:id>{2D3F3651-74B9-4795-BDEC-6DA2F431CB62}</em:id>
<em:name>Norton Toolbar</em:name>
<em:version>5.5</em:version>
<em:description>Symantec Corporation</em:description>
<em:creator>Symantec Corporation</em:creator>
<em:homepageURL>http://www.symantec.com</em:homepageURL>
<em:iconURL>chrome://coffplgn/skin/symantec.png</em:iconURL>
<em:locked>true</em:locked>
<!-- Firefox -->
<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<!-- firefox -->
<em:minVersion>3.0</em:minVersion>
<em:maxVersion>5.*</em:maxVersion>
</Description>
</em:targetApplication>
</Description>
</RDF>
The file in the IPSFFlgn folder is for the Norton IPS install and as I said it was already set for a maxversion of "5.*" see below.
This is the file unchanged and as I found it except for the highlight.
<?xml version="1.0" encoding="UTF-8"?>
<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:em="http://www.mozilla.org/2004/em-rdf#">
<Description about="urn:mozilla:install-manifest">
<em:id>{BBDA0591-3099-440a-AA10-41764D9DB4DB}</em:id>
<em:name>Norton IPS</em:name>
<em:version>2.0</em:version>
<em:description>Symantec Corporation</em:description>
<em:creator>Symantec Corporation</em:creator>
<em:homepageURL>http://www.symantec.com</em:homepageURL>
<em:iconURL>chrome://ipsffpl/skin/norton.png</em:iconURL>
<em:locked>true</em:locked>
<!-- Firefox -->
<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<!-- firefox -->
<em:minVersion>2.0</em:minVersion>
<em:maxVersion>5.*</em:maxVersion>
</Description>
</em:targetApplication>
</Description>
</RDF>
These folder/files are located in the 'C:program data\norton' under one of those long stringed {} folders in the NIS_ folder.
Following the proceedure mentioned above I opened the install.rdf file in the coFFPlgn folder with Notepad and changed the maxversion to "5.*" as shown above. After saving this file I reset the NIS tamper protection back to on. When I restarted Firefox I could then update to version 4.01.
Corsair...
That's right!
Rather than mess with changing Norton's files, I'd recommend installing the Add-on Compatibility Reporter add-on from Mozilla. It allows you to disable Firefox's add-on compatibility check for installed add-ons from inside Firefox itself which is a lot safer than mucking with Norton's files.
Do you have to start this process with Firefox 4.0? What if Firefox is already updated to 4.01?
Thanks!
Hi Morac... that's a great find. However, the write up for this Addon suggests that it only sends a report about which Addons are not compatible. I don't see where it mentions anything about turning off Firefox compatibility check.
However, it took me all of 10 minutes to fix 3 computers in our house. With ALL of Symantec's resources you'd think they would be able to jump all over this as soon as the 4.01 fix landed.
For that matter, being on the inside so to speak, they should have been aware of these things from the get go. I like many others am a loooooong time Norton user and I get fed up with these incompatibilities when other addon authors seem to have thier situation well in had.
@Tony_Weis: You stated: “I’m surprised more people aren’t concerned with the security concerns involved in manually modifying their Norton product. That’s a very risky operation, with serious security issues.” Please explain why changing the maxversion parameter from 4.0 to 4.0.1 is a “very risky operation” … especially after several customers have posted in this frum that they have made that change, it works, and (so far) they have not encountered any problems. Stop using FUD and start giving us some facts … explain the explicit risk associated with changing the maxversion parameter.
Folks, FYI, I am not quite sure why, but the NIS 2011 toolbar is working fine on my upgrade to FF 4.0.1. Windows 7, Ultimate 64-bit, SP1. Just lucky, I guess as the other upgrade problems have all hit me too.
same here - all works fine here too