[Script] WME Add-Ons V0.45 ==> Features moved in WME Toolbox

WME Add-Ons has stopped working for me as well

cleared the cache and it made no difference

problem fixed with update

Thanks

Hi all

I can’t find the link to download?

Can anybody help?

Thanks

http://www.waze.com/forum/viewtopic.php?f=8&t=36644

classic! XD

Alternate street names still not working in v0.44. Any plans to fix?

Interesting, using the d/l link in the OP, there is indeed a version .44, wonder what’s new… (no info in OP, as of this posting)

Edit: UR Icons still not changing properly based on ‘Open/Solved/Not Identified’ on .44

This needs to be made a priority, especially with the new UR communication features that are present in the beta. When that goes live, it’s going to be very important to be able to see different icons for URs.

Via my iPhone 4S

The UR Overview script now shows a different icon for URs with conversations. Not sure if it will conflict with this script or not.

According to the way Twister explained this feature, URO only reads the positions of the base icons and pastes its own icons on top, it doesn’t replace anything. You can see this by dragging the map around and noting URO’s icons disappearing.

After the URL change, doesn’t seem to work. I added new URL to the top properly, as I’ve done for other scripts, but addons still won’t load for me.

Would you please add in the header of the scipt the new editor url:

// @include             <new url>

THX, Stefan

Talking to me? Already did that, still doesn’t load.

How do you edit a .crx file? I thought the whole point of those is that you can’t edit them.

Created an issue/bug in the Google Code project for WME Add-ons. (#24). gdu usually seems to see things reported there, so…

Dunno how to do it to a crx file, but when installed the .js files are at:
C:\Users<user>\AppData\Local\Google\Chrome\User Data<Default|user>\Extensions
The folders match the ID’s that show up on the extensions tab in Chrome when developer mode is enabled.

I’ve changed some of the extensions to @include the new beta url but that doesn’t seem to be effective.

Sorry … it was a little bid unclear from my side … I ment gdu1971 and wanted him to change the header of the script so that all can suffer from it.

Stefan

edited the userscript, not the crx

I’ve updated this addon to work with the new beta editor (features remain exactly the same):

Firefox: http://www.wazeteam.com/firefox/injectit.user.js

Chrome: http://www.wazeteam.com/chrome/WME_Addons.crx

Thank you for your work.
I had installed WME addons. 0.44 in Chrome under tampermonkey taken from the first topic of this discussion that gave problems with the new address of the WME beta.
Now is the fixed version does not work with the 0.43 and tampermonkey, but only as an extension of Chrome.
It 'the same thing?