Download WassUp Version 1.7.2.1

The changelog:

- commented out the code for automatic page reload with ‘wscr’ GET parameter because it inflated the number of page views per visitor in Wassup’s logs. Also commented out other code related to ‘wscr’ GET parmeter in “wassup.php”.
- modified duplicate check in “wassupappend()” to remove the ‘wscr’ argument from the url being tested.
- changed “screen_res” variable assignment in “wassup_meta_info()”, “wassupappend()” and “wassupPrepend()” to include $_ENV['HTTP_UA_PIXELS'], a http header global sometimes sent by IE and IE Mobile browsers.
- changed the mysql query for main/detail chronology sublists in “wassup()” to include an “order by ‘timestamp’” clause instead of “by ‘id’” because delayed inserts can cause ‘id’ to be NOT sequential with ‘timestamp’. Also added ‘distinct’ to the select statement to exclude duplicates from list.
- in “main.php”, removed ‘attribute_escape’ from ‘stringshortener’ $input string because it put garbage characters (ex: �) in the resulting shortened urls. ‘stringshortener’ now outputs ‘$outstring’ or ‘false’ only.
- fixed czech language files

There are a lot of changes and some new languages added (thank guys! we have reached 25 language translations almost complete, you rock!).

Download WassUp Version 1.7.2

ChangeLog 1.7.2:

=============================

New features and improvements:

=============================

1) Updated Visitor Detail (Latest Hits) screen interface options:

-Extended the automatic timer and ticker to include a pause/restart

toggle option that is triggered when the mouse is clicked on the

countdown numbers.

-Modified the searchbox to restrict initial search parameters to the

current date range, not reset it to the last 24 hours.

2) Optimized how WassUp plugin functions are loaded into WordPress:

-Added a new function, “wassup_loader()”, to conditionally load WassUp

functions into WordPress so that only needed hooks are added. This

also fixes a sporadic activation error bug that appeared in some

WordPress 2.8+ configurations.

-Removed the standalone hooks for “wassupAppend” and “wassup_init”

and put them inside the “wassupPrepend()” function so that these

functions are “hooked” into WordPress only after “wassupPrepend”

determines that they are needed. This also makes it possible to pass

command-line arguments like “$cookie_value” and “$screen_res” to

these functions.

3) Modified WassUp variables and functions for consistency and to avoid

potential conflicts with other plugins:

-Renamed global “$version” variable to “$wassupversion” to avoid

potential name conflicts.

-Renamed “$siteurl” variable to “$blogurl” to avoid mixups between

WordPress admin url and the blog url because the term, “siteurl”,

is commonly used (incorrectly, IMHO) to refer to the url address of

wordpress admin files. I also made “$blogurl” a global variable.

-Renamed “createTable()” and “updateTable()” functions to

“wCreateTable()” and “wUpdateTable()” to avoid potential name

conflicts with other plugins.

4) Updated how WassUp creates and updates it’s tables after activation:

-Changed “wCreateTable()” to insert an initial “welcome to Wassup”

record in the new table when it creates it.

-Consolidated tests for default charset inclusion in the table

create/update statement into a single test command.

-Added DB_CHARSET existence to the test for charset inclusion.

-Removed the index (username,ip) from the create/update statement

because this caused a language display problem for non-romanic

languages in some WordPress configurations.

?(where table charset !== database charset)?

-Modified “wUpdateTable()” function to call “wCreateTable()” (and

‘dbDelta’ function) when updating table structure. This ensures that

the upgraded WassUp table will always have the same structure as new

installs. Previous statements that changed individual fields and

indices have been removed or commented out of “wUpdateTable()”.

5) Improved search engine lookups in “wGetSE()” and “seReferer()”:

-Added Bing to list of search engines in “wGetSE()”.

-Fixed redundant lookup of search engine data in “seReferer()” when

the data was already found in “wGetSE()”.

-Added a “break” command to terminate search engine comparison loop

instead of using “return”. This allows a page number lookup to be

done prior to function exit (return).

-Added a test to omit internal referrers from search engine lookups.

6) Changed “wassupAppend()” duplicate test to include userAgent in the

test so that page requests from a browser add-ons such as a feedreader

is not counted as a duplicate of an online page request.

7) Updated visitor screen resolution cookie and query parameter, ‘wscr’,

and added a javascript timer and function to automatically reload the

current page when a visitor has been online for 40 seconds so that

both cookie and ‘wscr’ can be seen and recorded by

