PC-Mike

I solved this by upgrading to the latest version, and that fixed it automatically for me. If that isn't possible or your are already on the latest version, I would consider trying a reinstall of your current version on top of itself. I don't know how you do that, but someone else is bound to know how. Hope you get it sorted without too much headache. Mike

I was was pretty sure that with v5.2.3 a definite corner was turned for the better (which is why I finally decided to upgrade now). Sure enough, this morning, votes for v5.2.x branch have leapt up. I think if we were to zero the poll results and start the same survey again now, we'd see an even higher preference for the latest branch emerge, as you have to remember, this survey was started in the thick of the problems in version 5.2.2 so voters had every reason to pick other branches as the best back then. Poll is due to close soon anyway. Love to see a last minute flurry of opinions... Mike

I've personally just moved from v4.4.2 to v5.2.3 this week (in part due to the votes here - plus my reading around the forums), and I've seen no problems in the shift. I'm glad I waited until now, but equally, I'm glad I'm not still waiting! This looks to be a good branch developing... and will hopefully only get better from here onwards. Mike

As others have said, I think you'll find that the 1st address is probably the same as the 3rd address. The postcode and road is identical. Woodside House is therefore presumably number 4 on Broadway Avenue. If they are in the process of moving, then the 2nd address might eventually take over. Is the 2nd address related to cPanel I wonder? Mike

