Search the Community

I recently upgraded to 5.11. And I saw the namesilo module required an upgrade After clicking on upgrade I get a white screen and this error in the logs [2025-02-26T17:33:16.450128+00:00] general.ERROR: PDOException: SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect integer value: '' for column `blesta`.`module_client_meta`.`client_id` at row 1 in .../blesta/vendors/minphp/db/src/PdoConnection.php:196 Stack trace: #0 .../blesta/vendors/minphp/db/src/PdoConnection.php(196): PDOStatement->execute() #1 .../blesta/vendors/minphp/record/src/Record.php(305): Minphp\Db\PdoConnection->query() #2 .../blesta/components/modules/namesilo/namesilo.php(168): Minphp\Record\Record->insert() #3 .../blesta/components/modules/namesilo/namesilo.php(105): Namesilo->setContactsFromServices() #4 .../blesta/app/models/module_manager.php(449): Namesilo->upgrade() #5 .../blesta/app/controllers/admin_company_modules.php(179): ModuleManager->upgrade() #6 .../blesta/vendors/minphp/bridge/src/Lib/Dispatcher.php(142): AdminCompanyModules->upgrade() #7 .../blesta/index.php(21): Dispatcher::dispatch() #8 {main} I noticed that the error is pointing to this for loop inside the function 'setContactsFromServices' which is called from the Upgrade() method. foreach ($client_contacts as $contact_client_id => $contacts) { $this->Record->duplicate('module_id', '=', $module_row->module_id)-> duplicate('module_row_id', '=', $module_row->id)-> duplicate('client_id', '=', $contact_client_id)-> duplicate('key', '=', 'contacts')-> insert( 'module_client_meta', [ 'module_id' => $module_row->module_id, 'module_row_id' => $module_row->id, 'client_id' => $contact_client_id, 'key' => 'contacts', 'value' => json_encode($contacts), ] ); } I guess this function call from the upgrade method is to retrieve all contacts for all domains and set them into the module_client_meta table. The issue as I see it is that the $client_contacts does not contain contacts per customer, but its key is an empty element. (data masked) Array ( [] => Array <-- I guess here should be the blesta client_id? ( [54789654] => Name1 [65465465] => Name2 [65465555] => Name3 ... ) ) I believe these lines are setting the client_id to [] so the $contact_client_id is null. $contact_ids = $domainInfo->response(true)['contact_ids']; if (!isset($client_contacts[$client_id])) { $client_contacts[$client_id] = []; } I can't get pass the upgrade method.

Hi there, I'm using the latest version of Blesta (5.4.1) and I've noticed that the last couple of domain names that I've registered via the admin side don't seem to have WHOIS privacy enabled even though I have checked the box. I am using the Namesilo module. Have anyone else experienced this? I have to log into Namesilo and manually change the setting.

how to renew domain on blesta? can i renew without waiting domain due date?

Is there a way to force the namecheap module to use ipv4 only? The api does NOT support ipv6 (verified by namecheap support) and it causing errors when trying to purchase domains.

Hi, I have been through lots of docs and forum topics but unfortunately I can't find resolution to following issue. 1. I have installed namesilo module , got API and followed this guide : https://docs.blesta.com/display/user/Namesilo I can import multiple TLDs from namesilo as packages to Package group named "Domains" . Then added this group to an order form. Now when I open order form I get this : Feature wise, it working fine. I have used "Domains" package group under "Domain Package Group" and "Package Groups" is empty , please refer image : But as you can see in first image, it is showing all TLDs I have imported so far using NameSilo module, I can't get it to show only few and rest on clicking show more. So, How can do it to show 3-4 tlds and rest on clicking "Show more" with NameSilo module created packages ? 2. If I change "Domain Package Group" on order form to "TLDs Pricing Packages" which is I suppose created by default by new Domain Manager from : Packages --> Domain Options --> TLD Pricing , and here enable few tld's manually assigning NameSilo as module then I get few spotlight TLDs and rest show up after clicking "Show more" . But then from here, I can't use NameSilo module created packages. Further, my Domain order form is giving error "No API key specified" (refer image below) . But I have specified namesilo and its api is working as I can create package etc. as when I change "Domain Package Group" setting to "Domains" Package I have created which is used to store "Namesilo" module created packages, then can connect to Namesilo api as I shown in first image. So, Now do I have to use "Default Domain Manager" , then how to use it to get it list domain packages created by Namesilo module or can I just not use this and use Namesilo created packages but with spotlight TLD feature?