“wassUpAppend()/wassupPrepend()”.

8) Updated “WassUp Options: Manage Files&Database” form and data:

-Added more WordPress/PHP/MySQL configuration settings to the list.

-Modified configuration settings in html to be an “unordered”

list (<ul><li>) instead of a series of paragraphs (<p>).

9) Added two new Wassup settings to WordPress options:

-”wassup_engine” is Wassup’s MySQL table engine type and is used to

avoid engine-related syntax errors in MySQL (ie. insert delayed).

-”wassup_table” contains the name of wassup’s table and is used to

set the variables “$table_name” and “$table_tmp_name”.

10) Added more security and sanitizing of table and forms to protect

against sql and script injection attacks:

-Wrote a new function, “wCleanURL()” in ‘main.php’ to replace

“clean_url” calls and sanitize URLS with either “clean_url()” or

“esc_url()” (WP 2.8+), depending on WordPress version.

-Added more checks to block script injections attempts disguised as

wassup query/form parameters.

11) Modified how WassUp data backup/export handles errors and sends data:

-Saved “backup_table()” errors messages in options variable

$wassup_options->wassup_alert_msg and displayed them after

“export_wassup()” terminates instead of echoing them to the screen

in middle of export.

-Replaced ‘print $sql;’ statement in “backup_table()” with a

‘return $sql;’ statement so that output is handled by the calling

function, “export_wassup()”, instead.

12) Internationalized Wassup 2.7+ dashboard widget function.

13) Improved “wGetStats()” statistics in ‘main.php’:

-Added “urlrequested” to the type of statistics output.

-Made stats results case insensitive in MySQL queries.

14) Improved “top 10″ stats output and tightened security in ‘action.php’:

-Replaced the inflexible ‘limit 10′ condition in ‘top ten’ stats with

a limit variable “$stat_limit”. Currently $stat_limit=10 but this may

be changeable by users in upcoming revisions.

-Replaced separate “urlrequested” stats query with a call to

“wGetStats()” function.

-[404] urls are no longer shown as links.

-If top 10 results count is less than 10, blank <li> statements are

padded to the output for styling consistency.

-Added a test for ‘wp-config.php’ in WordPress’ parent directory

when it is not found in the install directory (re Wassup forum post).

15) Renamed the “cache_check()” function to “wassup_foot()” to avoid

name conflicts with other plugins. Also place footer content inside a

single paragraph surrounded by html comment tags ‘<!–’ and ‘–>’ to

fix a css/float bug that showed up in some theme templates.

16) Updated “uadetector” class in ‘uadetector.class.php’ module to detect

more browsers, spiders and mobile user agents, operating systems, and

screen resolution.

17) Added more comments to code including new PHPDocumenter-style comments

