DavidD2

JSON works with no issues. All of the CSV reports produce this error: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated [2024-10-14T16:40:55.045150+00:00] general.ERROR: UnknownException: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /var/www/blesta.test.com/htdocs/app/models/report_manager.php:341 Stack trace: #0 /var/www/blesta.test.com/htdocs/vendors/monolog/monolog/src/Monolog/ErrorHandler.php(232): UnknownException::setErrorHandler() #1 [internal function]: Monolog\ErrorHandler->handleError() #2 /var/www/blesta.test.com/htdocs/app/models/report_manager.php(341): str_replace() #3 /var/www/blesta.test.com/htdocs/app/models/report_manager.php(358): ReportManager->formatCsv() #4 /var/www/blesta.test.com/htdocs/app/models/report_manager.php(325): ReportManager->buildCsvRow() #5 /var/www/blesta.test.com/htdocs/app/models/report_manager.php(232): ReportManager->buildCsv() #6 /var/www/blesta.test.com/htdocs/app/controllers/admin_reports.php(43): ReportManager->fetchAll() #7 /var/www/blesta.test.com/htdocs/vendors/minphp/bridge/src/Lib/Dispatcher.php(142): AdminReports->index() #8 /var/www/blesta.test.com/htdocs/index.php(21): Dispatcher::dispatch() #9 {main}

Admin area while trying to add a new service to a client. The first issue is the Universal Module (generic_server) has required fields, but at no point in the process to add a new service does it provide text boxes to input the required fields. I changed the Required? to no on the module and it doen't complain about the missing username, password, and domain but instead pukes up: I just want to be able to add a service to a client... [2024-10-14T16:33:41.526062+00:00] general.ERROR: UnknownException: Attempt to read property "meta" on null in /var/www/blesta.test.com/htdocs/components/modules/universal_module/universal_module.php:928 Stack trace: #0 /var/www/blesta.test.com/htdocs/vendors/monolog/monolog/src/Monolog/ErrorHandler.php(232): UnknownException::setErrorHandler() #1 /var/www/blesta.test.com/htdocs/components/modules/universal_module/universal_module.php(928): Monolog\ErrorHandler->handleError() #2 /var/www/blesta.test.com/htdocs/components/modules/universal_module/universal_module.php(873): UniversalModule->getServiceRules() #3 /var/www/blesta.test.com/htdocs/app/models/services.php(5251): UniversalModule->validateService() #4 /var/www/blesta.test.com/htdocs/app/controllers/admin_clients.php(8162): Services->validateService() #5 /var/www/blesta.test.com/htdocs/app/controllers/admin_clients.php(6656): AdminClients->processServiceStep() #6 /var/www/blesta.test.com/htdocs/vendors/minphp/bridge/src/Lib/Dispatcher.php(142): AdminClients->addService() #7 /var/www/blesta.test.com/htdocs/index.php(21): Dispatcher::dispatch() #8 {main}

#3: On invoices with refunds after importation via the WHMCS importer (causing overdue invoices in Blesta) : It's more involved and largely is related to our WHMCS customer's final invoices or SLA credits given over the years. If a refund is given to a customer on an invoice, and the invoice is marked paid/voided, WHMCS considers the paid or voided invoice as closed. Even though there is a technically a balance. While this does require manual correction, the manual correction isn't needed on Blesta... The correction should occur on WHMCS. After adding a line item to the WHMCS to reflect the refund to the customer, Blesta is happy. - The issue with the importer not applying multiple payments on a WHMCS invoice was related to credits which was also resolved by adding line items to subtract money owed on the invoices and removing the WHMCS credits. WHMCS credits being applied to invoice creates a transaction that is visible at the bottom, but the invoice itself is never marked while a line item reflecting the credit. WHMCS just has the transaction and marks the invoice paid. Blesta appears to want an actual line item. All of issue #3 can largely be attributed to the sloppy accounting that is allowed by WHMCS. While it all "just works" it's by no means clean accounting. In summary, my original list is largely resolved and I hope my posts help someone in the future.

If anyone sees this in the future: 1. Imported Stripe information from WHMCS is ready to bill. You need to choose the currencies in the module setup and then you can charge cards using existing stored CC information (Stripe tokens). Tested today and works. 2) My administrator login still did not work, but test client accounts I added before export from WHMCS did work.

Hi, I missed the Discord chat today, so I decided to post this here. I did a trial import of my WHMCS database a few days ago. The results were favorable and I'd say it puts Blesta at ~90%++ complete. A few questions and observations: 1) We use Stripe primarily. The import of my Stripe keys was fine. The import is also good at enabling the billing modules I need. Looking in the Blesta database, I see the Stripe cust and card ids in the table "accounts_cc". Am I correct to assume these customers are ready to bill via Stripe? Meaning, Stripe only needs these two variables, so it's good to go? 2) After the import my WHMCS administrator login did not work. The account was imported, i can see my username in the database, I can see a password hash in the database for my username, but my password didn't work. My primary concern is customers passwords don't work. I did set legacy passwords and algo to "whmcs" in the config file. Unfortunately, other than my admin password, I didn't have a customer account to test with. I'm just curious if you have seen admin logins not working after import. 3) The imported invoices are largely correct. It handles normal charges and credits properly. I did notice that it did not handle refunds correctly. So there was/is ~80 invoices that had refunds in the past that I'll need to correct manually. No biggie. 4) The import sets up packages properly. It did not setup add-on packages and it does not adjust prices on customers that do not pay the standard package price. For example, we have an add-on for firewall and an add-on for backup. We'll need to manually create these and then add them to the customers. As for the non-standard pricing, we'll need to manually adjust these on the customers that do not pay full price. Again, it's pretty good and gets us to a reasonable position to switch from WHMCS to Blesta in a reasonable amount of time. If you have suggestions/answers on any of the above, it would be greatly appreciated. I'm going to do another import after cleaning out a bunch of ancient data from our WHMCS database and also add test client accounts so I can verify password importation works.