WHMCS.Community

A flag, setting, parameter. Call it what you want. You're able to disable it. Removing it from templates doesn't require edits "all over". It's two files. In case you're not using a default WHMCS template, this change would have to be made once. That's weird. On our 3 installations, it's only checking active services, as it should. It wouldn't make any sense checking inactive/cancelled services. No, it wasn't. You said nothing useful was added in any of the updates. Security updates are included with the latest versions of WHMCS. You can't expect WHMCS to solve issues for the few percentage of users of EOL'ed versions that don't want to upgrade to later versions. Wouldn't you think that I was out of my mind if I was still on version 1.3 and expected them to release security fixes for that version, just because I didn't want to upgrade (whatever the reason was)?   It's not described in the documenation. WHMCS advises you to make customization to the menu by hooks - and it's great for modules. If a module needs to add a menu item, the module can do so by hooks. Everything is basically HTML and can be changed. See this:   There's plenty of alternatives to WHMCS, and you're free to use whatever you like. I get why you're frustrated, but I don't get why you're blaming WHMCS.

A setting? Last I read the SSL check needed a flag on the cron to prevent it running, then edits all over to remove the flags and refences. It's just a click and it's all gone now? Please point me to that documentation.  The point of having it disabled by default was that it was badly implemented and cause havoc. It was checking (and may still do) every domain in the system for an SSL certificate on the hosting account, even if there was no hosting account. With many hundreds (or more) domains in the system, it was literally DOSing yourself each time it ran. So yes, major features and changes should be optional to ENABLE, not on and a surprise when things go pear shaped. You stated this: " if you don't find the security updates or bug fixes useful, you don't have a reason to upgrade then. There has been a lot of bug fixes for WHMCS since 7.6". That was clearly intended to make it appear I don't care about it, when in fact there were none for my version that weren't implemented.  The point you appear to be missing is that I've just been told there's a very serious security issue that I need to pay $60 for more than one installation to fix, and it also include me having to upgrade, fix all the things it's broken, apply patches where needed and hope for the best. Basically, devote a large chunk of time to resolving this, move to a version that's even more bloated, and pay for the privilege. Cool.  Please link to the docs where it explains that bit about removing the includes to do whatever you want. 

You can still just edit it as HTML... In your header.tpl, you have this: <section id="main-menu"> <nav id="nav" class="navbar navbar-default navbar-main" role="navigation"> <div class="container"> <!-- Brand and toggle get grouped for better mobile display --> <div class="navbar-header"> <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#primary-nav"> <span class="sr-only">Toggle navigation</span> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> </div> <!-- Collect the nav links, forms, and other content for toggling --> <div class="collapse navbar-collapse" id="primary-nav"> <ul class="nav navbar-nav"> {include file="$template/includes/navbar.tpl" navbar=$primaryNavbar} </ul> <ul class="nav navbar-nav navbar-right"> {include file="$template/includes/navbar.tpl" navbar=$secondaryNavbar} </ul> </div><!-- /.navbar-collapse --> </div> </nav> </section> Remove the includes - you'll have no menu and can insert whatever you'd like. It has been possible to do it like that since they introduced editing the menu using hooks. Ok, so every feature you don't need should be disabled by default? Why complain about it when there's literally a setting that disables the functionality that you don't want? If you want a software that's tailored to your needs, you should have one developed.   Yes, it's difficult fixing bugs for a feature that isn't implemented yet. It's very rare that a feature that has been in WHMCS forever suddenly stops working.   No one is telling you to update to WHMCS 8. You could easily do with an update to 7.7. When that's said, version 8 is stable. We're using it on 3 seperate installations with no issues. The only issues we've had was with the new user implementation, but they have been fixed. You can disable that feature, by the way - like most other features they introduce.   My point was not that they supported it after EOL. My point was that you can't get mad at a company for not supporting something they clearly stated they won't be supporting.

You seem determined to downplay my concerns and make it look like I don't care about security, but that's not my problem. What is my concern is that hooks statement. "Change it as HTML"? Have a read: https://docs.whmcs.com/Editing_Client_Area_Menus If you're using a predefined hook made by WHMCS, you can edit it and *include* HTML in the hook file. If not theirs, you need to make one.  As for the SSL checks? That should have been optionally enabled, not automatically, then needing to edit all traces from the interface.  I think you'll see most of those are bugs introduced by the newer release versions which were then fixed. The pattern is: fast dev (every few months), short beta, short candidacy, fast release, then wait for the bugs that need fixing. The latest version has had tons of complaints, things we need as providers removed and so on. Is it any wonder I don't want to move to that version? As for your WindowsXP example? They supported it for 5 years after EOL. The current death of WHMCS versions is roughly one year.

its been 5 days its showing same status, have checked the cron and its running just fine. I am not able to send any email marketing campaign as its showing Queued my first  campaign now

Well, if you don't find the security updates or bug fixes useful, you don't have a reason to upgrade then. There has been a lot of bug fixes for WHMCS since 7.6. My argument is still valid - if I was on v5.3 (or even 1.3), I could say the same thing as you. That I don't want to be forced to upgrade because v5.3 has everything I need. You can't expect WHMCS to support versions that have been EOL'ed a long time ago. You don't see Microsoft patching security holes in Windows XP, even though that version is the golden version af Windows to a lot of users. You don't need to use hooks to change the menu. You can change it as HTML if you want to. SSL checks can be disabled.   If you were a software developer, would you really want to support every version of the software that you developed? Your code base will most likely have changed between major versions, which means fixing security issues is not the same for each version.

Updated our system yesterday to the latest version and suddenly clients can't update their details anymore.  Name and email fields are returned blank and it throws the following error: The following errors occurred: You did not enter your email address   See attached Any ideas?

I'd be far less upset if versions beyond the one I'm on were worth the cost of upgrading for us. Nothing I'd find useful has been added, and many, many things have been broken in them over time. Now I'll be forced to pay this and at the same time upgrade to an unwanted version, with all it's issues that will need fixing with hooks and tricks, menus that need PHP coding to change and SSL checks no one asked for and so on and so forth.  Kind of like having to get a stick, and finding it has two short ends, neither terribly clean. 

The issue is fixed already.

I think you're asking a bit too much. WHMCS v7.6 was EOL'ed almost two years ago. How can you expect them to provide security updates for that version? It's a miracle that they even provide one for v7.7-v7.9. If I was still on v5.3, I couldn't complain that there's no security fixes. It's just how it works.