Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Hi, On the Knowledge base , how can I disable the thumbs-up/down feature? I do not find any option on the admin panel. Maybe by editing some file? Thanks!
  3. Hi, The new language system with all the new languages seems great! I noticed you added Português, BR (pt_br) that is a lot different than Português from Portugal (pt_pt). Do you plan do add pt_pt language? It would be great.. after all pt_pt is the original Português Thanks
  4. Yesterday
  5. The error is: [2025-02-27T18:05:37.749399+00:00] general.ERROR: PDOException: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'netim_async' already exists in /public_html/vendors/minphp/db/src/PdoConnection.php:196 Stack trace: #0 /public_html/vendors/minphp/db/src/PdoConnection.php(196): PDOStatement->execute() #1 /public_html/vendors/minphp/record/src/Record.php(205): Minphp\Db\PdoConnection->query() #2 /public_html/components/modules/netim/lib/Database.php(14): Minphp\Record\Record->create() #3 /public_html/components/modules/netim/netim.php(48): Netim\Database\createAsyncDb() #4 public_html/app/models/module_manager.php(360): Netim->install() #5 /public_html/app/controllers/admin_company_modules.php(139): ModuleManager->add() #6 /public_html/vendors/minphp/bridge/src/Lib/Dispatcher.php(142): AdminCompanyModules->install() #7 public_html/index.php(21): Dispatcher::dispatch() #8 {main} Aleksa has offered a solution (missing word in the code) that I need to try!
  6. They can register with the same email, but not the same username. They will have to choose another username. If you force email to be the username, they will not be able to use the same email. What do you mean by select the home folder? Addon companies are for a SINGLE installation for Blesta, so the files are the same files. If you are doing a separate installation of Blesta (different copy of files), this is not an addon company and would violate the license. 1 license is for 1 install. Addon companies can be added under Settings > System > Companies. Your web server must point all the companies to the SAME docroot where your single Blesta install is located.
  7. Done, thanks! Looks like the old URLs redirect, so that's good.
  8. It used to use the WYSIWYG editor but there was a serious issue with the html it generated that would break the page so we had to remove it. We may look to see if we can resolve the original issue and add it back.
  9. This may be related to https://dev.blesta.com/browse/CORE-5360
  10. Last week
  11. I’ve also had this issue with Netim when using addon company. You can ask Aleksa via the discord chat to help you as he resolved it for me. If I remember correctly it was due to the module using the same MySQL tables as the main company or something along those lines (Something really simple).
  12. They have plugins and gateways for almost everything but they didn't write most of them. It would be great if those developers would port their extensions to Blesta. If our competitor can't build every integration themselves, we certainly can't either. We have to prioritize and implement things that have the largest impact. This creates an opportunity for 3rd party developers to make some $ by selling extensions we don't make. We run into cases all the time where we can't even sign up for a test account because we don't live in the country of the payment gateway, but developers based there have no trouble. So, asking the developers who built extensions for our competitor to make it available for Blesta also is what is needed.
  13. I posted this idea on your forum and you can't deny that the other system is the greatest power because it has plugins and gateways for almost everything. If you accept my idea, it would clearly make things much easier for you and for us too, and I'm not just talking about Brazil, but for everyone who uses Blesta.
  14. There is indeed a much better service than Pagbank (formerly PagSeguro). It would be Asaas, which provides several features, several payment methods, and allows you to send messages via email, SMS, and WhatsApp through their own platform. Pagbank create and update new API, but you could choose between one or the other. However, we ask that if you choose Asaas or PagSeguro, you leave all payment methods enabled, as we now have 4 payment methods: bank deposit, pix, credit card, and bank slip. Here are the documentation links, but I would prefer you to give preference to Asaas, as it offers many more features: Pagbank: https://developer.pagbank.com.br/ Asaas: https://docs.asaas.com/ I leave the two options up to you to choose from and atencion you to look at us a little, because what I notice is that in your system you have several gateways to the United States itself and other countries, but we have to use what you have and not what we need.
  15. I am using Namesilo 5.11 with Namesilo. When attempting to manually activate a domain transfer from admin side. I am given "Call to a member function get Contacts() on null". This occured 2 times but unable to reattempt as there is a separate bug reported in progress that stops me from troubleshooting further which is found here:
  16. After upgrading to version 5.11 and using Namesilo for domain transfers, a bug occurs when transferring a domain that is unlocked by the previous provider. The transfer gets stuck in the "Pending" status on Blesta's side, and if notifications are enabled, an error email is sent. The error message displayed is: "This domain cannot be transferred at this time." This error typically occurs when a domain is locked by the previous provider, but now it appears even for domains that are unlocked. Despite the transfer being successfully processed on the Namesilo side, the domain remains stuck in the "Pending" status. The transfer proceeds and completes on Namesilo, but Blesta does not update the status correctly. When attempting to manually activate the domain, the same error ("This domain cannot be transferred at this time") appears. The workaround is to edit the service, untick the "Use Module" option, and then activate it manually while the transfer is still in progress. This issue seems to stem from an API response error from Blesta, even though Namesilo successfully processes the transfer. It's an odd bug that causes the transfer to be incorrectly flagged as incomplete. I am getting this bug on 3 separate Blesta installs for all incoming domain transfers.
  17. The two fixes are confirmed to be resolved.
  18. Also https://dev.blesta.com/browse/CORE-5359
  19. I've created a task: https://dev.blesta.com/browse/CORE-5358 Fix is in the task
  20. We love Brazil. Is PagSeguro the best gateway for Brazil? Is there any documentation about the change they made online? Did they completely kill the API and implement a new API? Some specifics would be helpful. Also, if PagSeguro is not the best gateway for Brazil, maybe we should implement the best gateway instead of updating this one, one that doesn't secretly make API changes that break existing integrations.
  21. Hello, I found same issue as above mentioned. So, it can be count as a bug & need to fix it.
  22. Remove this gateway, it no longer works and you don't want to redo it. You could think a little about us Brazilians.
  23. I'm using HestiaCP with an Nginx template for Blesta, and while most things work fine, I'm facing issues with the error pages not displaying correctly and API calls or feed endpoints not functioning as expected. Below is my current Nginx configuration for both HTTP and HTTPS. I suspect the problem might be related to missing rewrite rules or improper handling of error pages and API routes. Any insights or modifications to make this work perfectly with Blesta Billing would be greatly appreciated.
  24. annalie3202

    Hey

    Hey
  25. Trial licenses can't be issued to "localhost" due to abuse. We would recommend installing on your web server. If you need a developer license for running on your local machine, we can issue developer licenses to direct monthly and owned license holders by opening a ticket from your account.
  26. Recently upgraded to 5.11.0 When logged in as a user and navigating to Manage Domain > Whois Tab, the “Update Whois” button doesn’t seem to work. Clicking it keeps you on the same page, and the button’s link is: https://my.blesta.com/client/services/manage/01/tabClientWhois/# However, the “Update Whois” function via the ACP works fine. Additionally, when I tried to add a contact, clicking “Add Contact” (Save) after inputting all the contact details via client side it displayed the following error in the header with a success green box. This header error shouldn’t show: object(NamesiloResponse)#1340 (2) { [“xml”:“NamesiloResponse”:private]=> object(SimpleXMLElement)#1341 (2) { [“request”]=> object(SimpleXMLElement)#1329 (2) { [“operation”]=> string(10) “contactAdd” [“ip”]=> string(13) “censored-ip” } [“reply”]=> object(SimpleXMLElement)#1336 (3) { [“code”]=> string(3) “300” [“detail”]=> string(7) “success” [“contact_id”]=> string(8) “24829894” } } [“raw”:“NamesiloResponse”:private]=> string(223) “ contactAddcensored-ip300success24829894 “ } Afterwards, I attempted to assign the new contact (e.g., Registrant, Tech, Billing) from the dropdown in the Whois tab and clicked ‘Save’, but the button doesn’t work.
  1. Load more activity
×
×
  • Create New...