NETLINK

Hello, A pro forma invoice is a document that states a commitment on part of the seller to deliver the products or services as notified to the buyer for a specific price. It is thus not a true invoice. Therefore, for EU businesses, if an invoice is a pro forma invoice, it should include the words "This is not a VAT invoice", or "Pro forma invoices should not be treated as VAT invoices". Would it be possible to add this as a feature? To add this text below or above the Terms. Or possibly in small font underneath where it says "Pro Forma Invoice".

That's great! I'm glad it's working. And any feedback or suggestions are more than welcome

Hey! Once you have the module installed, you can go to Settings -> Modules -> Manage (Namesilo) -> Add Account. There, you can add your username and API key. Once you have that done, you'll have to add a new (domain) product under Packages. Select Namesilo as the module and then choose your domain extensions. When you've that done, you should be good to go. To add already existing domains, you just go through the process of adding a new service under your test account, but you leave the "Provision using the Namesilo module" option unchecked. Let me know how you get on.

I wasn't too sure, but because it seems to work with "test.example.com" (in other words, the domain parts don't get mixed up), I thought maybe bug.

When looking up a domain that includes the "www." part, the order form mixes up the domain parts. Example: Check Domain Availability -> enter "www.example.com" -> press "Check Availability" or "Transfer". The form shows the following: examplewww..com ("Not Available" when using Check Availability option, regardless of whether or not root domain is registered) examplewww..com ("Available" when using Transfer option) I thought I should add this as a bug since a lot of people will enter the www subdomain, either because they're used to it, or because they can't distinguish or don't know the difference, and that can easily lead to lost business, especially when it's new/potential clients. This seems registrar/module and order form template independent. Version 3.5.2.

I didn't mean splitting wasn't important, or less important to you or others; I was just stating my own opinion, but I apologize for hijacking your thread.

http://www.blesta.com/forums/index.php?/topic/4873-split-invoice/?p=36735 Sorry for cross-posting. This thread seemed more fitting.

I've found myself splitting invoices in the past, on WHMCS, but I think merging would be more important. My use case is as follows... A client is behind on 3 or 4 payments. They request a total owed. It's easy for me to add up the total and communicate it to them, but then, sending one combined (pro-forma) invoice, specifying the grand total, is much more convenient than sending out 3 or 4 separate invoices. This causes confusion, and I've often had clients paying the amount specified on only one of the invoices. Then, it makes it awkward and time consuming to revert and explain that there are in fact 2 or 3 unpaid invoices left on the account. I've added some code to the online payment page, making it easier for clients to see all unpaid invoices and make one payment to clear them all when they click on the Pay Now link they get via email, but some people may still be old-fashioned, and prefer giving card details over the phone, and others still pay by cheque/check. In this case, I think combining would be very useful.

This still seems to be an issue in version 3.5.2. I'm trying to apply a check payment to an invoice.

Is this fixed in v3.5? I only just noticed this. Where a 100% discounted product is still coming up with the original VAT/Tax amount.

As I understand it, general contact types cannot be used for ccTLD registration. They have to be country specific contacts. When adding a contact, the contact type is required, and for ccTLDs, the contact type has to be set to "UkContact", "DeContact", "EuContact", for example. https://support.logicboxes.com/helpdesk/index.php?/Knowledgebase/Article/View/25/5/error-invalid-domainname-for-given-contacttype-while-registering-cctlds http://manage.logicboxes.com/kb/answer/790

I'm using 3.4.4. But a single transaction ID still seems to be getting passed to the verifyApply method in transactions.php when trying to apply credits. When I commented out line 704 in app/models/transactions.php, the payment was applied successfully. Line 699 to 706: if ($validate_trans_id) { $total = null; // The total remaining transaction amount is the maximum that amounts can apply if (isset($vars['transaction_id']) && ($transaction = $this->get((int)$vars['transaction_id']))) { $total = max(0, ($transaction->amount - $transaction->applied_amount)); } }

There seems to be 2 issues here. 1 is with rounding and floats not matching, and the other is with these lines of code in app/models/transactions.php: // The total remaining transaction amount is the maximum that amounts can apply if (isset($vars['transaction_id']) && ($transaction = $this->get((int)$vars['transaction_id']))) { $total = max(0, ($transaction->amount - $transaction->applied_amount)); } The problem, as far as I can see, is that when credit is being applied to an invoice, and the total credit amount needed to pay the invoice is the sum of two or more transactions. For example, the invoice amount is 100.00. A check payment of 90.00 is recorded, and then another check payment of 10.00. The total credit amount is now 100.00, from 2 transactions. However, the script above only uses the first transaction to determine the max credit amount, which would be 90.00.

In relation to the following bug, I'm unable to record check payments. Is there a workaround? http://dev.blesta.com/browse/CORE-1597 Even when the credit is 10 Cents more than the invoice total, I am unable to record the payment. Please see screenshot.

Good stuff. No problem.

Does the label still not show on invoices for new orders after installing the update? Domains you've added before the 1.0.8 update will show blank, as the label wasn't being saved when the module wasn't used to register the domains. Please let me know. You can report them here or at GitHub, whichever is handiest.

This should be fixed. Please try it with version 1.0.8. https://github.com/NETLINK/Blesta-Namesilo/releases/tag/1.0.8-alpha Or simply download the latest namesilo.php file and update it in the module's root directory.

Thanks for taking the time. I think I know where the problem is. I'll get back to you shortly.

Could you try deleting the service (domain) and adding it again? Then see if the Whois and Nameserver tabs are working correctly, and check the module logs under Tools -> Logs.

No, the full domain name should be visible on both client dashboard and admin back-end, whether or not you use the Namesilo module during setup. Can you confirm that it's version 1.0.7 you're using? You can check by going to Settings -> Installed Modules.

Do you have error reporting turned on in the config file? And the latest version of the module? https://github.com/NETLINK/Blesta-Namesilo/releases/tag/1.0.7-alpha Please PM me if you'd like me to take a look directly.

Sorry, I'm not following, but I'm happy to help if you could post more information.

Hi, Lucas. Could you post more details with info on how to reproduce and a screenshot?

The Enom Module domains Whois tab is unresponsive when trying to access it via the back-end and with error reporting turned on. When opening the URL directly (no ajax), the following error is returned: Oh noes!strlen() expects parameter 1 to be string, object given on line 54 in public_html/blesta/helpers/html/html.php Version: 3.4.3

When editing a (domain) package, add a pricing row using the "Add Additional Price" button, leave the row empty, remove it, then save the package information, the following error is thrown: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'term' cannot be null on line 124 in public_html/blesta/lib/model.php Printing Stack Trace: #0 public_html/blesta/lib/model.php(124): PDOStatement->execute(Array) #1 public_html/blesta/components/record/record.php(225): Model->query('INSERT INTO `pr...', Array) #2 public_html/blesta/app/models/pricings.php(93): Record->insert('pricings', Array, Array) #3 public_html/blesta/app/models/packages.php(1507): Pricings->add(Array) #4 public_html/blesta/app/models/packages.php(285): Packages->addPackagePricing('2', Array) #5 public_html/blesta/app/controllers/admin_packages.php(362): Packages->edit('2', Array) #6 public_html/blesta/lib/dispatcher.php(111): AdminPackages->edit() #7 public_html/blesta/index.php(21): Dispatcher::dispatch('/admin/packages...') #8 {main}