10RUPTiV

Hey folks... I know that someone posted a bunch of notes on how he manage to make Support Manager Pro working with PHP 7 and Blesta 4... But I can't find them anymore... Anyone having some notes on that ? thanks

I already have the free membership but I can't find the download link....

How I can download again the Resend welcome email plugin... I have the free access and I already buy some plugin... but can't find how to download again...

Hey folks... Is it possible to upgrade from 3.6 to 4.2 directly or I will need to upgrade to 4.0, and 4.1 before ?

Just for fun, in your country if my invoice with you it's 100$ with 2% late fee, I just need to give you 102$ even after 24 months ?

There are no real do and don't about late fees here. We have some guideline and we can do almost anything we want inside this guideline. So for us, we will charge late fees every XX days with no taxes!

No idea about other solution as we never used anything else. Before Blesta, we used something that we code in-house! And also, in Quebec, late fees (percentage) are not taxable but fixed amount are! We can work with the version you already have but having a way to just generate another invoice each XX days with the option to not applied taxes!

Here, in Quebec (Canada) , the way it work it's: - A new invoice for each late fee (we can't modify an invoice when it's already sent to a client) - Late fee are applied on the original amount and can be also applied on all late fees (it's business discretion) - Here, most of the companies are billing late fees every 30 days and calculated every day if you want. So, for example, Invoice #1001 on January 1st 2016 with a total of 100.00$ being paid only on December 31 2016. Every 30 days, a late fees of 2% (that mean 2$ here) are created as a new invoice, for a total of 12 new invoices with each of them 2$. So client with invoice #1001 need to give us 124$ on the December 31!

Do you think in the next update it can be possible to charge a late fees every XX days until paid ? Let say, client paid invoice only after 91 days and I set it up for 30 days, I need to charge him a late fee every 30 days!

Looks like it's working with the latest open source package!

And what happen if invoice ID 520 is late 2 times, using create a new invoice... this will create a third invoice OR modify the second one ?

Not the same.. Just to make sure. Create new invoice = create a new invoice each time a late fees is applied and Add late fee to invoice = Create one new invoice and modify this one for each late fees ?

Just download the package again, even if it's written 1.20 in the dashboard, under Blesta, it's 1.30 now! But still having the same option

Will check, just downloaded it this morning

I don't see the option to create another invoice...

But when you are billing a late fee on an already late fee. How do you calculated it ? Using the next number of days in the settings? So If I choose 45 days, each 45 days you are billing a late fees ?

yeah I know that. But is it calculated on an annual or monthly basis

And the percentage is it monthly or annual based ?

is it possible to have more than 30 days also ?

I would need to double check with the team here but last time they told me we can't really customize everything in the admin area because some javascript are in the encoded files. If you are sure that in all encoded files you have nothing at all about some javascript for the admin area I will them know! Last time, if I'm right, we were working on some new stats and graph module in the admin area using bootstrap!

Paul, Blesta team, Maybe I'm wrong but, the "header" of blesta that contain all the javascript calls are in the encoded files ?

Hi Paulo, Any news for this plugin?

We modify the core also! That's why I'm asking the Blesta guy to make it official so we don't need to modify the core each time!

@PauloVany chance to add some new features?

Instead of having a multi-select... why not using the same approch we did... having a Group called "Global" and create all custom field under this group. This way, don't need to change anything in the database...and like I said, we are using that since a while here and it's working fine everywhere!