Leaderboard

We are in a crunch to finish 3.5, and then we are focusing on the mass mailer. There has been overwhelming requests for it. Expect an initial release on the forums or on the marketplace after 3.5.

Yes i agree, but you forgot one thing, client details have to be always saved on the invoice and cannot ever be changed once the final invoice is generated

Blesta's work is heavily based on PHP. However, Python is my go-to language of choice. So, I decided to take Blesta's publicly available API SDK and convert it to Python using standard Python libraries (so no special pip commands needed!). Here's the link: https://github.com/anzenehansen/Blesta-Goodies/tree/master/api Right now it works just the same as the PHP version (I basically mirrored it to Python) but soon I plan on making it more Pythonic (hate that word but best way to describe it). I love ORM style solutions so that is one of the first things I'm going to turn it into. Its by default 755 if you git it, that was simply due to testing.

Dont compare what is incomparable Blesta = Great Script/Great Comunity/Great Forum Outhers (WHMCS/ClientExec/HostbillAPP) = No Comment Please Lisencecart dont make "smoke" and dont make "excuses", we all make bad decisions, its human, acept that @wanah: If you need help on making the changes you ask please PM me and I will do it for free, dont abandon Blesta "Boat" just yet Peace to all

Yes, I agree, and at least I did get my answer from the comunity. But just because a competitor is very bad, doesn't meen it's ok to not offer a good support. We aren't comparing with a competitor but between finishing our custom panel that's 60% finished or abandoning it to move to an existing solution. We tried the competitors pannel 3 years ago and got a refund. I tried besta about a year ago and decided it wasn't ready for our needs. Came back with high hopes but it's still unusable for our current legal requirements.

You should absolutely still use PDO, because who knows what will happen in the future.

I understand 3.0 was a complete rewrite, but this is a basic function, not luxury. If you have hundreds of clients, copying and pasting them into a mass email or using a 3rd-party app to mass email is clumsy and it is very necessary in our business to send out updates to all clients or clients within a certain product line. Just sayin'.

Thanks for your answer. I'll see where we are when/if blesta becomes compatible with vat registered EU companies. While the community seems very helpfull, no reply from official staff to presales questions in multiple days is quite worrying and makes we wonder if the support for paid customers would be reactive enough for us.

this feature need a core modification files. We are already requested this and still waiting thé implantation

LOL

That's probably why it will be here soon as the guys have that as their next major feature that I know of *don't tell anyone because they'll send the Blesta ninjas * haha

When the invoice delivery 'email' option is set for an invoice, the email is sent the next time the cron is run, and it is only delivered once. If sometime later the invoice is paid, then no other email is sent because it had already been delivered. We have a task scheduled to re-queue pro forma invoices for delivery again after payment (see CORE-1561), but it has not been completed yet.

Nice work! Just to anyone looking to implement this, it looks like it needs the associated Blesta plugin installed to work. Of course I discovered your work too late, after developing my own wrapper for python. It's pretty basic but also quite battle tested. You can feed in array args as a standard python dictionary and it outputs to the API in a format Blesta likes, e.g. {"vars": {"type": "cc", "account_id": "48"}, "client_id": 1} becomes [('vars[type]', 'cc'), ('client_id', 1), ('vars[account_id]', u'48')] It does have one external dependency though (the wonderful requests module).

I like your idea Paul, being able to force send the password reset from the admin client page would be preferable.

Personally I would prefer sending the password link. It's time sensitive and allows them to set their own password, which is preferable. Plus, sending a password in email is not secure. I would be open to this. I have had to, on several occasions opened up the client password reset page and entered a customers username to force one of these to them after they had trouble doing so on their own. Thoughts from anyone else?