Paul

We are not ignoring anyone. 5.1 is the initial release of the domain manager, it improves domains significantly, and it's really just the start. I count 15 tasks for the domain manager that are already done for the next release, version 5.2. If you want to write Blesta off because it doesn't import all your TLDs in the initial release, that's up to you. That doesn't negate the fact that it's still a major step in the right direction. Our staff don't typically respond to forum posts over the weekend.

Do you mean the log shown under Tools > Logs? The "Contacts" log here is kept indefinitely and are not rotated out automatically like other logs. It is hard to find stuff here though, and we should definitely show changes for a specific client under Actions on their profile page. See https://dev.blesta.com/browse/CORE-2223 for the task, will this accomplish what you are looking for? Maybe we can bump it up.

Just to add, the pricing for these config options will be able to be set under Packages > Domain Options > Configuration in the next release - version 5.2 of Blesta.

If you are using the domain manager, the option can be enabled under the TLD Pricing page (Packages > Domain Options) for registrars that support it. Currently the pricing would be set under Packages > Configurable Options > Options > ID Protection: Edit (and set the prices for each term. The current schema is the same price for all TLDs, but you could clone this option with different pricing, put it in a different group, and manually assign it to the Package (Under TLD Pricing > Edit > Advanced > "Edit Package" button. Swapping out the official config option group with the one you created. As a note, most of the registrar modules do not yet support ID Protection. If you check the box and get this error then it doesn't support it yet. We'll be adding support for these extra options to official registrar modules soon. The id_protection feature is unsupported by the selected registrar module.

This depends whether you are creating your own module, or using the Universal Module. For the Universal module, we recommend creating any fields that will not cost extra (like username, password, etc) as a service field on the product. See https://docs.blesta.com/display/user/Universal+Module#UniversalModule-ServiceOptions for docs and an example. For any fields that should cost extra, those should be created as Configurable Options, under Packages > Configurable Options. If you are creating your own module, then you would code in the service fields. The Extension Generator plugin can help you get started with development, and I believe it lets you define these fields https://docs.blesta.com/display/user/Extension+Generator

How do you get away with not paying VAT tax on both the original invoice for the credit, and the invoice for the credit consumption? It looks like you're simply not charging VAT on the portion of the service invoice that was paid with prepaid credit, but this doesn't seem like a very elegant solution. An invoice paid by credit would essentially be tax exempt, or partially tax exempt. At the time an invoice is generated, it does not know how it will be paid. Is the tax on your invoices edited/adjusted when they are paid, based on how much prepaid credit is applied to them? This would violate regulations in many countries that do not allow invoices to be modified after they are created. Also, what if the VAT rate changes between the time the prepaid credit is made and the service invoice is raised? Say it's 18% when the credit is made, and 20% when the service invoice is created. If an invoice-like document must be sent when a prepaid credit is made, this seems more logical: When a credit is made, create a new type of invoice.. maybe it's called "credit invoice" or something, to distinguish it from a normal invoice. Do not charge any tax at the time the credit is issued. When credit is applied to a service invoice later, calculate the tax rate like normal an assess the tax then. This avoids the problem with duplicate amounts appearing in invoice reports, because a different type of invoice is generated for credits, it's not the same. It avoids the issue with the tax rate changing, because it's only assessed when it's applied to a real invoice. And, it avoids having to edit/change an invoice on the fly to account for taxes that were paid with the prepayment.

The license "Blesta Owned Lifetime" does not have a yearly fee for updates. It's a special license type, that we may limit future sales of, adjust pricing, or discontinue sales for at anytime without notice. Those that have it will not need to pay anything in the future.

I think Cloudflare was having trouble yesterday. I got an error for about an hour from home, even though the network and servers at the origin were fine.

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?

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.

You have 2 overlapping rules, so the first matching level 1 rule is applied.

What version were you running before? I'm pretty sure this is normal, a result of markdown only wrapping paragraph tags around only content and not white spaces.

If you install 5.1 fresh you'll have the domain manager. If you upgrade to 5.1, then you need to install the domain manager under Settings > Company > Plugins > Available. If upgrading to 5.1.0 you should install the domain manager or you'll experience the above mentioned bug. That will be resolved in 5.1.1 so that it's not required to be installed.

Done, thanks!

Good idea, I've added this task https://dev.blesta.com/browse/CORE-4373

Thanks for the feedback. This would only be if the user was linked to multiple accounts. It would have to be a setting to allow this or not.

Blesta doesn't store the gateway on an invoice prior to payment because Blesta doesn't force a particular payment method on an invoice. Once payment is made, the details are stored. Any gateway can be used that supports the currency of the invoice. Are you saying you want to force a client to pay with a specific gateway? If not, what is the use case for having a gateway associated prior to payment, given that the actual gateway used may be different?

Well said. We appreciate you, and @TheMaster. If you search around, you can find plenty of bad things people have said about Blesta on these forums. We leave them because we believe in free and open dialogue. Censorship is against freedom of expression. People will say things that are wrong, and others will see it and it'll only hurt their own reputation. We would like to see @TheMaster stay. Obviously that's up to him.

That's wrong. My opinion is that there is nothing unethical here, and you are very much welcome. We do not censor all opinions we disagree with. If you want to throw all your hard work away because of some random person, that's up to you. Seems like you're giving up quite a bit to do so.

Overreact much? If one person's opinion causes this kind of reaction, I'm not sure how you get up every morning and carry on. Seriously. I happen to disagree with them, by the way, but we're not going to censor people on the forum because it hurts your feelings.

It wouldn't be the first time, people can judge for themselves. It doesn't seem unethical to me.

This issue has to do with using a comma as the decimal separator instead of a period? Does EUR normally use a comma?

What was the renew date for the service? If it is scheduled for cancellation, no invoice would be generated. If the scheduled cancellation is removed, then the service should be invoiced at the next daily invoice cron run. So, it can take up to 24 hours for an invoice to be generated. Note: "next daily invoice cron run" if the service should be invoiced based on the renew date.

Hello! We have a task to allow users to have access to multiple client accounts, potentially cross-company. It's likely it will be cross-company. Upon login, a user belonging to multiple client accounts will have to choose which one to use. There hasn't been a ton of demand for this, and there are some details to work out, but it is something we are planning to do. See https://dev.blesta.com/browse/CORE-3942

The license hasn't been transferred to you yet right? If this is the same ticket I'm thinking of, we have invoiced the original owned for the transfer fee and will transfer once paid. The email they provided matches the email you used to register for the forums.