The Macrotone Consulting IP Mapping component was created out of a desire to display IP addresses (and their source) on a graphical map to enable easier interpretation of hacking and spamming sources, but extended to a more generic IP mapping usage.
There being nothing suitable already existing it takes the idea from a few modules originally published by www.comlantis.com (now non existing) written by Serdar Gokkus and builds upon that with a full administrative component and integration with the output from Akeeba Admin Tools Web Application Firewall Log. It retains the visitor tracking (which was its original purpose) as written for Joomla 1.5 updated for Joomla 2.5 usage. Later version run upon Joomla 3.3 and above and support HTML5 geolocation determination.
This release which is for Joomla 3.3 and above only, modifies the handling of the mapper module as regards clustering and also adds an option to control a complete map refresh. See documentation for more details.
This release which is for Joomla 3.3 and above only, adds the ability to optionally use HTML5 geolocation determination for visitor data. There are also a number of improvements in the display options and a number of minor fixes applied.
This release adds additional DEBUG options to the back end. It also adds some additional checks for the use of CURL if Fopen is not permitted in the site PHP configuration. Additional checks have been added to permit more control over the fields displayed in the back end list, and it also introduces a separate table to enable finer control over robots that may be encountered. Formally this was a supplied list, but now the site administrator has the ability to specify additional robots to be excluded, if/when they become active. There are also a few minor corrections to resolve problems found with the earlier release.
This minor release corrects a few problems found with the earlier release and specifically a problem discovered if the IE browser is used in the back end of the site. It also addressed a potential problem if a Bootstrap template is being used and the mapper module is displayed within tabs.
This minor release corrects a few problems found with the earlier release and refines the synchronisation task so that it is slightly faster.
This release adds support for cron tasks, invoked either from a PHP CLI binary or from a front end URL link. The code has undergone some 'refactoring' and a few minor bugs have been corrected.
This release adds support for both Joomla 3.x and Joomla 2.5 in one installation. The release also changes the component to use JInput rather than JRequest which is deprecated.
This minor release adds a new option to display the last 'n' days worth of data in a map, where n is the number of days worth of data to display. It also corrects a situation where the Akeeba Sync icon was displayed even if Akeeba Admin Tools Pro was not installed upon the site.
This minor release corrects an apparently benign SQL error seen in the visitors agent module. It also introduces two new features. The first is integration with Akeeba Backup System Restore Points, and the second is the option to display a tabular grid containing the location data below the displayed map.
This minor release correct a sorting problem in the locations list view, and adds two minor enhancements. The first to mark private IP addresses as 'unknown' and the second to enable compaction of the location table resetting the unique id numbers of the entries. This latter enhancement will be useful for active sites where the id number is reaching the maximum for the table.
Minor release to improve performance by carrying out multiple updates when a new IP address is determined., and address a minor potential security concern.
Minor release to add styling to the administrators location display, and add additional index.html files for security.
The is the initial release of the component.
IP Mapping Overview
The full documentation is shown as web pages upon the site, and is also available as a PDF file, and this document only presents a brief overview of the functionality.
The component consists of an administrative back end and a couple of modules. The administrative back end comprises of the control of the main tables, which are used to hold the details of the IP addresses to be mapped and also the reasons why that are included. The back end component will automatically populate the geographical locations of the IP addresses when they are entered and all that is required is to configure an API key to enable the IPInfoDB to be accessed.
IP addresses can be entered manually, or by importing the IP addresses from a third party component (Akeeba Admin Tools Pro) or via the Visitor Agent module. The Visitor Agent modules need to be configured and placed in a location on your web site. Its placement should be upon every page where visitors are to be tracked. Typically this is in the footer (or header) of the web pages. The agent module will automatically store the geographical locations in the database. It also has the ability to prune the 'visitor' table entries when they exceed a certain age (or number).
The real work of the component is undertaken by the 'Mapping module' which reads the IP addresses from the database and displays them upon the web site. Multiple copies of the the mapper module are possible and configuration is made as to the 'reason' the IP address that are to be mapped. This is a 'multiple' selection of multiple reason types that are to be recorded on the same map if desired.
We trust this brief overview is sufficient to cover the main features of the components and you are requested to look at the full PDF documentation for more information.
If you find this component useful, you are requested to raise a review on the Joomla Extensions Directory, and possibly consider making a donation to assist in providing support and future enhancements.
Google™ is a trademark of Google Inc.
Google Maps™ is a trademark of Google Inc.
We would like to thank all the people who have donated their time and effort in providing translations for our extensions, either individually or as part of a translation team, so that they may be used by the wider community.
Requested features being considered for future releases.
|Requested Change||Possible Version for implementation|