Quotely Estimates for WooCommerce
| 开发者 | ruyhan |
|---|---|
| 更新时间 | 2026年7月20日 23:28 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Quotely Estimates for WooCommerce adds a frontend interface where customers can search your catalog, add products and quantities to a worksheet, and download a PDF estimate. Submissions are stored in WordPress so you can review, restore, or permanently delete them later, and you can re-download the PDF for any submission from the admin.
Features
- Frontend product search bound to your WooCommerce catalog (simple, variable, grouped and external products)
- Quantity controls, suggested products, and a live running total in the active currency
- Lead capture form with international phone validation (intl-tel-input — 70+ countries)
- Save & resume — customers email themselves a link to come back later
- Fully branded PDF export (TCPDF): company logo, name, tagline, footer note, store locations, PDF metadata — all editable from the admin
- Admin notifications: customer confirmation emails, HTML email body with token replacement, multiple admin recipients, From name/email, optional PDF attachment
- Admin submissions list with search, sort, workflow status (new / contacted / quoted / won / lost), trash, restore, bulk actions, CSV export, PDF re-download
- Admin dashboard widget with 30-day stats and top products
[estitofo_form]shortcode and a matching Elementor widget- WooCommerce HPOS and Cart/Checkout Blocks compatible
- Configure your branding under Estimations → Settings.
- Drop the
[estitofo_form]shortcode onto any page, or use the Elementor widget Estimation Tool. - Customers fill the form and receive a PDF; you receive the submission in Estimations → Submissions.
安装:
- Upload the plugin folder to
/wp-content/plugins/, or install it through the WordPress Plugins screen. - Make sure WooCommerce is installed and active.
- Activate the plugin.
- Visit Estimations → Settings to set your company branding for the PDF.
- Add
[estitofo_form]to any page, or insert the Elementor widget.
常见问题:
Does this plugin require WooCommerce?
Yes. Product data, pricing, and currency all come from WooCommerce.
Does it work with Elementor?
Yes. An Estimation Tool widget appears in the Elementor editor (Elementor 3.5 or higher).
Is it compatible with WooCommerce High-Performance Order Storage (HPOS)?
Yes. The plugin declares compatibility with custom_order_tables and cart_checkout_blocks.
How are submissions stored?
In a dedicated database table (wp_estimation_submissions). Soft-deleted rows go to a trash view and can be restored or permanently deleted.
What happens on uninstall?
The submissions table and the plugin's options are removed. Active submissions are deleted.
How is the PDF generated?
The plugin ships TCPDF (LGPL-3.0) for PDF generation. No external service is contacted.
更新日志:
3.20.0
- New:
estitofo_display_pricefilter — add-ons can adjust the prices shown in search results, suggestions and the REST API (used by Pro's role-based pricing). - Fix: the phone-number field layout broke under themes that restyle form inputs (e.g. Hello Elementor) — the input collapsed and the dial code rendered outside the field. The intl-tel-input structure is now enforced by scoped plugin CSS.
- Fix: on multi-page PDFs the page numbers were shifted by one page and a blank trailing page was appended (TCPDF's setPage() restores the auto-page-break flag per page).
- New:
estitofo_pdf_enginefilter — add-ons can supply a fully built PDF object to replace the built-in layout (used by the Pro add-on's multi-template engine). No behaviour change when the filter is unused. - Fix: when the server rejected a submission (missing phone, rate limit, spam check), the frontend still showed the success screen and generated a client-side PDF. Server errors are now shown to the customer and the form is restored.
- Fix: the View, Notes, status dropdown and Download PDF controls on the admin Submissions page did nothing, caused by a JavaScript settings-object name mismatch (estitofoAdmin vs estitofo_admin) that stopped the admin script from initialising.
- Fix: PDF download showed a critical error because two required TCPDF library files (
tcpdf_autoconfig.phpand the core font metric files) were missing from the bundledlib/directory. PDF generation now works again on all sites.
- WordPress.org review: renamed the plugin from the generic "Estimation Tool for WooCommerce" to the distinctive Quotely Estimates for WooCommerce, with a matching slug/text domain of
quotely-estimates-for-woocommerce. The internalestitofo_code prefix, the[estitofo_form]shortcode and stored option keys are unchanged, so existing installs upgrade without data loss.
- WordPress.org review: replaced the bundled
tcpdf/directory with a Composer + Strauss-managed copy underlib/where the main class is prefixed toEstitofo_TCPDF(and all sub-classes likewise). This eliminates the naming conflict that would occur if another plugin bundles a different TCPDF version — the classes are now completely isolated under the plugin's own namespace. - All plugin code updated to reference
Estitofo_TCPDFinstead ofTCPDF. - All files under
lib/include adefined('ABSPATH') || exit;direct-access guard as required by WordPress.org.
- WordPress.org review: moved TCPDF's
K_TCPDF_EXTERNAL_CONFIGandK_TCPDF_THROW_EXCEPTION_ERRORconstants intotcpdf/tcpdf.php(where they belong as library configuration) so they no longer appear in the plugin's own namespace scan. - WordPress.org review: added a
class_exists('TCPDF')early-return guard at the top oftcpdf/tcpdf.phpso the library is self-protecting against double-load regardless of load order. - Code quality: resolved all remaining WordPress Coding Standards violations — Yoda conditions, short ternaries, mixed class/function declaration, camelCase variable names, reserved keyword parameter names, deprecated
current_time('timestamp'), translator comment placement, and inline comment punctuation.
- Raised the minimum supported WordPress version (
Requires at least) from5.6to6.4in both the plugin header andreadme.txt. - Confirmed
Tested up to: 7.0(current WordPress stable) in both files. - Hardened TCPDF loading per WordPress.org review: the library is included only behind a
class_exists('TCPDF')guard, and TCPDF's ownK_TCPDF_EXTERNAL_CONFIG/K_TCPDF_THROW_EXCEPTION_ERRORconstants are wrapped indefined()checks to avoid conflicts with other plugins bundling TCPDF. - Fixed uninstall cleanup: rate-limit transients are now swept using the correct
estitofo_rl_key prefix (previously the obsoletewc_est_rl_prefix left orphaned rows inwp_options).
- Fixed mismatched "Tested up to" header: the plugin file header still said
Tested up to: 6.9whilereadme.txthad already been bumped to7.0. Plugin Check'smismatched_tested_up_torule (severity 7) was the only critical error remaining. Both files are now in sync at7.0(current WordPress major release). - Plugin Check
missing_direct_file_access_protection(severity 6) on all TCPDF vendor files: addeddefined('ABSPATH') || exit;immediately after the file-level docblock in each of the 31 PHP files undertcpdf/. The check ships expects every PHP file in a plugin to refuse direct access. Since TCPDF is only ever loaded from inside WordPress (whereABSPATHis defined), this guard never triggers and library behavior is unchanged.
- Renamed the main plugin file from
woocommerce-estimation-tool.phptoestimation-tool-for-woocommerce.phpso it matches the WordPress.org plugin slug. Plugin Check's "mismatched_plugin_slug" rule (severity 7) was the only critical-level error remaining; this fixes it. Internal references use__FILE__/plugin_basename(__FILE__)so no other code change was needed; the.pottranslation template's file-reference comments were updated to match. uninstall.phprewritten: all logic is now wrapped inestitofo_uninstall_cleanup()so no variables leak into the global scope.@unlink()calls replaced withwp_delete_file(). The@rmdir()call replaced with$wp_filesystem->rmdir()after loadingwp-admin/includes/file.php.class-estimation-pdf.php: everyerror_log()call is now tagged with// phpcs:ignore WordPress.PHP.DevelopmentFunctions.error_log_error_log(calls remain gated onWP_DEBUG, so they only fire in development). The three-linefopen/fread/fcloseblock inpng_has_alpha()is now a single boundedfile_get_contents($path, false, null, 0, 26)call.class-estimation-settings.phpimport handler:file_get_contents()of the uploaded JSON file replaced with$wp_filesystem->get_contents()via the WP_Filesystem API.class-estimation-mailer.php: the@file_put_contents()call that drops an emptyindex.htmlinto the tmp directory (to prevent directory listing) replaced with$wp_filesystem->put_contents().class-estimation-rest.php: added// phpcs:ignore WordPress.DB.SlowDBQuery.slow_db_query_tax_queryon the optionaltax_querybranch — the query is opt-in and capped byposts_per_page.- Public PDF endpoint (
Estitofo_Plugin::public_pdf): wrapped$_REQUESTreads in aphpcs:disable WordPress.Security.NonceVerification.Recommendedblock. The endpoint is HMAC-token-gated (validated viahash_equals()), so a nonce isn't applicable. - TCPDF vendor files: added a proper
/** */file-level docblock to the top of every PHP file undertcpdf/so Plugin Check'smissing_doc_commentrule (which doesn't honorphpcs:ignoreFile) is satisfied. The existingphpcs:ignoreFilepragma stays on the next line for PHPCS rules. TCPDF's own header comments below are unchanged.
- Plugin Check cleanup: renamed the six intl-tel-input retina image files from
flags@2x.png/flags@2x.webp/globe@2x.png/globe@2x.webp(and the_lightvariants) to dash-separated names (flags-2x.*,globe-2x.*). The@character isn't allowed in file names per WordPress.org's naming rules. CSS updated to reference the new names. - Removed four unused intl-tel-input assets (
globe_light.png/webp,globe_light@2x.png/webp) — never referenced by CSS or JS, removing them shrinks the plugin slightly. - Deleted the unused
tcpdf/config/tcpdf_config.phpfile (the 3.16.4 release switched TCPDF to load viaK_TCPDF_EXTERNAL_CONFIG = true, so this config file was no longer loaded by anything and was only triggering Plugin Check noise). - Added
// phpcs:ignoreFilepragma to the top of every PHP file undertcpdf/to signal "this is a third-party library, exempt from WordPress coding standards" to Plugin Check / PHPCS / WP.org's automated review. TCPDF's existing C-style file headers are preserved untouched on the lines below.
- Fixed "Constant K_TCPDF_THROW_EXCEPTION_ERROR already defined" PHP warning that appeared on the first PDF generation after the 6.11.3 upgrade. TCPDF 6.11.x's
config/tcpdf_config.phpdropped theif (!defined(...))guards on itsdefine()calls, so any constant the host plugin pre-defines (we setK_TCPDF_THROW_EXCEPTION_ERRORtotrueso PDF errors throw catchable exceptions instead ofdie()-ing) triggered a redefinition warning. Fixed by settingK_TCPDF_EXTERNAL_CONFIG = truebefore loading TCPDF —tcpdf_autoconfig.phpstill supplies all the samePDF_*/K_*defaults but through guarded checks. No TCPDF source files modified.
- Upgraded the bundled TCPDF library from 6.10.0 to 6.11.3 (latest stable). Brings PHP 8.5 deprecation fixes (curl_close, null array offset, imagedestroy, xml_parser_free), font-subsetting checksum fix, SVG rendering fix, image-on-footer fix, and the security/path-traversal fixes from 6.9.1–6.9.3. No API changes affect this plugin — generated PDFs are byte-identical aside from a
/Producerheader bump. - Bumped "Tested up to" to WordPress 6.9 (was 6.7) so the plugin shows up correctly in the WordPress.org plugin directory's compatibility filter.
- Trimmed the TCPDF bundle further: dropped the unused
images/(demo logo),tools/(CLI utilities),Makefile, andCHANGELOG.TXTfrom the shipped library — plugin remains under 4 MB.
- Settings page layout cleanup: the form is now rendered as a single unified card. Previously, tabs with multiple stacked
form-tableblocks (especially Pro Features) showed inconsistent padding, asymmetric borders, and section headings floating between cards. Section<h2>headings inside the form are now styled as proper section dividers, row spacing is even across all tabs, and the submit-button row integrates with the card via a hairline rule.
- Added an honest "Premium add-on" section to the readme description listing what the optional Pro add-on adds on top of the free plugin (WC order conversion, file uploads, reCAPTCHA, analytics, more PDF templates). Free plugin remains 100% fully functional on its own.
- Added one modest italicised line at the bottom of the Settings page mentioning the Pro add-on (hidden automatically when Pro is installed). Single sentence, single link — no buttons, no banners, no popups.
estitofo_pro_purchase_urlfilter so site owners / Pro can override the upsell URL.
- WordPress.org review revision — addresses all reviewer feedback:
- PDF and Notifications settings tabs are now fully functional in the free plugin (no locked UI, no Pro gating). All branding fields — company name, logo, footer, From name/email, customer email body with tokens, multiple admin recipients, PDF attachment — are available to every user.
- Renamed internal prefix from generic
wc_estimation_*/WC_Estimation_*to plugin-uniqueestitofo_*/Estitofo_*throughout: classes, defined constants, option keys, transients, AJAX action names, hook names, nonces, REST namespace, JS globals, shortcode ([estitofo_form]). The plugin slug and text domain stay the same. - Inline
<script>/<style>blocks in admin pages moved into a dedicatedassets/js/admin-settings.jsenqueued viaadmin_enqueue_scripts, and a new section inassets/css/admin-estimation.css. No more inline tags in PHP output. apply_filters('estitofo_save_settings', …)now receives an early-sanitized snapshot of the submitted array (every value run throughsanitize_text_field) instead of the raw$_POSTdata. Add-ons can re-sanitize their own keys as needed.- Added
Requires Plugins: woocommerceheader so WordPress can pre-check the WooCommerce dependency before activation. - Pro upsell UI removed from the free plugin — buyers who want Pro find it on the readme description; the free plugin no longer promotes paid features in the admin.
- Plugin header: Plugin URI and Author URI now differ — Plugin URI points to the WordPress.org listing for this plugin, Author URI stays as the author's homepage. Fixes the WP.org submission validation error.
- Pro upsell links centralised behind a single constant
Estitofo_Plugin::PRO_PURCHASE_URLso the destination is easy to swap when the Pro item is published. Default points to a CodeCanyon search URL (no 404) until the author updates it with the live CodeCanyon item URL.
- Slimmer footprint: stripped unused TCPDF font assets (CJK fonts, Arabic fonts, DejaVu TTF source folders, .z compressed font streams) — the plugin uses only the built-in PDF14 core fonts (Helvetica / Courier / Times / Symbol / ZapfDingbats), so 24 MB of unused font data has been removed. Plugin now downloads at ~1.5 MB instead of 6+ MB. PDF generation is byte-identical.
- New "Frontend Subheading" field on the General settings tab — the smaller line of text shown under the hero title is now fully editable. Leave it blank to hide the subheading entirely.
- Both heading and subheading are exposed as shortcode attributes (
[wc_estimation_tool heading="…" subheading="…"]) and Elementor widget controls. - General tab heading field gets a helpful description: "Big title shown above the estimation form. Leave blank to use the default."
- Search icon no longer overlaps the placeholder when themes override input padding. Forced
padding-left: 48px !importanton.wc-search-input(via a more specific.wc-estimation-wrapper .wc-search-inputselector), pinned the icon toleft: 16px / width: 18pxwith!important, and addedtext-indent: 0 !importantto neutralise theme rules. Net result: at least 14px clear space between the icon's right edge and the start of the placeholder text on every theme.
- Fixed: Default Phone Country setting (e.g.
bd) wasn't reflecting on the frontend becauseenqueue_assetswas reading the legacy standalone optionwc_estimation_default_countryinstead of the consolidatedwc_estimation_settingsarray. Now usesEstitofo_Options::get('default_country')so the saved value is honoured. - Default / Restrict Country settings are now native
<select>dropdowns with flag emoji, country name and dial code (e.g. 🇧🇩 Bangladesh (+880)) — no more typing ISO codes from memory. - Phone validator tightened back up: only the selected country is probed. Previous "OR across many countries" multi-check let invalid numbers slip through by accidentally matching a different country's pattern. New flow: try input as-typed → try leading-zero-stripped → both against the selected country only. Country mismatch (BD digits with US flag) is correctly rejected; valid BD
01851932715with BD flag is correctly accepted.
- Phone validator now runs the user's input through every libphonenumber call combination (
isValidNumber+isPossibleNumber, with raw input + E.164 + leading-zero-stripped form, with both upper- and lower-case ISO country codes) and accepts if ANY of them returns true. Bangladesh's leading-zero national format like01851932715now reliably validates against the BD flag because at least one of those combinations will recognise it. - Added an opt-in console diagnostic: append
?wcestphonedebug=1to the URL and every validation prints{input, country, accepted, tries: [...]}to the browser console — makes it trivial to see which library call accepted/rejected a given number.
- Phone validation rewritten to trust intl-tel-input + libphonenumber directly — no more layered custom logic. Switched
nationalModetotrueso the library expects users to type their local format (e.g.01851932715with the leading zero), which is what people actually do.isValidNumber()is now the single source of truth: green tick when it returns true, specific error message viagetValidationError()when false.
- Phone validation now correctly rejects country/number mismatches. Previous version had a "7–15 digits" universal fallback that accepted a Bangladesh number under the US flag. The new validator parses the input into E.164 (via
iti.getNumber()), verifies the resulting prefix matches the selected country's dial code, then asksisPossibleNumber()whether the full E.164 is plausible for that country. Valid01851932715with 🇧🇩 selected passes; the same digits with 🇺🇸 selected now fail.
- Phone validation: now correctly accepts national-prefix forms like Bangladesh's
01851932715. Previously libphonenumber'sisValidNumber()rejected the leading-zero national form even though it's how 99% of users actually type their number. The validator now layers four soft-pass checks:isValidNumber()→isPossibleNumber()→getValidationError()IS_POSSIBLE codes → digit-count plausibility (7–15). The wrong-country+xxprefix check remains a hard fail so the BD-on-US-flag case is still rejected.
- Phone validation: real-world-tolerant. libphonenumber's
isValidNumber()rejects perfectly-good numbers that aren't in the strictest canonical form (leading-zero national prefix, mobile/landline-only ranges, etc.). The validator now treats those as acceptable whengetValidationError()reportsIS_POSSIBLE(0) orIS_POSSIBLE_LOCAL_ONLY(4) — the field clears silently. Only real format errors (wrong country, too short, too long, invalid length) block submission. - Mismatched-country detection retained: typing
+xx…with a different flag selected still fails fast.
- Hotfix: the bundled
utils.jswas distributed as an ES module ending withexport default utils;. When loaded via a regular tag (as we and intl-tel-input both do) theexportkeyword threwUncaught SyntaxError: Unexpected token 'export', the globalwindow.intlTelInputUtilswas never set, and all country-aware phone validation silently degraded to the lenient fallback. Replaced the trailing 3 lines so the file works as a classic script: assignswindow.intlTelInputUtils = window.intlTelInputUtilsTemp.
- Phone validation no longer hangs on "Checking phone number…". The intl-tel-input
utils.jslibrary (country rules) is now pre-enqueued viawp_enqueue_scriptso it loads with the page instead of being lazy-loaded by intl-tel-input after init — eliminates the race window where validation got stuck waiting. - If
utils.jsis still blocked (CSP / hardened host), the validator now falls back to a 7–15 digit length check after 3 seconds instead of staying in "Checking…" forever.
- Phone validation: strict mismatched-country detection. Selecting a US flag and typing a Bangladesh number (or vice versa) now fails validation instantly with "Doesn't look like a valid United States number." Cross-checks
isValidNumber()againstintlTelInputUtils.getRegionCodeForNumber()and against any user-typed+xxprefix. - Form submit is now blocked while
utils.jsis still loading instead of falling through to a lenient length check — eliminates the race window where an invalid number could slip in before country rules arrived. - The submit button visually disables (greys out) while the phone field is invalid; the validation pill under the input shows a ✓ or ⚠ icon.
- Server-side: extra phone sanity check (7–15 digit length) and country-prefix verification when "Restrict to Country" is configured.
- PNG logos with transparent backgrounds now stay transparent in the generated PDF instead of being flattened onto white. When GD or Imagick is available TCPDF's _parsepng() extracts the alpha channel and embeds it as a PDF soft mask — your brand mark blends with the brand-coloured header band.
- The white-background flatten is only used as a true fallback when neither extension is available.
- Fixed: TCPDF crashed with
TypeError: in_array(): Argument #2 must be of type array, null givenand a chain of "Undefined property" warnings on PHP 8.2.x + opcache. Root cause: TCPDF 6.10 declares properties likeprotected $fontkeys = array();but never reassigns them in__construct(). On certain PHP/opcache combinations, the class-property default isn't materialised on the instance, so every later read returns NULL. We now run a reflection-based property pre-seed right afternew TCPDF()that force-initialisesfontkeys,numfonts,fonts,font_subsetting,pdfa_mode,isunicode,FillColor,DrawColor,TextColor,CoreFonts, and 9 other dependencies. The fix is contained inside our class — TCPDF itself isn't patched.
- Switched the default PDF font to core 'helvetica' instead of 'dejavusans'. Avoids loading external TTF font files — fixes the PHP 8.2+ "Undefined property: TCPDF::$fontkeys" warnings and the cascading
in_array(NULL)fatal that hit hosts without the GD extension. Non-Latin currency symbols still display correctly via the ISO-code fallback in money(). - Logo diagnostic now gives specific, actionable instructions when it detects "PNG with alpha + no GD + no Imagick" — the most common silent-failure cause. Tells the admin to either (a) upload a JPG / flat PNG, (b) enable the PHP
gdextension in php.ini, or (c) install Imagick. - Removed an experimental pure-PHP PNG alpha-strip that would have produced visually-corrupt logos.
- Logo: auto-backfills
logo_idfromlogo_urlon the PDF tab — older saved logos now work without re-uploading. - Logo embed: two-stage fallback — first tries raw-bytes via TCPDF's
@prefix, then falls back to a regular path-basedImage()call. If both fail, WP_DEBUG logs the exact stage that broke. - Logo diagnostic is now always visible (not hidden behind a "details" toggle) and shows: resolved path, readable flag, file size, extension, GD/Imagick availability, TCPDF loaded, safe-path, and bytes loaded.
- PDF logo: now embedded as raw image data via TCPDF's
@prefix instead of a filesystem path. This bypasses every open_basedir / mixed-slash / hardened-host issue that was preventing the logo from appearing. - New logo diagnostic readout in the Pro PDF tab — shows the resolved path, file size, and a precise reason if the logo can't be embedded.
- PDF design refinement: gradient-style header band (primary colour + accent triangle on the right + razor-thin lighter strip below), bigger total panel with a brand-coloured TOTAL stripe at the bottom, tighter spacing.
- Search icon: fixed overlap with placeholder text on themes that override input line-height. Input is now a fixed 50px tall with line-height matched for vertical centering, icon explicitly 20×20 with
!importantsize overrides.
- Fixed: search icon was clipping into the input on some themes — search input is now a fixed 48px tall with absolute-positioned 20px icon at 16px left inset.
- Admin: complete settings page redesign — modern card layout, branded heading badge, soft shadows, sticky tab styling, focus rings on inputs.
- Admin: submissions list — coloured status pills (using
:has()selector), animated modal with backdrop blur, customer info card in modal, cleaner action buttons. - Admin: Pro features showcase card at the top of the General tab — 8-feature grid with icons, shows "Pro license active" when licensed.
- Logo resolution: hardened
resolve_logo_path()with path normalization (collapses mixed slashes), 4-stage fallback (attachment ID → URL parse → reverse-resolve URL → strip thumb suffix), andWP_DEBUGerror_log diagnostics when resolution fails.
- Modern frontend redesign: hero card with gradient + brand-tinted "stardust", soft-shadow product cards, animated total counter, confetti on successful submit.
- Featured / popular products grid auto-renders below the search bar when the cart is empty.
- 3-step progress indicator (Browse → Your details → Done) advances visually as the customer moves through the flow.
- Country-aware phone validation — switching the flag re-validates against that country's format with a specific error message ("Number is too short for Bangladesh", etc.).
- Toast notifications replace inline yellow banners (success / warning / error variants).
- Sticky cart summary on mobile when the cart has items.
- PDF: complete redesign with brand-coloured header band, big "ESTIMATION" title, Bill-To card, zebra-striped product rows, total panel, and page numbers; product images render properly; PNG-with-alpha logos are auto-flattened; missing thumbnails get a vector placeholder; small quotations fit on a single page (no blank trailing page).
- Pro logo upload now stores attachment ID alongside the URL — PDF generation uses
get_attached_file()for rock-solid path resolution. Logo preview + Remove button in the admin. - Currency symbol HTML entities (e.g.
৳for BDT) now decode correctly; non-Latin symbols fall back to the ISO code (BDT, INR, THB, KRW, …) so amounts always render. - Settings → Tools tab gets a "How to add the form to a page" onboarding card with copy-to-clipboard shortcode, Elementor widget instructions (with auto-detection pill), and PHP template snippet.
- Save & resume: cart contents + contact fields persist to localStorage and survive a page refresh.
- Robust product search: simple / variable / grouped / external products all included; cascading fallbacks via
wc_get_products,name__like, SKU, and finallyWP_Query.
- Settings consolidated under a single
wc_estimation_settingsoption (one-time migration from v2.1 keys). - Added save & resume — customers email themselves a link that loads their estimation back in.
- Added admin workflow statuses (new / contacted / quoted / won / lost) with inline editing.
- Added admin dashboard widget (30-day rollup, latest leads, top products).
- Added CSV export from the admin list.
- Added REST API namespace
wc-estimation/v1(search, suggested, categories, save, resume) — front-end now uses REST with an admin-ajax fallback. - Product search now matches simple, variable, grouped and external products (was simple-only).
- PDF customization and Notifications are now Pro features. The free plugin still generates PDFs and sends a basic admin notification using defaults; the tabs in Settings show a Pro upgrade teaser when Pro is not active.
- Pro add-on integration: tab filter, settings-save filter, default-settings filter.
- Uninstall now also cleans up rate-limit transients and tmp PDF directory.
- Renamed to "Estimation Tool for WooCommerce" for trademark compliance.
- Added a Settings page for company name, logo, footer note, and store list (PDF branding is no longer hard-coded).
- International phone validation via intl-tel-input (no longer limited to Bangladesh); default and restricted country are configurable.
- Prefixed all AJAX action names with
wc_estimation_to avoid collisions. - Switched admin PDF download to
admin-post.phpPOST with nonce in body. - Added honeypot and per-IP rate limiting to public AJAX endpoints.
- Whitelisted list-table sort columns; sanitized all
$_REQUESTreads. - Replaced raw
date()calls withdate_i18n()/gmdate(). - Removed debug
console.log; internationalized all frontend strings viawp_localize_script. - Replaced direct HTML interpolation in JS with safe DOM construction (XSS hardening).
- Declared compatibility with WooCommerce HPOS and Cart/Checkout Blocks.
- Added Elementor minimum-version guard (3.5+).
- Added DB schema version option for forward-compatible migrations.
- Uninstall now removes plugin options as well as the data table.
- Improved data sanitization and security.
- Added separate admin JS/CSS assets.
- Added suggested product support for the frontend.
- Added uninstall cleanup and a WordPress readme file.