Icon and map assets are now bundled with the plugin instead of being loaded from a CDN. No action required.<\/p>","3.4.1":"
This release adds a proper uninstall routine. If you delete the plugin, all tracking data will now be removed automatically unless you opt out via the ULLT_KEEP_DATA_ON_UNINSTALL constant.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3694662,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3694662,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3694662,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"Banner-1544x500.png":{"filename":"Banner-1544x500.png","revision":3694759,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"Banner-772x250.png":{"filename":"Banner-772x250.png","revision":3694759,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Admin dashboard with login stats and \"currently active users\" widget.","2":"Session history table with search, filters, and CSV export.","3":"Login map showing recent logins by approximate location.","4":"Plugin settings screen (idle timeout, geolocation, tracking options).","5":"Last login\/first login\/login count columns on the Users list screen."}},"plugin_section":[262246],"plugin_tags":[60860,602,600,257747,9257],"plugin_category":[38,54],"plugin_contributors":[280597],"plugin_business_model":[],"class_list":["post-363861","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-last-login","plugin_tags-login","plugin_tags-security","plugin_tags-session-tracking","plugin_tags-user-activity","plugin_category-authentication","plugin_category-security-and-spam-protection","plugin_contributors-arjitsri","plugin_committers-arjitsri"],"banners":{"banner":"https:\/\/ps.w.org\/ars-vigilo-sessions\/assets\/Banner-772x250.png?rev=3694759","banner_2x":"https:\/\/ps.w.org\/ars-vigilo-sessions\/assets\/Banner-1544x500.png?rev=3694759","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/ars-vigilo-sessions\/assets\/icon.svg?rev=3694662","icon":"https:\/\/ps.w.org\/ars-vigilo-sessions\/assets\/icon.svg?rev=3694662","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"\n
ARS Vigilo Sessions records every user login and logout on your site and surfaces that information in an easy-to-read admin dashboard. Features include:<\/p>\n\n
This plugin stores IP addresses, browser\/OS strings, and (if geolocation is enabled) approximate location data tied to user accounts, in order to provide its tracking features. Site owners should disclose this in their privacy policy. All of this data is permanently removed when the plugin is deleted (see \"Data removal\" below), unless you opt out.<\/p>\n\n
IP geolocation is off by default. If you turn it on in ARS Vigilo Sessions > Settings<\/strong>, the plugin sends a visitor's login IP address to one of the following external services in order to look up an approximate location:<\/p>\n\n No other data (page views, form submissions, content, etc.) is ever sent off-site, and no lookup occurs unless geolocation is explicitly enabled.<\/p>\n\n This plugin bundles the following third-party libraries:<\/p>\n\n No. Deactivating only stops tracking and clears the scheduled cleanup cron event. Your session history, settings, and user meta remain intact so you can safely re-activate later without losing data.<\/p><\/dd>\n Yes, by default. When you delete the plugin from the Plugins screen, it automatically removes:<\/p>\n\n If you want to keep this data even after deleting the plugin (for example, to re-install later), add this line to your Session\/activity tracking only runs for logged-in users. Geolocation lookups are cached per user so they don't run on every request, and old session rows are pruned automatically based on your configured retention period.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
Credits<\/h3>\n\n
\n
assets\/vendor\/fontawesome\/LICENSE.txt<\/code>.<\/li>\nassets\/vendor\/leaflet\/LICENSE.txt<\/code>.<\/li>\n<\/ul>\n\n\n\n
ars-vigilo-sessions<\/code> folder to the \/wp-content\/plugins\/<\/code> directory, or install the zip file directly through the Plugins screen in WordPress.<\/li>\n\n
Does deactivating the plugin delete my data?<\/h3><\/dt>\n
Does deleting the plugin delete my data?<\/h3><\/dt>\n
\n
wp-config.php<\/code> before deleting:<\/p>\n\ndefine( 'ULLT_KEEP_DATA_ON_UNINSTALL', true );\n<\/code><\/pre><\/dd>\nDoes this plugin slow down my site?<\/h3><\/dt>\n
1.1.0<\/h4>\n\n
\n
ars-vigilo-sessions<\/code>). Updated the plugin header, text domain, translation template, and all user-facing admin menu\/page titles accordingly. Internal option names, database table, and function\/hook prefixes (ullt_<\/code>) are unchanged, so no data migration is needed.<\/li>\n<\/ul>\n\n3.5.0<\/h4>\n\n
\n
login-pulse<\/code>) to resolve a name-similarity concern raised during the WordPress.org plugin review. Updated the plugin header, text domain, translation template, and all user-facing admin menu\/page titles accordingly. Internal option names, database table, and function\/hook prefixes (ullt_<\/code>) are unchanged, so no data migration is needed.<\/li>\n<\/ul>\n\n3.4.7<\/h4>\n\n
\n
translators:<\/code> comments in the suspicious-login email builder \u2014 they must sit on the line immediately above the __()<\/code> call itself, not merely above the enclosing sprintf()<\/code>.<\/li>\n<\/ul>\n\n3.4.6<\/h4>\n\n
\n
date()<\/code> calls that build stored\/displayed timestamps with gmdate()<\/code> to avoid runtime-timezone-dependent output.<\/li>\ntranslators:<\/code> comments and switched to numbered placeholders on all remaining translatable strings that use sprintf()<\/code>\/printf()<\/code>.<\/li>\nfopen()<\/code>\/fclose()<\/code> on php:\/\/output<\/code> in the CSV export (a PHP output stream, not a filesystem path, so WP_Filesystem<\/code> doesn't apply).<\/li>\nuninstall.php<\/code> so its cleanup logic runs inside a function, scoping its working variables locally instead of leaving them as unprefixed globals; deduplicated the single-site\/multisite cleanup into one function.<\/li>\n$where<\/code> clause (its placeholder\/argument counts can't be evaluated statically, but are correct at runtime).<\/li>\n<\/ul>\n\n3.4.5<\/h4>\n\n
\n
<style><\/code> block to wp_add_inline_style()<\/code>.<\/li>\nHTTP_USER_AGENT<\/code> header before storing or parsing it, and consistently ran wp_unslash()<\/code> before sanitize_text_field()<\/code> on all $_GET<\/code>\/$_POST<\/code>\/$_REQUEST<\/code> reads.<\/li>\n$_POST<\/code> before passing it to wp_verify_nonce()<\/code>.<\/li>\nload_plugin_textdomain()<\/code> call (WordPress.org has auto-loaded translations for hosted plugins since WP 4.6).<\/li>\n<\/ul>\n\n3.4.4<\/h4>\n\n
\n
_e()<\/code> call now uses esc_html_e()<\/code>\/esc_attr_e()<\/code>, and remaining raw output (URLs, translated strings with embedded markup, numeric values) is now properly escaped with esc_url()<\/code>, esc_html()<\/code>, wp_kses_post()<\/code>, or absint()<\/code>.<\/li>\n$wpdb->prepare()<\/code> unconditionally, removing the conditionally-prepared query that Plugin Check flagged as an unescaped database parameter.<\/li>\ntranslators:<\/code> comments and switched to numbered (%1$s<\/code>, %2$d<\/code>, ...) placeholders for all translatable strings with more than one placeholder.<\/li>\n3.4.3<\/h4>\n\n
\n
3.4.1<\/h4>\n\n
\n