How to Fix Helpful Voting Not Saving

SoftwareRoad Knowledge Base can display a simple Was this article helpful? question at the end of published articles.

Visitors can select Yes or No, and the anonymous totals are shown under:

Knowledge Base > Analytics

If the buttons appear but the vote does not save, the cause is usually an inactive licence, an unpublished article, a disabled setting, a JavaScript error, a blocked AJAX request or an expired WordPress security nonce caused by caching.

Check the SoftwareRoad Knowledge Base licence

Helpful Voting requires an active SoftwareRoad Knowledge Base Monthly or Yearly licence.

Open:

Knowledge Base > Licence

Confirm that the licence status shows as active.

If the licence is inactive, expired or cannot be verified, public knowledge base features may not work normally.

Reactivate the licence

If the licence is not active:

1. Enter the purchase email used for the subscription.
2. Enter the SoftwareRoad Knowledge Base product key.
3. Remove any spaces before or after the details.
4. Select Activate Licence.
5. Clear the public website cache.
6. Test Helpful Voting again.

The purchase email must match the email connected to the active subscription.

Check that Helpful Voting is enabled

Open:

Knowledge Base > Settings

Find the Helpful Voting or Article Feedback setting.

Depending on the installed version, it may appear under:

• Articles
• Features
• Analytics

Enable Helpful Voting and select Save Changes.

Then open a published knowledge base article while signed out.

Confirm the feedback section appears

Scroll to the bottom of the article.

You should see wording similar to:

Was this article helpful?

with Yes and No options.

If the section does not appear at all, check:

• Helpful Voting is enabled
• The article is published
• The licence is active
• The article template has not been overridden
• The public page cache has been cleared

Check that the article is published

Helpful Voting is intended for publicly available knowledge base articles.

Open:

Knowledge Base > All Articles

Check that the affected article has the status:

Published

A draft, private, scheduled or trashed article may not accept normal public feedback.

Test the article while signed out

WordPress administrators may see a different version of the page from normal visitors.

Open the article in a private browser window.

This helps you test without:

• The WordPress admin toolbar
• Administrator permissions
• Logged-in page caching
• Editor preview behaviour
• User-role display conditions

Select Yes or No and wait for the confirmation response.

Do not test a preview page

A WordPress preview URL is temporary and may not behave like the final published article.

Publish or update the article, then use its normal public URL.

A preview address may contain parameters such as:

preview=true

Use the permanent article URL instead.

Check whether the vote confirmation appears

After selecting Yes or No, the feedback section should respond.

Depending on the current design, it may:

• Display a thank-you message
• Replace the voting buttons
• Confirm that the response was recorded
• Prevent another immediate selection

If nothing changes, the browser may not be sending the request.

If an error message appears, note its exact wording before refreshing the page.

Check Helpful Feedback Analytics

After submitting a test vote:

1. Return to your normal WordPress window.
2. Open Knowledge Base > Analytics.
3. Find the Helpful Feedback section.
4. Refresh the page.
5. Check the affected article.

Look for an increase in either the positive or negative total.

The Analytics dashboard may need to be refreshed before the latest vote appears.

Use a fresh article for testing

If you have already tested the same article several times, use another published article or a separate private browser session.

This helps rule out browser storage or previous feedback behaviour affecting the test.

Do not repeatedly vote on live articles simply to increase their totals.

Check JavaScript is working

Helpful Voting uses JavaScript to send the visitor’s response without reloading the entire article.

If JavaScript is broken, the buttons may appear but do nothing.

Open the browser developer tools and select the Console tab.

Then select Yes or No again.

Look for red error messages.

Common JavaScript problems

Helpful Voting can be affected by:

• A JavaScript error from another plugin
• A broken theme script
• Deferred script loading
• Delayed JavaScript
• Combined JavaScript files
• Aggressive minification
• Missing jQuery
• Content Security Policy restrictions
• A script removed as unused

One error elsewhere on the page can sometimes stop later scripts from running.

Test without JavaScript optimisation