Of course it is, they are two different systems... BUT you don't needed to use and track that login, as you are logged in by your forum account. Would you have felt happier if you didn't get the email? (so you didn't know how the trickery worked behind the scenes). If that is the case, you could just delete that email and be happier again. You don't need to track this account as you have a single integrated login (using your forum account). Mike

On the login page for Feature Requester, you can click the icon in the top right corner of the login box labelled something like "integrated login" (or something like that). This takes you back to the forum, but when you return back to the features page next time you are already logged in with your forum details. HOWEVER. You will lose any comment you just wrote on the feature page, so login first before making any comments, and return the features page... THEN write your comment. END RESULT: only one login shared between the two. Enjoy...

I thought some of you might be interested to see how the results looked at the point that v5.2.3 was released, in case this new release makes the v5.2.x branch much more stable and highly favoured and drastically changes the voting results in the poll from here onwards: As can be seen, v5.2.x is already the leading branch, but looking at the release notes for v5.2.3 there are LOTS of bug fixes in there. It will be interesting to see if v5.2.x branch now pulls right away from the others as it gains popularity, or whether the new release fixes some bugs, but also just adds a stack of new bugs into the mix. Ideally it would be nice to zero the results of the poll at this point, and start the vote again from scratch now the new release available (but the Poll options doesn't let me do that in this forum!), so we could all vote again with our new opinions. Mike

Or at least make WHMCS software more flexible, so that the Admin can choose which ordering method is used in their own install.... You could maybe have these options as a choice for the admin to pick from: Order by date ticket was opened Order by date of first customer response to staff comment (ie ignoring date of extra responses that add more info) Order by date of last response (how it is now) I'm sure there are other ways the tickets could be ordered, and having a choice of methods adds flexibility and potentially frustrates customers less! Mike

It is a fine line here I would suggest. Everyone is desperate for an immediate version update to roll together all the current post-release patches into a coherent stable system... however on the other hand, everyone is saying, that WHMCS team need to do better testing before making releases, so that bugs are removed before going live.... And therein lies the dilemma for Matt and crew... release to keep the masses happy without proper testing... and possibly make it worse.... or keep everyone waiting longer and longer for the next version until they are screaming... but release something proper and tested this time. Not saying this is what is happening right now... but I can see it would be easy to see that WHMCS (and therefore their customers eg us) lose out whichever route they take.... in other words: you can never please all the people all of the time. Maybe we should all ask ourselves this question: Which would we prefer... a rushed composite that is called v5.2.3 that might have more new bugs than it fixes... or wait in this current mess for longer, but get something more coherent for our patience? There are probably good arguments on both sides since it is already a mess... but I'm pretty sure ultimately we want better tested releases that get more stable even if they take more time. Just difficult to wait for that when it is currently broken right now... and we want it fixed yesterday!

Oh, it won't let me change the typo. Never mind. Everywhere I put v5.5.2 above, I obviously meant v5.2.2 !!! Now.... the results look quite different already anyway! v5.1.x has overtaken v4.5.x into second place, and both that and v5.2.x have left the v4 series for dust. This is understandable since I've seen many forum comments talking about v5.1.3 as their favourite (or least worst option!), in fact I was surprised that whole line only had one vote previously. So current conclusion looks like, despite all the problems and noise about the v5 series, that v5.1.x and v5.2.x are still the most recommended. I am suspecting the new features are too "must have" to turn down. Still lots of grumbles around the forums about bugs on the v5 series though, so many people are desparate for less bugs and more stability. Will we get that stability in a future v5.2.x release? Or must we wait for a whole new branch v5.x.x Am I right in my babbling assessments? What are your opinions? Of course these stats will change and get more reliable the more people vote, and statistical anomalies will be reduced further. So keep voting too.... Thank you all for your input, it is most helpful! Mike

Ha ha! (Whoops!). I will correct the typo above...

Thanks for the votes, so far. Also thanks Ditto for your thoughts, that is the general vibe I was picking up from the forums. Currently v4.5.x is jointly most popular with v5.2.x (with 3 votes each), although the numbers are currently too small to be statistically reliable, but it is an interesting trend. I'm guessing that the choices come down to - latest version wins on features, and v4.5.x is being rated for stability and lack of bugs. Certainly I think my personal choices come down to stay on v4.4.x for now, upgrade to v4.5.x (which seems almost pointless bothering, but has reliability in its favour), or jump to v5.5.2 (which seems risky and might cause problems I need to fix). The point is I'm going to need the features of the v5 series soon-ish, so will need to leap eventually. I think that v4.5.x still being popular does show up what a mixed bag all the v5.x.x branches have been though. If any of the v5.x.x branches got a stable, bug-free release, like v4.5.x, I suspect it would easily top the charts. Encouragingly v5.5.2 is obviously heading in the right direction though, so there is hope for the future if the remaining bugs get squashed. Keep voting though. I'd also love to hear some more opinions around this topic too.

Oh, and one more thought.... I guess in our minds, one version might be more stable, but a different version might have best features, and yet another version have best security etc. In the poll, I'm looking for the "balanced answer" that takes all these things into account for the poll result. However, if you want to discuss the detailed reasons behind the answer, you can do so on the thread, as I think that will help us all. You can also comment on the thread the breakdown of which version is most stable, and which is most feature packed, and which is most secure etc. I suspect there are a range of opinions on this, and I expect there are a range of versions still in use because there hasn't been an "ideal" version for a while... Thanks in advance for your thoughts! Mike

I am interested to know which version of WHMCS people currently recommend to install. I am still back on the v4.4 branch and am considering an upgrade, but unsure whether to upgrade, and if so, to which branch. Please answer the poll as to which branch you recommend as best (ie most stable, best features, most secure, least bugs etc.) If you recommend an exact sub-version within that branch, that is not the latest (eg v5.1.3), then post that in the thread. If you currently have a different version installed than you recommend, please answer poll for recommendation, but post in thread which version you are using. Thanks.

I used to have "do not send any email to my customers" set on NetEarthOne (LB platform). However, I have one customer set to use the LB login for access to the domain control panel for their advanced needs (I don't give most customers access there). Anyway turns out that they've been trying to use the forgotten password link for a while, without success and recently mentioned it to me. Of course I eventually tracked it down to the email settings I'd chosen for my customers (no emails from LB platform). However, the custom option allows you to choose exactly which emails to allow, so I now choose "no emails" to untick everything, then in custom settings, I manually re-tick just "send forgotten password emails", to be the only email allowed. This works perfectly for me and my scenario where everything is handled by WHMCS, so getting no duplicates, but allowing my customer to use advanced domain control and get password reminders for that. Hope this helps. Mike