John

Let me know what you think of this CORE-2222
 
It includes a provision for an additional functionality change whereby new customers will not have access to the client area until their order is approved. Having a 4th status makes this possible.

You're not losing your marbles. It's added as a "public note" on the invoice, which can be seen under the collapsible "Notes" section via the "Edit Invoice" UI within Blesta.

Blesta has some rate limiting built in, if you're using piping then it should not respond after, I believe the 5th email or so within a given period of time, which will kill the loop.
 
Don't you love it when someone signs up with an email address that goes to their support system, and then opens tickets?

I love the Active/Inactive/Fraud feature of Blesta, and it helps deal with fraud accounts. However, it's hard for us to use the inactive status because it will lock a user completely out of their account.
 
I would like to see something implemented where if a user is marked inactive, they basically get a read-only view of their account (past invoices, tickets and transactions) and nothing more. Maybe it can be a company wide setting of what actions they are able to do with an inactive account. The reason this would be necessary is because we are planning on integrating authentication for various systems into Blesta. We would like inactive clients to still be able to see a 'frozen' version of their account, but not access other resources, etc.
 
Additionally, a company wide option to allow the user to re-activate their account upon purchase of a new service would be good so that if someone leaves, they do not have to open a new account to come back.
 
Maybe a system to auto inactivate clients accounts who have no active services, open invoices, or open tickets would be a part of this as well?

Correct.

Good to know. Do you have to apply the 5.5 hotfix for it to be compatible with 5.6?
 
When I saw '5.5 hotfix' I just assumed 5.6 was not supported yet.
 
I was looking at the PHP site today and got a good laugh, because 5.6 is going to have support longer than 7.0 when it comes to security updates. As long as I can get it to work on 5.6 I will be one happy person 

5.6 is currently supported:
[root@server ~]# php -v PHP 5.6.23 (cli) (built: Jun 22 2016 08:56:52) Copyright (c) 1997-2016 The PHP Group Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies with the ionCube PHP Loader (enabled) + Intrusion Protection from ioncube24.com (unconfigured) v5.1.2, Copyright (c) 2002-2016, by ionCube Ltd. [root@server ~]# 7.0 the ioncube guys need to fix something in the beta first.

Testing should occur in a non-production environment with a trial or dev license Manually manipulating imported data can be done directly in the database, if you know what you're doing. This doesn't exist in Blesta as a feature, because it's not a normal function of the application. Someone could certainly create a plugin to allow invoices to be wiped out, but many localities do not allow this kind of behavior, so Blesta doesn't support it.

Awesome to see that this has been completed. Thank you!

I don't think Blesta has a module for ipay88. You could either write the module yourself, contact ipay88 and see if they would write it, or find a Blesta developer who could write it for you.

this can be done with a simple plugin ......
 
please remind me after ~20 days , i will code it for you free

Blesta: Janitor
Small Blesta plugin to automate cleaning of abandoned orders, invoices, and services.
 
Installation
Download the latest release version from our releases and then simply upload the janitor folder to ~/plugins directory on your Blesta installation.
 
How it Works:
Janitor creates two cron entries which can be configured both by the cron settings and by the direct plugin settings. All of the plugin’s settings are based on the time the order was created. It may be important that you not cleanup and cancel at the same interval if you expect the orders to be marked as cancelled for any amount of time.
 
Both cron tasks will never cleanup any orders or services which meeting the following criteria:
 
The order’s invoice has any amount paid towards it.
The order’s service is active or already cancelled.
The order’s invoice is completely paid and is already closed (database: invoices.invoice_date_closed)
Cron Task: Cancel Abandoned Orders
This task is designed to strictly check for open orders which have never had any payments attached to them. First, the task will cancel the order and then next, it will void the invoice with a message as described in the language file. This cron task will also cancel any services attached to the order. This part of the cron intentionally leaves orders, invoices, and services in the database, in the possible event of this data being used by sales automation, etc.
 
Cleanup Order Database
This task is designed to completely delete all related database entries related to the order. It will remove the orders database entry, the order_services entry, and provides you the option to either leave the services as marked cancelled, or completely delete the service from the database via the plugins options. Only canceled services will be deleted if this option is set. If the service on this task is any other status than canceled, as set in the ‘Cancel Abandoned Orders’ cron task, it will ignore the service entirely.
 
