Paul

White pages do indicate errors, please turn error reporting on. To enable error reporting, edit /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1); Then try again, hopefully you'll be able to see any errors.

We do have plans to allow simpler integration with third parties like Facebook, Twitter, etc. If I recall, there is a change that must be done to the authentication system, and then such an integration would be possible via a plugin.

OpenSRS requires the Domain Manager, which requires Blesta 4.0 and PHP 5.4+. There's an OpenSRS module already, that seems to be regularly maintained, which I would recommend for the interim: http://www.blesta.com/forums/index.php?/topic/3344-opensrs-beta-107-relesed Chances are we will likely be focusing on the domain manager and domain registrar modules for 4.1. We know that better support for domains has been highly requested and long awaited, and are working on implementing the best solution.

Nobody is blaming you, we're just trying to help figure out the issue. If you open a ticket with your Blesta login details, I would be happy to take a look and see if I can determine the cause.

All usernames must be unique already. We do have a task planned for username recovery, see https://dev.blesta.com/browse/CORE-1094

This is resolved in 3.6.0 beta 1, and will be included in 3.6. Please see https://dev.blesta.com/browse/CORE-1516 For a hotfix, see http://www.blesta.com/forums/index.php?/topic/4761-cpanel-8-char-username-restriction/?p=35458

Great! We would appreciate your contributions. We absolutely will post a link to it here when ready. We are in the process of auditing the code, and will publish it when complete.

For reference, here's how USPS suggests addressing APO's FPO's and DPO's. https://www.usps.com/ship/apo-fpo-dpo.htm

Mujahed graciously signed over the rights of the code to us. We will be going through it to ensure we don't have any concerns over the code base and committing it to Github as a free module. This will include the Tasty cPanel, Tasty Interworx, and DigitalOcean modules. This will allow the community to also help maintain the modules and submit pull requests to us for new features, fixes, or improvements. We may also bring in some of the advanced management functionality into our official modules, and we *may* completely take over and fully support and maintain the digital ocean module.

Authorize.net is a merchant gateway, and the customer doesn't need to know and may not understand what that means. The customer just needs to make a credit card payment by selecting "Credit Card" under "New Payment Details". Selecting that option will prompt for a credit card number.

Upload the contents of the "blesta" directory from the zip file, this was changed from public_html and should be updated. Sorry! Chances are there may be a failed dependency, but you should know more once you access /install after uploading the files. Post any issues you have here and someone will help.

If your .htaccess was blank (in your Blesta install directory), copy the one from the Blesta zip file.

I believe it's 10 minutes, and I thought there was a setting in the config for it. However, there is a setting in the config for max failed attempts. Look in /config/blesta.php for.. Configure::set("Blesta.max_failed_login_attempts", 10); Change the value of 10 to say 100. I believe they will be able to login. Then, change it back to 10 or a suitable number.

Nice catch naja7host! Please see CORE-1829

When the scheduled cancellation cancels the service, it will be processed through the module. It works the same as if you schedule a service for cancellation manually, except the plugin does that. Voiding unpaid invoices that are not past due at the time the service is cancelled is planned, but it has nothing to do with this plugin. See CORE-1686

A staff and a client email when cancelled? (see Mike's feature request http://www.blesta.com/forums/index.php?/topic/5112-notice-service-cancellation-email/) Or, send an email to clients, and Staff can BCC subscribe to that if they want. Would the emails need to be different?

A plugin was developed that allows for services to have their packages reassigned to a package within a different package group. Typically services can only be upgraded/downgraded to another package in the same group, this allows it to be assigned to a package of a different group. The plugin will be included, but not installed by default, starting with 3.6.0 BETA 2. To install: Download reassign_pricing.zip Unzip, and upload the reassign_pricing directory to /plugins/ Go to Settings > Company > Plugins > Available and click to Install This will add a new item under "Account Actions" on a client profile page called "Reassign Pricing". Please report any issues or suggestions in the beta forums. Thanks!

I created CORE-1827 and mentioned that in http://www.blesta.com/forums/index.php?/topic/5090-stuck-in-payment-loop/ I think this is the same issue?

Unique is the way to go!

Here's the direct link to beta 1, you need to be logged in https://account.blesta.com/client/plugin/download_manager/client_main/download/77/blesta-3.6.0-b1.zip

I don't believe this has ever worked that way, but it should. I have created CORE-1827 to address this.

Packages are being reworked to simplify it further, and one of the things we are working on is making it so that you don't have to select a module at all.

A plugin was developed that can automatically cancel suspended services. It will be included, but not installed by default, starting with 3.6.0 BETA 2. To install: Download auto_cancel_1.0.1.zip Unzip, and upload the auto_cancel directory to /plugins/ Go to Settings > Company > Plugins > Available and click to Install Configure the plugin Please note that this plugin is DESTRUCTIVE. It will scheduled services that are suspended for cancellation. If you don't want to automatically cancel suspended services after a certain period of time, do not install this plugin. This plugin is only compatible with Blesta 3.6 and greater Please report any issues or suggestions in the beta forums. Thanks!

If you haven't already, try enabling error reporting and try running the cron again manually. (Remove the -q option in your command for the manual run) Then run: php /home/user/public_html/blesta/index.php cron Or, try running it manually under Settings > System > Automation. You may need to turn your cron off for 5 minutes before running it manually.

Did you run the upgrade? /admin/upgrade