The one thing that I have found which I strongly prefered in dd-wrt over Tomato was the fact that I could use iMacros (a free plugin for Firefox) to "record" my configuration (the first time entered), after which, you could "replay" the recorded macros to reset the configuration (eg. after each flash, clear NVRAM, run the iMacro, and within minutes you would have the exact same setup as before, with the safety of NVRAM clear).

Having just come back to Tomato, I recorded my entries the first time around. I just flashed to the latest git build, and after performing an NVRAM reset, found that iMacros does not work…

For example, it gets stuck on the "Basic" page's password entry for pppoe.

I assume this has something to do with the way Tomato renders its pages… Is there anything that can be done to allow for iMacros to be used?

This would make life easier to the users, while at the same time save headache for the devs / forum dwellers telling users to reset NVRAM to people who were too lazy to do so because they would have to manually reenter all the settings/info.

@PortalCake: I've used this firmware since the Tofu / Thibor days. You might have gotten "lucky" with your upgrades as no NVRAM values had changed, but your router will NOT be functioning as expected if the devs change one, and you don't reset. The time (1 minute via iMacros or 10 minutes manually) is worth the knowledge that it's a clean environment in case there ARE issues. That is very bad information that you're passing as fact.

web_pb controls a "peakaboo" feature for the UI. When disabled (web_pb=0), password fields show as normal text fields.

In its default enabled setting, password fields have their contents obscured (eg "••••••") UNTIL they gain focus, at which point they are flipped to be text fields and reveal their contents. Clearly, as TB suspected, the scripting of this feature is confusing iMacros.

In general: clearing NVRAM is not nearly as necessary as some contend. Yes, if you're switching between firmware distros, or there's been major changes in the upgrade you're making, definitely clear it. But if you're just doing a minor upgrade, it's generally unnecessary.

People are advised to do it because, from a support standpoint, it helps rule out a lot of possibilities. I can't speak for dd-wrt, but in my experience with Tomato and TomatoUSB, the meanings of nvram values are generally quite stable, the default values rarely change, and the behaviour if an nvram variable doesn't exist is to act as if its default value is set; all of which, combined, mean that clearing NVRAM is usually not needed.

Using the backup/restore config file options, as a way of making it easier to clear NVRAM, is pretty silly. In most cases, restoring the config file basically defeats the purpose of clearing NVRAM; you might as well have not done it at all.

So, if things aren't working right, or behaving weirdly, by all means, clear NVRAM and manually reconfigure to see if that fixes it. But, outside of exceptional cases where it's specifically noted, don't feel obligated to go through this for every little minor version upgrade.