Download: https://github.com/nodecraft/janitor/releases
Issues/feature requests: https://github.com/nodecraft/janitor/issues

There's 2 or 3 that actually need to get done for beta. We're working on it, will be done soon. Updating minPHP and a couple other tasks were really involved, and required some refactoring and creation of new libraries. So, taking longer than expected, but almost there

We will be deploying a new server with a new website in the v4.0 timeline and forcing HTTPS for all connections. It's an issue currently with the existing website, and the current server. Soon

It's possible to accept ACH payments using Stripe
 
https://support.stripe.com/questions/accepting-ach-payments-with-stripe
https://stripe.com/docs/api#bank_accounts
 
Has anyone extended the Stripe gateway to do this?

It would be nice to have a notification if someone attempts to login but cancels at the two factor auth prompt. Right now I believe that there is no way of knowing if someone abandons the login process at the two factor auth page.

It would be nice to use blesta for SSO.
 
This way users can have the same login for blesta as they do other modules. In my case, it would be nice to share login for multicraft.

i agree with you in this . personally i can't switch to v3 until now just for 3 reason
-Domain Management
-Multilanguages
-Hosting Order Form
i know v3 is better than v2.5 , but i can't move from system that i have adapted it to my use (v2.5) , to a new one than i need wait fix's or spend mounth for adding and customizing . time is matter here .

Lets face the fact Blesta's domain management is TOTAL CRAP.. WHMCS and Clientexec do it way better in every way.
 
Blesta does NOT have a proper domain offering, period. seems to be that its just not a priority.
 
Domains are totally unique to generic products and should be treaded as such.
 
For webhosters, domains are part of hosting, the most important part.
  The enom module for Blesta is 10 years behind that of WHMCS..currently we have the bare minimal basics.
  What if one wants to only sell a domain ? Does not appear blesta support domain only products.  
Domain Transfers ?
 
Renew pricing ? Allot of domain renewals cost more than the initial registration fee
 
Name spinning ?
 
Importing and sync of prices from enom & namecheap ?
 
Importing and sync of TLD's and new TLD's from enom & namecheap ?
 
What about .co.uk that requires a 90day before expire renew ?
 
Direct managment of the domain hosted on the registrars nameserver ?
 
Proper whois lookup or usage of dig to check if non api domains are registered/available ?
 
A domain email module, where domain orders are emailed, still does whois checking for availability. Some tld's are still stuck in 1970.
 
Domain availability widget ?
 
^^ BLESTA FAILS FOR ALL OF THE ABOVE
 
---
 
I challenge Blesta to make a billing brawl using domain management and include enom's module...
   
btw if you want a reseller enom account, or access to the enom api sandbox , contact me and ill sort you out with an account.

Hello to all
I dont like to point to outhers but look at WHMCS, ClientExec, Hostbill or even Ubersmith, all work this way
Signature shows by default,
If you add an KB link or predifined responde, it shows at the beginning befor signature, and if you focus the cursor for exemple in the midlle of the Ticket it adds the predefined response and/or KB link in the focus position.
This is really easy to implement with some JavaScript and/or Jquery
I have alredy talk this in the past and if Im rong I have also add the quick solution. I will tey to post the solution here tomorow to add to core
Regards,
PV

+1 to be the default scenario .
 
default answer
 
signature

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?

It would be great if Blesta could support paypal billing agreements. This way, we can drop paypal subscriptions. If someone downgrades, upgrades, adds a service, etc, you need to cancel the subscription, and have the customer set it back up again. 
 
It's a very tedious process, especially when there's something simpler available with Paypal. The goal is the least amount of work a customer has to do, the better. Customers want things to just *work* and not have to perform billing's job. 
 
Can we get this feature put in place in the near-ish future please? 

We do our best to ensure that public betas don't have critical bugs, but it can happen. The whole point of a beta is to open things up so others can find issues we couldn't find and provide feedback so that we can make adjustments in functionality. We can't and won't recommend running a beta in production, but some people do it.
 
It's looking like we probably won't need a beta 6. Final release imminent (In by best robotic voice). 

as the title , add a option to allow admins to reorder the widget in the clients dashboard , that way we can order wich first and wich last from the widget available to clients .