Temporarily disable settings such as:

• Delay JavaScript
• Defer JavaScript
• Combine JavaScript
• Remove unused JavaScript
• Minify JavaScript
• Delay scripts until interaction

Clear every performance cache afterwards.

Test the article again in a new private browser window.

If voting begins working, exclude the relevant SoftwareRoad Knowledge Base scripts from that optimisation.

Check the browser Network tab

Open the browser developer tools and select the Network tab.

Select Yes or No.

Look for a new request sent to WordPress, commonly through:

admin-ajax.php

Select the request and check its status.

Common AJAX response codes

Possible response codes include:

• 200 for a successful request
• 400 for invalid request data
• 403 when the request is blocked or rejected
• 404 when the AJAX address cannot be found
• 500 for a server or PHP error
• 502 or 503 for a temporary hosting problem

The response body may provide more information about why the vote was not saved.

A 403 error when voting

A 403 response normally means the request was rejected.

Possible causes include:

• Security plugin restrictions
• Hosting firewall rules
• Cloudflare protection
• Anonymous POST requests being blocked
• Rate limiting
• Bot protection
• Invalid or expired WordPress nonce
• Country or IP restrictions

Review the website security logs immediately after running the test.

Check WordPress security plugins

Security tools can mistake article feedback for an unwanted anonymous form submission.

Review settings related to:

• Anonymous AJAX requests
• admin-ajax.php
• WordPress nonces
• Bot detection
• Spam protection
• Rate limits
• Firewall rules
• POST request filtering

Do not permanently disable website security.

Temporarily test the relevant rule, then create a narrow exception if it is confirmed as the cause.

Check hosting firewall logs

Some hosting providers use a web application firewall outside WordPress.

The firewall may block the feedback request before it reaches the plugin.

Ask the host to check for blocked requests to:

wp-admin/admin-ajax.php

Provide the approximate date and time of the failed test.

You do not need to send your SoftwareRoad product key.

Check Cloudflare security events

If the website uses Cloudflare, review:

• Security Events
• Managed rules
• Bot protection
• Rate limiting
• Custom firewall rules
• Browser challenges

Run a test vote and look for a matching blocked request.

Use a specific exception rather than disabling protection across the whole website.

Expired WordPress nonce caused by caching

WordPress uses security nonces to verify some public AJAX requests.

A nonce is only valid for a limited period.

If a cached article page is served for too long, the page may contain an expired nonce.

The voting buttons still appear, but WordPress rejects the saved response.

Signs of an expired nonce

An expired nonce may be the cause when:

• Helpful Voting worked previously
• Clearing the page cache temporarily fixes it
• Voting fails only for signed-out visitors
• The AJAX request returns 403
• The response mentions an invalid request
• The page has been cached for a long period

The article itself may look completely normal.

Clear the affected article cache

Clear the cache for the exact article being tested.

Also clear:

• WordPress page cache
• Hosting cache
• Server cache
• CDN cache
• Object cache
• Browser cache

Then open the article in a completely new private browser window.

Do not reuse a browser tab that loaded the old cached page.

Reduce long page-cache lifetimes

If voting works after clearing the cache but stops again later, review the public page cache duration.

A very long cache lifetime can continue serving an old security nonce.

Possible solutions include:

• Shortening the page cache duration
• Automatically clearing article cache regularly
• Excluding the feedback nonce from full-page caching
• Excluding knowledge base article pages where necessary

Use the least disruptive solution for your website.

Do not cache AJAX requests

The feedback request itself should reach WordPress.

Check that your caching system does not cache:

• admin-ajax.php
• POST requests
• AJAX responses
• Dynamic JSON responses
• Requests containing WordPress nonces

Caching a POST response can prevent genuine votes from being processed correctly.

A 404 error when voting

A 404 response may mean the AJAX request is being sent to the wrong address.

Check:

Settings > General

Review:

• WordPress Address
• Site Address

Both should use the correct live website domain and HTTPS address.

Problems can occur after moving between:

