Content not updating after hotfix 13.0.187

Matthew Stone asked on August 6, 2025 22:06

Hello after upgrading to Kentico v13.0.187, my client is experiencing an issue where when the make any edit on a page as simple as adding a period that the content doesn't update.

Only after a few times of saving does the change seem to take an effect. Then to role the change back, they have to refresh the page several times for the change to stick. I replicated the same thing locally on the project as well. I am not seeing any errors in the kentico error log related to this issue. I am not seeing any console errors either related to this issue. This only seems to have become an issue after the hotfix upgrade. The hotfix upgrade scripts were applied to the database as well.

The admin site and live site are on different urls, and both urls are running on https with the certs trusted. I have tried to reassigned the macros as well. I have also restarted the application, cleared the cache, and recycled the app pool.

I ran this script: SELECT * FROM CMS_SettingsKey WHERE KeyName IN ('CMSHotfixDataVersion', 'CMSHotfixVersion', 'CMSDataVersion', 'CMSDBVersion') to check the hotfix versions in the DB both on Prod and Local. While I did have a mismatch locally, there was no mismatch on prod and I am able to replicate the same issue on prod and locally. I checked the nuget packages locally which were deployed to prod and they are all matching the hotfix version of 187.

Any suggestions on what I can check for to see why they are having saving issues?

Recent Answers

vasu yerramsetti answered on August 8, 2025 09:23

Your edits only applying after repeated saves and refreshes—strongly point to either incomplete deployment or a file/code mismatch between environments. Redeploying all files cleanly and ensuring the hotfix fully applied should be your primary next step.

Deployment Consistency: issue where partial or incomplete deployment of files caused saving problems. Make sure every file from the hotfix (UI, binaries, scripts, etc.) was fully applied. If possible, redeploy all files from a known-good local build to both environments. Reference https://devnet.kentico.com/questions/x13-form-builder-not-allowing-updates
Hotfix Application Integrity: Even though the database version matches and nuget packages align, it's possible some hotfix steps didn’t fully apply, especially if custom files or old deployment modes interfere. Recommendation- Re-run the hotfix utility or installation process, confirm that all parts (code, files, SQL scripts) applied successfully, and ensure deployment/source control mode files were handled correctly.
Browser & Macro Layer Checks: Earlier versions had issues related to macro signing or caching. While your problem differs slightly, it's worth checking macro-related behaviors or signatures. Recommendation - Clear browser cookies/caches, test in incognito, and ensure macros are signed properly—or consider re-signing them.

0 votesVote for this answer Mark as a Correct answer

Matthew Stone answered on August 19, 2025 15:51

Development seems to be working fine on the CMS side with saving in the current hotfixed solution. I copied the CMS files from dev over to prod hoping that it would fix the issue. At first it was working, with no issue. But then the save issue started happening again. To be clear, when first clicking save the change appears to stick but then when you refresh and go back the edit is gone. After I moved the CMS files over from dev to prod the two errors I noticed were was one that was being thrown in the event log which is this.

Message: Exception of type 'System.Web.HttpUnhandledException' was thrown.

Exception type: System.Web.HttpUnhandledException Stack trace: at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Message: The CSRF hidden field was missing.

The other is in dev console which is this "/CMSScripts/WebComponents/components.js net::ERR_ABORTED 404 (Not Found)". I looked in this folder that I brought over from dev and there is a file in there labeled "components.esm.js" I also looked in a DancingGoat install to make sure there wasn't a difference version of the file without the .esm part and it was the same file.

So at this point im not sure if its a file issue or a db issue, any suggestions?

0 votesVote for this answer Mark as a Correct answer