Reason for asking: I want to clean up the list and remove everything that does not require a dataentry, in order to make this a valuable list for identifying missing dataentries.
@tmomas This is brilliant! What a good way to test the import process.
I looked at the dataentry's for routers that I know about, and note the following. Except for the trailing "" (see below), I see no reason to change anything in the import process.
WNDR3700v2:
Links to firmware (factory & sysupgrade) on the dataentry page seem OK.
OEM Firmware link points to .de page
WNDR3800:
OEM Firmware link points to .de page
Links to the four variations of firmware look OK. (WNDR3800, WNDR3800ch) and (factory, sysupgrade) each on their own dataentry pages.
Dataentry page for WNDR3800_CH doesn't have links to OEM page or wikidevi page.
Archer C7v2:
There are a zillion (well, 6) images because of TP-Link's (stupid) FCC change to "prevent" upgrades.
il...factory
il...sysupgrade
factory-eu
factory-us
factory-(no country) <- has link from dataentry page
sysupgrade <- has link from dataentry page
We will probably have to add a Comment to the dataentry (manually) that describes how to find the right factory image. Or say "Check the Device Page" in the comment
How about "See devicepage for other international firmware versions."?
BTW: The import is finished. ToH is live now.
I'm currently checking available fwfiles, add them to dataentries or create new dataentries.
Sadly, oftentimes there's not much hardware information available -> Still work to be done later, to fill in the missing information.
Or 'See Device Page for regional (US, EU, International) versions."?
Congratulations!
Yeah, that'll always be a problem. I'm pretty sure dataentry and device pages get filled in for routers that are actually well-supported. The others will just languish (and hopefully) be easy to distinguish from the more popular ones.