• HTTP and HTTPS
• www and non-www
• Staging and live domains
• Temporary and final hosting addresses

Check redirects affecting admin-ajax.php

A redirect rule should not send WordPress AJAX requests to:

• The homepage
• A login page
• Another domain
• A security challenge page
• A cached copy

Review redirects in:

• WordPress plugins
• Hosting settings
• Cloudflare rules
• Server configuration
• Custom theme code

The AJAX request needs to reach the current WordPress installation directly.

A 500 error when voting

A 500 response normally means a PHP or database error occurred while saving the feedback.

Check:

• WordPress debug log
• Hosting error log
• PHP error log
• Database errors
• PHP memory limit
• Recent plugin updates
• Recent theme changes

Note the exact time of the vote so the matching log entry is easier to find.

Check WordPress Site Health

Open:

Tools > Site Health

Review any warnings relating to:

• REST API
• Loopback requests
• Database
• PHP
• HTTPS
• Scheduled events
• Server communication

Not every Site Health warning affects Helpful Voting, but it can reveal wider WordPress problems.

Check the feedback database data

SoftwareRoad Knowledge Base saves anonymous article feedback so it can be displayed in the Analytics dashboard.

If the public request succeeds but the totals do not change, WordPress may be unable to write the result.

Possible causes include:

• Restricted database permissions
• A database error
• A damaged analytics table
• An incomplete website migration
• An incomplete backup restore
• A server running in read-only mode

Database checks should be completed by an experienced administrator or developer.

Check after moving the website

If Helpful Voting stopped after a migration:

1. Confirm the plugin is active.
2. Confirm the licence is active.
3. Save the Helpful Voting setting again.
4. Resave WordPress permalinks.
5. Clear all caches.
6. Test while signed out.
7. Check PHP and database logs.
8. Confirm all plugin database data was included in the migration.

The article content may work even when feedback storage was not copied correctly.

Check after restoring a backup

A restored backup may contain:

• Old plugin settings
• An inactive saved licence
• Cached article pages
• Old security nonces
• Older feedback totals
• Missing analytics data

Save the plugin settings again and clear all caches before testing.

Check database permissions

The WordPress database user normally needs permission to insert and update plugin data.

A read-only database can allow visitors to read articles while preventing votes from being saved.

Ask the hosting provider to check whether the WordPress database user has normal write permissions.

Do not share database passwords publicly.

Do not edit analytics data manually

Avoid manually adding, deleting or changing helpful vote values in the WordPress database.

This can cause:

• Incorrect totals
• Damaged records
• Missing article relationships
• Database errors
• Unreliable Analytics reports

Create a full backup before any database investigation.

Check the article ID has not changed

Helpful feedback is connected to the WordPress knowledge base article.

If an article was deleted and recreated, the new version has a different WordPress post ID.

Old feedback totals may remain connected to the previous article rather than the recreated one.

Avoid recreating articles solely to fix a voting issue.

Check the article has not been moved to Trash

A trashed article should not receive public votes.

Open:

Knowledge Base > All Articles

Check both published content and Trash.

Restore or republish the correct article if needed.

Check the article is not unlisted

An unlisted article can still be available through its direct URL.

Helpful Voting may still appear on a directly accessed unlisted article, depending on the current article settings.

However, the article remains excluded from normal search and category discovery.

Unlisted status is not normally the main cause of a vote failing to save, but confirm that you are testing the intended article.

Check the article template

A theme or page builder may override the standard SoftwareRoad Knowledge Base article output.

This can result in:

• Buttons appearing twice
• Duplicate element IDs
• Missing JavaScript data
• Feedback appearing outside the article wrapper
• Scripts not loading
• Buttons being covered by another element

Test using the standard knowledge base article template where possible.

Duplicate feedback sections

If Helpful Voting appears twice on one article, check whether it was added:

• Automatically by SoftwareRoad Knowledge Base
• Manually inside the article content
• Through a theme template
• Through a page builder
• Through a reusable block
• Through custom PHP code

Remove the duplicate copy.

Only the plugin-generated voting section should normally be used.

The buttons cannot be selected

The buttons may be covered by another element.

Possible causes include:

• Cookie banners
• Sticky footers
• Invisible page-builder containers
• Overlapping sidebars
• Custom CSS
• Mobile navigation overlays

Use browser developer tools to inspect the button.

Temporarily disable custom CSS to test whether the element is being blocked.

The button changes but Analytics does not

If the public page displays a successful confirmation but the Analytics total does not change:

1. Refresh the Analytics page.
2. Check the correct article.
3. Check whether the vote was grouped with an existing total.
4. Clear the WordPress administration object cache.
5. Check database and PHP logs.
6. Test another article.

The public confirmation should only be trusted after confirming the request received a successful response.

Analytics may need refreshing

The Helpful Feedback dashboard does not necessarily update while it remains open.

Reload the Analytics screen after each test.

Check:

• Yes total
• No total
• Overall feedback percentage
• Correct article title
• Correct article row

The wrong article total changes

This can happen if:

• A page builder duplicated article markup
• A cached page contains old article data
• The article was duplicated incorrectly
• Custom code changed the article ID
• The public URL redirects to another article

Check the article URL and its WordPress post ID.

Clear all page caches.

The vote saves only while signed in

This normally suggests anonymous requests are being blocked.

Check:

• Security plugin rules
• Hosting firewall
• Anonymous AJAX access
• Cloudflare challenges
• Expired nonces on public cached pages

Helpful Voting is intended for normal visitors, so testing while signed out is important.

The vote saves only while signed out

This may be expected if logged-in editors are treated differently, or it may be caused by an administrator-specific JavaScript conflict.

Test with:

• A logged-out private window
• A normal subscriber account
• An administrator account

The public visitor experience is the most important test.

Voting works on one article but not another

Compare the affected articles.

Check:

• Published status
• Article template
• Public URL
• Page cache age
• Custom blocks
• Custom CSS
• Duplicate feedback markup
• Redirects
• Article ID

Clear the cache for the individual broken article.

Voting fails on every article

If every article is affected, check shared systems first:

• Active licence
• Helpful Voting setting
• JavaScript files
• AJAX requests
• Security rules
• Page caching
• Database permissions
• Plugin conflicts

This normally points to a site-wide issue rather than one article.

Voting works on desktop but not mobile

Check:

• Mobile cache
• Responsive overlays
• Cookie banners
• Sticky navigation
• Touch event errors
• Mobile-only JavaScript optimisation
• Buttons being too close together
• Page-builder mobile visibility rules

Test on more than one mobile browser where possible.

Voting works in one browser only

A browser extension may block the request.

Test:

• Another browser
• Private browsing
• Extensions disabled
• Another device
• Another internet connection

Privacy or ad-blocking extensions may block scripts or AJAX requests.

If the problem only affects one browser setup, the website may be working normally.

Check Content Security Policy

A strict Content Security Policy may block:

• Plugin JavaScript
• Inline configuration
• AJAX requests
• External dependencies

Open the browser Console and look for Content Security Policy errors.

Update the policy carefully to allow only the required website resources.

Do not weaken the full policy unnecessarily.

Check cookie and consent tools

Some cookie or privacy tools delay JavaScript until consent is given.

If the SoftwareRoad Knowledge Base feedback script is incorrectly classified as marketing or advertising, Helpful Voting may not work until the visitor accepts optional cookies.

Review the consent tool’s script categories and blocking rules.

Anonymous article feedback may still need to be described in your privacy policy, but the technical classification depends on your own website setup and legal requirements.

Helpful Voting and privacy

Helpful Voting is designed to collect anonymous Yes and No totals.

Visitors do not need to provide:

• Name
• Email address
• Customer account
• Written comment

The data helps you understand whether an article appears to solve the visitor’s problem.

Your hosting, security and analytics services may separately keep technical server information.

Do not use Helpful Voting as the only quality measure

A Yes or No total provides useful guidance, but it does not explain why someone selected No.