how can add a feature like free domain when customer go with our higher plan only.

We are in the process of fully spec'ing out the Domain Manager plugin for 4.1 and would love your feedback. I want to give you a basic overview of what we're considering for the Domain Manager, and get your feedback. We want to resolve the current issues and frustrations with how domains are currently handled. Please understand that the new domain system may not include everything in the first release, but our goal is to build the proper foundation so that it can easily be improved upon in the future. What is the Domain Manager? The Domain Manager is a plugin that will be responsible for all things domain related. Think of the Order System, and the Support Manager which cover all things related to orders, and support, respectively. How will I define pricing? A pricing grid will exist, likely under Domains > TLD Pricing where the price can be set for each TLD for 1 through 10 years for Register, Renew, and Transfer. This will provide a simple pricing grid, with different price options for Register, Renew, and Transfer. Additionally, special pricing can be set on a Client Group level, which will override the default pricing. Additionally, domain extras like ID Protect, Email Forwarding, and DNS Management will be options on a per-TLD basis and pricing can be set for these. The customer would be able to check if they want these options during checkout. Question: Is it sufficient to have a single price of ID Protect, Email Forwarding, and DNS Management for all TLDs, or would you want the ability to set a different price for these extra options on each TLD? Are domains services? This is a question that has resulted in much debate internally. My personal thoughts are that domains are very unique and do not easily fit with services. I am proposing that domains be treated completely separately from services. This means there would be a separate table in the database that stores domains and information unique to domains like: Domain Name, Registrar, Status, Date Registered, Date Expires, Management Features Available, Expiration/Renewal Reminders, Last Sync Date, and whether to Auto Renew or not. If domains are not services, they will not be listed with services. For the Staff area, I propose a new Domains widget on client profile pages. For the client area, I propose a new primary nav link called Domains. The Domain Manager would be responsible for renewing domains, and invoicing for them and services and domains would not appear on the same invoices, even if they are billed on the same day. Question: What are your thoughts on domains not being considered services? What about email templates? The domain manager would create several new email templates, likely to include the following: Domain Registration, Domain Transfer Initiated, Domain Transferred, Domain Renewed, Domain Expired, Domain Renewal Notice (domains listed are going to expire in the next x days). What about automatic things? The Domain Manager would be responsible for the following Automation Tasks: Send expiration emails at the reminder intervals Renew domains that are set to automatically renew Synchronize renew dates with the registrar at a given interval What about Registrar Modules? The Domain Manager would implement its own module system, and existing registrar modules would not be compatible. The new registrar module system would be drop-in similar to the existing, but these would be enabled and configured under Domains > Registrars. New registrar modules would likely be more lightweight than current registrar modules as the plugin would implement the common features across registrars. What management features would be available? This will depend on the specific registrar module, but the following features would be supported: Register, Transfer, Renew Domain (obviously) with Renew Domain being an option for Clients and Staff Manage DNS for Domain (Get, Update DNS zone records if DNS hosted by registrar) Manage Registrar Lock for Domain (Enable, Disable registrar lock) Manage Email Forwarding for Domain Manage ID Protection for domain (Enable, Disable ID Protection) Manage Contacts for Domain Whois (Registrant, Admin, Tech) Update Name Servers for Domain (Get Name Servers, Update Name Servers) Register Name Servers (Unsupported by many registrars or not commonly done by average users, may be optional for first release) What about existing registrar modules? Existing registrar modules would be incompatible with the Domain Manager plugin. However, services using current domain registrar modules will continue to work as they do now. Any bulk features? We plan to have bulk features for both Staff and Clients. For Staff, under Domains > Browse Domains and under the Client Profile, Domains Widget. For Clients, under the Domains page. Bulk editing/tasks would work similar to selecting invoices for delivery with a checkbox on the left and some options to choose from like Renew Domain, Manage ID Protection, Domain Lock, Name Servers. I'm certain I'm missing something, but wanted to give you a rough overview of what we are planning and get your feedback. Please let us know what you think!

