Jump to content

Kian

GearHead
  • Content Count

    1955
  • Joined

  • Last visited

  • Days Won

    72

Kian last won the day on January 7

Kian had the most liked content!

Community Reputation

314 Excellent

About Kian

  • Rank
    Senior Member

Recent Profile Visitors

11171 profile views
  1. The security issue is that {php} tag gives designers the possibility to run PHP code. Except for developers, no one should be able to use PHP code.
  2. As I told you months ago, I am no longer interested in fighting against another tax puzzle. I have enough of tax rules, electronic invoicing, crazy accountants, rules that keep changing overnight, Brexit, MOSS yes/no, tax stamps, special tax regimes, GDPR, cookie law, split payment, Italy, Germany, USA, Finland, Sweden, Australia and silly requests. All while WHMCS keeps releasing bugs. I still need to support WHMCS v5, v6, v7 and v8 simultaneously due to customers still running older versions. The standard reply you could expect from another developer is "Not my problem, upgrade WHMCS". Similarly, I also support third-party modules and templates developed by my own competitors just to be helpful. Try asking to any of my competitor if they're willing to move a finger for me. Nope. Every developer lives in his own world. Every conflict they cause with other modules is not their business. Especially when they are the sole responsibile of the issue due to their horrific js and css rules. Enough is enough. It's 14 years that I'm fixing problems caused by WHMCS, colleagues and competitors. All while I keep up with the crazy world of billing. As I said you in another occasion, I'm pretty sure I can fix your problem easily. But the idea that when you start issuing RCTI another bug of WHMCS v8 will force me to rethink everything from scratch is depressing. I'd pay 10k just to stop WHMCS from releasing updates. The best gift i could ever ask for. Sadly, I keep finding devastating bugs but I no longer report them. If WHMCS doesn't care of bugs, why should I? Let's enjoy what we have and fly low 🤞 Anyway feel free to submit a new ticket with details and passwords but I don't guarantee you anything. If I sense another bug I'm out.
  3. You have a problem with your auto increments. I suspect that during installation or upgrade an error prevented WHMCS from completing the queries that define A_I on tables. You should add them manuslly or submit a ticket to WHMCS.
  4. One thing that annoys me is that in WHMCS there's no clear difference between Deprecated and Removed. As you know there's a big difference between them but to me it looks that WHMCS use both terms as synonymous. If they remove Six I want to ⚰️ Why? Don't you like an ocean of white with paddings that extend from Milan to Tokyo? I have a 34" inch display 21:9 and with twenty-one I'm reading contents as if they were written on a recepit. Every page I open hurts my eyes. All white and bland. We have huge screen space but less information. I don't know about you guys but my full-time job can't be to keep up with unwanted changes and bugs of WHMCS. I'm still dealing with bugs that originate from v4 to v8 and now there's Bootstrap 4 and twenty-one. Maybe this is the reason why WHMCS developers are almost extinct. Back to the new template system, if they remove six I'm probably done with this software. I also work with Amazon, eBay and tens of other Marketplaces including couriers and logistics networks. They are a joke compared to WHMCS maintainability. Let me explain. If you happen to have modules with many front-end pages you are screwed because: You need to make your templates compatible with Twenty-One In the same time you still have to support Six And people that are still running WHMCS v5, v6, v7 and v8 (not v8.1) Basically we are talking about doubling efforts. Imagine you have 3 modules with lot of complex front-end pages. Now you have to maintain 6 templates. This is ridiculous. "Minimal" is the new word to use when you want to say "I am lazy and I don't want to spend time creating a decent UI hence let's pretend this is minimalism"
  5. Quoting from docs. Like when? Weeks? Months? Years?
  6. https://docs.whmcs.com/Live_Chat_Addon
  7. Yes but editing tpl doesn't give you the possibility to run custom PHP scripts (when using hooks isn't possible).
  8. With an .htaccess rule like this one RewriteRule ^$ ./anypageyouwant.php [L] You can replace default index page with anything you want.
  9. Speaking in general, the more index you have the faster SELECT proform. Especially if such index are used for JOIN. And we all know that the above tables are super-connected with eachother. That being said, there is another side to the coin. The overuse of index slows UPDATE, INSERT and DELETE statements. Simply put, it's a competition between data retrieval and manipulation. You can't be fast at both* In other words with the above queries on paper you make "reads" faster but be prepared to wait a little longer when you update prices, configurable options etc. * Actually you can. On tables with heavy data manipulation you ideally use only the primary index. This way updates, iserts and deletes are super fast. When it comes to retreiving data, every X minutes you export & sync data to a secondary table fully indexed. This way you can perform select, sort, join, group, having, where (...) in the most efficient way.
  10. There's nothing wrong. What you see here is the result of Hook Debug Mode. It shows you when/how each hook fires. FraudCheckFailed is an hook point that as far as I know always triggers as it's part of WHMCS workflow even if you are not using any anti-fraud system.
  11. I could be wrong (I'm not using standard module functions in my projects) but your my_mod_activate() function should be based on the latest version of your module. Let's say you released the following versions: 1.0.0 1.0.1 - You changed this: UPDATE sometable SET animal = 'Dog' 1.0.2 - You changed this: UPDATE sometable SET animal = 'Cat' In my_mod_upgrade() you have the following: function my_mod_upgrade($vars) { $currentlyInstalledVersion = $vars['version']; if ($currentlyInstalledVersion < 1.0.1) { // UPDATE sometable SET animal = 'Dog' } if ($currentlyInstalledVersion < 1.0.2) { // UPDATE sometable SET animal = 'Cat' } return; } my_mod_activate() need to be like this: function my_mod_activate() { // CREATE sometable (animal VARCHAR(30) NOT NULL) // INSERT INTO sometable (animal) VALUS ('Cat') } As you can the the activation uses "Cat" (the value of the latest version). That said, your my_mod_config() needs to go with version 1.0.3. In other words fresh installation do not trigger upgrade function. function my_mod_config() { $configarray = array( "name" => "My Module", "description" => "Description goes here....", "version" => "1.0.3", "author" => "ChrisTERiS", "language" => "english", "fields" => array( )); return $configarray; } Edit: please, ignore my versioning (the 1.0.0). I suspect that WHMCS supports only 1.0 format.
  12. It is worth to say that the linked hook only tracks page views. Moreover the same approach can't be used to track other events (eg. purchase).
  13. This feature does not exist in WHMCS but can be implemented. You can automatically assign each quote to the person who created it using sessions and an action hook.
  14. Don't put the article about "regime dei minimi" in company details. It should be placed in invoice footer. Same goes for "marca da bollo".
  15. Make sure you used TCPDF syntax. invoicepdffooter.ppl doesn't use Smarty. Something like follows. $pdf->Ln(-5); $pdf->SetFont($pdfFont, '', 6); $pdf->MultiCell(140, 5, 'The cat is on the table', 0, 'C', '', 1, 35, '', true);
×
×
  • 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