Bartucxp

Hello, Exact page url: adminpanelurl/configticketspamcontrol.php There wasn't pagination on this page before. Of course, pagination is cool but we should have option to see all records in a page or we should have an option to search within blocked senders. When we block an email accidently, it is impossible to find and remove it from spam control page(3500+ records, 72 pages). Our only choice is to find and delete it using phpmyadmin(when searching an email address with domain). Regards

This is reasonable, but not my responsibilty. Also, cant wait to get hacked on critical security updates. --- Please don't get me wrong, I realise whmcs is a great system and testing every single function under different conditions is a very big job. I never said it is simple. But I believe it is very necessary. Even if not every single functionality, at least core functions and most used modules should be tested. I just make a recommendation. I'm here to criticise for a good purpose.

There was an error before caused by a misspelling. A letter error. Can't remember the exact error right now but a letter in a function name was incorrect, there was no way to miss it if that page was visited before releasing it. Also last update, resellerclub module was not working, there is no way to miss it if someone tried a resellerclub function. WHMCS is a big system with thousands of users. I believe spending few days for testing everything with only 2 php versions(5.2.x and 5.3.x) will be fine. I can see this is not what you're doing. I don't know your test procedure but missing that kind of errors basicly shows that it is not being tested enough before releases. Because some errors doesn't require different scenarios.

What I'm suggesting is exactly this. Almost everywhere provides test api credientals so I suggest everything to be tested on live data. Just one test before a release, I understand it may cause some expense but everything would be much better.

It happens sometimes(don't know why, maybe client somehow submits same form twice or something), I suggest you to simple remove both orders and place a new order for your client.

Hello, For about a year, each upgrade breaks things(without an exception). With each upgrade, somethings stops working. Critical things like currency convertion or resellerclub module gets hotfixes but most fixes takes really long time(for example, mass mailing was working fine and it was broken on October 2013 with an upgrade and it got fixed with 5.3.4 upgrade. It took months!). WHMCS is a system that shouldn't have such errors. Companies are at stake here. You provide a great script that have many tools, people/companies having some habits using it(no one is using it the same way!), and when you break something that is important to someone, you can't know how much trouble it causes. Except for admin side, last upgrades(5.3.3 and 5.3.4) also affected client side with conversion problems, invoice redirect problems and resellerclub etc.. domain registration problems. I believe if you hire just one person and provide him/her with all the service subscriptions supported by WHMCS(such as resellerclub subscription, cpanel server, etc.. only one of everything provided with whmcs) and this person runs tests for everything before each release, everything would be much better. I'm saying this as a PHP coder, you did test everything when you code something for the first time, right? I mean, didn't you test resellerclub api when you first created it? Of course you did, but why you don't test it again when you change things about it? It is not just me, but everyone says that you're the only company to break things with upgrades. You can simply check web hosting and webmaster forums to realise that. If you don't trust one person about that, simply build a beta test team and make sure every single function of WHMCS is tested before release, isn't that how it is supposed to be? Of course I understand you can't test everything before releases(even with a beta test team) and there will always be bugs. Also you fix things with updates. But it is not important to end user when you fix something that is already working or when you make it work better. Please take this only as a suggestion. I started using whmcs before whmcs 4.0 version. I know how it used to be, there were no erros after upgrades, at least upgrades broke nothing and when a bug is reported, a hotfix used to issued in few days. But now, everything is broken with upgrades one by one and fixes takes months unless you consider it to be "critical". But you forget that some little things also can be very critical for your users. Everything wants you to work the way you used to work. People are looking for other solutions. Big companies are preparing their very own automation systems and small ones are just looking for something they can switch to. I small research will make you realise that. Regards Cihan

Just upload resellerclub module from 5.3.3 version, you'll be fine.

It is happening on 5.3.4(updated today). I've uploaded modules/registrars/resellerclub folder that belongs to 5.3.3 and problem solved which means resellerclub module provided with 5.3.4 is not working. Using PHP 5.2.17(if related somehow).

Exact error on domain register: Fatal error: Call to a member function getLastTLDSegment() on a non-object in /home/user/public_html/modules/registrars/resellerclub/resellerclub.php on line 0

Hi, I'm also using 5.2.17 but I can't update it because of some other software on the server.

Thats not only about holidays. I wish it was. When a server is having trouble, we must inform users on this server. You can't know what problems this causing for us. We must make server migrations and tell clients to change nameservers. Just because we can't mass mail to them, some of our plans like this one is still on hold. There is a broken server and we must change it - tell customers to change nameservers. We can't do it! I hope you can understand this. Holidays was just an example. I'm not saying that you're not working to make whmcs better. But maybe you're following the wrong way? I've reported an error and I'm sure fixing it would take less time from writing ticket answers. So everyone would be happy. Also if you can check my other ticket about unicode chars in PDF invoices( #CRS-649318 ), I've found the solution on the forum. It was because smarty fonts directory has changed. I had no idea! Instead of creating a case number for it, they would explain this to me. A simple file copy solved the problem and if I didn't take a look at forums, I'd wait for upgrades for a solution. Thats makes people feel you don't even care about tickets-don't investigate problems- and you only answer so you can say "we answered the ticket". I hope I made my point. Thanks for your interest and I hope you can get it fixed for me on Monday. Regards

Yes, I'm aware of that, but how can you let a critical problem(at least for us) least for months and not even resolved in 5.3.3 upgrade? Is that so hard to fix that? Fixing this will be very good for our business. Because of that error, we're looking for other solutions to migrate from whmcs. Because its been 4 months and error didn't get fixed, also each upgrade adding new errors instead of fixing previous ones. Please tell me if I'm wrong here, but an upgrade is supposed to fix somethings, not break. If it break things that is critical for our business, there should be hotfixes since your code is encoded.

Sure, it is #CVI-016605 Thats a new ticket, but the ticket that no one cares is this one: #KYX-678432 We used to get hotfixes in few days for such errors about 1-2 years ago. But now some errors doesn't even get resolved for months(example: #KYX-678432)

This is email template content(domain registration confirmation): {if $domain_tld eq "tk"}..........{else}.........{/if} Which results in that: Fatal error: func_get_args(): Can't be used as a function parameter in /home/username/public_html/includes/classes/WHMCS/Smarty/Compiler.php on line 0 Because of that error, while adding payment to invoice(for domain registration), I get same error and F5 results in adding payment twice. Removing if condition from email template solves the problem(that was working before 5.3.3 upgrade). I didn't try that for other mail templates, but I assume it is the same for others too.

I got smarty compile error on add payment twice after 5.3.3 upgrade which results in double posting payments. But it only happened twice so I have nothing to create a ticket as that doesn't happen all the time and no one will be able to reproduce this error(including me). It just occurs randomly. New version doesn't seem to be reliable.