Jump to content

agentblack

Senior Member
  • Content Count

    37
  • Joined

  • Last visited

Community Reputation

2 Neutral

About agentblack

  • Rank
    Level 2 Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Original ticket opened May 11. Today May 14th and so far, only one helpful, meaningful response. The rest, useless, canned responses that don't actually fix any of the issues. We have been battling to rebuild our billing server after the latest released completely hosed the entire box. We had to reimage the machine and have been piecing things back together ever since. Thankfully we had a database backup. However, here's our latest dilemma with this reinstall process. We squash one bug with the help of the one useful tech that responded to our ticket but in doing so, it's created half a dozen new ones. Thus far the tech that responded after that provided another useless, canned response without even logging into the server to check on the error (which they hound you for access when you open the tickets). We were having the error that requires you to check the remember me box in order to log in. The one helpful tech was able to resolve that, but it created a new set of issues: [Thu May 14 10:23:31.679981 2020] [php7:notice] [pid 4847] [client 208.74.120.226:57835] [WHMCS Application] ERROR: Whoops\Exception\ErrorException: Module 'xmlrpc' already loaded in Unknown:0 Stack trace: #0 /var/www/html/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\Utility\Error\Run->handleError(32, 'Module 'xmlrpc'...', 'Unknown', 0) #1 [internal function]: WHMCS\Utility\Error\Run->handleShutdown() #2 {main} {"exception":"[object] (Whoops\\Exception\\ErrorException(code: 32): Module 'xmlrpc' already loaded at Unknown:0)"} [], referer: https://website.com/adminfolder/systemadminlog.php [Thu May 14 10:27:08.285120 2020] [php7:notice] [pid 4854] [client 208.74.120.226:49320] [WHMCS Application] ERROR: Whoops\Exception\ErrorException: Module 'xmlrpc' already loaded in Unknown:0 Stack trace: #0 /var/www/html/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\Utility\Error\Run->handleError(32, 'Module 'xmlrpc'...', 'Unknown', 0) #1 [internal function]: WHMCS\Utility\Error\Run->handleShutdown() #2 {main} {"exception":"[object] (Whoops\\Exception\\ErrorException(code: 32): Module 'xmlrpc' already loaded at Unknown:0)"} [], referer: https://website.com/adminfolder/configgeneral.php?nocache=M0DNH1YweHJIVGtC [Thu May 14 10:27:26.069185 2020] [php7:notice] [pid 4851] [client 208.74.120.226:64090] [WHMCS Application] ERROR: Whoops\Exception\ErrorException: Module 'xmlrpc' already loaded in Unknown:0 Stack trace: #0 /var/www/html/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\Utility\Error\Run->handleError(32, 'Module 'xmlrpc'...', 'Unknown', 0) #1 [internal function]: WHMCS\Utility\Error\Run->handleShutdown() #2 {main} {"exception":"[object] (Whoops\\Exception\\ErrorException(code: 32): Module 'xmlrpc' already loaded at Unknown:0)"} [], referer: https://website.com/adminfolder/login.php?redirect=%2Fportal%2F So the unhelpful response was to check our php.ini's (to which we only have one in operation), and make sure it's not loaded. So we go through these circles and of course, it's only in the one file. So we bounce apache2 and now we have a wall of errors: [Thu May 14 17:40:51.102479 2020] [ssl:warn] [pid 11046] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name PHP Warning: PHP Startup: Unable to load dynamic library 'gd2' (tried: /usr/lib/php/20180731/gd2 (/usr/lib/php/20180731/gd2: cannot open shared object file: No such file or directory), /usr/lib/php/20180731/gd2.so (/usr/lib/php/20180731/gd2.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 PHP Warning: PHP Startup: Unable to load dynamic library 'gmp' (tried: /usr/lib/php/20180731/gmp (/usr/lib/php/20180731/gmp: cannot open shared object file: No such file or directory), /usr/lib/php/20180731/gmp.so (/usr/lib/php/20180731/gmp.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 PHP Warning: PHP Startup: Unable to load dynamic library 'openssl' (tried: /usr/lib/php/20180731/openssl (/usr/lib/php/20180731/openssl: cannot open shared object file: No such file or directory), /usr/lib/php/20180731/openssl.so (/usr/lib/php/20180731/openssl.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 PHP Warning: PHP Startup: Unable to load dynamic library 'pdo_mysql' (tried: /usr/lib/php/20180731/pdo_mysql (/usr/lib/php/20180731/pdo_mysql: cannot open shared object file: No such file or directory), /usr/lib/php/20180731/pdo_mysql.so (/usr/lib/php/20180731/pdo_mysql.so: undefined symbol: mysqlnd_allocator)) in Unknown on line 0 PHP Warning: PHP Startup: Unable to load dynamic library 'bcmath' (tried: /usr/lib/php/20180731/bcmath (/usr/lib/php/20180731/bcmath: cannot open shared object file: No such file or directory), /usr/lib/php/20180731/bcmath.so (/usr/lib/php/20180731/bcmath.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 PHP Warning: Module 'imap' already loaded in Unknown on line 0 PHP Warning: Module 'mbstring' already loaded in Unknown on line 0 PHP Warning: Module 'soap' already loaded in Unknown on line 0 PHP Warning: Module 'xmlrpc' already loaded in Unknown on line 0 [Thu May 14 17:40:51.123716 2020] [ssl:warn] [pid 11057] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name [Thu May 14 17:40:51.127467 2020] [mpm_prefork:notice] [pid 11057] AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming normal operations [Thu May 14 17:40:51.127496 2020] [core:notice] [pid 11057] AH00094: Command line: '/usr/sbin/apache2' [Thu May 14 17:40:56.918125 2020] [php7:notice] [pid 11067] [client ip address:53473 ] [WHMCS Application] ERROR: Whoops\\Exception\\ErrorException: Module 'xmlrpc' already loaded in Unknown:0 Stack trace: #0 /var/www/html/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\\Utility\\Error\\Run->handleError(32, 'Module 'xmlrpc'...', 'Unknown', 0) #1 [internal function]: WHMCS\\Utility\\Error\\Run->handleShutdown() #2 {main} {"exception":"[object] (Whoops\\\\Exception\\\\ErrorException(code: 32): Module 'xmlrpc' already loaded at Unknown:0)"} [] [Thu May 14 17:42:43.490393 2020] [mpm_prefork:notice] [pid 11057] AH00169: caught SIGTERM, shutting down [Thu May 14 17:42:43.565376 2020] [ssl:warn] [pid 11092] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name PHP Warning: PHP Startup: Unable to load dynamic library 'gd2' (tried: /usr/lib/php/20180731/gd2 (/usr/lib/php/20180731/gd2: cannot open shared object file: No such file or directory), /usr/lib/php/20180731/gd2.so (/usr/lib/php/20180731/gd2.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 PHP Warning: PHP Startup: Unable to load dynamic library 'gmp' (tried: /usr/lib/php/20180731/gmp (/usr/lib/php/20180731/gmp: cannot open shared object file: No such file or directory), /usr/lib/php/20180731/gmp.so (/usr/lib/php/20180731/gmp.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 PHP Warning: PHP Startup: Unable to load dynamic library 'openssl' (tried: /usr/lib/php/20180731/openssl (/usr/lib/php/20180731/openssl: cannot open shared object file: No such file or directory), /usr/lib/php/20180731/openssl.so (/usr/lib/php/20180731/openssl.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 PHP Warning: PHP Startup: Unable to load dynamic library 'pdo_mysql' (tried: /usr/lib/php/20180731/pdo_mysql (/usr/lib/php/20180731/pdo_mysql: cannot open shared object file: No such file or directory), /usr/lib/php/20180731/pdo_mysql.so (/usr/lib/php/20180731/pdo_mysql.so: undefined symbol: mysqlnd_allocator)) in Unknown on line 0 PHP Warning: PHP Startup: Unable to load dynamic library 'bcmath' (tried: /usr/lib/php/20180731/bcmath (/usr/lib/php/20180731/bcmath: cannot open shared object file: No such file or directory), /usr/lib/php/20180731/bcmath.so (/usr/lib/php/20180731/bcmath.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 PHP Warning: Module 'imap' already loaded in Unknown on line 0 PHP Warning: Module 'mbstring' already loaded in Unknown on line 0 PHP Warning: Module 'soap' already loaded in Unknown on line 0 PHP Warning: Module 'xmlrpc' already loaded in Unknown on line 0 [Thu May 14 17:42:43.586265 2020] [ssl:warn] [pid 11096] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name [Thu May 14 17:42:43.589060 2020] [mpm_prefork:notice] [pid 11096] AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming normal operations [Thu May 14 17:42:43.589089 2020] [core:notice] [pid 11096] AH00094: Command line: '/usr/sbin/apache2' [Thu May 14 17:43:12.027646 2020] [php7:notice] [pid 11105] [client ip address:53481 ] [WHMCS Application] ERROR: Whoops\\Exception\\ErrorException: Module 'xmlrpc' already loaded in Unknown:0 Stack trace: #0 /var/www/html/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\\Utility\\Error\\Run->handleError(32, 'Module 'xmlrpc'...', 'Unknown', 0) #1 [internal function]: WHMCS\\Utility\\Error\\Run->handleShutdown() #2 {main} {"exception":"[object] (Whoops\\\\Exception\\\\ErrorException(code: 32): Module 'xmlrpc' already loaded at Unknown:0)"} [], referer: https://website.com/adminfolder/index.php [Thu May 14 17:43:23.759270 2020] [php7:notice] [pid 11121] [client ip address:53485 ] [WHMCS Application] ERROR: Whoops\\Exception\\ErrorException: Module 'xmlrpc' already loaded in Unknown:0 Stack trace: #0 /var/www/html/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\\Utility\\Error\\Run->handleError(32, 'Module 'xmlrpc'...', 'Unknown', 0) #1 [internal function]: WHMCS\\Utility\\Error\\Run->handleShutdown() #2 {main} {"exception":"[object] (Whoops\\\\Exception\\\\ErrorException(code: 32): Module 'xmlrpc' already loaded at Unknown:0)"} [] Out of the dozens of programs we use, this one is the ONLY one that provides sub-standard support, has this many bugs/issues after every upgrade, and is becoming more and more of a time suck just to maintain. Even paid for a priority ticket and still getting canned, unhelpful responses. What's the point of paying for support and then priority support just to get canned, generic answers? I'm hoping someone here can better assist as I'm getting really fed up with the generic answers from a company I'm paying to support us when I have problems.
  2. You get used to it after a while.. Take a look at the feature request section. https://requests.whmcs.com/ some stuff has been in there as long as this request and nothing. Eventually you just stop asking and hope they don't break the product with each update.
  3. Thanks everyone for the comments. Evolve, no we aren't however we found the zombie module that was the cause of the issue. We were using ticket secure data module in the past but opted to discontinue its usage for operational reasons. We thought we had removed all of the files from the system however we found that it hadn't been completely removed. It took two days and a thread on WHT before we were finally able to get pointed in the right direction.
  4. Hoping for faster support here since main ticketing support is taking forever. Prior to upgrading to 7.9, we were able to run feedback score reports and be able to see our open support tickets, however since the 7.9 upgrade, we now get 0 /var/www/html/vendor/illuminate/database/Connection.php(333): PDO->prepare('select count(*)...') 1 /var/www/html/vendor/illuminate/database/Connection.php(706): Illuminate\Database\Connection->Illuminate\Database{closure}(Object(Illuminate\Database\MySqlConnection), 'select count(*)...', Array) 2 /var/www/html/vendor/illuminate/database/Connection.php(669): Illuminate\Database\Connection->runQueryCallback('select count(*)...', Array, Object(Closure)) 3 /var/www/html/vendor/illuminate/database/Connection.php(342): Illuminate\Database\Connection->run('select count(*)...', Array, Object(Closure)) 4 /var/www/html/vendor/illuminate/database/Query/Builder.php(1583): Illuminate\Database\Connection->select('select count(*)...', Array, true) 5 /var/www/html/vendor/illuminate/database/Query/Builder.php(1569): Illuminate\Database\Query\Builder->runSelect() 6 /var/www/html/vendor/illuminate/database/Query/Builder.php(1974): Illuminate\Database\Query\Builder->get(Array) 7 /var/www/html/vendor/illuminate/database/Query/Builder.php(1894): Illuminate\Database\Query\Builder->aggregate('count', Array) 8 /var/www/html/modules/addons/ticketsd/hooks.php(0): Illuminate\Database\Query\Builder->count() 9 /var/www/html/includes/hookfunctions.php(0): WHMCS\Utility\SafeInclude::{closure}(Array) 10 /var/www/html/vendor/whmcs/whmcs-foundation/lib/Admin.php(0): run_hook('AdminAreaPage', Array) 11 /var/www/html/vendor/whmcs/whmcs-foundation/lib/Admin.php(0): WHMCS\Admin->output() 12 /var/www/html/portal/supporttickets.php(0): WHMCS\Admin->display() 13 Next Illuminate\Database\QueryException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'whmcs.mod_ticketsd' doesn't exist (SQL: select count(*) as aggregate from mod_ticketsd where usertype = client and tid = 960 and depid = 1) in /var/www/html/vendor/illuminate/database/Connection.php:713 Stack trace: 0 /var/www/html/vendor/illuminate/database/Connection.php(669): Illuminate\Database\Connection->runQueryCallback('select count(*)...', Array, Object(Closure)) 1 /var/www/html/vendor/illuminate/database/Connection.php(342): Illuminate\Database\Connection->run('select count(*)...', Array, Object(Closure)) 2 /var/www/html/vendor/illuminate/database/Query/Builder.php(1583): Illuminate\Database\Connection->select('select count(*)...', Array, true) 3 /var/www/html/vendor/illuminate/database/Query/Builder.php(1569): Illuminate\Database\Query\Builder->runSelect() 4 /var/www/html/vendor/illuminate/database/Query/Builder.php(1974): Illuminate\Database\Query\Builder->get(Array) 5 /var/www/html/vendor/illuminate/database/Query/Builder.php(1894): Illuminate\Database\Query\Builder->aggregate('count', Array) 6 /var/www/html/modules/addons/ticketsd/hooks.php(0): Illuminate\Database\Query\Builder->count() 7 /var/www/html/includes/hookfunctions.php(0): WHMCS\Utility\SafeInclude::{closure}(Array) 8 /var/www/html/vendor/whmcs/whmcs-foundation/lib/Admin.php(0): run_hook('AdminAreaPage', Array) 9 /var/www/html/vendor/whmcs/whmcs-foundation/lib/Admin.php(0): WHMCS\Admin->output() 10 /var/www/html/portal/supporttickets.php(0): WHMCS\Admin->display() Ticket support is trying to tell us that this is a third party modification and that the 7.9 update doesn't bother those, however we downloaded 7.8.3 from WHMCS site and wouldn't ya know, /vendor/illuminate/ is included with that download. So this isn't a third party mod that we installed however WHMCS is saying it is. In checking our database backup done before the upgrade. I have also gone back to early December and November database backups and this table doesn't exist there either. Anyone have ideas? Thanks.
  5. @HardSoftCode thank you for providing that clarification. Tried reaching out to you guys on twitter and through your website but received no responses. Additionally your website created an error upon submission of a contact us form. Knowing this information, we will proceed. Thank you!
  6. It'd be nice if WHMCS would include the ability, by default and without the need of extra modules, to enable an encrypted area for clients to leave sensitive information when they open a ticket. Being hamstrung waiting on a third party dev to update a module before you can take advantage of security/feature enhancements in a new release of WHMCS is annoying. Thanks
  7. We'd love to use that module but they still have not updated it to 7.5 yet. They keep doing everything else BUT that module.
  8. I shouldn't be expected to use a "work around" for years just because one exists. This is just laziness upon the devs. A bug in the software, is a bug that shouldn't be there. Looking at how many people it affects before deciding to fix your product is again, laziness. You just effectively said with your statement that, "oh we know our product has bugs, but we have your money now, so bugger off, we don't care." If I am having a defect with your product, I expect that defect to be fixed. Be it security, bug, bloat, whatever. I don't expect you to turn a blind eye to it and expect me to continue to pay you 100$/year for software that you knowingly won't fix. 700 out of how many reported? How many bugs older than 1 year remain outstanding? How many bugs older than 2 years remain outstanding? How many critical bugs, how many security related bugs? 700 bugs could be as simple as a missing . in a sentence or a poor language translation. Some clarity to this statement to give us more context upon what actual bugs you've fixed would be helpful. and a great many of these features had to be stripped from our install as it errors out with PHP7. Could you at least update your software and bring it to current release of PHP before you muck it up anymore? Oh really? Have you looked at your requests section lately? Don't feed us a corporate line of muck, we're not falling for it. While the new forums are a good start, how about keeping your customers happy so they continue to recommend your product? Selling based upon reputation alone is only going to last you for so long before it runs out. Then what? We are left with a product full of bugs that have been reported and not fixed. Thousands of enhancements to make the product better and yet they're ignored. Why should we utilize our precious time every day to report things to you if you won't do anything with them unless you deem it worthy? What benefit do we get? If your feedback/requests forums are any indications, there are no benefits to reporting it since, as you say, "everything is evaluated." and "always on the lookout for issues gaining a lot of traction." How much traction does a feature enhancement require before you'll give it a look? I'm sure I can pay a bunch of people to start upvoting things to finally get the attention needed to fix the product. Matt, I appreciate where you're coming from, but most of your statement is corporate banter. Your customers want to see action. We want to see outstanding issues resolved. Bugs shouldn't take years to fix just because two people are inconvenienced. There are some universally understood priorities with product development and I'm sure most would agree: 1) Security issues 2) Major bugs 3) Enhancements to product 4) Minor bug fixes It may be high time for WHMCS to take a step back from number 3 and focus your attention on 1, 2, and 4. Polish up the product, make it shine, then get back to adding user requested enhancements. Note I said user, not those with the biggest Amex Platinum cards. AB
  9. @yggdrasil I appreciate your comments on this thread but lets keep it to the topic at hand. Mr @bear has generally always been fair and respectful, even in the face of rudeness from folks. The current state of WHT is not the topic of this thread. If you wish to take that conversation offline with Mr. Bear please feel free. Thanks.
  10. Regarding this: "being clear about which topic is problematic is critical to actually improving things" Let me make it crystal clear for you: the rate of development to add features that users truly need or want moves at the pace of the United States Congress. It's slow, it appears to take no input from the user base, and needless features are being added to the software that likely the majority of people don't use. Regarding this: "The feedback Ive gotten from customers is that they want major new features, and quality of life refinements, and bug fixes, and on-going maintenance, and back porting fixes, and documentation, and engagement. Implementing feature requests and new ideas we have is balanced with these other priorities. If there are areas you feel like we need are imbalanced, that is valuable feedback. My experience has been that majority of our customers want an 'all of the above' approach, not just one or two elements.I think that seeing a lot of feature requests being generated is a sign that WHMCS is a useful and important product. When you have a tool that solves some problem for you, it gives you space and time to notice new problems that the tool might be able to help you with. This happens to all software programs of a minimum level of complexity. Jamie Zawinski summed up this trend with his maxim: "Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones that can." The number of feature requests coming in reflects the many different and innovative ways people are using WHMCS, the dynamic nature of this industry, and how central WHMCS is to our customers business." Forgive me while I contain my disdain for this response. Any software development company would tell you that customers want enhancements/features, QOL improvements, bug fixes, maintenance, and improved documentation. I believe your statement is a generic canned response and shows the general lack of understanding of what your user base wants. Looking over all of the feature enhancements requested the majority of it appears to be administrative back end enhancements needed to make the product function as needed/expected. Yet there are many requests that have been pending for four years or more. The lack of response from WHMCS to these issues really shows that WHMCS is out of touch with its userbase and isn't paying attention to the ongoing requests from it's users. You've started down the right path on ending support for older versions, which takes care of back porting fixes, however this is overshadowed by the fact the product is somewhat stagnant. There hasn't been many "ground breaking" enhancements for the back end user. No ticket priorities, no easy way to duplicate product add on's, no way to discount only the base product not add on's, etc. The only thing that might be considered "ground breaking" is the annoying feature of entering your admin password every time you enter a sensitive area. And even this feature is annoying at best with no option to let us turn it off. The documentation for the product leaves a bit to be desired and generic canned responses from support like "its your server configuration, sorry." does not lend itself to being helpful in allowing your users to troubleshoot their own installations. Want less support tickets? Give us documentation that allows us to walk through the issues of your software and gives us a direction to go when trying to resolve something your software broke or isn't compatible with (i.e: PHP7). I can't tell you how many hours we have spent removing bloat from WHMCS to get it working properly with PHP7 and most of it stems from all of the integrations with things, generally payment processors and control panels. A suggested list of focus areas for WHMCS should be: 1) security issues 2) compatibility with newer technology (php7, etc.) 3) Bug fixes 4) On-going maintenance 5) QOL enhancements 6) New features as requested by the user base not those who likely pay a handsome sum of cash to WHMCS. 7) documentation. 8 ) Tighten up on your supported versions. 1 Major previous release support as LTS, and current tree only. Older versions are no longer supported and no longer receive security or bug fixes. Regarding this: "Those programs which cannot so expand are replaced by ones that can" Your product is on the verge of being replaced. I wouldn't hang your hat on that quote by Jamie. Your failure to listen to the feedback and needs of your customer's is becoming your own undoing. We are asking you to innovate, asking you to improve your product so we can continue to grow and be successful partners, and yet I'd have better luck talking to the dust bunnies in my CPU fan. Your user base is passionate, dedicated, and growing frustrated by the lack of innovation from WHMCS. You have years and years of requests in the feedback forum and most are "under consideration" or "declined", the vast majority of which have zero comments from WHMCS on an idea of when we can expect it or if ever. We need functionality today to fix a pain point that has been evident even when we were a client many years ago. We left because you didn't have that functionality. We came back because we outgrew our previous CRM/Billing system (ClientExec for those curious), and yet a feature we requested four years ago, still hasn't been considered or even given an estimate of when it will be added. To get that functionality, we will need to spend several hundreds of dollars to outsource the work to ModulesGarden. Would WHMCS like to chip in to those costs we bear to make your product functional? Would WHMCS comp the annual renewal of maintenance for us? How about the ongoing costs back to ModulesGarden every time you have a version change? These types of issues are going to be the undoing of WHMCS. I'd be happy to pay more to our ongoing maintenance if I knew it was going to get us the features and enhancements we desperately need. Regarding this: "I think that seeing a lot of feature requests being generated is a sign that WHMCS is a useful and important product. " Let me pick up my chin from the floor for just a minute. Feature requests or product enhancements being generated is one thing, but when you do nothing with that information, it makes your product no longer useful or important. When dozens of people "up vote" a request, do you still see this is a feature request, or a deficiency in the software? If it's the former then I'd kindly ask you to rethink that. If it's the latter, then why haven't you moved on it yet? If dozens of people are telling you its a pain point, when does it move from a feature request to a product deficiency that probably deserves some time or at least a response from WHMCS? Your product is no longer useful or relevant when you stop incorporating features that are requested by your user base, especially when dozens of them ask for the same feature. Is the only way to get development in the product is by breaking our the Amex Platinum and getting cozy with someone? Because if that's the case, let me know who and I'll be on my way to England. Regarding this: "The idea that if WHMCS were working as fast as it should, the number of open feature requests would go down, does not match my experience of how software evolves - for any product Ive ever worked on. Software where the number feature requests go down over time is typically software that is dead or abandoned." Really? Because that's not been my experience. My experience has shown me that when customers are happy, they tell others. Others join the ecosystem and bring new ideas along. If there is a decline in requests over time, then that generally means you've made your clients happy or the next new shiny thing hasn't happened yet. Aren't happy client's what we are all after in the first place? And if WHMCS works as fast as it should, I'm pretty sure you'd accomplish more work than the United States Government at the moment. However, we all know that you are doing something on the product, as evidenced by the Weebly and SSL features recently released, but I do not believe your attention is on the right subjects at the moment. Attention needs to be paid to requests made by your users. I looked in the requests forum and I did not see a Weebly topic or SSL integration that jumped out at me. Could you share with us where you received feedback that those two pieces were worth of the scant developer time? Regarding this: "Ultimately our company leadership has to take all of the information they can gather and make choices. Feedback from the community is an important part of the information they consider. That feedback comes in many different ways. The feature request system is a medium we have found helpful. If your feedback is "we want more new features", we hear that. If the feedback is: "these four features requests are really important to me and here is why" - that is also helpful. If you can order them by priority - even better." We have already done this for you by the numerous "up votes" people have attached to the feature requests and yet those requests have fallen upon deaf ears. Again, if someone needs to break out the Amex Platinum to finally get the attention the users are asking for on the product, tell me when and where, I'll be on a plane. Regarding this: "I also appreciate the feedback on the difficulty in finding specific ideas that has come up. Sorting through 1000+ items is not a simple problem. Feedback on how we can make that easier would be great. " Easy. Set honest and realistic expectations of time on when/how features can be implemented. Can this feature be implemented in 30/60/90 days? Does this require a major rewrite of code? Where WHMCS is dropping the ball is by not talking to us. Not letting us know realistic expectations from a development side. Have some different status' other than "under consideration". Assign some time expectations to the requests. Easy, moderate, difficult to implement and where it realistically falls on your roadmap. I get some things require far too much development time to be practical, however if a third party developer can knock something out in a few weeks, why would we expect you to take four years to do it? Your lack of communications back to us is your own worst enemy. Regarding this: "Im not sure this is a defence of the feature request system, but I hope that it does work as a defence of interaction and communication. As an employee, I am most successful when I deliver high quality software that adds value for my customers. WHMCS as an organization is best off if we provide the tools our customers need. Our customers are better off when WHMCS solves problems. The most effective way to get there is collaboratively." I must respectfully shake my head at this response. I appreciate where you're coming from but when only one side of the equation is doing the work, that is not a collaboration. We've given you everything you need to let you know where customers stand, and yet talking to my CPU dust bunnies would accomplish more than expecting WHMCS to proceed on user feedback. WHMCS needs to spend some serious time reviewing the requests already in the system and begin to map these out for users. Let us know when we can expect things. The lack of communications from WHMCS is one of the biggest frustration points to date.
  11. John, not sure why your reply isn't showing up for me, however in regards to your question about what features have been pending for years, here is a small sampling: https://requests.whmcs.com/topic/support-ticket-custom-field-type-for-encrypted-data 7 up votes and this had to be done by a third party vendor to make available. Which means now we would have to pay two folks instead of having it as a core piece of the software. Our pain point: https://requests.whmcs.com/topic/configurable-options-duplicate-copy 4 years. 10 up votes. 400$ out of pocket to enable this functionality plus ongoing upgrade costs. Edit: This one seems to be able to be knocked out in just a matter of days, maybe a month at most. https://requests.whmcs.com/topic/i-want-to-be-able-to-edit-my-whmcs-support-ticket-priorities 4 years. 34 up votes. While not a priority for us, this would certainly become helpful later for us. https://requests.whmcs.com/topic/promotions-apply-only-to-configurable-options-upgraded-hard-drives-memory-etc 4 years. 15 up votes. This is a minor pain point for us as we have found a work around, although annoying. https://requests.whmcs.com/topic/multi-company-support 4 years 177 up votes. How many up votes before serious consideration is given? These are just some examples of things that have been suggested and on the outward appearance, no consideration given.
  12. We originally were a WHMCS customer, left because of stagnant development and ongoing issues with PDF invoice generation. We went to ClientExec and enjoyed the product but we outgrew it and came back a few years ago to WHMCS. We have been looking at Blesta as an alternative but we would likely have to give up a few of the integrations we already have. We are not to the point we need Ubersmith yet, but we have used them in the past with success. We actually left Ubersmith and came to WHMCS.
  13. I agree, there are many enhancements, but there's also a lot the software is missing to make it stellar.
  14. John, I appreciate the answer but if you truly pride yourself on listening to the customers, then why is almost every feature request set to under consideration, with a vast majority of them many years old? I get you have limited resources but seriously, we can't get an update from the dev team with a "hey, we are still looking at this!" or something to let us know it's actually being considered? I submitted a comment the other day and it was immediately set to under consideration with no involvement from you for a while, at which it was deleted and rerouted to a topic already opened. Four years John. I shouldn't have to pay a dev 400$ to fix the software because it's missing a basic component.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated