Tyson

Are the support department SMTP details still correct? It sounds like since you changed DNS that the server can no longer communicate to fetch tickets, or has otherwise caused another error. You can disable the "Download Tickets" automation task so that it is not run by cron automatically. Update your configuration file to enable error reporting. Then wait a little while (5 to 10 minutes) and try to run the cron manually from Settings > System > Automation. Are there any errors displayed? If so, what are they?

I believe this is CORE-1794. All of the transaction data shown would be optional. We could only show what we have, if we have anything in the first place.

You could try this in /plugins/order/views/templates/standard/types/domain/lookup.pdt .

Blesta doesn't currently have an option to deny accepting payments unless they are for specific invoices. A customer could add a payment now for something like a renewing service later (i.e. pre-pay), and Blesta will treat it as a credit on their account. However, it is possible to hide the "Make Payment" button, but it would require you to update a core template in the source code. To otherwise forcefully deny payments from customers would require additional logic to be added.

Thanks for the notice. It does look like it's treating credits as revenue in those stats. CORE-2276

If you disable the cron from running, and then run it manually from within Blesta instead, do invoices get delivered using your invoice customization images? My guess is the answer is 'yes'. In that case, the issue is probably that the cron you have setup runs on the server as a different user--a user that, perhaps, does not have read access to the uploads directories or the file itself.

Everything that runs affects performance in some way. The cron tasks usually complete fairly quickly, and in the background, so you're unlikely to notice performance degradation.

I assume you have setup a cron job already, correct? It is very likely that 1 cron job is already setup which runs all tasks. This is the behavior we recommend when setting up a cron job, and what is described in the documentation. The alternative I mentioned is to run each task individually, where each task is started from a separate cron job. If you continue to receive this message on the System Status plugin: ..then I would suggest:

I don't think a quantity adjustment is suitable in createFromServices. The invoicing would become much more complex if quantity had to be considered there. It is not meant to consider input variables since it is dependent on the service information. Eventually, this functionality will be removed for a better solution yet to be created.

A customer can register from a dedicated Client Registration order form, as Licensecart described, or they can register during the order process when purchasing a product.

CORE-2056 is still an open issue, so no, it's not in v4.

If you can call "bl_getState" successfully, then I would expect you could call "bl_getBuildProcess" successfully too. Everything you have looks correct. There may be some other issue, or possibly a bug somewhere. You may need to debug Payments::getBuildProcess in Blesta to see why a blank error is being set.

You can setup a cron job to run all cron tasks or only a specific cron task. You can run a specific cron task by updating the cron task URL to append the name (method) of cron task you want it to run, e.g. Setting a cron task path to "/path/to/cron/createinvoices" would run the "createinvoices" cron task only.

The link takes you to the password-reset page (that already exists in the core). If we were to support a modal/on-page way of resetting a password, then the Order plugin would have to implement it itself, with or without support from the core. That would require additional code to be written, and is a bit of duplication having it in multiple places. Not saying this is a bad idea, but probably more work than a beta will allow. Might be best for a future version.

It sounds like your browser has the ability to go back to the last AJAX request. Never seen that before.

That's a question I'm going to pose to Cody. What constants? Blesta uses the minphp constants. Do you want to create new constants or overwrite the current ones?

I changed mine from one tab to two tabs, and now the graphs fail to load due to a JS error. And also when changing back to one tab. In any case, this is assigned CORE-2267

Cody who?

Are you familiar with SQL at all? The transaction received report lists a record for each transaction. Including client services would include ALL client services. You may or may not be able to limit the client services listed to those specific to that transaction. In any case, they could be listed in their own column, each on a new line. For the custom fields, I would need to know the exact custom field names you want to include, or whether you want to include all custom fields. If all custom fields, there would be another column in the CSV, similar to the services, that lists each custom field on a new line. If you only want 2 specific custom fields, then those can be in their own individual columns, or can be combined into a single column, each on a new line. I just want to make sure you understand the way the information will be displayed in the CSV, as it may be difficult to work with, for instance, if you are importing it into another application.

Firefox 48.0.2 on Windows 7 has always shown graphs for me. I'm aware of one thing to fix with the graphs (probably be in beta 2), but I'm not sure whether it will resolve the graphs-not-loading issue. We'll have to wait and see.

Have you tried it in another browser?

It will be in beta 2. I didn't have time to review it prior to the current build being released.

It would be if another dependency in the project supported it. Not sure why it wouldn't.

What browser/version are you using?

Haven't tested it yet, but does it always occur, or only for some tickets? Does the content of the reply make a difference? Does the reply contain any tags? Does it use the tag keyword braces at all (i.e., "{" or "}")?