Tyson

Take a look at the documentation on linking to a product. Although not specifically defined, config options may work similar to this example. Domains are separate from other packages and AFAIK that must be provided via POST. The only way I see that working is if you configure your links to submit a form to a particular product, but I have not tested that behavior.

Is there a log entry for the ticket? i.e. The status has been changed to Closed. Apr 7 2016 12:55 PM by System

You could also create a custom report in Blesta to fetch the data in a CSV.

Add a from column where?

It looks like the same issue is occurring now for invoices. Each userid in tblinvoices should be non-null as well.

Sounds like there was a validation error attempting to save the changes. You may need to process the change yourself instead. #6 refers to the `service_changes`.`id`. You can fetch the record by running this query: SELECT * FROM `service_changes` WHERE `id` = 6 ; The `service_changes`.`data` for that record contains all the changes for the service that should have been made, but couldn't be due to the error. You could use this information to update the service yourself from the admin UI, and then mark the service change complete, i.e.: UPDATE `service_changes` SET `status` = 'completed' WHERE ID = 6;

I believe the service renewed because it had a paid invoice ($0) that was generated from the service change.

Are there any package groups in the package_groups table? You may want to turn on error_reporting in php to see if there are any run-time errors occurring. It could be that there is either an error, or you have a lot of records to import and it is taking some time to process.

The Shared Login plugin does not support logging in with two-factor authentication. It would only be useful for users that have it disabled.

I'd say to expect 30-40 hours to develop a basic-to-intermediate functional module for someone somewhat familiar with modules in Blesta but unfamiliar with your integration API. That would include research (e.g. reading API docs), communication (back/forth with you on required features before/during/after deployment), development, and testing. Add 15-20% for additional features/changes that will likely arise before completion.

What is the issue exactly? The service term change of $0.00 is not accurate? What would be accurate? What package prices are used (to/from)? What config options have changed [and how much do those cost (to/from)]? It sounds like the term change resulted in no additional prorated cost, or perhaps even a credit to the client (if you have that enabled) for the price difference. If that's the case, then this may be normal behavior.

Do you have Blesta configured to queue service changes? Is your Process Service Changes automation task running? If so, it could be possible the service fields/options that were ordered are not valid/produce an error when attempting to provision them.

Under [settings] -> [billing/Payment] -> [invoice Customization], at the bottom is a Font Family selector. Choose a font (or add another font) that supports that character.

It sounds like your WHMCS database may not have a valid userid for every contact from tblcontacts. This value becomes the client ID in Blesta, so one must exist. You may need to update that database table to ensure each record contains a non-null userid.

An invoice that is due today, at midnight, means (in Blesta) that it is due any time today. However, if you set the Suspend Services Days After Due setting to a value of '0', it will suspend services whose invoices are due (earlier) today. I don't think that is what you want. You would have to update Services::getAllPendingSuspension to fetch invoices that are due before the suspension date at the end of the day.

I'm not sure whether that is something we can tell PayPal Subscriptions to do. It may be necessary for the client to update their subscription to change the auto-payment date (if that's possible).

You will upgrade to v4 just like any other v3 upgrade as long as you have Support and Updates still valid.

The comma is your decimal separator?

What if you want to see errors from the client interface due to some issue? In a live environment, you shouldn't have error reporting on at all.

Do you want to suspend a service before the invoice for it is due? I believe the setting that controls this behavior is called "Suspend Services Days After Due", meaning suspension should occur after the invoice is due and not before. In what cases would you find suspending the service before the invoice is due useful? If the problem you're having is with the way suspended services are not based on calendar day, but a 24 hour difference, then I think a possible resolution here is to update it to respect the calendar day instead.

There's no ETA on this module's completion yet. Other tasks have taken priority for the time being. I would suspect that we would come back around to determine when this task could be done post v4.1.

The auto-close ticket email uses the Ticket Updated email template. These are all the tags available.

I've never seen that error before, but it looks like something internal to the H2o library. It might be that H2o is not being used properly. If this occurs with the default Support Manager, and you can consistently duplicate it, could you send over the details of the ticket and ticket replies so I can see if I can duplicate it too?

A feature for moving client data to another client (e.g. services) would inevitably require that any open invoices for the service be moved as well since they are tied together. Otherwise, the invoice would need to be voided on the old client and created anew on the new client.

Can you dump the response and any errors? i.e. print_r($response->response()); print_r($response->errors()); What you have looks like it should work to me. Are you able to perform a simpler action, like the example in the docs--fetching a user by ID? $response = $api->get("users", "get", array('user_id' => 1));