When RF was turned off there was no longer a wlan_ip to go off to build the links.
There is actually still a psuedo IP, the mapping script just wasn't looking for it.
Now it will find this IP if it detects "meshrf = off" in the json file.

coded checks for different versions fo the json file.
also included new Mikrotik hap Lite devices.

Removed an errant "echo" that would cause output in "silent" mode.

When the polling script parsed through the interfaces looking for the
wlan MAC address and ip (and the LAN ip) it always had issues with the
different versions of the json file on different firmwares.
I think this has finally been solved.
The polling script should pull the proper info from even a 3.15.1.0 node
now and if those nodes have location info they should now appear on the
map too.
The admins of those devices should be strongly reminded to update!!

I mistakenly removed the red and green dot from the status area of the
admin page. They are restored now.

Parallel node polling will work now, but it is not recommended on large
networks, as there is still no control over how many scripts are
spawned. Small networks of should be just fine.
(this has been tested many times on a network of 20-30 (sometimes 100's)
with no issues)
Use at your own risk though.

New warnings in "Test Mode" to alert when a nodes location has been
"fixed" or not. It's very noticable now.

Some general clean up/typo fixing and removal of things that were long
due for removal.

fixed some file attributes.

Added some things to be used in the near future but are not done yet.

73

Can change the non mesh markers info without having to recreate now.

The polling script can now find the info for some nodes that it could
not before, such as firmware 3.15.1.0b4, this was a pleasant side effect
of trying to remove some of the bunk entries i nthe database.

The polling script will now also try to check and "fix" the database,
this is due to changes in the newer AREDN firmwares (anything beyond
3.17RC1)
Some of those changes were made by me, just for the map. :)
These DB "fixes" also include removing some columns that were no longer
and were making the DB much larger than it needs to be, this will also
help cut down on the memory footprint when loading the webpage.

The numbers at the bottom of the map reflecting nodes and link, should
be more accurate now (I hope).

The Map legend has been change to use pure HTML5/CSS, the only images
are the small circle icons, this may cause issues with very old
browsers...

Removed some files that were no longer needed or forgetten about.

Finally finished a rough version of some admin pages that allow for
maintenance of the DB, fixing node locations, removing nodes, etc...
Username/Password is required to use the admin pages.
You must create an intial user/password.
When you first load the admin page it will ask you to create an initial
user.
This initial user is a "super user" and will be able to create other
users.
(more info is on the admin pages themselves)

Fixed a stupid mistake in export2csv.php.

Rearranged the columns in the node_info datebase which make the data
more readable when exported as CSV file.

Removed old DB columns that were now unused.

Changed the *.css-default file(s) to *-default.css so that IE will use
them without complaints.

More than a few other little changes here and there...

browser.

(also testing README.html generation)

There is now a new file: "custom.inc" that can allow the user to make
site specific overrides, keep sql passwords out of the main ini file,
etc...
This is completely optional and not required. The file may even be
safely deleted if wanted.

Also some typo fixing in the README file.

Removed user-edited files so they do not get overwritten when updating
the scripts.
The user-edited files are now contained in the user-file.tar.gz archive.
Once decompressed they will not be effected by future "git pull"
operations.

Made changes to how the scripts find the included files, the whole thing
can now just live in one directory, allowing for easier future updates.

Added http-meshmap.conf file to plug in to apache configs. This allows
the <WEBROOT>/meshmap directory to live virtually anywhere on the
filesystem.

Updated README file to reflect these new instructions.