Jump to content

Kian

GearHead
  • Content Count

    2051
  • Joined

  • Last visited

  • Days Won

    101

Kian last won the day on January 20

Kian had the most liked content!

Community Reputation

389 Excellent

About Kian

  • Rank
    Senior Member

Recent Profile Visitors

13613 profile views
  1. I don't see how having many files is a security risk. If I manage to upload a backdoor on your system, nothing prevents me from burying it in includes/api, naming it addclients.php and obfuscating it with ionCube so that you will never know what is going on. More intelligently I could simply inject my backdoor in an official file of WHMCS. For example I can deobfuscate clientarea.php, add my backdoor and make it accessible with a specific query string. Then I re-obfuscate the entire thing to complete my job. Unless you are constantly watching access log you can't realize what is going on. Not to mention I could hide myself even better using a query string that looks as standard as possible. Personally I protect my system against this kind of problems running a script every couple of hours that compares the checksum of every file I have on the server with the ones included in the official release of WHMCS (same version). If I find a mismatch, the script makes this file harmless (eg. renaming it clientarea.php.suspicious) and sends me an email. Similarly the script also detects php files that are not part of the official release of WHMCS. In this case I review all these potential intruders on a panel where I can whitelist them in case it's a false positive (eg. my own scripts) or destroy them and make further analisys. I was going to release this toy for free on Github but things happened.
  2. Trovato il problema. In Moduli > Billing Exension > Impostazioni > Fatturazione Elettronica > Percorso FTP (facoltativo) avevi indicato il percorso public_html/admin/fatture/ che tuttavia non esiste nel nodo FTP. Per essere più precisi con quell'host, username e password entri direttamente nella root del nodo per intenderci dove ci sono le cartelle INVIATE e NON_INVIATE. Avendo indicato il path public_html/admin/fatture/, il modulo cerca di mettere il file XML dove hai indicato ma siccome quelle directory non esistono, ricevi il risposta il messaggio d'errore "Invio XML al server FTP non riuscito". Ho provveduto a rimuovere dalle impostazioni il percorso e provato a generare con successo un XML. La fattura in questione è la numero #5 con ID #120 (il link diretto è invoices.php?action=edit&id=120). Non sapendo se il tuo WHMCS è in produzione o ancora in fase di test, ho riportato indietro di 1 il Next ID delle fatture così che la prossima fattura generata sarà di nuovo la 5. Quando hai finito di controllare ricordati di eliminare la fattura che ho generato per il test. Detto questo ho notato una stranezza. C'è un leggero ritardo credo nell'esecuzione delle query nel database. Non so come spiegarlo ma è come se ci fosse a monte un qualcosa che fa da cache e che recepisce le cose con un delay. Ad esempio quando ho convertito la proforma in fattura, ho dovuto refreshare un'altra volta la pagina per vedere il cambio di ID. Stesso discorso quando ho generato l'XML. Anche se il modulo lo aveva creato ed inviato al nodo FTP, al refresh della pagina vedevo ancora il pulsante Genera XML. Refreshando subito è diventato blu. Quanto a Digiting, questo è già integrato con BX. Vai su Moduli > Billing Exension > Impostazioni > Fatturazione Elettronica > Intermediario e premi il tasto Manuale. Ti si aprirà il modale mostrato in basso. Basta che switchi da Manuale a Digiting. Ovviamente per poterlo utilizzare dovrai prima contattare quelli di Digiting ed acquistare il loro servizio. Prima però faccio alcune precisazioni che sono visibili anche nella documentazione della fatturazione elettronica. Con Digiting non c'è nessuna partnership in corso nel senso che se acquisti il loro servizio noi non guadagnamo niente. In seconda analisi non ho assolutamente idea di quanto costi. Anni fa quando ho realizzato l'integrazione ho chiesto più volte delucidazioni sul prezzo senza avere informazioni esaustive. So che c'è chi ha pagato 99, chi 200, 250... in altre parole il prezzo che vedi indicato nel modale di BX è puramente indicativo. Per il resto ti confermo che se utilizzi il loro servizio con l'accoppiata di BX non dovrai muovere un dito. Con il cron giornaliero BX genera gli XML e li mette nel nodo FTP. Poi passa Digiting che li preleva e trasmette all'AdE. Se è tutto ok vengono, gli XML vengono impostati come "verdi" (Consegnate e Non Consegnate). Al contrario se ci sono problemi (es. CF che non esiste in anagrafe tributaria) viene impostata in "rosso" (Scartata). Se premi il pulsantino dedicato (Esito)... Vedrai nel modale le motivazioni esatte dello scarto come in questo screen d'esempio che tuttavia non riguarda uno scarto ma una fattura consegnata con successo. Ti ricordo comunque che puoi anche lasciare in Manuale e risparmiarti i soldi di Digiting. Se emetti meno di 24.000 fatture l'anno, puoi tranquillamente inviare gli XML massivamente una volta ogni 10 giorni su un servizio come quello di Aruba che è economicissimo.
  3. Ho provato qualche ora fa ad accere a quella stessa fattura "blu" (simboleggia che l'XML è stato generato) e mi risulta che l'XML è stato rimosso dal nodo FTP. Di fatto mi propone se voglio o meno fare il detach dal database ovverosia dire al modulo di dimenticarsi di quell'XML. Per caso hai risolto? C'erano problemi con il percorso del nodo oppure hai un qualche genere di automatismo che sposta o elimina gli XML? p.s. Ti consiglio di rimuovere lo screenshot o quanto meno cambiare il path amministrativo da "admin" a qualche altra cosa per questo motivo.
  4. PREAMBLE 👋 Given the complexity of modules, delivering support is challenging especially when you customers made us clear more than once that modules' pricing was more important than the possibility of having better support. We are not blaming, we are just stating a fact. Since providing a decent customer support to so many people maintaining the same price isn't possible , on October 2021 we completed the transition from a free to a premium support with direct communication, guaranteed response and intervention times. Keep in mind that all modules will still work and be supported by us. It's just that free support via ticket is no longer provided. Premium support is the only form of support that allows us to meet high standards. Moreover the service is reserved to a limited number of customers in line with our SLA. NEED HELP? 😵 We understand that many still need a way to get problems solved without the need to purchase a dedicated plan for support. Here is where this board comes to help. This board acts as a place where you can get support by me (no guarantee) or by fellow users that are using your same module. Don't forget this board is public and anyone can view so avoid sharing credentials or revealing screenshots. Use direct messages to share sensitive data. Also don't forget there is plenty of documentation available on our site. Who knows... maybe this new form of "open support" could be more beneficial than years of spent dealing with tickets. I don't exclude the possibility of moving to Reddit or something similar in case board admins think we are out of place. PARLI ITALIANO? 🇮🇹 Allora dillo così potrò risponderti in italiano.
  5. I am more than glad to discuss this since it gives me the opportunity to prove that what moves me. Surely I'm not the best business man and developer of the world but I have a lot of direct experience since I'm playing with WHMCS since 2007. Let's go. If I had a euro for every time I heard that, I would own a Ferrari. There are probably 50k providers using WHMCS. Can you imagine how many developers and CEOs are out there? Ones that use this software on a daily basis sharing the same needs and requirements. There are many opportunities and potential customers to fulfill the growth of multiple companies. There's room for everyone. This market is rich and can provide for everyone. That being said, apart from the usual Modulesgarden and few more companies, I can't see anyone showing up with a module that solves something relevant and that is maintained for more than a couple of weeks. Why is it like this? Short answer: easier said than done & the devil is in the details. WHMCS gives people the perception to be a developer-friendly environment. One sees action hooks, API and concludes that making modules and adjustments is not a big deal till you begin coding for real and relize that this is far from being true. When I started in 2007 there were tens of developers actievely releasing modules. They all disappeared. Today there are less than 5 companies left and probably only 1 or 2 are capable of assisting you decently while they maintain their softwares in this WHMCS that keeps growing bugs, bloats and stupid ideas. It is also worth to underline that many of these companies are focusing on meeting small and trouble-free needs like creating templates, micro-management scripts, integrating some kind of services with API and payment gateways. With very few exceptions, nothing can match the complexity of Modulesgarden works. In essence we are talking about a market with almost no competition so two questions arise. First. Why in such a rich market with almost no competition and many needs that are waiting to be satisfied no one is investing money into module development? Second. If this market is rich and creating modules is easy, why Modulesgarden and others are expanding or moving to other markets? For me the answer is that creating modules for WHMCS is not like creating plugins for WordPress where tens of thousands of devs are welcome. In WHMCS no one gives a flying duck of your work. They never valued nor considered the job of third-party developers that are helping them to sell their product. This shouldn't surprise us as they don't even care about their own customers. Also don't forget that as a developer you are required to pruchase WHMCS in order to start coding. As for me, I started building this monster (Billing Extension) in 2014 exactly because I had the idea that coding in WHMCS was relatively easy and profitable. I was wrong as hell. Unfortunately I couldn't predict years or bad twists by WHMCS. To make matters worse, unlike most of my competitors, I focused on the dark side of WHMCS aiming to fix its issues and add missing features. If I could go back in time, I would stay away from billing. Profit-wise, creating a template or couple of payment gateways would have been the best decision but I don't regret it since I learned many things and met many people. So today I have a module so complex that would take a company of the size of Modulesgarden to support customers and maintain its code. I tried to scale-up. I hired developers, added more funds, merged modules rebuilding them from scratch with the same framework (1 year of work), wrote 500+ pages of docs in two languages, tried to increase prices (...) but it was still not enough. All while WHMCS from day to night release once another a version that breaks the mega-complex script that took you one month of work and that still needs to work in the old way only for people running older versions of WHMCS 🥵 After 3 consecutive years of Ok-ish results and nightmares due to WHMCS releases, I was still dealing with the same problem. I needed more funds to hire more developers but customers didn't want to support us with price increases because (I quote) «We don't need support», «Your module can't cost us more than WHMCS, Plesk or cPanel licenses», «I only use one feature». Fair enough, got it. Ironically few years later WHMCS increased prices up to $1.299.95/mo and put an end to life-time licenses 🤔 In retrospect, I should have raised prices anticipating the trend started by WHMCS, Plesk, cPanel and competitors. You can't grow customers and face increased complexity and challenges driven by poor management of WHMCS keeping the same cheap price. You end up investing tons of man-hours debugging the impossible and money doesn't grow on trees. In conclusion for me it was time to let it go. Funding such an unsustainable business just because you happen to have other sources of income doesn't make it better. You are just prolonging an agony. And for what? Cons: More nightmares, working on 25 December, at night, 12-hours per day (even 16 during emergencies 😑), being permanently unable to keep up with the so-called "stable" releases of WHMCS, receiving five new tickets every time you close one, being "stalked" and "hated" by customers, negative reviews, dealing with all the crazy stuff involving billing and e-invoicing and that unexpected change that forces you to update your module so that it works with: five, six, twentyone, ThemeMetro, Swiftmodders, bootstrap 3, 4, my uncle, my grandmother... give me a break. Pros: some profit that doesn't repay you for the toxicity you have been subjected to. In all honesty it is not worth the effort. I prefer to invest in a grid bot to buy low and sell high on a random crypto. It feels better even when I lose 1k in less than a minute. This reminds me the 2007-2012 period when I was running a quite successful game hosting provider. Everything was going fine. Good vibes, revenues, high dedication, passion for what I was doing till people started playing with ddos attacks to fulfill their egos and live the "hacker-life". At that time anti-ddos protection was very costly. I was spending 28 times the money spent by attackers to ddos me. When you spend 80% the money just to cover firewall and bandwidth costs with servers still lagging, you know it is time to sell your toy and move on. Many years later on a different market and for different reasons the story repeated with WHMCS. Ask me anything but when it comes to gameservers and WHMCS my wallet is closed and my time is better spent on a bycycle in the attempt to win a race on Zwift even if it hurts and leaves you panting like a lizard on a hot rock. Atm I' happily working on a different market that is way more complex than WHMCS but it is still more rewarding. There's a bigger pool of talents and teaching stuff is easier. Not to mention we can plan incomes, expenses and predict changes well ahead simply because there's no entity like WHMCS that feels the urge to pump out sloppy updates driven by nothing that resembles user feedback not couting shady collabs. In my opinion these are only ways to perform well as third-part developer of WHMCS: Making small scripts that are not subjected to WHMCS decisions Work for providers with deep pockets Find a way to gather tens of software developers, designers and specialistys in various fields Embracing open source hoping providers sponsor your project and that other devs come to help. If I had to choose I'd go for open source but considering risks and the fact that WHMCS doesn't care about you, why should I spend my reputation for them? Why should I keep supporting them in chains? At this point I would create my own system
  6. I feel the urge to reply on this matter because what you are saying is wrong on many levels. I'm fine with people leaving bad reviews and not renewing me but I refuse to be compared to what WHMCS is doing. First thing first, at the moment I have direct access to 78 systems where BX is installed and working plus hundreds more that I know are working fine. That being said, unlike WHMCS I'm not saying that the module is problem-free. The vast majority of these problems would be easy to solve if only I had time for the usual stuff: get FTP/backend credentials, connect, see the error, fix the problem. But I can't keep up with such a big number of providers and their requests. I don't even have time for presales questions that would easily bring me money just answering to a couple of questions. In other words, I am not avoiding difficult tickets focussing on ones that bring money. This puts me miles away from what WHMCS is doing. For them it's money > anything else, even reputation. For me it's pure and simple lack of time. I am democratically ignoring every incoming request including ones from coming from huge providers, ones that end up buying dedicated support and that spend weeks trying to get my attention. As I said earlier, I even dropped customers who purchased Pro plan (199€/month each) simply because Business and Enterprise plans were already too much demanding and I don't want to do overselling with the time I don't have. Before covid pandemic I burned 45.000€ of my personal money (I have more sources of income) in the attempt to fuel my business with more resources to meet customers' expectation so please, don't put me on the same level of WHMCS. Unlike them, I invested more than I was earning. I'm working in the hosting business since 2007 and let me tell you that the last 3 years before pandemic got me no profit. I paid expenses and made my developer rich 😁 I'll tell you more. We stopped selling BX multiple times in the attempt to buy us time to hire a new developer and finishing writing documentation. This is something you don't see from WHMCS. They often give you final releases without documentation. We planned to increase BX price multiple times to halve the number of active customers (less tickets) increasing inflow of money. We wanted to reach 399€/year in 3 years but we immediately discarded the idea when the first price increase occurred in 2020 (from 95€ to 149€/year). We received so much complaints in response that we decided to stop. Customers valued cheaper price more than the idea of having better support so unlike WHMCS, we listened to customers and end up building dedicated (paid) support. I'm making modules since 2008 and I spent probably 2 years merging them into bigger and more complete modules keeping the same price. For example BX was born as a combination of 3 modules I was selling 95€/year each. As you can imagine, I lost money from this decision but I did it because I didn't like what my competitors were doing. They were selling tens or tiny modules aiming to maximize profits at the expense of ease of use and maintainability. As if it wasn't enough, I am seriously considering to release all my modules as free and open source on Github. Time will tell. That being said, next time you think I don't move a finger unless I get money, please remember what I just told you. I'm open to criticismI about my decisions and my abilities as a developer, human being etc. but don't compare me to WHMCS greediness. We are on two different planets. BX surely wasn't the module for you and we failed to meet your expectations. I agree with you. I am not here making excuses. Parts of my plans for WHMCS have failed. The best I can do is focusing on a small number of customers hoping the rest can use BX without the need to contact me. Unhappy customers can freely open PayPal disputes. I never reply so that they can get their money back by default. From time to time I even allow them to use the module for free for one year so that they have time to find alternatives. Let me conclude by saying that there must be a reason why there are less than 4 software-companies left in WHMCS. Most of them don't even have employees. With very few exceptions, we all fail to meet expectations. Guess why... 🤔
  7. I'm responding just to point out few things. As for the issue reported here, we're cointinuing here. This is true and not a secret. I don't care about WHMCS anymore (not my products) for reasons described in "Submit ticket" page on my website. My job now is to make sure modules keep working with WHMCS. I no longer try to improve WHMCS features, workaround its numerous bugs or follow their poor decisions. To borrow a phrase favoured by WHMCS, I have no plans to switch my life to purely focussing on bugs/defects and code optimization of a software owned and poorly maintained by another company. WHMCS staff don't care about fixing their software. Me neither. I did for 15 years but enough is enough. Actually it is more expensive. The cheapest plan was Pro (199€ / month) but it has been retired to allow me to focus on customers with Business and Enterprise plans that cost not less than 5 times that price with the service being restricted to Italian providers. Understand that Billing Extension is immensely complex and complexity leads to lot of questions, requests and customizations especially when you face the many problems and shortcomings of WHMCS. Focusing on a small group of companies that can speak my language is mutually profitable and manageable. I didn't plan it but it is what it is. I tried for a decade to follow the steps of Modulesgarden where many devs are capable of handling hundreds of customers but this doesn't work with this module. Try finding developers who are experts in such a very specific position. One that masters WHMCS and understands advanced concepts of billing and electronic invoicing for multiple countries and legislations. I never found one. The amount of time I need to invest to get a developer fluent with such topics is unsustainable given customers' demands. As a reference, on average I need to spend 2 hours on Skype/Zoom with the customer just for showing features and configure part of the settings. Following this, add a couple of hours for fine tuning and the inevitable advanced requests. Not counting when they ask me to teach them how to do stuff in WHMCS & BX. Lastly most of the times when they realize my knowledge of WHMCS and hosting in general, I am "condemned" to be their main and only contact person for all requests. I know it is awful for customers with no support plan but I can't do the impossible. I can't keep up with incoming requests neither grow talents at a sustainable speed. For sure not for a module that costs just 149€ / year in such a framework - WHMCS - that is getting worse from years, that has lost connection with customer base and that I don't think has a future. As if it wasn't enough, it drained my passion for coding. For this reason there's plenty of documentation available in two languages. To people expecting replies, I can only suggest to stop renewing the module if they can't live with my silence. I am truly sorry but life is one and I can't be victim of this platform. WHMCS is now my secondary job I do for a very limited number of customers. My main job is still coding but on a different market and for a company that deserves my time. Peace 👍
  8. Scusa il ritardo (son stato malato). L'errore è decisamente strano in quanto alla row 3 della query presente alla riga 575 dell'installer, c'è l'aggiunta di alcuni record in tbladdonmodules. Il tuo sistema lamenta che il numero di valori forniti è diverso dal numero di colonne che è necessario valorizzare. tbladdonmodules ha 4 colonne obbligatorie: id, module, setting e value. Fatta eccezione per id che è un auto increment, posso assicurarti che le altre 3 colonne sono valorizzate. È come se la tua tabella tbladdonmodules fosse diversa rispetto a quella originale di WHMCS. Ad ogni modo per fare prima apri un ticket mettendo nel messaggio il link a questa discussione e fornisci le credenziali FTP così che possa darci uno sguardo.
  9. Il modulo non si installa perché c'è una precedente installazione bloccata (non conosco i motivi). Per risolvere accedi a phpMyAdmin ed elimina tutte le tabele con prefisso bx_. Fatto questo ripeti l'attivazione del modulo. Se dovessi avere un altro errore scrivi qui. p.s. Se occorre fai tutti i backup del caso
  10. Ciao, segui quanto indicato in questa guida per individuare l'errore che è la causa dell'Oops e riporta qui il risultato. Molto probabilmente ci sarà certamente un Fatal Error.
  11. Hello, I was trying to install and activate your Addon module called "Billing Extension", but after putting all the files in the root, it seems like I can't activate it. When I click the Activate button for that module, an error occurs "Oops! Something went wrong". I really tried everything to fix it but I can't.
     
    It also says
    PDOException: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'bx_cashflow' already exists in /home/hoosty/public_html/modules/addons/BillingExtension/core/BillingExtension_Admin/Installer.php:575
     
    May you help me please? I really tried everything I can to fix it but nothing worked, thanks a lot ...
     
     
  12. Thank you for letting me know that. I didn't know I was still GearHead. Since I left, I occasionally browse from phone / chrome book where titles are missing. I'll DM someone from WHMCS to have that title removed. Side note: when I left, I still had hope in WHMCS. I was expecting something good to happen that's why I kept my title. The idea was to wait for 2 months for a sign they were finally on the right path. I was ready to come back even willing to share details on how they can fix billing and SEO in their software but we all know how it is going. I happily moved to another market and eventually forget about this community, GearHead and my 2-months deadline. Every community I love eventually dies 😪
  13. For the simple reason I don't want people to rely on crappy scripts that serve no use especially when someone is selling it for real money on Marketplace. I've seen plenty of companies relying on such scripts throwing money out of the window running Ads on Facebook based on fake, missing or buggy event trackers. People only read titles. They see "Facebook Pixel" and they go all-in.
  14. This is all crap. The first module is a copy of the third. Basically one guy went on Github, stole the code and made a commercial module. The second is useless since it can only track PageView event. Same goes for the other two that can track PageView, AddToCart and InitiateCheckout. Pretty much useless. One needs Facebook Pixel to track things like Contact (leads), Registration, CustomizeProduct and Purchase. In conclusion, people think that tracking events on Facebook Pixel in WHMCS is easy but that's not true. It took me weeks if not months of attempts and coding but I left this community so I am not willing to share details.
  15. Could you help me with this issue?

     

×
×
  • 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