swg Posted September 16, 2008 Share Posted September 16, 2008 First off, before the complaint, we absolutely love this product and have never looked back after switching from that other company quite some time ago. Now the complaint.....Is there a way to get these little bug fixes after a new version releases? I hate to bug Matt or waste time going through all these threads to get my install up to snuff between version releases. Can we not have a place to go to download these updated files etc. in between releases? 0 Quote Link to comment Share on other sites More sharing options...
mattpark Posted September 16, 2008 Share Posted September 16, 2008 Isn't this the point of a version system... I.e. Major release = 3.7 Bug fix release = 3.7.1 Bug fix release = 3.7.2 0 Quote Link to comment Share on other sites More sharing options...
swg Posted September 16, 2008 Author Share Posted September 16, 2008 Have you looked at how many 'Resolved' and 'Fixed' there are since 3.7.1 release? Even something like this http://forum.whmcs.com/showthread.php?t=14018 where the file is there for us to download is better than having to email Matt or wait IMO. If there is a fix to a bug we should have access to it without having to wait for another release. Sorry, must be me wanting to keep things up to date. 0 Quote Link to comment Share on other sites More sharing options...
kcackler Posted September 16, 2008 Share Posted September 16, 2008 I'm in complete agreement swg. This is why I wait two weeks or so after an upgrade is released, to actually upgrade. That way the bug fixes are in the downloaded file... 0 Quote Link to comment Share on other sites More sharing options...
Iceman Posted September 17, 2008 Share Posted September 17, 2008 Yes we also agree. I have asked for this several times but had no luck. Why on earth would I want to install a buggy version where I need to ASK for the bug fixes that already exist? EDIT: This is why I wait two weeks or so after an upgrade is released, to actually upgrade. That way the bug fixes are in the downloaded file... Hang on...are we missing something? We need some clarification here. Once a bug is fixed is it put into the latest downloadable zip file version? If yes than that is better than needing to ask. However, confirmation on this would be appreciated please. Cheers, Paul 0 Quote Link to comment Share on other sites More sharing options...
Iceman Posted September 17, 2008 Share Posted September 17, 2008 Just adding to this, I downloaded the latest whmcs_v371.zip file from the ClientArea and checked the latest file modifications. The most uptodate files are dated 12/09/2008, so any fixes after that date it seems are not included. Cheers, Paul 0 Quote Link to comment Share on other sites More sharing options...
chickendippers Posted September 18, 2008 Share Posted September 18, 2008 Bug fixes are not often released immediately - they are collated and then released in the next point release or main build. However, if a bug that is showing as fixed is affecting you, you can open a ticket to enquire if a fix is available for the current version. http://forum.whmcs.com/showthread.php?t=14017 0 Quote Link to comment Share on other sites More sharing options...
Iceman Posted September 18, 2008 Share Posted September 18, 2008 Ok here's some feedback then... Why upgrade to a version with known bugs with known available fixes which you then need to find out for yourself the hard way that the glitch is a KNOWN bug??? There is no EASY WAY to SIMPLY patch WHMCS to have all the latest bug fixes. A simply repository with the latest bug fixes as they are released would suffice. Instead we have to first search the forums, or find out the HARD WAY that a bug is "affecting us" then specifically request the bug fix. If a bug has been confirmed, and a fix is available then please make it public knowledge (or at least to paying clients) and EASY TO FIND, so that we can procede with implementing those fixes. I do not understand why it has to be so tedious for us, by only providing the fixes if we REQUEST it and only after we find out that it is a bug after all? Cheers, Paul 0 Quote Link to comment Share on other sites More sharing options...
Iceman Posted September 18, 2008 Share Posted September 18, 2008 Ok...is this the solution?... we should be submitting a new support ticket each week to check for NEW bug fixes...right? Cheers, Paul 0 Quote Link to comment Share on other sites More sharing options...
Si Posted September 18, 2008 Share Posted September 18, 2008 So far, in the past week, I've had to download 3.71 4 separate times to get bug fixes which weren't there in the previous downloads - and in at least one forum post (can't remember which), Matt actually attached a file with a bug fix to the thread to download that file. However, I only knew about it because I was on the forum searching for a solution to my problem since the upgrade. IMHO, I think this has only become a real issue with 3.71 because it was a major upgrade from 3.62 and I do believe 3.7 (while it was in beta for some time) was not tested properly before being moved to stable and released. (IMHO). I've never seen these issues happening before (or at least as much) with previous upgrades.....although I do agree, I feel there needs to be a fundamental issue addressed here. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS CEO Matt Posted September 18, 2008 WHMCS CEO Share Posted September 18, 2008 If a bug has been confirmed, and a fix is available then please make it public knowledge (or at least to paying clients) and EASY TO FIND We do, that is what the bug reports forum is for and [FIXED] or [RESOLVED] is prefixed by us to the title depending on if it's confirmed to be an issue or if it turns out not to be. As has been confirmed before, any issues reported and fixed within the first 72 hours of a new release are added to the download. Anything after that time should be minor enough not to warrant that. Collectively bug fixes are then grouped together and released in a furthur point release update every few weeks if required. If we look at the current reports since after the 72 hour cut-off period, we have: [FIXED] Active Support Tickets Link Incorrect [FIXED] Email merge field auto-inserts wrong value Both fixed are very minor issues - one a link that had intentionally linked to the main ticket listing but some people felt it would be better otherwise and one where an auto insert merge field inserts a different value to the one clicked. If either of those are really affecting you, sure, as the bug reports forum notice says you can contact us to request an update for it. There were also 3 reports yesterday I see which are as yet unchecked but again fairly minor and not new in 3.7 so if they haven't affected you until now, shouldn't do before 3.7.2 is released. Si, 3.7 hasn't been any different to other releases in recent times. Beta testers can only do so much and they don't catch everything just the same as we don't in our in-house tests. You've had 2 reports confirmed in the past week which have helped to make WHMCS better so thanks for your input. We do need people like you who upgrade early in order to identify and resolve issues and I'm sure you'll agree, no sooner had you posted and they were updated to a fixed status. WHMCS is not like some where people are left without resolutions. Matt 0 Quote Link to comment Share on other sites More sharing options...
Si Posted September 18, 2008 Share Posted September 18, 2008 Si, 3.7 hasn't been any different to other releases in recent times. Beta testers can only do so much and they don't catch everything just the same as we don't in our in-house tests. You've had 2 reports confirmed in the past week which have helped to make WHMCS better so thanks for your input. We do need people like you who upgrade early in order to identify and resolve issues and I'm sure you'll agree, no sooner had you posted and they were updated to a fixed status. WHMCS is not like some where people are left without resolutions. Matt Hi Matt, I'm not complaining, and yes, as I've given credit before in another thread for issues that have arisen have been addressed quickly, (jeez is better here than 'ancientbill', however, there were issues that the readme didn't cover which, weren't necessarily issues but if it had, would have saved me a lot of headaches this week - I know things change and before I do any upgrade I make any changes offline BEFORE I make the upgrade, but this upgrade's readme left issues not addressed and which only became clear when things started going wrong in a live environment. (These don't include the 2 bug fixes I reported and you solved). merge fields in email templates not working product order form urls not working and server mod_rewrite failing to correct it Nominet's PGP mod missing being replaced entirely by the new EPP mod (and so I had to re-upload it from an old version after a few domain renewals and registrations failed) It seems that the release of 3.71 announcement came out with all of the bells and whistles (rightly so), but with none of the warnings about what you need to watch out for and get ready to change before or when you make the upgrade. I do understand when you say "We do need people like you who upgrade early in order to identify and resolve issues" and I publicly apologise if I've been a little tedious to deal with this past week and if I've made any comments that have added to your grief, but I've had a lot on besides WHMCS and I guess the last thing I should have done this week was an early upgrade and so my stress levels have been a tad high trying to get everything sorted with everything else going on. Just my thoughts. Si 0 Quote Link to comment Share on other sites More sharing options...
Zorro67 Posted September 18, 2008 Share Posted September 18, 2008 perhaps I can add another perspective. My licence comes from my primary hosting provider, and ussually i wait a week or two before downloading the lastest version. However, i've found they often only upload one version, and may not update it with later patched versions. So for me, and i'm sure there are many other like me, it may be difficult to know whther the version we have is actually patched. reseller licence holders don't have the luxury of accessing beta licences, nor of a developer licence, so we have to go live with what ever is available. We have to rely on the stability of the platform from the moment we upgrade. to be fair, I've only struck 2 problems, and one of those was related to a post installation step that should have included in the instructions. However, by placing patches in a repository, you allow all customers whether direct or through a reseller, access to the most up to date resolutions to problems. (and perhaps a few less support tickets for yourself) Cheers 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.