Leaderboard

It would probably be a good idea to disable the pay button on click so that it cannot be clicked more than once.

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!

Hi everyone! Anyone who knows me will know I'm a massive fan of Blesta and to show my appreciation I've registered and configured an IRC channel. I spend a lot of time on IRC on a number of channels so it seemed natural. If the admins are not okay with this please let me know, it's more an enthusiast channel than an official one though. I'd love to see some users and members of the forum on the IRC channel, I use a bouncer so am logged in 24/7. You can access the channel using the details below Through your existing IRC client - irc.freenode.net - ##blesta You could also try the web interface here - http://bit.ly/2b8tbRk Looking forward to speaking to you!

if i well understand your idea, a simple module can do this perfectly . so i give you a road to begin . the module will have a rows, the rows as a levels, then every row has a culomns, every culomns has a set of user/pass entered, in a texteare , eash one in a new line , now the user order a apliance, the module will take the first user/pass , send it to the client and remove it from that database . and so .... i code it for you if you want .

@PauloV @naja7host @timnboys <- One of these guys may be able to help you.

Automating this by pulling from a pool of credentials would require a simple module. Doing it in the way Mike describes, requires staff to manually enter the information before accepting the order. With a module, you could pull these credentials out of MySQL or a text file and provision automatically. So, the answer is, out of the box you can but you have to manually enter the credentials before approving the order. To do so automatically, you need a simple custom module. There are some developers on the forums here that can help you out with a custom module for probably not too much if you want to go that route.

CORE-2250 Thanks

On a side note the issues people were facing in other topics with Blesta being on the same server as Plesk and accounts not being created I haven't had any issues with. So glad to be a part of this amazing community!

LogicBoxes Extended LogicBoxes Extended For Blesta is a module created specially for LogicBoxes API to enable you to automate the provisioning and management of domains in your Blesta system. With its help you will be able to set up your TLDs & gTLDs with just a few clicks to start reselling them to your customers right away! Features: Edit All The Contact Information (Whois) Change Name Servers Set Forwarder Set Child Name Servers Get Authorization Code Change Authorization Code Ability To Sell Private Whois (Using Options) Automatic Synchronization of Expire Date for Transfered Domains DNS Manager Versions: Update 1.0: First Version Released. Update 1.1: Optimized for Blesta 4.0. Update 1.2: DNS Manager NOTE: If you want sell "Private Whois", you need add a Option like the following screenshoot. Screenshots: Download: LogicBoxes Extended is available in the Blesta Marketplace for only $49.99 per year or $199.99 one time and you can order here https://marketplace.blesta.com/#/extensions/32-LogicBoxes Extended

Great! I would suggest downloading and installing the free trial if you haven't already. The demo is a little out of date, and installing the free trial will set up a private environment you can fully test. www.blesta.com for download link and install docs.

If you don't define a price for the other years, they won't be available to select. Still, it may be a good idea to define renew prices for those years even if you don't for new domains. If I have a domain that is paid up for 6 years, I might want to add 4 more to max it out. The templates would exist, however the way we are looking at it is that the reminder interval will be defined for each domain. This will be pulled in from somewhere, either by the module, or an option for the TLD. So, if there are no reminder intervals defined, no reminders will be sent.

Yes, you can certainly do that. Mike mentions putting the quantity to 8, but this won't accomplish what you want which is to send the unique credentials to the user. If you create 8 packages with a quantity available of 1 you can accomplish this. The user will see 8 possible packages during checkout though, which might be confusing. After the packages are ordered, mark them as inactive.

You hit the nail on the head with your last sentence. No one controls the pricing apart from ICANN and the TLD registries. It's also never been an expectation for customers to be locked into domain pricing. If you really want a workaround to this, businesses can offer a coupon code / discount to bring the price back down. But it should be at their discretion. But in most common scenarios, price increases are passed on in the domain world.

Awesome so you want to make a "package" and use the universal module with 3 fields (I think) as so: URL (provided after): Username: Password: And set the order form to "Require Manual Review and Approval of All Orders" then after you get an order, you can accept the order on the Billing tab on the Order Widget. Then go to the client profile and click on pending > manage and enter the details and click save.

Email piping for the support system and using SMTP for outgoing mail are completely separate and should not affect each other in any way, except that all outbound email, including that of the support system, would use SMTP for outgoing mail. If SMTP is not working for the support system, it shouldn't be working for any email. Double check that your credentials are correct and that the necessary ports are open at your firewall.

See CORE-2249. This has been requested before as well, but an excellent idea.

Thanks for your reply. I wish for these firewalls to be stand-alone products. I'm a bit confused still if this is possible; to present the pre-configured appliance types (3 types) as stand-alone products. If a customer orders type "Firewall A", blesta draws from the inventory of that firewall type (if inventory exists), and (here's the important bit) once the payment is approved, the customer is provided the unique login credentials which I have pre-created when we deployed the device, not credentials created by the customer. The take-home point is that each device has unique login credentials preconfigured, thus I need to create pools of these appliances each as a product with unique attributes. You clearly provide a huge amount of support here in the forum. Thanks for that effort.

@Licensecart Dedicated servers @Max Okay, sounds good. We'll give it a shot. Thanks for your product.

Module still works as intended with latest Blesta version. Cannot guarantee any long-term support though. Number of Blesta users is very low.

DO module has a problem with Blesta 3.4. up. I checked, works excellent on 3.2.2