Blueberry3.14 Posted November 29, 2013 Share Posted November 29, 2013 Version 5.2.13 and version 5.2.14 is a mistake! It's a disaster! User older versions! WHMCS does not seem bother fixing the errors of the new version. Our business is also at hold trying to fix all the new bugs and problems!!!! What the hell is going on?????? Specifics on what exactly you did and what is wrong would be good if you're looking for help... 0 Quote Link to comment Share on other sites More sharing options...
openmind Posted November 29, 2013 Share Posted November 29, 2013 Also let us know if you bothered to read this thread and tested on a dev install first. 0 Quote Link to comment Share on other sites More sharing options...
kobus4u Posted November 29, 2013 Share Posted November 29, 2013 Well if my other threats have not been deleted.... And I have read through all and tested everything. We cannot create new clients, add, change anything, it always says invalid token!?? I have also read through other threats with the same problems but whmcs does not seems to bother with the problem everyone have with the invalid token. This is serious as we are losing money everyday!! 0 Quote Link to comment Share on other sites More sharing options...
openmind Posted November 29, 2013 Share Posted November 29, 2013 So in other words you didn't test this on a dev install, you tested on your live installation and are now jumping up on down on the forums demanding action because you have uploaded the patched files, something has clearly gone wrong and your business is broken. I would suggest opening a ticket with support. 0 Quote Link to comment Share on other sites More sharing options...
Infopro Posted November 29, 2013 Share Posted November 29, 2013 Well if my other threats have not been deleted.... And I have read through all and tested everything. We cannot create new clients, add, change anything, it always says invalid token!?? I have also read through other threats with the same problems but whmcs does not seems to bother with the problem everyone have with the invalid token. This is serious as we are losing money everyday!! Threads are not deleted on these forums unless they are spam, or duplicates. I delete both, often. Yours on the other hand, was merged into an existing thread, here: Invalid Token Errors on Quotes and many other pages - WHMCS Forums You'll note my post on the end of that thread just made. A longer thread with more users having the same issue, is more important, and noticeable, than many separate threads. 0 Quote Link to comment Share on other sites More sharing options...
kobus4u Posted November 29, 2013 Share Posted November 29, 2013 So in other words you didn't test this on a dev install, you tested on your live installation and are now jumping up on down on the forums demanding action because you have uploaded the patched files, something has clearly gone wrong and your business is broken. I would suggest opening a ticket with support. No It just happened, did not install a patch or something, maybe you must bother to read people's exact problems before committing on their posts, trying to be funny, smart and clever, if you don't have something better to do go get a hobby or try unraveling the truth of life by trying to figure out how to stick your head into a flaming meteor shower. Then we can sit down and have some tea and discuss your ordeal... Sounds good?? - - - Updated - - - Threads are not deleted on these forums unless they are spam, or duplicates. I delete both, often. Yours on the other hand, was merged into an existing thread, here:Invalid Token Errors on Quotes and many other pages - WHMCS Forums You'll note my post on the end of that thread just made. A longer thread with more users having the same issue, is more important, and noticeable, than many separate threads. Okay noted, thank you. 0 Quote Link to comment Share on other sites More sharing options...
SeanP Posted November 29, 2013 Share Posted November 29, 2013 No It just happened, did not install a patch or something The token errors should be fixed in the latest version (5.2.14 for the 5.2 series, and 5.1.15 for the 5.1 series). Just remember to clear your template cache (the template_c folder) and your web browser cache after patching. I am running 5.2.14, and am not having any token issues anywhere. 0 Quote Link to comment Share on other sites More sharing options...
Infopro Posted November 29, 2013 Share Posted November 29, 2013 No It just happened, did not install a patch or something, maybe you must bother to read people's exact problems before committing on their posts, trying to be funny, smart and clever, if you don't have something better to do go get a hobby or try unraveling the truth of life by trying to figure out how to stick your head into a flaming meteor shower. Then we can sit down and have some tea and discuss your ordeal... Sounds good?? While he may have been assuming too much, and going a little far in making his point, his "offer for tea" was shorter than yours. Some might say a bit weaker even. - - - Updated - - - Okay noted, thank you. Sticking to the issue at hand here is far more interesting to read than you taking shots at someone who does help others on these forums, and has probably, like me, read way too many threads and comments related to small, easy to avoid mistakes that has broken multiple peoples sites in recent days. We should be trying to help each other on these forums, not attacking. Please keep that in mind. 0 Quote Link to comment Share on other sites More sharing options...
kobus4u Posted November 29, 2013 Share Posted November 29, 2013 The token errors should be fixed in the latest version (5.2.14 for the 5.2 series, and 5.1.15 for the 5.1 series). Just remember to clear your template cache (the template_c folder) and your web browser cache after patching. I am running 5.2.14, and am not having any token issues anywhere. Thank you, I will quickly try this. 0 Quote Link to comment Share on other sites More sharing options...
kobus4u Posted November 29, 2013 Share Posted November 29, 2013 While he may have been assuming too much, and going a little far in making his point, his "offer for tea" was shorter than yours. Some might say a bit weaker even. Sticking to the issue at hand here is far more interesting to read than you taking shots at someone who does help others on these forums, and has probably, like me, read way too many threads and comments related to small, easy to avoid mistakes that has broken multiple peoples sites in recent days. We should be trying to help each other on these forums, not attacking. Please keep that in mind. For sure. This still does not give him the right to undermine and be sarcastic to people with small problems in his eyes... this "small" problems are emotionally large in some people, like me, fighting hard to make a living. 0 Quote Link to comment Share on other sites More sharing options...
Infopro Posted November 29, 2013 Share Posted November 29, 2013 I could not agree more with you. One small mistake can be a HUGE PITA. And that's what troubles me to see around here the most. Thread after thread, post after post of people in trouble on these forums on every single update that comes out. Doesn't matter which one, every one that rolled out this past year, this forum got fired up with upset users. That should not be the case. WHMCS users are not bloggers, or forum owners, they're Web Hosting Providers that should know how to backup and restore a database. Roll back a failed update. Test an update first for basic things on a development site to ensure their business website stays online no matter what. Understand ticket response times and much, much more. I have no details or statistics to tell how many tickets are generated on a regular basis that could have been solved in less than 2 minutes had the user actually read the changelog for details on an update and took precautions like testing it first due to template changes, or at minimum, skimmed the docs before opening a ticket asking how to do something. But I bet you that number is quite high. All those tickets take man power too. And when you have a serious issue, you might be, probably are, in line behind multiple, unneeded tickets. If you are serious about your business, you should be paying closer attention to details. You customers depend on you. It's as simple as that. Please accept my apologies if anyone is offended by my comments here, that is not my intent. 0 Quote Link to comment Share on other sites More sharing options...
epretorious Posted December 1, 2013 Share Posted December 1, 2013 Just remember to clear your template cache (the template_c folder) and your web browser cache after patching. That seems like useful advice -- Thanks, SiteOx! I'll be sure to remember that. 0 Quote Link to comment Share on other sites More sharing options...
epretorious Posted December 1, 2013 Share Posted December 1, 2013 (edited) ...And that's what troubles me to see around here the most. Thread after thread, post after post of people in trouble on these forums on every single update that comes out. Doesn't matter which one, every one that rolled out this past year, this forum got fired up with upset users. FTR: I've performed multiple upgrades over the past year and -- so far -- none of them has caused a loss of data or any kind of disruption. There is one caveat, however: I follow a simple procedure that may be overkill with every upgrade... Backup the WHMCS installation to a separate directory outside of the DocumentRoot. Backup the WHMCS database. Delete the entire WHMCS installation from the DocumentRoot. Extract the new version to the DocumentRoot.. Create the overrides subdirectory in the lang directory. Remove the install directory from the new installation. Copy... the .htaccess file from the backup directory to the admin directory of the new installation, the configuration.php file from the backup directory to the the new installation, the custom template directory from the backup directory to the WHMCS templates directory of the new installation, and the lang directory from the backup directory to the WHMCS lang directory of the new installation. [*]Install any 3rd-party modules into the new installation. This usually only requires extracting the files that are located outside of the DocumentRoot to the new installation. The entire process takes about 2 minutes and seems to be very robust. It would probably only take a few seconds if I took the time to script the entire thing but I feel more comfortable performing the process manually following the recipe that I've created. Feel free to share your thoughts on this process. I have no details or statistics to tell how many tickets... could have been solved in less than 2 minutes had the user actually read the changelog for details on an update and took precautions like testing it first... IMHO: I've performed multiple upgrades over the past year and -- so far -- none of them has had -- what I would consider -- adequate documentation. Edited December 1, 2013 by epretorious fixed a minor typo. trimmed the second citation. 0 Quote Link to comment Share on other sites More sharing options...
Infopro Posted December 1, 2013 Share Posted December 1, 2013 Feel free to share your thoughts on this process. That reads to me like you're not the System Administrator I'm concerned with, getting into trouble. But, hold that thought: IMHO: I've performed multiple upgrades over the past year and -- so far -- none of them has had -- what I would consider -- adequate documentation. This thread may not be the best place for this, but I'd be interested to hear your concerns and suggestions on this to make the upgrade documentation better. If you'd like to gain other users feedback to go along with yours, please feel free to start a new thread and let's have a conversation about that. Thanks in advance! 0 Quote Link to comment Share on other sites More sharing options...
epretorious Posted December 1, 2013 Share Posted December 1, 2013 (edited) This thread may not be the best place for this, but I'd be interested to hear your concerns and suggestions on this to make the upgrade documentation better. If you'd like to gain other users feedback to go along with yours, please feel free to start a new thread and let's have a conversation about that. Thanks, InfoPro: IIRC, I've still got all of the upgrades: whmcs-bridge.2.2.4.zip whmcs_v512.zip whmcs_v513_patch.zip whmcs_v5210_incremental.zip whmcs_v5212_incremental.zip whmcs_v5213_full.zip whmcs_v5214_full.zip whmcs_v522_incremental.zip whmcs_v522_stable.zip whmcs_v5.2.7_incremental.zip whmcs_v5.2.7.zip whmcs_v528_full.zip whmcs_v528_incremental.zip whmcs_v529_incremental.zip I'll go back over the doc's; put together some thoughts, and; start a new thread if the doc's are as disappointing as I recall. Edited December 2, 2013 by epretorious 0 Quote Link to comment Share on other sites More sharing options...
openmind Posted December 2, 2013 Share Posted December 2, 2013 No It just happened, did not install a patch or something, maybe you must bother to read people's exact problems before committing on their posts, trying to be funny, smart and clever, if you don't have something better to do go get a hobby or try unraveling the truth of life by trying to figure out how to stick your head into a flaming meteor shower. Then we can sit down and have some tea and discuss your ordeal... Sounds good?? - - - Updated - - - Okay noted, thank you. I rest my case and Infopro is on the money. It is tedious to re-read continuous posts berating WHMCS for peoples own mistakes. And for the record I don't have time to try all the fun things you suggested, I'm too busy running a business... 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.