Compare feedback with:

• Article views
• Search Analytics
• No-result searches
• Support emails
• Recent product changes
• Common customer questions

A highly viewed article with poor feedback should normally be reviewed first.

Helpful Voting worked before but stopped

Review recent changes such as:

• New caching configuration
• Security plugin update
• Cloudflare rule change
• Theme update
• Plugin update
• PHP update
• Website migration
• Backup restore
• Licence renewal problem
• JavaScript optimisation change

Reverse or test the recent change on a staging website where possible.

Test for a plugin conflict

Use a staging copy of the website.

1. Keep SoftwareRoad Knowledge Base active.
2. Deactivate other plugins.
3. Open an article while signed out.
4. Submit a test vote.
5. Check Helpful Feedback Analytics.
6. Reactivate plugins one at a time.
7. Repeat the test.

Pay particular attention to:

• Security plugins
• Caching plugins
• JavaScript optimisation plugins
• Cookie consent tools
• Database optimisation tools
• Form protection plugins

Test for a theme conflict

On staging, temporarily switch to a standard WordPress theme.

Open a published knowledge base article and test Helpful Voting.

If it works, review the original theme for:

• JavaScript errors
• Article template overrides
• Duplicate IDs
• Content filters
• Custom AJAX rules
• Overlapping page elements

Reinstall the plugin files

If scripts are missing or damaged:

1. Create a full WordPress backup.
2. Download a clean copy of SoftwareRoad Knowledge Base.
3. Replace or reinstall the plugin files.
4. Activate the plugin.
5. Check the licence.
6. Confirm Helpful Voting is enabled.
7. Clear all caches.
8. Test a published article.

Do not uninstall plugin data unless you understand what will be removed.

A practical Helpful Voting test

Use this process to test the complete feature:

1. Confirm the Monthly or Yearly licence is active.
2. Confirm Helpful Voting is enabled.
3. Choose a published article.
4. Note its current Yes and No totals.
5. Clear the article page cache.
6. Open a new private browser window.
7. Load the public article URL.
8. Select Yes or No once.
9. Wait for the confirmation.
10. Check the browser Network request.
11. Open Knowledge Base > Analytics.
12. Refresh Helpful Feedback.
13. Confirm the relevant total increased.

If the request fails, record its HTTP status and response message.

Contact SoftwareRoad support

Contact support when:

• The licence is active
• Helpful Voting is enabled
• The article is published
• The buttons appear
• A signed-out test was completed
• Cache and security settings were checked
• The AJAX request still fails
• The vote confirms publicly but no total is saved

Include:

• Website address
• Affected article URL
• SoftwareRoad Knowledge Base version
• WordPress version
• PHP version
• Browser used
• Exact behaviour after selecting Yes or No
• AJAX response code
• Browser console errors
• Relevant PHP or database errors
• Caching plugin or service
• Security plugin or firewall in use
• Whether the issue affects every article

Do not publicly share your full product key or WordPress password.

Helpful Voting troubleshooting checklist

Before contacting support, check that:

• The Monthly or Yearly licence is active
• Helpful Voting is enabled
• Settings were saved
• The article is published
• The normal public URL is being tested
• The test is not using a preview page
• Testing was completed while signed out
• The feedback buttons are visible and selectable
• JavaScript errors have been checked
• The AJAX request reaches admin-ajax.php
• Security plugins are not blocking anonymous requests
• Hosting firewall and Cloudflare logs have been reviewed
• The article cache has been cleared
• The page is not serving an expired nonce
• AJAX POST requests are not being cached
• JavaScript optimisation has been tested
• WordPress and Site addresses are correct
• PHP and database errors have been checked
• The WordPress database can save new data
• Website migrations or backup restores have been considered
• Duplicate feedback sections have been removed
• Plugin and theme conflicts have been tested on staging
• The Helpful Feedback dashboard was refreshed

Helpful Voting should save normally once the article is published, the licence is active and the browser can send a valid AJAX request to WordPress without being blocked by caching or security rules.