Paul

It looks like you're trying to edit an existing Config Option. What did you change?

If they are considering making some changes or creating their own module, we can provide a free dev license to them. Feel free to mention that if you chat with them again.

I don't suggest changing the module for the package in the database manually unless you really know what you're doing. It's very likely that each module utilized different service meta data. So, I'd suggest setting up a test install with both modules, and create a service with each. Then, look in the database at the data to see what is stored and how. Specifically, the service_options table, which stores things like the domain and username. The key and data will need to be translated for all fields to the way the official Interworx module works. If you don't do this, and update the service_options for every service that you're converting, it will likely break.

Are you using PHP mail or SMTP? If you're not using SMTP, try switching to SMTP. If you have access to your mail server logs, check those and see if any errors are produced. If it's intermittent, maybe it's a network or rate limit issue? If you're not running Blesta 4.0.1, I'd suggest upgrading. We upgraded Swiftmailer (the mail library) in 4.0, though I'm not aware of any bugs that could cause that in the previous version.

Do any other emails go out? Check your mail settings. Settings > Company > Emails > Mail Settings

Downloads in the download manager can be restricted to clients who have a specific product/service/package.

There is no distinction between upgrade and downgrade, if the package group setting allows "Upgrades/Downgrades" they can do either.

We added 28 new events to 4.1. You can see them in the documentation at https://docs.blesta.com/display/dev/Event+Handlers (Search the page for 4.1)

When we build this into the core, what if we add late fees to the same invoice, unless proforma is enabled.. if proforma is enabled, then create a new invoice for late fees?

Welcome and thanks for sharing!

One other person reported that the "Apply Payments to Open Invoices" task was getting stuck. No spinning gear icon under Settings > Company > Automation for it? Does it seem to be pretty consistent in terms of not applying payment if the invoice was generated previous to the credit for all clients? Reproducible? I would double check, and maybe re-save company (Settings > Company > Billing/Payment) and client group settings, verifying that "Automatically Apply Loose Credits" is checked in both places.

Ok, so a couple points: When a payment account is created, if it's the only one, set it as the default. When a payment account is created, and it's not the only one, ask if it should be the default?

So it creates a new invoice just for the late fee? Is that the most common way, or do some places add it to the existing invoice? I know in some places you can't edit the invoice once it's been created, but I don't know if they have exceptions for late fees. Just curious, in case we add to the core in the future.

I thought I had replied to this earlier, but I guess I never hit submit - Web server shouldn't matter for doing backups, except for the username that it runs as. You should check the following: Does mysqldump exist on your server? To test, SSH in as your user and run "mysqldump", it should show usage. Does your web server user have permissions to execute mysqldump? Is the temp directory set under Settings > System > General > Temp Directory, and is it writable by your web server user? Via SSH, you can run a test database export to see if it should work: mysqldump -u MYSQLUSERNAME -pMYSQLPASSWORD DATABASENAME -r database.sql MYSQLUSERNAME, MYSQLPASSWORD, and DATABASENAME should be replaced with the correct details, which you can find in your ~/config/blesta.php config file if you aren't sure. (NOTE that there is no space between "-p" and the password, this is important). After it runs, what's the size of database.sql? (ls -la)

Glad to hear it is working! If you changed from PHP 5.6 to 7.0, I'm assuming you applied the hotfix for Blesta that contains 3 files necessary for PHP 7. If you didn't, nothing would be working.

I uploaded an updated whmsonic module, see original post. Also added a sample welcome email.

Are you running any custom code? Custom theme, custom module, custom plugin that is using any hooks/events? It's not common for apply payments to open invoices to get stuck. When did the issue originally occur? Think back to just before that, did you make any changes to the installation or system beforehand? Are there any payments that need to be applied to open invoices? If the cron failed for whatever reason, it can take up to 6 hours for the task to be marked as crashed and re-try. Is it currently only "Apply Payments to Open Invoices?". Is there a "clear" option next to the task? Can you provide a screenshot of Settings > Company > Automation, showing the task? I don't recall seeing any trouble tickets. The forums are perfectly fine for support, but they are not as actively monitored as our ticket system, and they are public so there is less that we can do. It seems like your other issues were resolved through the forums though. I don't see how the failure for loose payments to be applied to invoices would cause loss of business. New orders would have payments applied directly to invoices.

A new Centovacast module is available, but it's an early alpha. To install, download the attached centovacast.zip and unzip the file. Upload the centovacast directory to ~/components/modules/ and go to Settings > Company > Modules to install it. centovacast.zip Please give it a spin and give us your feedback. Here's a sample welcome email you can use for your Package:

It'll work on Windows. Here's an example of setting up a scheduled task in Windows to run the cron for Drupal. https://www.drupal.org/docs/7/setting-up-cron-for-drupal/configuring-cron-jobs-with-windows You'd just change the path to be that which you mentioned (https://sub.domain.com/cron/?cron_key=PUT_HER)

Unlocked. Any feature requests are best to be at https://requests.blesta.com, so it's ok with me if it's a duplicate so long as it's not in the same place. Regarding this feature, the support system does not support HTML, but it does support Markdown. So, we would be open to adding a markdown editor like stackedit.io, and we already have a task for this.. see https://dev.blesta.com/browse/CORE-2299

It sounds like you may have pending service changes that are unable to be processed for whatever reason. Take a look in your service_changes table. You may need to remove any items that are in here as they are unable to be processed. If you do so, be sure to back it all up first.

I would highly recommend not modifying existing tables. Plugins are designed to be able to create or modify their own tables, but modifying core tables could prove very problematic. In terms of tying into existing functionality, you might look at Event Handlers also known as hooks. Tying into the Invoices.add event, would allow you to edit an invoice right after it's created and add additional line items or make other modifications to it before it's emailed out. If you need to display additional information on an invoice that's not there now, or can't be added by modifying an existing invoice, you should create your own tables for this data. It then may be necessary to create a custom invoice template that one could use instead of the default, that could fetch the information from those new tables for display.

Here's a basic rundown of importing cPanel accounts manually https://docs.blesta.com/display/user/cPanel#cPanel-ImportingcPanelAccounts

Yes, when you create your Packages, check the "Enable Pro rata" option, and set the Pro rata Day, and Pro rata Cutoff Day.

So this only happens on the order form, not if clients are making a payment from within the client area. This file is responsible: ~/plugins/order/views/templates/wizard/javascript/checkout_complete.js (If you're not using wizard the path may be different. Here's the code: $(document).ready(function() { $(".payment_buttons form").first().delay(5000).queue(function() { $(this).submit(); }); }); You can change the delay (5 seconds) by increasing the value in milliseconds. 5000 can be changed to 20000 and then it'll redirect after 20 seconds.