Tyson

Which services do not appear? Those using Logicboxes as you mentioned here? Any others? Can you illustrate the steps to duplicate this? It would be useful to know what package settings you have configured for the service that you're adding. Whether the service was added manually, from the order form, etc. may also be useful.

The remaining untranslated definitions are not included in English for language packs. Blesta automatically defaults to a English definition if your language pack is missing it, so It would be redundant to include untranslated definitions from the translator. And as Cody mentioned, translating the files manually can lead to other issues, like BOM. It also becomes very easy to create syntax errors, especially if you're not familiar with PHP and escaping characters, as well as sprintf-style variable replacement.

I'm not aware of a problem with service listings. Can you create a new thread about that issue? I'd like to keep this topic focused on the "customer-id" issue.

Does the fix I provided above resolve these issues? I'd like some input from those that this issue affects before I mark this resolved. Blesta requests the whois/nameserver information, but it may not be immediately available from the server. If you give it some time to setup, does it appear later?

Two issues here: First parameter should separate words using underscore, i.e. "client_groups" Third parameter should be a valid set of key/value pairs for the specific action you're calling from the ClientGroups API e.g. $response = $api->get("client_groups", "getList", array('company_id' => 1));

I stumbled on "total", "incredible" and a few other words, so I guess I'm a "kid".

It sounds like there may be 2 or 3 things going on here. The first error that says to use GET finally clicked with me. We had a similar issue in v2 a couple years ago because the live and test APIs behave differently. This is why some of you experienced a problem, while we couldn't duplicate it in our test environment. I believe the solution to this problem is the following: Update /components/modules/logicboxes/apis/commands/logicboxes_customers.php (line 177) return $this->api->submit("customers/search", $vars); change to: return $this->api->submit("customers/search", $vars, "GET"); Then try creating another service and let me know what happens. You unchecked the "Use Module" checkbox when you added the service? And it still attempted to add it using the module? That doesn't sound right.

I read this as "I'm sitting in the emergency room with my wife at the moment. Two 9mm shots to the kidney, and a bladder infection." For a second there, I thought you got shot. And then I wondered why you would be on the forums at a time like this.

Thanks for the info. Were there any logs that came before this one? Seeing all Input/Output in sequence for the entire transaction when attempting to add a service, whether successful or not, would be ideal.

It can be used that way. If knowing the password is important, you shouldn't click to generate one for that field, and should instead create one manually.

Could someone that experiences this issue send me the Module Log data associated with Logicboxes when this "customer-id" error occurs? You can omit sensitive information in the data and post screenshots here or PM them to me.

This feature already exists. When a client logs in, their dashboard lists their invoices with an option to "View" each one. Clicking this will download the invoice PDF. Does this not happen for you?

Maybe it was bad luck I was born! Since it was on Friday the 13th.

The way it works is intended. Previously, it was a plain text field along with some other fields in Blesta, but those needed to by made into password-type fields. We plan to come back to this to improve how passwords are generated such that you would have an option to view the generated password.

It'd be easier to look at the Support Manager documentation which lists all of the tags available to each of the email templates. You'd want to use one of the {ticket.department_email}, {ticket.department_id}, or {ticket.department_name} tags. And yes, you can use conditionals as described in Customizing Emails.

The best answer is for everyone to know the answer! I'm really curious, especially since it seemed like a bug with using subdomains as a hostname.

The route to the client interface is set in /config/routes.php I haven't tested whether it will work correctly if you leave it blank, but I imagine so. There may be conflicts if you use the Portal plugin at the same time.

Is http://my.hostingdifferent.com/client/ not the correct URL? The links appear to work. To me, it looks like the only issue is that the cron does not set the correct hostname when a subdomain is used.

If you have a PayPal sandbox account, you can test a payment with it just to make sure that's what the issue was.

Oh, the cron job wouldn't have handled the payment back from the gateway--it gets processed immediately once it's received. Strange that your credits cron task is unable to apply a transaction to a blank transaction number--you may want to look into why that's happening. But for the PayPal issue, the only thing that comes to mind is that you may have a notify URL set in your PayPal account, which tells PayPal what URL to notify about the payment transaction. Blesta gives PayPal the notify URL automatically, but perhaps you have one set in PayPal that is overriding it, and thus payment notifications are never making it back to Blesta. I think you forgot to remove your API password/key from that screenshot.. you may want to generate a new API password/key now.

Not sure I follow how a payment that hasn't been recorded from PayPal relates to the cron applying credits to a transaction? What's in the gateway logs? Have you actually received the payment in your PayPal account? What's the status of the payment with PayPal? It may be that the payment hasn't been completely processed yet, and therefore has not notified Blesta.

This happens with the Invoice Delivery (Unpaid) email template? The {client_url} tag is generated from the company hostname and the URI to the client interface. The client URI looks correct, it's just that the company hostname is wrong? Does this occur when you send an invoice manually (under the Client profile, check the box next to an invoice and email it to yourself), or does this only happen when the cron sends the email?

This was fixed in v3.0.2 as reported @ http://www.blesta.com/forums/index.php?/topic/839-client-url-doesnt-detect-folder-location/ and http://www.blesta.com/forums/index.php?/topic/809-payment-url-template-field-not-the-correct-url/ As mentioned in How To Report a Bug, you should try searching for the issue first before creating a new bug report.

Assuming you're using cPanel, the cPanel module documentation and the documentation on customizing emails should help.

Can you provide more information as described in How to Report a Bug? A "Permission denied" error and a "Please enter a valid domain name" error are very different--under what circumstances do these occur?