NameSilo Domain Module This module is a complete solution for domain registrations and transfers through NameSilo. This module builds upon and continues the work by @NETLINK. He and I will be jointly contributing to this project and we welcome any other contributions on GitHub. An old thread related to this plugin was at https://www.blesta.com/forums/index.php?/topic/3399-namesilo-plugin Features Domain registrations Domain transfers Supports all NameSilo-supported TLDs by dynamically listing the available ones to package creation Proper .us/.ca support with necessary fields on order forms NameSilo audits Sync service's renewal date with domain expiration date Register/manage nameservers/hosts Set/change nameservers Update WHOIS details Lock/unlock domain Retrieve EPP code DNSSEC management Check email validation & resend validation email if needed Toggle WHOIS privacy Manually extend registration Transfer status tracking Screenshots Coming soon Installation https://github.com/knownhost/Blesta-Namesilo/blob/master/README.md Upgrading Nothing special is required except when updating from <1.8.0. In this case see the "Other" section below. Known Issues A domain transfer can be ordered for more than 1 year. NameSilo's API does not allow a transfer to extend more than one year so the extra years would be lost if not manually corrected. I'm unsure of how we'll solve this at this point. Future Plans Update for Blesta's new domain management system when release. This will be the v2.0 milestone and will likely be mostly a rewrite of the module. Clean code and remove unnecessary code. Manually extending as an admin should support invoicing/queuing to post-payment. We should be able to do this with the proration logic. DNSSEC management Implemented! Source This module is fully open source and can be found on GitHub. Two repos are kept fully updated with releases currently being built on the second: https://github.com/knownhost/Blesta-Namesilo https://github.com/NETLINK/Blesta-Namesilo Download I will make every effort to maintain the listing in the marketplace at https://marketplace.blesta.com/#/extensions/80-NameSilo Module GitHub will always definitely be up-to-date: https://github.com/NETLINK/Blesta-Namesilo/releases Other The version 1.8.0 release is a major update building upon @NETLINK's work. The new auditing features will not work properly until you "manage" and save your NameSilo account settings. Everything else should be fully backwards-compatible.

Hello! Has anyone found a way to list domain pricing? Or, can anyone tell me how to best edit the domains page: /order/config/preconfig/domains If there is no plug n play to do the listing, I am planning on building a simple table at the bottom and listing prices. Any help is appreciated, thanks!

I am posting this "solution" (bug?) in case anyone else had my issue. I realize there are previous threads about this here, here, and here (for example) but I didn't want to further hijack or necro their threads as neither involved NameSilo. In my case, I am using the NameSilo module(s) I tried both the original and the fork: https://github.com/NETLINK/Blesta-Namesilo https://github.com/mrrsm/Blesta-Namesilo I ended up using the latter because it dynamically pulls all the valid TLD's that NameSilo currently supports I did not test any other Domain Registration modules. Issue: It ALWAYS generates a "That domain name is not supported." and does not show the TLD under "Check Domain Availability" Solution: it was because I (intentionally) set the Package as a "Restricted" package -- it simply does not work with the NameSilo Blesta modules(s). Once the Package is set to to "Active", it works. I followed Paul's documentation about "Selling Domains" to the letter I did not find documentation or posts stating that Domains couldn't be Restricted Packages. The documentation simply says "'Active' is the default, 'Inactive', and 'Restricted' are also available." I actually did want to use the module as a Restricted Package to only some existing customers I used "Set Packages" prior to testing the Order so that the appropriate user(s) had access to it I only have a "Domain Package Group" selected and not "Package Group" selected as suggested here. Hope this helps someone else. Thanks

I would like a way to resell GoDaddy domains with Blesta. API: https://developer.godaddy.com

I migrated my data into a trial version of Blesta using the Import Manager, I have the eNom module installed and configured, I've created a package group called "domains," and I've set up a package for each TLD we need in the domains group. Now I'm trying to figure out from the documentation how to get my clients' domains set up. Most of my clients in WHMCS have at least one domain registered. They didn't make it in the migration as services, so I guess I need to set them up manually; however, I don't see any way to do it and make the next invoice coincide with when the domains are due to renew. How is that done in Blesta?

Hello Paul/Tyson/Cody, On this Post http://www.blesta.com/forums/index.php?/topic/4279-logicboxes-domains/ a problem was found by the user rfhmendes. If we have (almost everyone will have) multiple TLD's Packages on the same "Group", and we have enable the option for client "Upgrade/Downgrade", "Change Packages", Clients can Change the "TLD", and this cannot happen I propose for now a Quick fix to disable on Type "Domain" the option on Client Area to "Change Package", for later on, on the new Domain System you can implement a final solution Thanks in advance