merlinpa1969 Posted November 21, 2013 Share Posted November 21, 2013 Since the upgrade when I answer a support ticket I keep getting the following The status of this ticket has changed since you started replying which could indicate another staff member has already replied. Are you sure you still want to submit this reply? I am the ONLY one logged in, Browser cache is cleared and template_c has been dumped Not a real big deal just a pain in the butt, 0 Quote Link to comment Share on other sites More sharing options...
ckh Posted November 21, 2013 Share Posted November 21, 2013 I get this on all three whmcs instances I applied the latest update to. Came here to see if I was the only one, apparently not... 0 Quote Link to comment Share on other sites More sharing options...
leckley Posted November 21, 2013 Share Posted November 21, 2013 Same issue here as well... 0 Quote Link to comment Share on other sites More sharing options...
DigitalEnigma Posted November 21, 2013 Share Posted November 21, 2013 Hi, I opened a ticket for this, below is the fix I was provided:- Open your /admin/templates/*your active template*/viewticket.tpl file and make the following modification: FIND: &blocksender=true REPLACE WITH: &blocksender=true&token={$csrfToken} 0 Quote Link to comment Share on other sites More sharing options...
SeanP Posted November 21, 2013 Share Posted November 21, 2013 Can this thread be made into a sticky? 0 Quote Link to comment Share on other sites More sharing options...
sol2010 Posted November 22, 2013 Share Posted November 22, 2013 (edited) Also seeing this issue - along with "Invalid Token" appearing when I click into support ticket to reply. The above fix did NOT work for me. Clearing browser cache & Cookies and emptying templates_c folder on server did NOT solve the issue either. Time to revert back to 5.212 Other threads on similar issues (seems like these are not being acknowledged). http://forum.whmcs.com/showthread.php?81894-Invalid-token-error-after-upgrade-to-5-2-13-patch [annoyingly has been closed] http://forum.whmcs.com/showthread.php?81939-Upgraded-to-5-2-13-now-search-box-doesn-t-work-in-top-right-corner http://forum.whmcs.com/showthread.php?81938-update-from-5-2-12-to-5-2-13-error-WHOIS Edited November 22, 2013 by sol2010 0 Quote Link to comment Share on other sites More sharing options...
Chris74 Posted December 16, 2013 Share Posted December 16, 2013 Also seeing this issue - along with "Invalid Token" appearing when I click into support ticket to reply.The above fix did NOT work for me. Clearing browser cache & Cookies and emptying templates_c folder on server did NOT solve the issue either. Time to revert back to 5.212 Other threads on similar issues (seems like these are not being acknowledged). http://forum.whmcs.com/showthread.php?81894-Invalid-token-error-after-upgrade-to-5-2-13-patch [annoyingly has been closed] http://forum.whmcs.com/showthread.php?81939-Upgraded-to-5-2-13-now-search-box-doesn-t-work-in-top-right-corner http://forum.whmcs.com/showthread.php?81938-update-from-5-2-12-to-5-2-13-error-WHOIS We recently updated from 5.2.12 to 5.2.14 and soon after I started receiving missing token errors, search box problems etc. I fully cleared my browser (firefox) from the history menu and everything is fine for me. My colleague had these issues with the support tickets as above and she cleared her browser cache in Firefox from Tools > Options > Advanced > Network. This didn't resolve the problem. Clearing everything - cookies - cache - offline data - etc resolved the issue. So I would advise that anyone who is experiencing this problem simply has not properly cleared their browser. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.