Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Yes it is lifetime i have had mine for many years, but you will have to pay $39 a year for updates and support
  3. Just did a quick test, importing manually an existing order using phpmyadmin It seems easy; for each existing certificate, it's necessary: - inserting a record in services table with following fields: - pricing_id (value change according to your Blesta installation) - client_id - module_row (not understood yet what is this and how to manage it: I just set the very same value of another exiting certificate) - date_added - date_renew (certificate expiring date, or maybe certificate expiring date less 15 days... ) - inserting two records in service_fields table: - the first record with service_id from the corresponding record in service table, with thesslstore_order_id as key, and with order id# from thesslstore as value - the second record with service_id from the corresponding record in service table, with thesslstore_token as key, and with token id# from thesslstore as value Everything seems to be working fine, and the user is able to manage his certificate using Blesta If I'm not missing something, it's almost trivial, and writing a script to import certificates from a CSV should be an easy half-day task...
  4. yes right, i use PHP 7.4 i tested it now also with PHP 7.3. The message is also logged under 7.3 in my case.
  5. Regarding this error message that you see in your logs when viewing a ticket. I had already tracked down an exact matching error caused by the KB the other week, but I had not spotted that it was also appearing with support tickets. It is an error that is appearing under PHP 7.4, so I presume that you are running PHP 7.4 like me. It has taken me considerable time to finally put the information together such that I can post about the bug here - I've added in the error that you have observed when viewing tickets because I was also able to re-create it. I believe that the error from the support tickets is related to the error from the KB because they are the same/very similar and are all from the support manager plugin, so thanks for mentioning it, as I was able to combine it all into my one topic. I'm not a developer, but I can't see how these errors could be related to this particular problem with double line spacing not being displayed in the client portal, however.
  6. Yesterday
  7. Hello, I have narrowed down that a large number of errors in the blesta logs (logs_blesta) folder is being caused by the Support Manager plugin when browsing the Knowledgebase (KB) and using Support Tickets under PHP 7.4. There are no visible problems with the functioning of the KB or Support Tickets, however, if you have robots trawling your KB, or use your Support Desk a lot, you get a lot of errors appearing in your logs. So I have been trying to find out where the errors in the logs are coming from and enabling error reporting once I have narrowed it down, so that I can tell you the exact pages. I am running Blesta v5.1.2. It is important to note that these errors appear in the general-error and general-notice logs and they only appear under PHP 7.4 and they do not appear under PHP 7.2. To eliminate it being an issue with my existing install, I installed a fresh install of Blesta v5.1.2 and re-created the problem. Focusing on the KB for now; I have attached a video showing where the errors occur (please be patient, as I was a bit slow with the mouse cursor!). With error reporting enabled, you can see from my video that the errors are logged as you browse the KB (URL: /client/plugin/support_manager/knowledgebase/) and the articles (eg. URL: /plugin/support_manager/knowledgebase/view/1/this-is-a-test-kb-article-no-1/1/). The errors are as follows: From general-error log (these only appear with error reporting enabled): [2021-07-16T20:45:36.016244+00:00] general.ERROR: UnknownException: Trying to access array offset on value of type null in /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php:252 Stack trace: #0 /home/username/public_html/dev/blesta/vendors/monolog/monolog/src/Monolog/ErrorHandler.php(232): UnknownException::setErrorHandler(8, 'Trying to acces...', '/home/username/...', 252, Array) #1 /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php(252): Monolog\ErrorHandler->handleError(8, 'Trying to acces...', '/home/username/...', 252, Array) #2 /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php(52): Parsedown->lines(Array) #3 /home/username/public_html/dev/blesta/helpers/text_parser/text_parser.php(52): Parsedown->text('This is a Test ...') #4 /home/username/public_html/dev/blesta/plugins/support_manager/views/default/knowledgebase.pdt(42): TextParser->encode('markdown', 'This is a Test ...') #5 /home/username/public_html/dev/blesta/vendors/minphp/bridge/src/Lib/View.php(163): include('/home/username/...') #6 /home/username/public_html/dev/blesta/vendors/minphp/bridge/src/Lib/Controller.php(321): View->fetch('/home/username/...', NULL) #7 /home/username/public_html/dev/blesta/vendors/minphp/bridge/src/Lib/Dispatcher.php(173): Controller->render() #8 /home/username/public_html/dev/blesta/index.php(21): Dispatcher::dispatch('/dev/blesta/use...') #9 {main} [2021-07-16T20:45:52.826547+00:00] general.ERROR: UnknownException: Trying to access array offset on value of type null in /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php:252 Stack trace: #0 /home/username/public_html/dev/blesta/vendors/monolog/monolog/src/Monolog/ErrorHandler.php(232): UnknownException::setErrorHandler(8, 'Trying to acces...', '/home/username/...', 252, Array) #1 /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php(252): Monolog\ErrorHandler->handleError(8, 'Trying to acces...', '/home/username/...', 252, Array) #2 /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php(52): Parsedown->lines(Array) #3 /home/username/public_html/dev/blesta/plugins/support_manager/views/default/knowledgebase_view.pdt(15): Parsedown->text('Here I am writi...') #4 /home/username/public_html/dev/blesta/vendors/minphp/bridge/src/Lib/View.php(163): include('/home/username/...') #5 /home/username/public_html/dev/blesta/vendors/minphp/bridge/src/Lib/Controller.php(321): View->fetch('/home/username/...', NULL) #6 /home/username/public_html/dev/blesta/vendors/minphp/bridge/src/Lib/Dispatcher.php(173): Controller->render() #7 /home/username/public_html/dev/blesta/index.php(21): Dispatcher::dispatch('/dev/blesta/plu...') #8 {main} From general-notice log (these appear all of the time with error reporting disabled): [2021-07-16T20:41:34.532923+00:00] general.NOTICE: E_NOTICE: Trying to access array offset on value of type null {"code":8,"message":"Trying to access array offset on value of type null","file":"/home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php","line":252} [2021-07-16T20:41:34.533888+00:00] general.NOTICE: E_NOTICE: Trying to access array offset on value of type null {"code":8,"message":"Trying to access array offset on value of type null","file":"/home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php","line":258} [2021-07-16T20:42:34.438278+00:00] general.NOTICE: E_NOTICE: Trying to access array offset on value of type null {"code":8,"message":"Trying to access array offset on value of type null","file":"/home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php","line":252} I then identified that these errors are also appearing for Support Tickets: So the same errors above from the general-notice log that appear for the KB, also appear when you view a support ticket (URL: /admin/plugin/support_manager/admin_tickets/reply/1/) and then the errors will re-appear multiple times every minute when you leave the support ticket open in the web browser (ie. just viewing the ticket and not doing anything on it) with error reporting disabled. This is the same as DannyXYZ is reporting here. Secondly, this time with error reporting enabled, when you open a ticket or update the ticket with a reply from the Staff Portal (URLs: /admin/plugin/support_manager/admin_tickets/add/ or /admin/plugin/support_manager/admin_tickets/reply/1/), you again also receive an error very similar to the KB from the general-error log - screenshot attached: [2021-07-30T22:00:13.139661+00:00] general.ERROR: UnknownException: Trying to access array offset on value of type null in /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php:252 Stack trace: #0 /home/username/public_html/dev/blesta/vendors/monolog/monolog/src/Monolog/ErrorHandler.php(232): UnknownException::setErrorHandler(8, 'Trying to acces...', '/home/username/...', 252, Array) #1 /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php(252): Monolog\ErrorHandler->handleError(8, 'Trying to acces...', '/home/username/...', 252, Array) #2 /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php(52): Parsedown->lines(Array) #3 /home/username/public_html/dev/blesta/helpers/text_parser/text_parser.php(52): Parsedown->text('This is reply N...') #4 /home/username/public_html/dev/blesta/plugins/support_manager/models/support_manager_tickets.php(1911): TextParser->encode('markdown', 'This is reply N...') #5 /home/username/public_html/dev/blesta/plugins/support_manager/controllers/admin_tickets.php(401): SupportManagerTickets->sendEmail('1', Array) #6 /home/username/public_html/dev/blesta/vendors/minphp/bridge/src/Lib/Dispatcher.php(142): AdminTickets->add() #7 /home/username/public_html/dev/blesta/index.php(21): Dispatcher::dispatch('/dev/blesta/adm...') #8 {main} [2021-07-30T22:05:31.180411+00:00] general.ERROR: UnknownException: Trying to access array offset on value of type null in /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php:252 Stack trace: #0 /home/username/public_html/dev/blesta/vendors/monolog/monolog/src/Monolog/ErrorHandler.php(232): UnknownException::setErrorHandler(8, 'Trying to acces...', '/home/username/...', 252, Array) #1 /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php(252): Monolog\ErrorHandler->handleError(8, 'Trying to acces...', '/home/username/...', 252, Array) #2 /home/username/public_html/dev/blesta/vendors/blesta/parsedown/Parsedown.php(52): Parsedown->lines(Array) #3 /home/username/public_html/dev/blesta/helpers/text_parser/text_parser.php(52): Parsedown->text('This is reply N...') #4 /home/username/public_html/dev/blesta/plugins/support_manager/views/default/admin_tickets_replies.pdt(90): TextParser->encode('markdown', 'This is reply N...') #5 /home/username/public_html/dev/blesta/vendors/minphp/bridge/src/Lib/View.php(163): include('/home/username/...') #6 /home/username/public_html/dev/blesta/vendors/minphp/bridge/src/Lib/Controller.php(222): View->fetch('/home/username/...', NULL) #7 /home/username/public_html/dev/blesta/plugins/support_manager/controllers/admin_tickets.php(580): Controller->partial('admin_tickets_r...', Array) #8 /home/username/public_html/dev/blesta/vendors/minphp/bridge/src/Lib/Dispatcher.php(142): AdminTickets->reply() #9 /home/username/public_html/dev/blesta/index.php(21): Dispatcher::dispatch('/dev/blesta/adm...') #10 {main} I have taken the above errors from the logs of the fresh development install that I made purely to test these bugs. However, I have correlated that the errors match exactly with my production install. I have attached the development install's log files to this topic. The log files dated for the 16th July cover the KB errors and the log files dated for the 30th July cover the Support Ticket errors. Blesta v5.1.2, Support Manager plugin version 2.27.2. Cloudlinux, PHP 7.4, MariaDB 10.3.30. Thank you very much indeed. 2021-07-16_21h45_16.mp4 general-error-2021-07-16.log general-notice-2021-07-16.log general-error-2021-07-30.log general-notice-2021-07-30.log
  8. I've created CORE-4428 to deal with this.
  9. Sounds like a feature request. I'm not sure where it goes, either Blesta or TheSSLStore directly. I like it and that would be a great benefit.
  10. Remitur

    Tax Rules

    What's your country? AFAIK, in no european country it's required local VAT applied to the selling of services...
  11. Certificates require to be reissued every 12 months, it's true, but SSL services can last up to 6 years (WHMCS stop to just 3 years), and in the meanwhile the user can reissue his certificate whenever he wants or needs on his own and without our support... so it's quite important importing existing certificates too. (But I'm studying it and it seems not too difficult, even operating just on phpmyadmin ...)
  12. Good idea, I'll give that a shot. I know that thesslstore wrote the module themselves, so it would be up to them to add the extra features. The existing import would be a great feature, but now that certificates need to be recreated annually, not as much a big deal.
  13. It seems you're forced to import all of them. A trick (that allows you not to delete 100 or more articles) could be importing them in a "parked products" group, and then move out of this (hidden) group just the required products. This "parked products" will be full of garbage, but this is not an issue... I see there're other functions about Thesslstore module, that do exist in the WHMCS version and that are lacking in Blesta's version: existing certificate importing (that allows to specify just thesslstore's order ID#, Blesta's client id#, and import existing certificate creating a service under specified client id#) mass price update renewal report
  14. @Fartuh we are working on our own custom SaaS platform which includes builtin billing and Automation's for our products . so we will not use blesta any more
  15. Last week
  16. galaxy

    Package question

    I would like to create a package for services that require a username & password. For example, a mailbox. What is the correct method to create service fields to hold things like email_address, username, password, etc. ? Would that be configurable options? I want to make sure its not an "option" but something that is required, and be able to do validation on it.
  17. Being that you're evaluating that, do you know how to import say 4 or 5 of their products? Or do you have to import hundreds and weed them out?
  18. I have tested this on my install and it isn't just you. You are correct that if you put a double space (I call them double lines) in a support ticket reply, the double lines are lost when the ticket is viewed in the client portal only. It is important to note that the double lines appear absolutely fine when viewing the ticket in the staff portal and as DannyXYZ has explained, it is fine on emails. So there is a discrepancy here with how the client portal is displaying the text. As an aside, the "preview" button doesn't show what actually appears in practice for new lines either - this can throw you off, so best to ignore the preview and go by what you see.
  19. it's a different way to manage prepaid credit. A common way to manage it in many european countries, respecting VAT laws, is the following: - customer buys 100 of credit; I invoice 100 + 20% VAT, customers pays 120, and has 100 of available prepaid credit - customer buys service A , priced 10 I deduct 10 from his credit, process the order, and (if required by local laws) I issue this invoice: service A 10 prepaid credit: -10 subtotal: 0 VAT 20%: 0 Total: 0 (if local laws do not require a "zero value invoice" to be issued, I can send to the user just a receipt/note/mail message/whatsoever, just to keep note of how his credit was spent) - customer buys service B, priced 110 I deduct all his remaining credit (90), and issue following invoice: service B 110 prepaid credit: -90 subtotal: 20 VAT 20%: 4 Total: 24 So user pays 22, and I go on releasing his service... Cross checking: - the user did two payments: 120 and 24 (total 144) - I issued two invoices: 120 and 24 (total 144) - I released two services, valued 110 and 10: total 120 (and 120 + VAT = 144)
  20. Where can we find official government documentation on this? The problem is this: Let's say a client makes a $100 payment for credit. If we invoice for the credit, the amount would be applied to the invoice, and there would no longer be a credit. If on the other hand, the credit is both invoiced and remains as an account credit, then at a later time a client receives $100 worth of invoices and the credit is applied to those invoices, the initial $100 credit has been applied to $200 worth of invoices. Additionally, the client may be able to submit this to their tax authority as a $200 deduction. How do you reconcile that?
  21. Prior to 5.1, modules didn't have types. A minor tweak is needed to make the module compatible with the domain manager, and we have provided the information to them. The module would continue to work outside the domain manager as it was, but the minor update to make it compatible is the best solution.
  22. I do see this module in GitHub and it doesn't use the updated API. The module needs to extend the RegistrarModule class and not just Module. You'll probably need to contact the author if you're not a programmer. https://github.com/hexonet/blesta-ispapi-registrar
  23. I'm on 5.1.2 and using cached invoices. I usually generate invoices on the admin area or modify existing ones. But but if I select to re-cache the invoice on save (when manually editing), they are cached in the admin's language and not in the client's language. That wasn't a problem when they were generated on the fly, but now when clients want to view or download their invoices, the wrong language cached versions are provided. Steps to reproduce: 1. Enable invoice caching 2. From the admin area, choose a client with different language settings than the admin's. 3. Edit something about an invoice and select to regenerate cached version. 4. View the invoice from the admin area and from the clients panel (both are in the admin's language not in the client's one). 5. Optional.. Change the admin's language and repeat the procedure. Now the invoice is cached in the new admin's language. I think it would be better that invoices are generated, cached and re-cached in the client's language when invoice caching is enabled.
  24. I've got captcha enabled on all forms Although when ordering while logged out, if you want to register, everything is fine, you get the captcha on the register form But, if you are logging in, the captcha is not on the login form This happens on this URL /order/cart/index/game This also occurs on a clean Blesta install, version 5.1.2
  25. I'm on 5.1.2 A. Login Problems Admins can't login to the admin area when maintenance mode is enabled and the admin user has two factor authentication enabled. Steps: 1. Enable 2 factor authentication to the admin 2. Enable maintenance mode 3. Try to start a new session on a incognito window or something like that. It returns to the login page. If you disable 2 factor authentication, the admin can start session in maintenance mode. B. UI Problem When maintenance mode is enabled, the alert banner in mobile browser overflows. I tried in safari and chrome. Landscape mode has no issues.
  26. I use VPN for Kodi, and this solution is also suitable for managing Belst's admin panel. This provides an additional degree of protection.
  1. Load more activity
×
×
  • Create New...