Hi d2,
I’ll see what I can do! It probably won’t be super soon since I’ve been much busier lately. The hiding part is fairly simple to do, but an intuitive user interface is what will take a bit more time.
I have faith… Although I have been managing mine by shutting down the scripts I don’t happen to need all the time and added them only when I feel I do… Few extra steps that this can take care of. Thanks John, Brooklyn NYC USA
Sent from my XT1080 using Tapatalk
Since this afternoon the script crash my WME in Firefox 
I have disable all scripts and the only one crashing WME for me is “WME Keep My Layers”.
The screen stay grayed during launch and it stay like that.
If I disable the script then all works fine.
could you take a screenshot of what it looks like?
Actually, no need. I think I found the issue, which is related to Firefox security. I implemented a workaround for Firefox users and it appears to be working as a satisfactory alternative. Please try update version 0.4.7.2.
Thanks for pointing out the problem!
the 0.4.7.2 works fine now 
No more grayed layer
Thanks for solved the problem so quickly 
Great! Thank you for following up. Happy to hear that resolved the problem.
I seem to have “&lo%20…%20ueFilter=0” stuck on the end of every PL now, whether I am running KML and/or toolbox or not. I think this happened after I followed a google HO permalink that was pasted back into google HO. I can’t seem to get rid of it whether or not I am running keep my layers (0.4.7.8) and/or toolbox, even if I start over with a new editing window and a properly-formed permalink.
WME is collecting junk for us?
Since Keep My Layers can strip out all kinds of junk from the PLs, can it offer us some relief from this problem?
I’ve updated KeepMyLayers to version 0.4.7.9. Assuming you have auto-reset of layers enabled and you have saved at least one layer preset, it will now automatically and aggressively rid you of the badly formatted PL “virus” upon loading a PL with layers and/or filters.
For example, after you’ve updated KmL, click one of these PLs:
https://www.waze.com/editor/?env=row&layers=1029
https://www.waze.com/editor/?env=usa&layers=1029
https://www.waze.com/editor/?env=il&layers=1029
I’ve lost the ability to save, create, or view any layers. I’m on Firefox 38.7.1 which is a bit older (no choice in the matter on this PC); will try from another PC with a more modern Firefox version later, but I seem to recall the same problem.
On this PC, however, there’s no layer shown on the dropdown and clicking where the layer name used to be generatesEmpty string passed to getElementById(). in the console. Same for clicking the save button etc. The preset switched also doesn’t show any layers and instead just shows the initial instructions. I did have this working previously, though I only had two presets.
click to enlarge
Originally this script was interfering with loading WME until I force updated to 0.4.7.10 from 0.4.7 earlier today. Since then I’ve completely removed and re-added the script to Greasemonkey with no improvement.
Hey aBshield, thanks for letting me know about a potential bug. However, I can’t seem to replicate the issue. I’m testing the current version of KeepMyLayers on Firefox 45.0.1 and am having no problems with loading, saving, nor switching. I did note that when I forced an update in GreaseMonkey, it required a few page refreshes before the updated KmL was actually running. I’m not sure why that is the case. As for the “Empty string passed to getElementById()” error, that only shows in Firefox and I don’t know what causes it. Just panning the map around will also produce the error, so it’s not just KmL that experiences it. Seems benign though.
What happens if you double click on the layers icon and try adding a new preset from there? Btw, if your presets are all gone, it’s likely that your Browser cache, history, cookies, etc were cleared. Unless you turn on the option to sync between Beta-Prod editors, your settings won’t get saved after cleaning your browser. You can use that option to preserve your presets, even if you are not a Beta tester.
Anyway, please try adding the preset from the KmL preference pane and let me know what happens. Thanks!
Well before I make you crazy, let me try the other PC later that has Firefox 45 on it. I do remember that my presets seemed to be gone, but I don’t remember if I tried to create new ones or not.
On this PC with the older 38.7.1, clicking on the buttons, including the preferences, has no effect. So I can’t even see the preferences screen anymore.
You’re correct in that the empty string issue is when clicking anywhere on the map, and not just the layers drop down. Should have checked that, apologies for the false lead.
Checked on the other PC with Firefox 45.0.1. Same exact symptoms. None of my clicks on the icons seem to generate a result.
Have you tried turning off other scripts to see if something else is the culprit? That can help track down the issue and we can either ask the developer to adjust their code or I can see if I can put in a workaround.
Yes, I should have mentioned that I disabled everything except this script and the issue persisted. This included everything from Greasemonkey and the WME toolbox extension. I also tried WME from a new private window with no change as well which should discount any bad cookies or other cached data as the issue, unless there could be bad data in another location. I’m willing to try any other remediation that would prove helpful.
I believe I’ve found the issue… Which, as always, had to do with Firefox permissions. I’ve implemented a workaround for FF users so version 0.4.7.12 should now work for all. Sorry about that, FF-friends.
Hey TheLastTaterTot, I found a small bug, round icons overlap panel with layers.
That’s because you have to many layers… Just kidding…
Lol
Sent from my XT1080 using Tapatalk
LOL @jdelosa
@d2-mac: Unfortunately, there is no simple solution to the bug that you’re reporting. The round icons must stay on top for it to be clickable over the darkened save screen. (for those times when WME stops loading after saving) I’m still thinking about how to implement your request for hiding specific layers from the menu, so that would be an eventual solution.
@TheLastTaterTot: I prepared two proposals that are easy to control. I’ll be glad if you use both Or you can think of something completely different
Hiding unused layers:
Switching layers into two columns:
