NoonElite Audit Engine vs Post Author IP

NoonElite Audit Engine lets you build professional, branded audit quizzes that engage your visitors, score their responses, and capture qualified leads — all without writing code. Core Features (Free) Unlimited audit quizzes with multi-category scoring Customisable branding (accent colours, logo, agency name) Shortcode embedding: [noon_audit type="your-slug"] Lead capture with GDPR-compliant consent and marketing opt-in Risk-band scoring (Critical / High / Moderate / Low) Honeypot anti-spam on all forms Full lead management dashboard with pagination Quiz theme mode (auto-detect, force dark, or force light) Glass morphism background effect option Branded “Powered by” credit (opt-in only) Pro Features (available via NoonElite.com) Salesforce CRM integration (auto-sync leads as Salesforce Leads) HubSpot CRM integration (auto-sync leads as HubSpot Contacts) Cloudflare Turnstile anti-spam (invisible CAPTCHA for lead forms) CSV lead export Bulk CRM re-sync for missed leads Source Code This plugin uses React in the frontend to process forms and score leads interactively. To comply with WordPress.org guidelines, the uncompiled source code for these features is bundled directly within the plugin structure. You can find the uncompiled frontend code and package configuration inside the frontend/ directory. To build the project development assets for review: 1. Navigate to the frontend directory: cd frontend/ 2. Install dependencies: npm install 3. Compile the production assets: npm run build The built assets will map directly to the files present in frontend/dist/. External Services This plugin connects to the following third-party services under certain conditions. Please review the details below. Cloudflare Turnstile (Pro) When Cloudflare Turnstile is configured in Settings → Security, the plugin uses it to verify form submissions as a spam prevention measure. A challenge token is sent to the Cloudflare Turnstile API for server-side verification before a lead is saved. Service: Cloudflare Turnstile — https://www.cloudflare.com/products/turnstile/ Data sent: Challenge response token and visitor IP address When: On every lead form submission (if Turnstile keys are configured) Terms of Service: https://www.cloudflare.com/website-terms/ Privacy Policy: https://www.cloudflare.com/privacypolicy/ Salesforce API (Pro) When Salesforce integration is enabled in Settings → Salesforce Integration, the plugin authenticates with the Salesforce REST API using OAuth 2.0 client credentials and creates Lead records for each captured lead. Service: Salesforce — https://www.salesforce.com Data sent: Lead name, email, company, audit score, risk band, and category scores When: After a lead is submitted on the front end, or during a manual bulk sync from the admin Leads page Terms of Service: https://www.salesforce.com/company/legal/agreements/ Privacy Policy: https://www.salesforce.com/company/privacy/ HubSpot API (Pro) When HubSpot integration is enabled in Settings → HubSpot Integration, the plugin uses the HubSpot CRM API to create or update Contact records for each captured lead. Service: HubSpot — https://www.hubspot.com Data sent: Lead name, email, company, audit score, risk band, and category scores When: After a lead is submitted on the front end, or during a manual bulk sync from the admin Leads page Terms of Service: https://legal.hubspot.com/terms-of-service Privacy Policy: https://legal.hubspot.com/privacy-policy Freemius This plugin uses the Freemius SDK for license management and to offer optional premium upgrades. Freemius collects non-sensitive usage data (with opt-in consent) to help improve the product. Service: Freemius — https://freemius.com Terms of Service: https://freemius.com/terms/ Privacy Policy: https://freemius.com/privacy/

This plugin records the IP address of the original post author when a post first gets created. The admin listing of posts is amended with a new “Author IP” column that shows the IP address of the author who first saved the post. The plugin is unable to provide IP address information for posts that were created prior to the use of this plugin. Links: Plugin Homepage | Plugin Directory Page | GitHub | Author Homepage Hooks The plugin is further customizable via four filters. Typically, code making use of filters should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain). c2c_show_post_author_ip_column (filter) The ‘c2c_show_post_author_ip_column’ filter allows you to determine if the post author IP column should appear in the admin post listing table. Your hooking function can be sent 1 argument: Argument : $show_column (bool) Should the column be shown? Default true. Example: /** * Don't show the post author IP column except to admins. * * @param bool $show_column Should the column be shown? Default true. * @return bool */ function post_author_ip_column_admin_only( $show ) { if ( ! current_user_can( 'manage_options' ) ) { $show = false; } return $show; } add_filter( 'c2c_show_post_author_ip_column', 'post_author_ip_column_admin_only' ); c2c_get_post_author_ip (filter) The ‘c2c_get_post_author_ip’ filter allows you to customize the value stored as the post author IP address. Your hooking function can be sent 2 arguments: Arguments : $ip (string) The post author IP address. $post_id (int) The post ID. Example: /** * Store all IP addresses from local subnet IP addresses as the same IP address. * * @param string $ip The post author IP address. * @param int $post_id The post ID. * @return string */ function customize_post_author_ip( $ip, $post_id ) { if ( 0 === strpos( $ip, '192.168.' ) ) { $ip = '192.168.1.1'; } return $ip; } add_filter( 'c2c_get_post_author_ip', 'customize_post_author_ip', 10, 2 ); c2c_get_current_user_ip (filter) The ‘c2c_get_current_user_ip’ filter allows you to customize the current user’s IP address, as used by the plugin. Your hooking function can be sent 1 argument: Argument : $ip (string) The post author IP address. Example: /** * Overrides localhost IP address. * * @param string $ip The post author IP address. * @param int $post_id The post ID. * @return string */ function customize_post_author_ip( $ip, $post_id ) { if ( 0 === strpos( $ip, '192.168.' ) ) { $ip = '192.168.1.1'; } return $ip; } add_filter( 'c2c_get_post_author_ip', 'customize_post_author_ip', 10, 2 ); c2c_post_author_ip_allowed (filter) The ‘c2c_post_author_ip_allowed’ filter allows you to determine on a per-post basis if the post author IP should be stored. Your hooking function can be sent 3 arguments: Arguments : $allowed (bool) Can post author IP be saved for post? Default true. $post_id (int) The post ID. $ip (string) The post author IP address. Example: /** * Don't bother storing localhost IP addresses. * * @param bool $allowed Can post author IP be saved for post? Default true. * @param int $post_id The post ID. * @param string $ip The post author IP address. * @return string */ function disable_localhost_post_author_ips( $allowed, $post_id, $ip ) { if ( $allowed && 0 === strpos( $ip, '192.168.' ) ) { $allowed = false; } return $allowed; } add_filter( 'c2c_post_author_ip_allowed', 'disable_localhost_post_author_ips', 10, 3 );