UpiCRM - complete changelog = 3.15.6 = * Fixed (WordPress.org review, November 17): upicrm.php checked for exported / log files and called get_current_user_id() and get_user_meta() while the plugin file was being loaded, before WordPress loads its pluggable user functions. On a standard installation get_current_user_id() returns 0 at that point, so the per-user "Thanks, got it" / "Remind me later" settings were never read (the notice could not be hidden) and the notice was registered for every user who could open the dashboard; where the user functions are not guarded the call is fatal. The whole check is now the function upicrm_export_files_admin_notice() on the admin_notices hook: it shows the notice only to UpiCRM administrators (the only users allowed to dismiss it or delete the files), reads the user's own hide / remind-later state first, and only then looks at the export folder. Front-end requests no longer touch the export folder at all. * The export folder listing tolerates a missing or unreadable folder (glob() returning false). * Turning the Spam Filter on/off now also checks the UpiCRM administrator permission (it already checked the nonce). * Removed leftover debug markup (HTML comments) from the Users Center and the filtered Excel export. = 3.15.5 = * Security: old-format Lead Aggregation API keys are no longer accepted at all. The old default key was a sha1 of the two site host names, so anybody could calculate it; 3.15 kept accepting it while "Accept legacy API keys" was on. That setting, the Referer comparison and the code that calculated such keys were removed: a key is now only a secret stored on both sites, compared with hash_equals(). * New: automatic replacement of old keys. A site that still holds an old-format key makes a new random key and offers it to the address stored for the other site (rotate_key). The other site does not trust the request: it calls back the address it has stored for the first site and asks whether that site is waiting for exactly this key (confirm_rotation, only a SHA-256 travels). Only then both sites save the new key. Needs https addresses (filter 'upicrm_integration_rotation_allow_http' for private networks) and 3.15.5 on both sites; it runs in WP-Cron after the update, when an old key is refused, and from the "Replace the old keys now" button. Until then requests with an old key get a fixed "old format" answer, and the sending site sends those leads again after the key was replaced (50 per run). * UpiCRM > Lead Aggregation and a notice on UpiCRM's screens and the Plugins screen explain what to do; a connection whose address is not https has to get a new key by hand ("Generate" on one site, same key on the other). * Security: the UpiCRM permission field of the WordPress profile screen is shown to, and saved for, WordPress administrators only (manage_options + edit_user). Before, the save handler had no check, so any logged-in user could post upicrm_user_permission=2 with their own profile and become a UpiCRM administrator. * Security: UpiCRM access is given on purpose. A user without a stored permission now has no access (0) unless it is a WordPress administrator (manage_options = UpiCRM admin); before, every logged-in user without a stored permission counted as a "UpiCRM User", so on a site with open registration or a shop every subscriber / customer could open the leads. The "default role for new WordPress users" setting (Users Center) is "Not a UpiCRM User" on new installations. On update from an earlier version: administrators without a stored permission get 2; users without a stored permission who have leads assigned to them or a place in the Users Center tree get 1 (they keep working as before); and the default-role setting is changed from "UpiCRM User" to "Not a UpiCRM User" (change it back in Users Center if every new user should be a UpiCRM user). Permissions that are already stored for a user are not changed. * Security: a stored permission of 0 ("Not a UpiCRM User") was treated as 1; it now really means no access (menus, screens, AJAX, AI/MCP abilities). * Security: every admin action handler now calls upicrm_require_permission() next to its nonce check (Users Center, Data Types & Fields, e-mail notifications, lead routes, web services, import, export, GDPR, spam filter, AI/MCP settings, Lead Aggregation, reset / delete-all). Users Center only stores permission 1 or 2 and only for existing users. * Security: UpiCRMUsers::is_have_permission_to_lead() always returned true. A user limited to "only leads assigned to me" can now open, edit and change only own leads and those of users below him/her; the Edit lead screen checks it too. * The quick links in notification e-mails (change status / assign to me) changed the lead as soon as the link was opened. They now show a confirmation form; the change is made by its POST with a nonce. * upicrm.php no longer calls set_include_path() (it replaced PHP's include path for the whole request), no longer reads UTM parameters or writes $_SESSION while the file loads, and the Lead Aggregation endpoint is a function hooked to init instead of code at file level. upicrm_get_referer() was removed. * Lead referrer: the first external website the visitor came from (campaign cookie); when that is unknown, the page the form was sent from. (In 3.15.3 and 3.15.4 the page of the form was stored whenever the browser sent a Referer header.) * Fixed: the Edit lead form posted to an address with a broken id (esc_url() on a number), so the save did not find the lead. * The form ids in the field-mapping markup of Data Types & Fields are escaped with esc_attr(). = 3.15.4 = * Fixed: Lead Management could stop with a PHP error ("strpos(): Argument #3 ($offset) must be contained in argument #1 ($haystack)") on PHP 8 when a lead that was received from another site (source_id 0) had an empty or very short content. The "Remote form" name was cut out of the content with string offsets (strripos() + 12, strpos() - 1); when the marker was missing the offset was past the end of the text, which PHP 8 reports as a ValueError. The name is now read with json_decode() by the new function upicrm_remote_form_name(), which never fails: names with a comma, quotes or non-English letters (they were shown truncated or as \uXXXX codes) are right, and an empty or nameless content gives an empty cell. * The CSV / Excel exports use the same function (before, a remote lead without a form name raised an "Undefined array key" notice there). = 3.15.3 = * Fixed: UTM / campaign data and the referring website were almost never saved with new leads. They were kept in a PHP session, and the plugin does not start one. UpiCRM now remembers them in a small first-party cookie ("upicrm_utm", set by a few lines of JavaScript so it also works with page caching): the UTM parameters of the landing page and the first external referrer - first touch wins. A session, if another plugin runs one, is still honoured. * New: UpiCRM > GDPR has a "Campaign cookie" setting - off, until the browser is closed, 7, 30 (default), 90 or 180 days - with an explanation for your privacy policy. The cookie can also be disabled in code with add_filter( 'upicrm_enable_utm_cookie', '__return_false' ). A suggested privacy-policy text was added to Settings > Privacy > Policy Guide. * Saving the GDPR settings now requires a UpiCRM administrator. = 3.15.2 = * Fixed: UpiCRM > Data Types & Fields ended with "There has been a critical error" on sites that run Ninja Forms 3 (the plugin called Ninja Forms 2 functions that no longer exist). Ninja Forms 3 forms, fields, form names and the "import existing data" step now work; Ninja Forms 2 is still supported. * New: "import all existing forms plugins data into UpiCRM" (UpiCRM > Import) now also imports past Elementor Pro submissions (Elementor > Submissions), keeping their original date, IP, browser and referer. It sends no e-mails, can be run again without creating duplicates, and continues in the next click on very large sites. A result message shows how many submissions were imported. = 3.15.1 = * Fixed: Lead Management no longer freezes on "All Time" (or any large date range). The table used to build every lead in one page request - with several thousand leads the server ran out of resources, the page broke halfway and the loading spinner stayed forever. The table now loads one page of leads at a time (search, column filters, sorting and paging are done by the server), shows a "Loading leads..." indicator, and shows an error message if a page cannot be loaded. * Fixed: "Delete Selected leads" deleted nothing (the list of selected ids was reduced to a single number). * Fixed: the column filter boxes keep working after a column is hidden and shown again with "Choose Fields to display". * The selected date range (All Time / 1 Month / custom ...) is now remembered between visits. = 3.15 = * Security: Lead Aggregation (receiving leads from other UpiCRM sites) now works with a secret API key: the new "Generate" button on the Integrations screen creates one. The old default key is only a hash of the two site addresses, so anybody can calculate it; it is accepted only while "Accept legacy API keys" is switched on (on for sites that already use integrations, off for new installations). Keys are compared in constant time, saving a lead needs a POST request, unknown actions are rejected, and a status check with a wrong key no longer changes anything. * Security: removed the public "upicrm_on_load" AJAX action and the unused page-footer script; the request that sends pending notifications now carries a signed token. * Fixed: activation and updates create every table with dbDelta(), including the web-service header columns that were never created before; re-activating the plugin no longer replaces edited fields, statuses and e-mail templates; no PHP notices, warnings or database errors on activation and on the admin screens with WP_DEBUG on. * The four unprefixed options that were copied to prefixed names are no longer deleted from the options table. * TLS certificates are now verified on requests between sites (a site with a self-signed certificate can use add_filter( 'upicrm_integration_sslverify', '__return_false' )). * Fixed: the "Custom Export" link on the Export screen crashed with a fatal error and was described as working without a login. It now needs a logged-in UpiCRM user and a short-lived key that is part of the link. * The list of lead fields is no longer read from the database on every page load. * DataTables updated to 2.3.8. = 3.14 = * The admin screens no longer bundle Bootstrap or Font Awesome: layout, buttons, tables, the multi-select drop-down and the lead-log window are UpiCRM's own styles and scripts, and icons are WordPress's Dashicons (about 1.3 MB less). DataTables was updated to the official 1.13.11. * Export and import files are now removed automatically after 24 hours, and export file names are long random strings. * Fixed: the "export latest leads" and web-service parameter actions now check the user's permission. = 3.13 = * Security and review fixes: all files the plugin creates (exports, imports, logs) now live in one protected folder inside the uploads directory (wp-content/uploads/upi-crm-universal-crm-solution, found with wp_upload_dir(); an existing "upicrm" folder is moved there) and are only handed out through permission-checked download links. Log files for web services and the integration debug log are downloaded the same way. * All AJAX actions now have a UpiCRM-specific prefix and check both a security nonce and the user's UpiCRM permission; the web-service parameter removal and the "export latest leads to CSV" actions had no check before. Leads received from other sites or by integration calls are sanitized before they are stored. * Removed the copies of WordPress core functions (get_user_by, get_userdata, get_the_author_meta) and the manual load of pluggable.php; no more unlimited time/memory limits (a bounded limit is raised only inside export/import tasks); option names that had no prefix were renamed (values are kept). * Updated Bootstrap to 3.4.1 (the official release) and removed the remote-script references from the code. = 3.12 = * Admin screens no longer include the commercial "SmartAdmin" theme files. The Dashboard, Lead Management and the other screens now use WordPress's own card style, UpiCRM's own stylesheet, and the date pickers, tabs and notifications are provided by UpiCRM itself. Bootstrap, Font Awesome and DataTables (all open-source) remain bundled; see assets/resources/THIRD-PARTY-LICENSES.txt. * The Dashboard line chart is drawn by UpiCRM, so the charting, flot, vector-map, sparkline and widget libraries were removed (about 2.6 MB less in the plugin). * The date fields now open a calendar (WordPress's bundled jQuery UI datepicker). * License information made consistent: GPLv2 or later in the plugin header, the file header and license.txt. = 3.11 = * New: connect AI assistants (Claude, Gemini and other MCP clients) to your leads. UpiCRM now registers 12 abilities with the WordPress Abilities API (WordPress 6.9+): list forms, statuses and users; search and filter leads (date range, form, status, assignee, free text, UTM, untouched for N days); get one lead in full; lead statistics; find duplicates; change status, assign, add a note, create a lead; and export leads to Excel/CSV through a signed one-hour download link. Nothing is deleted by any ability. With the free MCP Adapter plugin and an Application Password they become MCP tools. * New: UpiCRM > AI / MCP settings screen - master switch (off by default), separate Read / Write / Export switches (Write is off by default), the capability required to connect, optional masking of email/phone in lead lists, an export row limit, connection instructions and an audit log of the last 500 calls (kept 90 days, no personal data). Level-1 UpiCRM users only reach their own leads and their team's. Changes made by an agent are recorded in the lead history as "via AI agent". Exports are kept in a protected folder and deleted after 24 hours. * New: the Export screen can filter by lead status as well as form and date range. * New: the same tools are also offered through the AI Site Manager gateway plugin (tools named upicrm_..., category "upicrm") when it is active - API keys, or sign-in with OAuth for claude.ai connectors - and this also works on WordPress versions before 6.9. The same switches, permissions and audit log apply. * Sites running WordPress older than 6.9 are not affected: the abilities are simply not registered. * Fixed: changing a lead's comment in Lead Management could stop with a fatal error on PHP 8 (an undefined variable in the save handler), and the change log raised a warning when no comment was supplied. = 3.10.3 = * Fixed: the Excel download added in 3.10.2 opened a page saying "Export file not found" - the download address was being HTML-encoded inside the page script, so the file name never reached the download handler. Excel and format-template downloads now work. = 3.10.2 = * Export screen redesigned: the form picker, date range and the Excel/CSV download buttons now sit in one "Download leads by filter" panel, with a live count of the leads that match and the buttons disabled when nothing matches. The form picker shows a short summary instead of overflowing into the date fields. * Fixed: the Excel download could end in an "Internal Server Error" on some servers because it linked straight to the file in wp-content/uploads (with a doubled slash in the address). Excel downloads now go through the same secure download used for CSV, which also checks the user is allowed to export. = 3.10.1 = * Export filters: the form filter is now a searchable multi-select - type to find a form, tick as many as you need (or "Select all"); leave it empty to export every form. Works for both the Excel export and "Export all leads data to CSV". = 3.10 = * Export filters: on a site that receives leads from other UpiCRM sites, the form filter now lists each remote form by name (taken from the lead's "Form Name") with its lead count, instead of one combined "remote leads" entry, and leads that arrive with no form name can be exported as their own group. Sites that only send leads, or do both, show their local forms and any remote forms together. = 3.9 = * New: export leads with filters. The Export screen now lets you export only the leads of a single form and/or a date range, for both the Excel export and "Export all leads data to CSV". The form list shows every form that has leads (with their lead counts). * Fixed: custom date ranges (the Export screen's Start/End dates and the Lead Management custom date range) produced an invalid database query on PHP 8 and returned nothing; the same fix also repairs "latest leads" exports for users who only see their own leads. Dates typed as dd.mm.yyyy, dd/mm/yyyy or yyyy-mm-dd are now read unambiguously instead of being guessed. = 3.8 = * Fix: admin styles no longer leak into other plugins' pages (e.g. The Newsletter Plugin lists hidden). UpiCRM's admin CSS/JS now loads only on UpiCRM's own screens, and every rule in its stylesheets is scoped to UpiCRM's own admin wrapper. = 3.7 = * Fixed the "Map existing forms fields" screen showing a blank, unlabeled row when a form field has no label or placeholder set (e.g. a plain acceptance checkbox, or a hidden field) - every field now also shows its internal field ID, and clearly says "(no label on the form)" instead of leaving the row blank. Applies to every supported form plugin, not just one. = 3.6 = * Fixed the real cause behind Elementor forms appearing to "lose" their field mapping, or showing a "Field mapping attempt failed" error: Elementor identifies each form with a non-numeric id, which was being truncated down to a small number before being stored - different forms could truncate to the same number and silently share (or overwrite) each other's field mapping and leads. Every Elementor form now gets its own stable, permanent internal id instead. Existing Elementor form mappings need to be set up again once after this update (previously-collided leads cannot be automatically un-mixed); new leads and new mappings are unaffected going forward. The now-obsolete "forms sharing an internal id" warning notice was removed since this can no longer happen. = 3.5 = * Fixed: marking a lead as spam via the inline status dropdown in the Lead Management table (not just the bulk "Change Selected leads status to" action) now also asks for a category, and correctly saves it. * Added "Thanks, got it" / "Remind me later" options to the CSV/Excel export privacy notice, so it can be dismissed for good or snoozed for a day instead of reappearing on every admin page load. = 3.4 = * Spam Filter: marking a lead as spam is now done through the existing lead status dropdown (a new "Spam" status), instead of a separate button - use the same "Change Selected leads status to" control you already use for every other status. Choosing the Spam status also asks for a category (IP / Email / Domain / User-Agent / Content keyword / Other) so the reason is recorded. * Spam Filter: added a master on/off switch ("Enable automatic spam filtering for new incoming leads") at the top of the Spam Filter screen, so automatic rule-based blocking/flagging of new leads can be fully disabled while keeping manual spam marking available. * Spam Filter: Hebrew translation added for the Spam Filter screen and its new controls. = 3.3 = * New: Spam Filter. Block or flag incoming leads by IP address, email address, email domain, User-Agent, or content keyword, with a whitelist that always takes priority. Matched leads are still saved (never silently discarded) - "Flag" tags a lead for review while routing/notifying as normal, "Block" saves the lead but suppresses auto-routing, notifications, and outbound sync for it. A new "Spam Filter" admin screen lists blocklist/whitelist rules and all flagged/blocked leads with their match reason, with one-click "Whitelist & Restore" and delete. Seeded with rule suggestions found by analyzing real spam patterns. This is an initial version for testing - please report anything that looks wrong before it's considered final. = 3.2.4 = * Fixed the likely real reason recent fixes weren't visibly taking effect: every one of the plugin's own CSS/JS files was loaded with a fixed version number that never changed between releases, so browsers (and any site-level caching) had no reason to ever re-download an updated file - even though the underlying file had genuinely changed. Every plugin-owned CSS/JS file's version number is now tied to the plugin version, so it changes on every release going forward. = 3.2.3 = * Fixed the real cause behind 3.2.2's still-broken RTL layout: the plugin's right-to-left stylesheet was being loaded into the page before its base stylesheet instead of after, so every right-to-left correction was silently being overridden back to its left-to-right default. This appears to have been the case for as long as the plugin has had a right-to-left stylesheet, not something introduced recently. Right-to-left (Hebrew) layouts should now render correctly. = 3.2.2 = * Fixed: the calendar picker icon on the GDPR page's date-range fields was oversized after a recent icon-font change and could sit on top of part of the input, intercepting clicks meant for the field. The icon no longer intercepts clicks. = 3.2.1 = * Fixed: translated strings (Hebrew and all other bundled languages) were never actually loading, on any site, regardless of locale - the plugin never told WordPress to load its own translation files, and separately those files were named inconsistently with the plugin's own text domain. Both are fixed; translations should now display correctly for non-English site locales. * Fixed a layout bug on the Data Types & Fields screen (introduced in 3.2's Existing Fields/Existing Statuses restructuring) where that section could render overlapping the field-mapping area above it. = 3.2 = * Hebrew (he_IL) translation completed: the translation file was last updated in 2022 and was missing roughly 40% of the plugin's current text (it now covers all 339 current strings, translating the 193 that were missing while keeping every existing translation unchanged). * Continued the move toward native WordPress admin styling (visual/structural only, no functional changes) on the Data Types & Fields, Email Notifications, Auto Lead Management, and Lead Aggregation screens, including their tables: replaced Bootstrap-style panels, buttons, and icons with WordPress-native equivalents, and removed unused/dead leftover code from those screens. * Added RTL-mirrored spacing rules for the icon and layout changes introduced in this and the previous release, so right-to-left (Hebrew) layouts stay visually aligned. = 3.1 = * Fixed: the jQuery UI calendar popup on date fields (GDPR historical-data deletion, Export, and elsewhere) was very likely never actually appearing anywhere in the plugin due to a script loading bug - the field quietly worked as a plain text box instead. The calendar picker should now appear correctly. * Fixed a markup error on the Web Services page's "Enable Service" checkbox that could cause it to render incorrectly in some browsers. * Continued the move toward native WordPress admin styling (visual/structural only, no functional changes) on the GDPR, Users Center, Import, Export, and Web Services screens: replaced Bootstrap-style buttons and icons with WordPress-native equivalents, and removed unused/dead leftover code from those screens. = 3.0.1 = * Admin UI cleanup, first step in an ongoing move toward native WordPress admin styling: removed ~550KB of unused bundled CSS files, and scoped the DataTables library to only load on the Dashboard and Lead Management screens instead of every UpiCRM admin page. No visible change to any screen. = 3.0 = * Version numbering updated to 3.0. = 2.3.9.43 = * Moved the "Enable Audit Log for lead management" setting from the Data Types & Fields screen to the Lead Management screen, where it belongs. = 2.3.9.42 = * Fixed: on the Data Types & Fields screen, Elementor form field mappings that were correctly saved and working (leads mapped correctly) could still show as unmapped in the "Map existing forms fields" dropdowns. * Added a warning notice on the Data Types & Fields screen if two Elementor forms are found sharing the same internal id (can happen after duplicating a form) - they may share the same field mapping. = 2.3.9.41 = * Fixed: "1 leads" now reads correctly as "1 lead" on the Dashboard. * Web Services: the 10 custom header-parameter rows now start collapsed to 2 (plus any row that already has saved data), with an "Add another header" link to reveal the rest, instead of always showing all 10 blank rows. * Grouped related checkboxes on the GDPR and Email Notifications settings screens into clearer visual sections. * Row-action icons (save, remove, resend, etc.) in the Lead Management table now show a busy state while their request is in flight, and can't be double-clicked mid-request. * Dashboard's "Manage Leads" / "Export to Excel" links now show a hover state. = 2.3.9.40 = * Clearer default notification emails: "New Lead" now sends as "New Lead notification" with a subject including your site name and the form it came from; "Change User" is now "Assign Lead - Notification Email"; "Change Lead Status" is now "Lead Status Change - Notification". (Only applies if you haven't already customized these - your own wording is left alone.) * Two new placeholders available in any email template: [sitename] and [form-name]. * Moved the "follow-up after N days" status settings to the Email Notifications screen, next to the templates they use, instead of the Data Types & Fields screen. * Renamed a mislabeled section heading on the Email Notifications screen from "Lead Management" to "Default Notification Settings". = 2.3.9.39 = * Fixed the lead audit log popup for real this time: the security token it needs was declared in a way that could go out of scope for the click handler, causing "nonce is not defined" in the browser console and an endless spinner. Made it reliably available instead. * The Save icon next to each lead in the table is now larger and blue, to stand out from the other row actions. = 2.3.9.38 = * The lead audit log popup now shows a clear error instead of spinning forever if it can't load - working on tracking down the underlying cause, this makes the failure visible in the meantime. = 2.3.9.37 = * Fixed: Elementor forms built with nested sections/inner-sections/containers (common on more complex page layouts) were invisible to the "Map existing forms fields" screen - the detection only looked exactly 3 levels deep. It now finds a form widget at any nesting depth. = 2.3.9.36 = * Fixed: the field-mapping dropdowns on the "Data Types & Fields" page (Map existing forms fields section) were showing as a run-on wall of text instead of a dropdown list, for every form type (Elementor, Contact Form 7, Gravity Forms, etc.) - a leftover from an earlier security hardening pass that was too aggressive about stripping HTML. The dropdowns work again, and the underlying values are still properly escaped. = 2.3.9.35 = * Fixed: the new "days in status without contact" follow-up settings were added to a page with no menu link in the previous version - moved them to the Data Types & Fields page (Statuses tab), where the Lead Status list already lives. = 2.3.9.34 = * New: optional thank-you/confirmation email sent to the lead themselves right after they submit a form (off by default - enable it under Email Notifications). * New: automatic follow-up emails when a lead sits in the same status for too long without being contacted - set the number of days and the template per status under Lead Statuses. * The email template editor is now a full rich-text editor (bold, links, lists, etc.) instead of a plain text box, for both the built-in and custom templates. = 2.3.9.33 = * Added nonce (CSRF protection) verification to the last few flagged spots: the filtered Excel export, the chunked CSV export (now also sends a security token from the browser), and two unused bulk-update endpoints for the leads table. = 2.3.9.32 = * Fixed several nonce-protection code comments from the previous version that were using the wrong classification and so weren't actually silencing the automated code checker's warnings (the checker distinguishes between form/link submissions differently, and a few comments had it backwards). * Added a required translator note for a message that includes a dynamic link. = 2.3.9.31 = * Added nonce (CSRF protection) verification across the remaining screens flagged by the automated code checker: settings, custom statuses/fields, lead table actions (reset/delete all), import/export (including the sample-file download and form-import actions), dashboard, lead editing, privacy tools, and email notification templates. * Fixed several previously-added protection comments that were placed on the wrong line and so weren't actually taking effect. = 2.3.9.30 = * Added nonce (CSRF protection) verification to the Users Center screen, which previously had none: adding/editing a user, setting default permissions for new WordPress users, resetting the user hierarchy, and the "remove user" action. = 2.3.9.29 = * Documented the last 2 "unsanitized input" findings from the automated code checker (both already safe - each value is sanitized individually inside a loop, which the checker can't see from the surrounding line). = 2.3.9.28 = * Fixed the last batch of "unvalidated/unsanitized input" findings from the automated code checker across 8 files (privacy tools, settings, lead routing, leads table, import/export, lead aggregation) - added missing existence checks and sanitization to request-data reads that were missing them. = 2.3.9.27 = * Removed the unused Google Authentication settings page - it had no menu entry to reach it and the credentials it saved were never used by anything (the feature they were for was removed earlier). = 2.3.9.26 = * Added missing existence checks before reading several form/request fields (Web Services, User Center, Elementor integration, and lead-tracking data) so a missing field can't trigger a PHP warning. * Removed one more piece of dead/unreachable code (an orphaned AJAX handler in the Web Services screen with no way to actually be called). = 2.3.9.25 = * Closed the remaining gaps in the automated code checker's "unprepared SQL" findings - documented a batch of already-safe queries whose justification comment was on the wrong line to be recognized (all comment-only, no logic changes). * Documented why several time-limit/memory-limit adjustments are necessary (used only for large CSV/Excel exports and a background sync task, never based on user input). = 2.3.9.24 = * Removed an unused bundled third-party UI library (SmartUI) that was never actually loaded by the plugin - reduces plugin size and removes the last remaining third-party code from the Plugin Check report. = 2.3.9.23 = * Closed a gap from the previous round: several already-safe SQL queries (using $wpdb->prepare() correctly) were still being flagged by the automated code checker because a documentation comment was missing, not because of an actual problem - added it across 13 files. * Documented the last few remaining findings that are already safe (a plugin-internal exception message, a table-name-only query, and two WordPress core update() calls). = 2.3.9.22 = * Prefixed global variables that could collide with other plugins/themes ($SourceTypeID, $SourceTypeName, and ~50 template-local variable names across 8 admin screen templates), per WordPress.org's naming-convention checks. * Updated the readme.txt listing metadata: matched the title to the plugin's actual name, trimmed the short description, reduced tags to 5, updated "Tested up to", and removed references to the Affiliates and Social Networks features that were removed earlier. * Documented several remaining Plugin Check findings that are intentional and safe: a WordPress-core-compatible function/filter name that must keep its exact name to work correctly, and two scripts deliberately kept loading in the page head (see 2.3.9.19's fix) rather than the footer. = 2.3.9.21 = * Resolved the remaining "unescaped SQL parameter" Plugin Check findings across the data-access classes (all were already using $wpdb->prepare() correctly - just needed a documentation comment for the automated checker). * Replaced a deprecated direct parse_url() call with the WordPress-recommended wp_parse_url(), and removed a manual translation-loading call that's unnecessary for WordPress.org-hosted plugins (handled automatically since WordPress 4.6). * Documented several remaining "missing nonce" Plugin Check findings that are already safe: two are on WordPress core's own user-profile-save hooks (already protected by WordPress's own nonce check), and two are read-only actions (a dashboard date filter, a CSV export) that don't write to the database. = 2.3.9.20 = * Hotfix: the Leads Management table still failed to load after the 2.3.9.19 fix, because a second bug in the same code path was corrupting the "remembered visible columns" setting on every page render (not just on save) - `esc_js()` was being used to embed a JSON value directly into an inline script, which HTML-encodes quote characters and breaks the JSON. Replaced with proper JSON encoding for script embedding. = 2.3.9.19 = * Hotfix: the Leads Management table (and other admin screens) failed to load at all ("$j is not defined" in the browser console) because a recent WordPress.org compliance fix moved several core scripts to load in the footer, but the plugin's own inline scripts run earlier in the page and depend on them being available immediately. Reverted those scripts to load in the page head as before. * Fixed a bug where the "remembered visible columns" setting on the Leads table could get corrupted (HTML-encoded instead of stored as plain JSON), breaking the page for anyone who had customized their visible columns. = 2.3.9.18 = * Resolved the "direct database query" family of Plugin Check findings (direct query, no caching, unescaped parameter, schema change) across all data-access classes and the setup file - reviewed every flagged query and documented why each is safe for a custom-table plugin. * Bumped the minimum supported WordPress version to 4.7 (was 4.3, from 2015) to match functions already in use (`sanitize_textarea_field()`, `wp_parse_url()`). * Fixed a latent bug that would fatal-error on every lead-history write under PHP 8+ (an undefined-variable call to `mysqli_set_charset()` left over from before the plugin used `$wpdb`). * Added nonce (CSRF protection) verification to two remaining admin actions that had none: the Lead Routing "change order" action and the Lead Aggregation status-check/remove AJAX actions. = 2.3.9.17 = * Removed the Affiliates feature entirely (the standalone "Affiliates Center" admin screen, its public shortcodes, the "UpiCRM Affiliate" user permission level, and the "Assign lead to affiliate" option in Auto Lead Management) - not used and not supported going forward. * Fixed several nonce (CSRF protection) checks that were verified in a dispatcher method but not visible to WordPress's automated code checker from the action method itself - checks are now duplicated at the point of use for the leads/web services/settings/existing-statuses/web-service-parameters screens, and a missing nonce was added to the lead-routing "remove" AJAX action. * Fixed a duplicate-array-key bug in the Users screen that silently hid the "UpiCRM Admin" permission option. = 2.3.9.16 = * Removed the bundled PHPExcel library entirely (an abandoned third-party dependency, last updated around 2015) and replaced it with a small dependency-free Excel export/import writer built specifically for this plugin's needs. Reduces plugin size and removes the last major third-party-code submission risk. Old-format .xls uploads are no longer supported for the "Upload & Import" Excel template feature - please save as .xlsx first (CSV import/export is unaffected). * Completed the CSV export/import admin screen security pass (nonce verification, input sanitization, the forbidden move_uploaded_file() fix) that was still in progress in 2.3.9.15. * Fixed a real SQL injection vulnerability in the filtered-export query (admin-only, but a genuine unescaped-parameter issue) and added the missing "no direct access" guard to functions.php. * Removed the "Social Networks Integration" promotional tab (an upsell panel for a separate paid add-on) and its now-unused Google Sign-In leftover code. = 2.3.9.15 = * Testing checkpoint for the WordPress.org submission-prep pass: nonce verification (CSRF protection) and input sanitization added across most admin screens (leads, lead routing, users, settings, statuses, Google auth, dashboard, email notifications, web services, affiliates, integrations/lead aggregation, privacy/GDPR tools, exports), SQL queries reviewed and parameterized where real user input is involved, cURL calls replaced with the WordPress HTTP API, raw file operations replaced with the WordPress Filesystem API, and several other WordPress coding-standard fixes (date/rand functions, script loading). A small number of admin actions reachable only via unsigned links or undiscoverable AJAX callers are still flagged internally for follow-up. Not yet included in this build: readme.txt metadata updates and the CSV export/import screen (still being fixed in the background) - see project notes for details. = 2.3.9.14 = * WIP checkpoint during a larger WordPress.org submission-prep pass (added the required "no direct access" guard to all plugin files, started fixing SQL query safety, nonce verification, and input sanitization across the admin screens). Not all findings are resolved yet in this build - see project notes for what remains. = 2.3.9.13 = * Fixed several output-escaping findings that were missed in the previous release's cleanup pass (a wp_die() message, a stray leftover suppression operator, and the WordPress selected() helper's output in several forms) * Fixed a real security issue in the Leads table renderer: several fields were displayed without escaping, including some sourced from data a site visitor can directly control (browser User Agent, Referer header, and UTM campaign parameters submitted with a lead) - now consistently escaped everywhere this renderer is used, including in the front-end affiliate shortcode * Version bump only, to make sure the correct build is being tested (a same-version reupload can look identical to a testing tool even after real changes) = 2.3.9.12 = * WordPress.org submission prep: resolved all output-escaping findings from the Plugin Check tool's security scan across the plugin's admin pages, classes, and templates - all dynamic output (translated text, user data, URLs) now goes through the appropriate WordPress escaping function * Reduced package size by relocating WordPress.org listing assets (screenshots, banner, icon) out of the shipped plugin, where they never belonged, and by lossless-optimizing the remaining bundled images * Removed further unused bundled code found during the audit = 2.3.9.11 = * Fixed 2 translation calls that were missed in the previous release's Plugin Check cleanup (googleauth.php, integrations.php) * Removed an entirely unused, never-loaded 5.7MB bundled Google API library (Google Auth/Gmail integration that was never wired into any menu) - plugin folder size reduced from 22MB to 13MB * Removed other unused bundled code: PHPExcel's locale/translation files and unused export formats (PDF, legacy Excel, HTML, CSV writers - only Excel2007 export is ever used), a duplicate old admin-pages folder, a duplicate mapping library version, unused theme demo images, and several unused CSS files * Fixed a real bug: the Affiliates Center page was loading a stale, unescaped duplicate of its form template due to a leftover file with a space in its name; the correct underscore-named file (already in place) is now the only one and was already the one actually used * Removed leftover diagnostic logging that wrote raw lead data to the debug log, added temporarily while fixing Lead Aggregation in a previous version and never cleaned up * Added the required License field to the plugin header (WordPress.org submission requirement) * Removed a stray development-tool folder that had no place in the plugin package = 2.3.9.10 = * WordPress.org submission prep: resolved all 794 findings from the official Plugin Check tool, all internationalization (i18n) issues * Fixed the text domain everywhere in the plugin (including the plugin header and load_plugin_textdomain call) to match the WordPress.org slug 'upi-crm-universal-crm-solution' instead of the old 'upicrm' - 756 occurrences across 54 files * Added missing translation-domain arguments to 27 translation function calls that had none * Fixed 9 translation calls that passed a dynamic/ternary value instead of a literal string (not translatable as written); two of these (in the Lead Aggregation screen) were actually calling _e() on an already-translated string a second time - now output directly with proper escaping instead * Removed a stray extra argument from 2 translation function calls = 2.3.9.9 = * Fixed a fatal PHP error on PHP 8+ that broke Excel export and import entirely: the bundled PHPExcel library used old-style curly-brace string/array offset syntax (e.g. $var{0}) which PHP 8 removed. Repaired the syntax in the 20 affected library files (PHPExcel core, Calculation engine, and readers) without changing any behavior * Verified with a full syntax lint across all 413 plugin files - zero parse errors * Fixed a duplicate/malformed "Stable tag" field in readme.txt left over from a previous edit * Prep work for WordPress.org Plugin Directory submission = 2.3.9.8 = * Major front-end performance fix: UpiCRM was running its expensive pending-notification check (two full multi-table-JOIN queries against the leads table) on every single page load, site-wide - including pages with no form at all. Moved to a periodic WP-Cron schedule (every 10 minutes) instead, cutting this to near-zero cost on normal page views while preserving full functionality * The "Delayed by AJAX" lead-aggregation send check similarly no longer pings admin-ajax.php from every visitor's browser on every page load; moved to its own WP-Cron schedule (every 5 minutes) * Added indexes on the leads table's pending-notification flag columns so even the periodic cron check runs fast * Scheduled cron events are cleared on plugin deactivation to avoid orphaned WP-Cron entries = 2.3.9.7 = * New lead notification emails (and the optional CSV-attachment email) now fire via a non-blocking background request right after the lead is created, instead of waiting for whichever page load happens to hit WordPress's wp_loaded hook next * Fixes a real-world timing issue: forms that redirect to a "thank you" page were often the ones stuck sending the pending email, delaying the visitor's own confirmation page while the notification email was sent synchronously * The previous wp_loaded-based sending still runs as a safety-net fallback, so nothing is lost if the background request doesn't fire (e.g. blocked by a firewall) = 2.3.9.6 = * Lead Aggregation (master/slave sync): added an optional debug logging toggle to help diagnose why leads aren't transmitting to a remote master (logs request URL, HTTP status, curl errors, and remote response) * Lead Aggregation: fixed a bug where a rejected send (e.g. wrong API key) could be silently mis-parsed instead of being recorded as a failed transmission = 2.3.9.5 = * Fixed a major CSV export performance issue caused by missing database indexes on leads_campaign, leads_integration, and users table join columns (was causing full table scans on every export query) * Added automatic database index migration so existing installs get these indexes added on upgrade, and new installs get them from first activation * CSV export: fixed downloaded file not saving in some browsers by forcing a proper file download instead of relying on direct navigation * Removed temporary diagnostic logging added while investigating the export performance issue = 2.3.9.4 = * CSV export performance: removed millions of redundant object instantiations in the per-field lead rendering code * CSV export performance: stopped re-decoding each lead's JSON content on every field (now decoded once per lead) * CSV export performance: cached repeated unserialize() calls on the fields configuration * CSV export performance: memoized form-name lookups so leads sharing the same source form no longer repeat the same query * CSV export: increased batch size per request now that per-row processing is much cheaper = 2.3.9.3 = * Fixed PHP 8+ deprecation notices (implicit-required params in statistics/web service classes, str_replace() with null) * Fixed fatal error on Plugins page caused by a non-static method called statically (GDPR file-deletion notice) * Fixed undefined array key notices on the Export page date filters * CSV export: added a progress bar and background processing so large exports no longer time out or hang the browser * CSV export: switched large exports to keyset pagination so each batch stays fast regardless of dataset size * CSV export: removed a redundant database query that ran on every single field of every lead, significantly speeding up exports * Minor code hardening around the leads CSV export process (memory/time limits, permission scoping) = 2.3.8.8 = * Fixed min ver wp on readme file = 2.3.8.7 = * Verified comp. WP V6.0 = 2.3.8.6 = * hot fix - data integrity + email functionality = 2.3.8.5 = * hot fix - data integrity and presentation bug. = 2.3.8.4 = * General bug fixed SMTP email = 2.3.8.1 = * WP5.8 compatibility = 2.3.8.0 = * added functionality to affiliate managament (BETA) * bug fix - REST API = 2.3.6.4 = * CF7 bug fixed - not redirecting after submit = 2.3.6.3 = * CSV file export by mail gub fix * more features to Affiliate managment - Beta = 2.3.3.2 = * genral bug fixed * Affiliate capabilities - beta = 2.3.0.5 = * general bug fix * inbound web service improvment. * CF7 compatiblity fix = 2.2.11.3 = * added feature leads management table now supports horizontal scrolling for responsive devices. * added feature attachments from gravity forms open directly with http link = 2.2.11.2 = * Fixed bug compatibility with Elementor Forms = 2.2.10.8 = * Minor UI fix. = 2.2.10.7 = * Fixed bug compatibility with Elementor Forms. = 2.2.10.6 = * fixed compatibility with Contact Form 7 = 2.2.10.5 = * backward competibility with new wp email api. = 2.2.10.4 = * fixed bug lead routing table working but not presenting content. = 2.2.10.3 = * Added feature: choose default ole - UpiUser & UpiAdmin for a new WordPress user - admin or subscriber = 2.2.10.0 = * support for Social Networks ads leads import UpiCRM extension. see section "Social Networks Integration" under UpiCRM menu. * Elementor Forms - advacned support and API. = 2.2.9.3 = * Added: support for Social Networks ads leads import UpiCRM extension. see section "Social Networks Integration" under UpiCRM menu. * General bug fixes. = 2.2.9.2 = * Added feature: sort rules by processing order - users can now determine the order to the processing of the rules. = 2.2.9.0 = * added: send leads to remote UPI server based on automated rules = 2.2.8.3 = * fixed leads export with date selectoin * general bug fix - aggregation etc. = 2.2.8.2 = * fixed bug in DB configuration when installing * fixed - security issue XSS = 2.2.8.0 = * added - free header paramaters in webservices =2.2.7.0 = * added more option to auto lead management * general bug fix = 2.2.6.0 = * genereal bug fix * add user_agent option for outbound webservice * add foundation for Social Networks leads integration * fixed foundation for Google docs lead integration = 2.2.5.6 = * bug fix save configuration = 2.2.5.5 = * bug fix save configuration = 2.2.5.4 = * Fixed - bug preventing saving auto leads and email templates. update db. = 2.2.5.3 = * Fixed - bug preventing saving auto leads and email templates. = 2.2.5.2 = * Improved Audit log view - trim and view functionality * Fixed - send cc to email template * Fixed - special characters in mail template = 2.2.5.1 = * Added feature: Lead audit log. Track leads changes - now all lead management actions are logged and presented on the lead management table. * Minor fixes. = 2.2.4.2 = * fixed issues with database error upon activation * fixed issue generatin error message "header already sent" = 2.2.4.1 = * added - delayed transmission to remote integration server in order to improve user performance and experience * bug fix - presentation issue with wp-forms * complete CF7 entry integrity check before storing forms entries. = 2.2.3.0 = * Added suport for WPFORMS = 2.2.2.7 = * Fixed bug on submitting forms with Contact form 7 = 2.2.2.5 = * Fixed bug on UpiCRM users dhashborad to refelct accurate data in tables. = 2.2.2.4 = * Fixed Bug On UpICRM Dashborad to show correct values in main leads received graph = 2.2.2.3 = * minor bug fix missing privacy_class.php file. = 2.2.2.2 = * Added feature: advacned capability of sending emails by templates to either users, admin or web site visitors upon submitting a lead, according to automated rules and conditions. * Added feature: choose if UpiCRM will send email notifications to UpiCRM users, admins, or none at all. * Added choice: allow UpiCRM to revert to smtp email function of the server, or use only Wp-Mail function. This was added as a debug option for email sending. = 2.2.1.2 = * fixed bug with Ninja forms fields mapping = 2.2.1.0 = * renewed support for Ninja Forms after newer version API change. = 2.2.0.5 = * Minor bug fix - delete private information * Added action and user notice - delete old exported files from server = 2.2.0.2 = * Added GDPR advacned feature: transmit private information to a 3rd server and store only meta data on site. * Added GDPR advanced features: wipe personal data from site = 2.1.10.2 = * bug fix - auto lead managment solution * new feature - option to select form to collect / not collect leads * new feature - reset field mapping per chosen form = 2.1.9.2 = * fix "Form Name" all exported formats = 2.1.9.1 = * Fixed bug of the impossibility of filtered export, if NOT selected dates * Changed The export algorithm in csv, this option for tests. Thanks Sumer Edmison! = 2.1.9.0 = * Added few options in filtered export to xlsx file * Added an alternative import method from csv file for tests * Fixed Export format in csv file * Added option for UpiCRM User: view only associated Leads * Fixed Google api error in console log * Returned Direct edit Lead Status * Added minor interface changes = 2.1.8.5 = * Added "Form Name" in Autolead managment * Added to filtered export fields: Referer, UTM Source, UTM Source, UTM Medium, UTM Term, UTM Content, UTM Campaign * Added select filter in column "Lead Status" * Fixed php warnings,notice,deprecated functions = 2.1.8.4 = * Fixed many php warnings,notice,deprecated functions * Fixed: Reducing the size of the Lead table * Fixed incorrect remote form view * Added feature : export to csv = 2.1.8.3 = * Fixed bug - field Form Name from Master to Slave from Lead Aggregation feature. * Added feature: Replaced filter type text to select in Leads Table field "Assigned to". = 2.1.8.2 = * Added feature: separated import and export fields = 2.1.8.1 = * Added feature: status deletion = 2.1.8.0 = * Added feature: lead management table now saves state and filed choices. * Added feature: lead manegement table now saves default date range = 2.1.7.8 = * Tested with WordPress 4.7 * Added default number of rows in table - lead management = 2.1.7.7 = * General bug fixes (activation, plugins collisions) . = 2.1.7.6 = * Added: "Not A UpiCRM User" option to new WordPress users. * Added: inbound web service now accepts both POST and Get methods. = 2.1.7.4 = * Added feature: Round-robin lead distribution. * fixed - auto lead management bug. * fixed - import from Excel presentation bug. = 2.1.6.2 = * fixed Bug - dashbaord date range errors * fixed bug - lead routing error * tested stable WordPRess 4.6.1 = 2.1.6.1 = * added Web service : inbound / outbound web services integration * fixed bug in integration domain * fixed : integrate to a remote server subfolder installation of wordpress * fixed : UI issues = 2.1.3.0 = * Fixed bug - Upi users tree view * added - date range selection on dashboard * added - more view on dashboard: Country * fixed - minor UI issues. * fixed - syntax error preventing dahsboard from apearing on previous versions of php = 2.1.2.1 = * fixed bug - export to Excel * Added PT_BR translation = 2.1.2.0 = * Added: custom date picker in the lead manamgenet screen, soon (next version) to implement in the Dashbaord screen as well. * fixed - some collision with a custom made function - users request. = 2.1.1.1 = * Fixed - screens doesn't load because of plugins/jquery collisions. * Added - send lead to rmeote server using web service, autmcatically, by using rules, and manually. = 2.0.4.2 = * Fixed - Notifications and emails not sent bug. On some unique conditions emails were NOT sent from the system. We have fixed that. * Fixed - some presentation issue on main leads table = 2.0.4.1 = * Added - lead routing / content manipulation based on 2 conditions. (if counrtry contains France and product contains "shoes" than assign lead to "Johnny"...) = 2.0.3.1 = * Added Content manipulation - enable text edits/manipulation based upon field's data (if field X contains "data" then fields "Y" equals "Hello" ... * General bug fixing. = 2.0.3.0 = * Added auotmation / field contents manupulation - example: "If Field 'country' contains 'Italy' then change Field 'continent' to 'Europe'. = 2.0.2.1 = * Caldera Forms support added * Italian translation added * bug fixes (edit/view leads) * improved leads edit / view screen. = 1.9.2 = * Fixed general UI issues - collision with Avada, Page Options, and other UI problems. For Any issue you still have problems with please conatct our support with access details to a staging/dev environment on which we can test and resolve the issue. = 1.9.4.1 = * Integration Center: UpiCRM can act as an aggregator of leads from multiple / remote web sites. This means that a UpiCRM master can receive leads from any other UpiCRM "slave" , as long as the connection (pairing) is performed. UpiCRM can work in complete orchestration, receive / send leads from and to multiple servers at the same time. * Minor UI / Bug fixes. * Improved e-mail notification: use [field-*] (* - UpiCRM field name) in order t include lead details in e-mail subject (New Lead from John Smith – UK…) * Send mail bug fix = 1.9.6.1 = * Removed CSS objects in order to prevent UI problems. * Added new feature: Import from Excel file - you can now import new data into UpiCRM! = 1.9.7.2 * Muti-server envorinment: UpiCRM can act as an aggregator of leads from multiple / remote web sites. * Adanced User/roles hirerchies: UpiCRM is designed to work in a multi-user / global organization environment, with up to 5 tiers of users, per your choice / definition. = 2.0 = * Improved UI , Dashboard and more. * Bulk actions applied to multiple leads in the leads management table. * Improved lead management table. * Advanced User management and user hierarchies = 2.0.0.1 = * solve jquery collision issues with plugins (WPML...) = 2.0.1.0 = * Added default date range for leads managment table. * Improved view/edit leads details.