Alk

If I have a signature that I want to add a blank line to at the beginning, ie: I can do this on the HTML signature, but when I put a blank line at the beginning on the Text signature, it is removed when I click on save. So to get 1 blank line to save, I have to enter 2 blank lines at the beginning on the text signature, ie: On the text signature I have to enter: To get this to save:

Resellerclub has just sent round an email saying: I'm just wondering how Blesta can best be used to cater for this change? any thoughts please? Thanks!

This bug is fixed in the latest 3.1.3 release. Thank you Blesta

I +1 this too as I currently have to check manually every month. Something to automate this would be very helpful.

To clarify; if you are trying to create a "one time" pricing term package (or attempting to add a "one time" pricing term to an existing package) you will hit the error from CORE-1056. Whereas the issue that we are both experiencing (and I'm speaking for SimWhite here but it sounds as though it's the same situation) is because the package is already existing from v3.0 and we are trying to edit it. I am using the cPanel module and I do not have to edit any fields in the package to have this error appear. So, I click to edit the package -> without changing any data -> click the Update package button -> receive the error. I have included screenshots of before and after. I hope that this is clearer.

Mike, have you tried removing the limit on the total number of accounts that the reseller can create? I am the only reseller on my VPS and I am successfully using my reseller account with Blesta. I don't have a limit on the total number of accounts that the reseller can create. Comparing my settings with yours, this is what else is different: dns: park allow the reseller to use all global packages allow creation of packages with parked domains allow creation of packages with unlimited bandwidth allow creation of packages with unlimited diskspace allow creation of packages with a dedicated ip view server information view server status resync ftp passwords super privs: Account Modification Bandwidth Limiting Modification Quota Modification

Yes, I cannot find the copy contact option either. Please would someone explain where it is?

Paul, I'm really sorry, but is it possible to please bring back this feature sooner than v3.3? http://dev.blesta.com/browse/CORE-621 It was one of the reasons why I bought Blesta...As a shared reseller, without the use of this feature you have no easy way of emailing your clients. I would also like to add a feature request to the plugin; as in v2.5, to be able to choose to email inactive/active clients, and different contact types. Thank you.

I'm not sure - you may need to investigate this further because according to SimWhite's original post, the fix for CORE-1056 has been installed already...

Mike is right. I've found the video which Paul did explaining it: http://videos.blesta.com/video/64763991

Yes, I also came across this issue the other day. So I have a package that I created in version 3.0. Like SimWhite, it is set for "one time". I don't even edit the package, click the update button and receive the same error message. The term box is greyed out because it is "one time" and I therefore assume that this is were the issue is.

Perhaps I'll have to do some testing to find out, as in my scenario, the services would all be recurring, just at different terms. Eg. the domain would expire in 2 years, the hosting in 1 year. To clarify if my Blesta is behaving as intended; it is not showing the paypal subscribe button on checkout of a recurring web hosting service? only the pay now button. If I exit out of the checkout process without paying, and go to pay via the client portal, I get the pay now and subscribe buttons.

OK, thanks for clarifying. It is good to know this as I therefore conclude that customers will have to be careful what they paypal subscribe to. I assume that they could subscribe to the total amount on the invoice and the recurring payment amount would then be incorrect (due to the different terms). Or is there a method to prevent this from occurring?

On renewal, does Blesta send separate invoices for each service? or if multiple services are due for renewal on the same date (regardless of whether some are being renewed for 3 months and others for 1 year) they are all put together on one invoice?

Yeah, OK Paul that is an effective use for it as you say and that is a good process that I can adopt as well. Thank you.

I have a question regarding paypal subscriptions, which I'm afraid that I haven't been able to test myself, and so I wonder if someone could clarify for me please. I understand that when a client checks out and chooses "Paypal Standard payment" that they are only presented with the one time payment button and no option to paypal subscribe. This makes sense, in case there are multiple services on order with different expiry dates etc. However, how does Blesta handle the scenario when a client has a domain renewal for 2 years and a hosting renewal for 1 year, when they are both due for renewal on the same date? Does Blesta send separate invoices for each service, thereby the client is able to PayPal subscribe to each service individually? I hope that this makes sense - thanks!

What's proposed seems great. As version 3.3 is 2 major versions away, do you think that in the interim it would be sensible to remove the "generate password" button which is currently present in the Staff Portal? (given the aforementioned issue with it)

Excellent, that sounds great. Apologies for duplicating this issue.

Just picking up on this; is there any further news on the progress of this forthcoming feature please? Just to throw an idea out there; how about emailing the password to the client automatically (or with a checkbox option to choose to do this, which is pre-checked?) Assuming that most users will end up emailing the new password to the client anyway, unless it is done over the phone for security (hence the option). This will confirm to the client that their password has been reset and what it is now set to.

When going through checkout, having selected the offline payment method, the final "Almost there..." step states "to complete your order click the pay button below." however, as it is an offline payment method, there is no such pay button.

I was surprised to find that after upgrading from 3.0 to 3.1 I had to manually upgrade each individual plugin, module and payment gateway. I was surprised because I did not see this step mentioned in the written documentation (only the video now that I have looked at it) and secondly I do not recall that it was not mentioned as part of the web based upgrade process. So I have 3 feature requests please: To put this step as part of the written documentation To mention this step as part of the web based upgrade process To take this further and do an "upgrade all" button to upgrade all plugins, modules, payment gateways that it can in one go, and presenting a list of any leftovers that have to be done manually.

...and I know why I was having a problem now - It was me being silly. I created a new account for myself as part of the Blesta 3 install and I didn't spot that the account with permission to the support area was the account migrated from Blesta 2.5 (it had the same name, ie. my name, just a different email address). So the particular account I was using didn't have permissions after all - I was getting confused. Likewise, it was the migrated admin account from Blesta 2.5 that had the migrated tickets assigned to it which is why I didn't see them. lol Thanks again Mike - have a good night.

Ah OK - not too dissimilar from what I did originally. Well, based on your experience, I've uninstalled and reinstalled the plugin (I only had my test tickets to loose) and having set everything up again it is working as it should. It definitely seemed to be a staff permissions issue, so in hindsight I probably could have avoided this by removing my staff permissions and putting them back in place again. Thanks for your help Mike.

Yes I have thanks Mike - it's all ticked in those permissions. I've thought about reinstalling the plugin but thought it must be something I've not set. Perhaps I'll hold off doing this until one of the Blesta team see this thread as perhaps it's a bug after migrating from Blesta 2.5.

Hello, I have a few "test" support tickets which have been migrated from Blesta 2.5 and I have created a test ticket in Blesta 3. Although I can see the support tickets from within the specific Client's Portal, no tickets are listed in the staff portal. I'm unsure why this could be. Could someone point me in the right direction please? Thanks very much