Jump to content

cluster

Members
  • Posts

    33
  • Joined

  • Last visited

  • Days Won

    1

cluster last won the day on December 27 2021

cluster had the most liked content!

cluster's Achievements

  1. Thanks that helped, the timeouts were too low ... I have adjusted: wait_timeout = 3600 connect_timeout = 1200 interactive_timeout = 1200 I don't know why but the whmcs date format for all affiliate tables is different from the whmcs date format - so the affiliate page in blesta now shows an error message about wrong date format ... whmcs date format is set to d/m/Y but the affiliate tables use e.g. 2015-11-12 Is there any sql query which can convert the date format in the affliate tables from Y-m-d to d/m/Y?
  2. I searched all the whmcs tables and emptied the following which did not have a valid userid tbloauthserver_access_tokens tbloauthserver_clients the same error message is still displayed, only customers and invoices are imported. I am a little disappointed that there is no feedback here ... I was able to import everything from whmcs in a wisecp installation (except for cancellations & domains price list). When will these problems be fixed in the blesta import script?
  3. Debian Buster / PHP 7.4 (fpm) / MariaDB 10.3 WHMCS 7.10.3 Blesta 5.2.1 I have tested an import from whmcs with a few errors ... not imported: Packages, Services, Affiliates, SupportTickets, Servers, Domain price list Cients are imported but many inactive are shown as activ, only clients from whmcs with status closed are set to inactive, but both (closed & inactive) needs to be set as inactive in Blesta. The import completed but the following errors ocurred: importTransactions: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away on line 196 importPackages: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 importPackageOptions: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 importServices: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 importSupportDepartments: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 importSupportTickets: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 importAffiliates: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 importMisc: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 another try w/ debug mode enabled: importCurrencies took: 0.0036 seconds ----------------- importInvoices ----------------- importInvoices took: 185.6431 seconds ----------------- importTransactions ----------------- importPackages ----------------- importPackageOptions ----------------- importServices ----------------- importSupportDepartments ----------------- importSupportTickets ----------------- importAffiliates ----------------- importMisc ----------------- decrypted 0 values using WHMCS' custom algorithm decrypt took: 0 seconds total time took: 1026.206 seconds Array ( [error] => Array ( [0] => The import completed but the following errors ocurred: [1] => importTransactions: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away on line 196 [2] => importPackages: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 [3] => importPackageOptions: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 [4] => importServices: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 [5] => importSupportDepartments: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 [6] => importSupportTickets: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 [7] => importAffiliates: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196 [8] => importMisc: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 196
  4. or could this simply added to a custom (default) order template? e.g. if domain == required > show domain check incl. transfer & own domain option
  5. Is there an order template which can do a domain check when using a direct link to a hosting product? There should also be an option to select a dominan transfer or use an own domain. That would be pretty important as most customers choose the hosting package first.
  6. Blesta 5.2.0 PHP(fpm) 7.4 Debian 10 This is a dev installation where I have activated debugging System > Automation /admin/settings/system/automation/ shows: file_exists(): open_basedir restriction in effect. File(/usr/sbin/php) is not within the allowed path(s): (/var/www/my.mydomain.tld/:/usr/share/php/). file_exists(): open_basedir restriction in effect. File(/usr/sbin/php) is not within the allowed path(s): (/var/www/my.mydomain.tld/:/usr/share/php/) on line 110 in /var/www/my.mydomain.tld/htdocs/app/controllers/admin_system_automation.php UnknownException::setErrorHandler Line 232 /var/www/my.mydomain.tld/htdocs/vendors/monolog/monolog/src/Monolog/ErrorHandler.php Monolog\ErrorHandler->handleError Line file_exists(): open_basedir restriction in effect. File(/usr/sbin/php) is not within the allowed path(s): (/var/www/my.mydomain.tld/:/usr/share/php/) on line 110 in /var/www/my.mydomain.tld/htdocs/app/controllers/admin_system_automation.php Printing Stack Trace: #0 /var/www/my.mydomain.tld/htdocs/vendors/monolog/monolog/src/Monolog/ErrorHandler.php(232): UnknownException::setErrorHandler() #1 [internal function]: Monolog\ErrorHandler->handleError() #2 /var/www/my.mydomain.tld/htdocs/app/controllers/admin_system_automation.php(110): file_exists() #3 /var/www/my.mydomain.tld/htdocs/app/controllers/admin_system_automation.php(143): AdminSystemAutomation->getPathToPhp() #4 /var/www/my.mydomain.tld/htdocs/app/controllers/admin_system_automation.php(96): AdminSystemAutomation->createCronCommand() #5 /var/www/my.mydomain.tld/htdocs/vendors/minphp/bridge/src/Lib/Dispatcher.php(142): AdminSystemAutomation->index() #6 /var/www/my.mydomain.tld/htdocs/index.php(21): Dispatcher::dispatch() #7 {main}
  7. I would like to use guzzlehttp with a panel module, but it's not installed ... how can this be solved? require section of my composer.json module file: "require": { "blesta/composer-installer": "~1.0", "phillipsdata/priority-schedule":"^1.0", "guzzlehttp/guzzle": "^7.0" }
  8. are my Blesta declarations correct in this part? 'reseller_name' => $params['user_name'] = $this->user_name, 'reseller_pass' => $params['password'] = $this->password, 'action' => 'create', 'domain' => $params['domain'], 'hp_name' => $params['package_name'], 'admin_name' => $params['username'], 'admin_pass' => $params['password'], 'fname' => $params['client']->first_name, 'lname' => $params['client']->last_name, 'firm' => $params['client']->company, 'zip' => $params['client']->zip, 'city' => $params['client']->city, 'state' => $params['client']->state, 'country' => $params['client']->country, 'email' => $params['client']->email, 'phone' => $params['client']->telephone, 'street1' => $params['client']->address1
  9. can someone help to make these whmcs declarations compatible with blesta? I've already adapted the first two for reseller_name & reseller_pass ... return apiRequest($params, [ 'reseller_name' => $params['user'] = $this->user_name, 'reseller_pass' => $params['password'] = $this->password, 'domain' => $params['domain'], 'hp_name' => $params['configoption1'], 'admin_name' => $params['username'], 'admin_pass' => $params['password'], 'fname' => $params['customer']['firstname'], 'lname' => $params['customer']['lastname'], 'firm' => $params['customer']['companyname'], 'zip' => $params['customer']['postcode'], 'city' => $params['customer']['city'], 'state' => $params['customer']['state'], 'country' => $params['customer']['countryname'], 'email' => $params['customer']['email'], 'phone' => $params['customer']['phonenumber'], 'street1' => $params['customer']['address1'], 'street2' => $params['customer']['address2'] ]);
  10. ### edit ### solved - allow_url_fopen=1 so I guess re-captcha needs allow_url_fopen enabled ######### Blesta: 5.2.0 PHP: 7.4 I have activated Recaptcha (v2) but something doesn't seem to work, the Google Keys are correct even when entering the Captcha it is marked as correct ... so I can no longer log into the admin area because an incorrect captcha error is always shown again and again
  11. I don't like to use Discord because a real community forum is more helpful & clearer for many things ? Question does the Blesta companies addon work together with Blesta CMS for the different companies?
  12. I have now set the date format as follows, so it's displayed exactly the same result as in the whmcs. blesta: d/m/Y > 02/10/2021 d/m/Y H:m > 02/10/2021 10:10 whmcs shows a different parameter (DD/MM/YY) maybe whmcs internal but results are now identical DD/MM/YY > 02/10/2021 10:10 I think the date format should match before start a migration - right?
  13. ### bump ### i can't use DD/MM/YYYY from WHMCS it shows everything twice in BLESTA date format will that work for the import from whmcs to blesta? WHMCS > Global Date Format DD/MM/YYYY BLESTA > Date Format d.m.Y Date Time Format d. M. Y H:m:s
  14. can I migrate from WHMCS if the date format is different? or should I have to use exactly the same date format as set in WHMCS? WHMCS > Global Date Format DD/MM/YYYY BLESTA > Date Format d.m.Y Date Time Format d. M. Y H:m:s
  15. Is there any chance to change the Blesta internal captcha to show only capital letters? The upper and lower case is sometimes difficult to recognize and it takes a lot of attempts.
×
×
  • Create New...