Justin Wood (Callek) wrote:
On 7/9/2011 3:05 PM, JD wrote:
Upgrading to SM2.2 has disabled DOM Inspector 2.0.10pre. I can't seem to
find a way to get a later version and I can't find it's install.rdf
file. Any suggestions?
This is a surprised-to-me issue, that I noticed after upgrading my
"production use" 2.1 to 2.2 as well. Caused due to the fact that
"shipped-with-2.1" DOMi ver was 2.0.10pre, and thats not on AMO.
So when we checked AMO for a compat version (or a compat-bump) on
update, the check against 2.0.10pre didn't find any results, and AMO
will never offer an older version of the extension than the one you are
running, so 2.0.9 (which was marked as compat) wouldn't get marked as
compat.
Anyone with a brand new profile would have had a working DOMi, and "we"
(myself and the DOMi owner) is working on a solution that can fix this
(emmediately) and for the future.
Did you see my other replies?
Maybe to help you and the DOM owner fix this problem, all I did was edit
the install.rdf file in the .xpi file so the SM version was changed to 3.0.
I've learned to edit install.rdf files and all my old add-ons work. I
couldn't find the install.rdf file for DOM Inspector so I did the edit I
described.
--
JD..
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