ex: (/**, @package, @subpackage)

-Added a disclaimer in plugin comment and in “readme.txt” file.

-Added a requirement of WordPress 2.2 or higher in plugin description.

-Added a note about incompatibility with “Super-cache” plugin in

“readme.txt” usage section.

18) Wrote a new function, ‘microtime_float()’, to output microtime as a

float value, similar to PHP 5′s microtime(true). This is used in

WassUp timer and in the PHP profiler module (see below).

19) In Wassup development copy (unreleased), added a PHP profiler module,

‘profiler.php’ to /lib directory and included the profiler in Wassup

code when in debug mode.  This PHP profiler identifies potential code

bottlenecks that slows down WassUp.

========================

Bugs and security fixes:

========================

1) Fixed a bug in ‘main.php’ “wGetStats()” function that caused an error

whenever there are no stats to print.

2) Fixed a bug in “wassupAppend()” that caused all spam check (referrer,

previous spam) to be disabled whenever Akismet spam check was

disabled.

3) Fixed a bug in “wGetSE()” where the locale “SK” was incorrectly

appended to a search engine whenever the search domain was not in the

array of “known” search engines.

4) In “wGetLocale()” function, renamed language codes: Ko to Kr,

Da to Dk, Ur to In, and both He and Iw to Il so that they match

country codes that have an associated flag image. (Closes ticket #85)

5) Removed the index “(username,ip)” from WassUp’s table structure to fix

a language display problem in some non-romanic languages.

6) Fixed bug in Visitor detail/latest hits that caused [expand all]

and [collapse chronology] button options not to be printed when

“items-per-page” was set to an amount different from 10 or 20. (Closes

ticket #97)

7) Fixed WassUp script execution vulnerability by escaping code lines

that included “html_entity_decode” and “urldecode”. Used

“attribute_escape” as the escape function.

8) Fixed a bug in “wassup_foot()” function (formerly “cache_check”) that

caused the wassup footer line to be split up by span/div floats in

some theme templates.

9) Replaced “eregi” and “eregi_replace” functions with “stristr”,

“str_replace” or “preg_replace” because all PHP POSIX regex functions

are deprecated since PHP 5.3 and deleted since PHP 6.

For details, see http://www.php.net/manual/en/function.ereg.php

Download WassUp Version 1.7.1

The main changes are:

• RSS invalid fixed
• “string(y) “post-xxx”" error fixed
• “Illegal request permission denied” error fixed
• some little changes to fix small problems
• added a new dashboard style and data, now you can watch some “current users online” details on the dashboard.

we apologize but the new WassUp version 1.7 has a lot of bugs and issues, we are sorry but this new version has a lot of new code (as you can see on the release changelog), so we received a lot of requests and we are just fixing every bugs.

The development SVN has the new fixes yet, so if you are impatient you could take the new 1.7.1 version from this SVN:

svn co svn://svn.wpwp.org/var/svn/wassup/trunk wassup

Thanks to Alex from Automattic, we discovered a bug on the Akismet spam function, we apologize but due to this bug some of your Akismet stats could be invalid, that’s not a huge problem but you have been warned. Now we fixed it.

Some of the bugs discovered in version 1.7 could be examined from the latest forum posts, thank you all to report them.

Version 1.7.1 is coming in few hours, if you discover bugs please write us.

Download WassUp Version 1.7

Here is the main changelog for this version 1.7:

Changelog Summary:
21 feature improvements
15 bug fixes

=============================
New features and improvements:
=============================

1) Modified Wassup to include the following design/interface changes

• -Added a top horizontal menu in the contextual menu area of WordPress 2.7+ for each page of WassUp. This improves page navigation because in WordPress 2.7 submenus are located at the bottom of the page and may be off-screen.
• -Added the word “WassUp” to the page heading on each submenu page and included the standard plugin icon in the heading for WordPress 2.7+.
• -Added a mouse-over effect using jQuery that causes the “delete” and “table” icons to be swapped with a slightly larger image.
• -Added a background color to the jQuery delete effect so the colorchanges just before the div disappears.

2) To make WassUp run in WordPress 2.6+ secure configurations that have “/wp-content/” in a directory different from WordPress itself, added a new constant, WASSUPURL, to point to WassUp’s plugin page url. Also added GET parameter, “wpabspath=ABSPATH” for “action.php” so it will also run. “wpabspath” is mime64 encoded to mask ABSPATH value before being passed on the URL.

3) Added more security and sanitizing of table data to protect against sql injection attacks:

• -Wrote a new function, “wSanitizeData”, to clean the wassup record of potentially harmful code prior to insert into mySQL.
• -Used “clean_url” WordPress function to sanitize referrer urls. This replaces the previous “htmlentities/urlencode” functions.
• -Cleaned the output of “Stringshortener()” and “AddSiteURL()” functions, inside these functions, before the output is sent. Removed sanitizing done after output, as it is no longer needed.
• -Wrote code to block hackers from using WassUp to hack WordPress by checking page requests for certain words found in malicious code and denying access when found.
• -Added a security test for logged-in user in “action.php” that aborts the program if no login is detected. This was needed because AJAX requests bypass normal WordPress login checks.

4) Updated MySQL code in “MainItems” class to improve performance and security:

• -Changed MySQL “select” statement to “SELECT SQL_BUFFER_RESULT” to reduce incidents of timeouts and memory errors on large data sets. Available for ISAM and MyISAM engines only, ignored by other engines.
• -Increased MySQL “wait_timeout” to 120 seconds.
• -Used ‘sprintf’ PHP function to build MySQL query strings in a cleaner and safer manner (similar to wpdb::prepare in WP2.3.3+).
• -Wrote a new method “MainItem::buildSearch” to generate the search portion of MySQL queries and protect against SQL injection in user-input.
• -Changed “mainItems” class constructor to accept up to 5 arguments, 3 required (table_name,to_date,from_date) and 2 optional (whereis, limit) that are used to set class variables. This replaces the requirement to set object variables separately and outside the object definition and reduces the chances of coding bugs.
• -Modified “mainItem::theChart” method to return chart URL only (no html code) for more flexibility in chart display.  Removed “$chart_pos” argument as it is no longer needed.
• -Changed the code to generate charts from “if-elseif” to “switch-case” so more charts can be generated for more date ranges.

5) Added three new settings in WassupOptions:

• -”wassup_admin” for separate recording of logged-in administrators.
• -”wassup_exclude_user” to exclude recording by username.
• -”wassup_version” for use in updating Wassup tables on activation.

6) In Wassup Options page, made the following changes:

• -Added input fields for Administrator recording and username exclusion in “Statistics Recording” section.
• -Disabled “wassup_geoip_map” input field when ‘curl_init’ does not exist.
• -Internationalized messages about Curl errors.
• -Expanded the list of MySQL server and PHP settings in “Manage Database” section.
• -Moved page heading out of “settings.php” into “wassup.php” to keep page headings in one location for easier editing.

7) Added new key, “wassup_time_range”, in WassupOptions::getKeyOptions (formerly “getItemOptions”) method as the name for time range filters.
It is used to display a list of time range options for the select form on WassUp’s main/detail page.

8) Modified WassUp main/detail page to include the following:

• -Increased the number of time range filter choices to include “6 hours”, “3 months”, “6 months”, and “all time”.
• -Extended search filter to include “username” and “comment author” in the search range (in mainItems::buildSearch).
• -Moved chart code to the bottom of page and wrote a jQuery script to insert the chart at the top of page…to minimize browser timeouts due to slow up page load.
• -Administrators are listed as “Administrators” instead of “Logged-In User” to distinguish them from regular visitors.

9) Modified “createTable()” function to include the following:

• -Created a new index on “username”.
• -Changed  “CREATE TABLE” to “CREATE TABLE IF NOT EXISTS” so tables are created only if needed.
• -Changed “wp_wassup_tmp” table creation to use “CREATE TABLE LIKE” syntax instead of making a second call to “createTable()”. For MySQL 4.0 or less, the 2nd call to “createTable()” is still used.

10) Modified “updateTable()” function to include the following:

• -Included a test for “wassup_version” to limit updates to only those needed for the current WassUp upgrade
• -All of ‘wp_wassup’ indices except ‘id’ are dropped and rebuilt with every upgrade. This should improve WassUp performance because indices get inefficient and corrupt over time.

11) Modified “insert_into_wp()” function to include:

• -Changed number of parameters to 2, table name and table record (an associative array). This replaces the over 20 parameters previously required and simplifies the function.
• -Changed “INSERT” syntax to “INSERT DELAYED” to queue the insert request in the background when wassup table is locked or busy.
• -Used PHP’s “sprintf” to build the MySQL insert statement and used new sanitizing function, “wSanitizeData()”, to clean up data. This is like “wpdb::prepare” for pre 2.3.3 versions of WordPress.

12) Changed “wassupAppend()/wassupaPrepend()” code to include:

• -Added IP and Hostname to wassup cookie contents to reuse hostname for multi-page visits from the same IP and avoid multiple ‘gethostbyaddr’ lookups on one IP.
• -Added “user-agent”, “browser”, “spider”, and “os” fields to the query for “duplicate check”. If results show same visitor within 3 minutes (but not duplicate) these values are reused, avoiding additional tests.
• -Added new exclusion controls by “username” and for administrators.
• -Moved search engine detection and language detection to after all exclusion control are done to avoid unnecessary tests on excluded records.
• -For detected hack attempts, URLrequested field is prepended with “[404]” to distinguish it from valid page requests. WassUp detail reports do not create a link for these requests as the link would not exist.
• -Used PHP’s “ignore_user_abort(1)” to prevent premature aborts and window close from affecting recording. “wassupAppend” finishes recording in the background whenever a user interruption occurs.
• -Increased script execution time to 0.5 hour when wassup table is optimized as this can be slow on large tables.
• -Changed automatic purge of “wp_wassup_tmp” table to be less frequent (3 minutes interval) to avoid slowdowns due to table locks or busy server.

13) Finished javascript/cookie to record user resolution, but moved the code from “wassupAppend()” to “wassup_meta_info()” where it is now part of the document <head> and can retrieve the javascript screen variables to save in a cookie. Since cookies are not readable until a new page load, it is only on a 2nd pageview that screen resolution is recorded. To get around this shortcoming, the screen_res cookie has a longer lifespan (48 hours) and, for multi-page visits, the first screen-resolution is retroactively updated in wassupAppend()”.

14) Wrote a new class, “uadetector”, that compares user-agent to the 10 most popular user-agents, then builds on the “detector” class to identify more obscure user-agents. It can detect IE8, Win7, Win2008, Windows 64-bit os versions, and mobile devices.

15) Wrote a new function, “wMajorVersion()”, to return the major number from a version string. This function is used to make sure that browser information stored in wassup table is limited to browser name and major version number only. Common browsers will now be counted more accurately in WassUp statistics.

16) Wrote a new function, “validIP()”, to identify and return a valid IP address from a list of IPs. This is used find a visitor’s IP when IP forwarding or a proxy server is used.

17) Updated “wGetSpider()” function to include the following:

• -Added tests to identify MSN and Yahoo robots by their hostname or IP as these crawlers don’t always use a unique user-agent string to distinguish themselves from regular visitors.
• -Added a “break” to exit foreach loop immediately after user agent match is found.
• -Added tests for obvious script injection bots.
• -Added a new return parameter, crawlertype, to distinguish Robots, feed readers, link checkers, etc. For script injection bots crawlertype=”H” is returned which then causes spam=”3″ (hack attempt) to be set in wassup record.
• -Removed wildcards and version#’s from spider array because wildcards are not matched and version number can change.
• -Added new agents and removed obsolete agents from spider array.

18) Wrote a new function, “wGetStats()” to compile and output statistics in an ordered array for “top ten” and widget stats.  Currently this is only implemented for “top ten” referrers.

19) Modified “spyview()” function to add an optional 5th parameter, “spy_datasource”. This parameter is the name of the wassup table used as the source of spy data. The default is “wp_wassup_tmp”. However, when “spy” page is first opened, “wp_wassup” is used to populate the screen and chart with 10 initial data points.

20) Wrote a new function, “backup_wassup()” to output wassup SQL data to a file. Intended as an alternative to “export_wassup” which times out
on large tables. Currently not implemented.

21) Added a Debug mode to print out some useful information about the page you are surfing (blog and admin pages). “$debug_mode” is assigned only once in the beginning of “wassup.php”, then declared global in all functions where it is used in “wassup.php”, “main.php”, and “uadetector.php”. In “action.php” it is passed as a GET parameter. you have to manually activate it by set it to TRUE in wassup.php ($debug_mode=true;)

=============================
Bug fixes and code cleanup:
=============================

1) Fixed the problem with WassUp widget that caused the widget options to be inaccessible after being set once. Also changed widget so that
there is no data displayed when WassUp is inactive (not recording).

2) Updated main/detail page and “action.php” to send a keep-alive “heartbeat” output to the browser (<!–heartbeat–>) and increased PHP script timeout length to help prevent browser timeouts when MySQL is slow  to respond.

3) Removed redundant sanitizing functions such as “htmlentities(attribute_escape())” and “urlencode(attribute_escape())” on $_POST, $_GET, or database variables and replaced them with either a single “attribute_escape()” function or a test for a valid numeric value.

4) Removed the redundant “attribute_escape” from the prepare statement in “insert_into_db()” function because “prepare()” does it’s own sanitizing of data.

5) In “createTables()” function, removed the test for $wpdb->supports_collation() because that method is only available in wordpress 2.5+ and does the same thing as the existing version check for mySQL 4.1 (redundant).

6) Commented out “wp_cache_flush() because it clears the database cache and could cause WordPress to run sluggishly on slow servers.

7) Replaced “wp_get_current_user” with “get_currentuserinfo()” which sets the $current_user global in “WassupAppend/WassupPrepend” functions. Plugins can override “wp_set_current_user” and this could affect logged-in user detection. It is unknown whether this change fixes the reported problem with WassUp not tracking logged-in users when a login management plugin is installed.

8) Removed “is_admin()” test before calling “wassupPrepend()” because it caused all “hack attempts” to be omitted from recordings.

9) Created variables “$URLQuery” and “$stickyfilters” to replace $_SERVER['QUERY_STRING'] in link creation for user selectable filters on Wassup Detail page…to prevent parameters from being reset whenever a new filter is selected.

10) In WassupOptions class, changed user role names to match WordPress user role/level numbers (fixes bug reported in wpwp forums). Role names are now standard WordPress names (no pluralization) and is translatable by WordPress itself, not just Wassup.

11) Set “wassup_active” option to inactive in “wassup_uninstall()” and for “Options ==>Uninstall” to stop recordings before “wp_wassup” table is deleted…to avoid any problems with Wassup’s delayed inserts and background operations (see new features above).

12) Fixed several problems with the “spyview()” function in “main.php”:

• -Replaced MySQL query with a simple select statement with no “group by” clause. “group by id” was unneeded because `id` is a unique field and any groups on it would have exactly one member.
• -Inserted missing quotation marks in $_SERVER[HTTP_USER_AGENT] on lines #660 and 779.
• -Added a test for ‘curl_init’ so “spy” will run even when a user don’t have ‘Curl’ on their server. Line #654.
• -Fixed a bug that caused the list of visitor records to occasionally display without any color-coding. Reset $unclass to “sum-box” after each “foreach” iteration and changed PHP code that sets the <div> class.
• -Reduced the frequency of “No Activity” messages” by increasing the modulo number to “99″ in line#763.
• -Added a test for existence of $data[1] on line #695 to prevent PHP warnings.
• -Removed a redundancy check on “username” in elseif statement on line#642.

13) In the “top ten” report, added the condition “spider=”” to “top browsers” and “top os” to prevent spiders from skewing statistics.

14) In “action.php”, replaced “$wassup_options” with “$wassup_settings” because “$wassup_options” is not defined in the “action.php” module.

15) In “wGetLocale()” function, added code to swap japanese language code “ja” to Japan country code “jp”, for consistency and flag display. Country code swaps (or a flag) is still needed for the languages: ko, he, ur, and da.

thank you all for your effort to translate WassUp in your preferred language, we got a lot of fans who helped us. Thank you very much!

This new version has very few changes in the core but a lot of changes in the language files, here is a little changelog:

- New dashboard item for Wodpress 2.7
- Few bugs fixed
- Language files completely changed

Download WassUp 1.6.5

Here is the list of WassUp translations and the current status as you can see it on the Launchpad official WassUp translations page.

WassUp finally got their language translations on the Launchpad site. Now we need your efforts to complete and correct the translations, so please, if you have a Launchpad account and you wanna help us, this is the Translation status for wassup

Actually WassUp supports the following languages:

• English
• Brazilian Portuguese
• French
• German
• Italian
• Japanese
• Norwegian Bokmal
• Polish
• Spanish
• Turkish

Thank you all very much!

here I am to annouce you I just release the WassUp 1.6.4 version, the development is still slow but I found the time to add a new language and fix some small things.

First of all thanks to Clauber Santos who translated WassUp in Brazilian Portuguese I hope you like it. Then I added every Bot/Spider/searchEngines listed in the wiki trac and finally I fixed some small bugs.

Please, as usual, write some feedback on the forum if you get in trouble with this new version or if you have some new idea.

Download WassUp 1.6.4

I don’t know if you checked the WassUp official site recently but I would like to tell you I added WassUp as Facebook Page (yes I’m a Facebook fan!) so if you like it you can find your preferred statistics plugin on Facebook too.

Again, I wish you a very happy new year!

this is a very fast post to let you know I just released the 1.6.3 version of WassUp.
This version hasn’t new features it only fixes some old bugs and add the spanish language (thanks to Hans Christian). Please let me know if the translation is good or not.

Unfortunately I have a lot of things to do so the time to work on WassUp is almost zero, I hope I will be available for it as soon as possible, in the meantime thank you everybody to help us with your comments on the forum.

Download WassUp 1.6.3

P.S.
I tried WassUp 1.6.3 on the new development version of WordPress (2.7) and it works very fine! So no worry to upgrade your WordPress platform version when 2.7 will be available, WassUp is just fully compatible with it.

This version fixes some bugs and add a new way to look at the Spy view. Now (if you have the PHP Curl installed) you can add a Google Map that displays the visitors location  by their IP.

This new feature is based upon the Hostip.info API (a GEO IP tracker) but unfortunately the data is quite old so you could get some locations wrong.

I would like to improve this new tool so this is only the start, but please suggest your ideas.

This is the changelog for 1.6.2 version:

• fixed typo in wassup.php (pregi_replace)
• added Google Map on Spy view (you have to activate it in the options)
• added selection by type of users in Spy view
• added two missing flags
• added some new spiders/bots
• fixed some minor bugs
• added French language

Download WassUp 1.6.2

As usual please refer to the WassUp Forums if you have problems and stay tuned for the next version.