Alk

Without config/blesta.php, nothing that is encrypted in the database will be recoverable. Blesta's database backup backs up the database only. You should at a minimum store your config/blesta.php config file on your computer. We recommend backing up all files and the database prior to any upgrade/downgrade but having a normal backup procedure for your files, and uploads directory is recommended as well.

Ah, the config/blesta.php file also; I hadn't realised that was also necessary, but I can see why. I'm trying to cover all bases for a disaster recovery. Thank you for your response.

Hi Paul,
 
Thank you very much for your help. Due to an unrelated issue, my webhost has moved my account to another server. Consequently, the SFTP backup settings are now saving correctly and I have successfully sent a backup offsite. So it must have been something about the server that my account was previously on (both servers appear to be setup very similarly with CageFS). Really odd, but I am relived that it is now working.
 
Thanks for everyone's help and sorry to have wasted your time as this is not a bug.

Glad you got up and running I'll close this for you now as it's not a bug .

Hi Paul,
 
Thank you very much for your help. Due to an unrelated issue, my webhost has moved my account to another server. Consequently, the SFTP backup settings are now saving correctly and I have successfully sent a backup offsite. So it must have been something about the server that my account was previously on (both servers appear to be setup very similarly with CageFS). Really odd, but I am relived that it is now working.
 
Thanks for everyone's help and sorry to have wasted your time as this is not a bug.

sometimes i feel you are against any complialt to blesta even if is true .
 
we know the stuff is busy in coding new feature and making big changes , but answering here or in tickets should be regular and quick as soos as possible , even if the feature/request will not implemented , but if the client/visitor see a anwser that give a good sensation about the active staff .

Would a moderator be able to move this topic to the feature requests forum please?
 
I've been playing around with the buttons again, now that the order form page has been updated in 3.2. So now I'm using the following buttons:
 

https://www.paypalobjects.com/webstatic/en_US/btn/btn_paynow_cc_144x47.png
 

https://www.paypalobjects.com/webstatic/en_US/btn/btn_subscribe_cc_147x47.png
 
Which results in the order form looking like:

 
For comparison, it originally looked like:

 
But what (in my opinion) previously looked so unprofessional was the pay invoice page:

 
Now it looks like:

(all the buttons match and line up)
 
All I did was change the URLs to the images in /components/gateways/nonmerchant/paypal_payments_standard/views/default/process.pdt. Would Blesta consider making these buttons standard please, as my alternative PayPal buttons are neater and more helpful to users? 

Most of the email templates don't include attachments, so you're correct that the "Include any attachments" checkbox would have no noticable effect for those email templates. However, the setting is available if any templates are added attachments in the future, or if plugins send any themselves.
 
The task, CORE-1274, adds tags that can be used in the Ticket Updated email template to provide a way for you to determine whether the ticket, or the current ticket reply, has any attachments. "Attachments" refers to attachments to the ticket, not to the email. The support email does not include attachments because they may contain sensitive information.

Thank you all, I did understand it this way.

CORE-1567 thanks!

As you know, there is already an "order received (mobile)" email template available and this is the email that I receive. I propose that the unique link is available universally, to both the "order received" and "order received (mobile)" email template because it would be so much easier to approve an order with one click whatever device you are on (but particularly mobiles!).

A new email template will be in v3.4 that will be used to send these non-merchant gateway payment receipts.

CORE-1362 fixed in 3.3.0-b2.

Thanks PauloV. Really sorry but I never updated this thread to say that I got to the bottom of my error; after a significant number of hours I found a bug, which I worked with the blesta team to resolve a few releases ago.

Thanks PauloV. Really sorry but I never updated this thread to say that I got to the bottom of my error; after a significant number of hours I found a bug, which I worked with the blesta team to resolve a few releases ago.

Thanks PauloV. Really sorry but I never updated this thread to say that I got to the bottom of my error; after a significant number of hours I found a bug, which I worked with the blesta team to resolve a few releases ago.

Anyone using resell.biz to register domain their customer's domain names, and they want to add domain privacy to the order, they can do it by using the "options" feature.
Goto 'packages' 'options'
Create a package group named: Domain Privacy
Create a package option named: Domain Privacy
In the 'Value' box add: purchase-privacy=true
Add the option to your group and save.
 
Finally, update the domain package by adding the Domain Privacy Group under 'configurable options'
Done  
When the customer checks the domain privacy option box during the order process an arrow will show up on the order form under the domain name that is being ordered. It will have the additional price for privacy.

Hi Mike,
 
Thank you very much for checking this out for me; I have finally got to the bottom of the issue.
I had to recreate my "Domains" package group and all the LogicBoxes packages. Naturally, I then had to re-add the newly created "working" LogicBoxes' packages to my clients. Now that I have done all of this, the order form works correctly and the LogicBoxes orderids have been fetched, so now the domain details are showing (they weren't before). Fingers crossed that this will also mean that the domains will now start to auto-renew as well! Thanks! 

For information folks, charging for Privacy protection will start on 6th August 2014: http://cdn.resellerclub.com/mailers/rc/uk-paid-privacy-protect-now-live-30-07-14.html The API changes are listed in the link.

I want to add some further information to this bug report as this needs to be recognised as an issue by Blesta.
 
So if you want to use an order form for domain purchases only, you setup the order form as per the attached screenshot. IE. You set a "Domain package group", but not any other "package groups".
If you also select to use any of the wizard or ajax based order form templates (the standard template doesn't have this issue) you will be presented with a blank page, prompting you to "make a package selection" - as illustrated in the screencast.
Furthermore, as illustrated in the screencast, whilst with the "wizard slider" and "wizard boxes" templates you are presented with a blank page prompting to "make a package selection", you still get the "show cart" button to allow you to continue through checkout. However, with the "ajax boxes" and "ajax slider" templates, you don't get the "show cart" button, so you are completely stumped and cannot continue checkout!
 
At the moment, the only workaround is to use the Standard order form template if you are only selling domains.
 
I have to also point out that it is necessary to have a separate order form for customers who only want to order a domain name because if you attempt to only use one wizard or ajax based order form for all services which you offer (ie. an order form which has a domain package group set + other package groups) the customer cannot only order a domain name without being forced into having to purchase another package with the domain name due to the way that the wizard and ajax based order form templates work. The only way to prevent this is to use the standard order form template. I have opened a feature request for this issue here: http://www.blesta.com/forums/index.php?/topic/2984-do-not-pre-select-a-package-on-order-form/

I want to add some further information to this bug report as this needs to be recognised as an issue by Blesta.
 
So if you want to use an order form for domain purchases only, you setup the order form as per the attached screenshot. IE. You set a "Domain package group", but not any other "package groups".
If you also select to use any of the wizard or ajax based order form templates (the standard template doesn't have this issue) you will be presented with a blank page, prompting you to "make a package selection" - as illustrated in the screencast.
Furthermore, as illustrated in the screencast, whilst with the "wizard slider" and "wizard boxes" templates you are presented with a blank page prompting to "make a package selection", you still get the "show cart" button to allow you to continue through checkout. However, with the "ajax boxes" and "ajax slider" templates, you don't get the "show cart" button, so you are completely stumped and cannot continue checkout!
 
At the moment, the only workaround is to use the Standard order form template if you are only selling domains.
 
I have to also point out that it is necessary to have a separate order form for customers who only want to order a domain name because if you attempt to only use one wizard or ajax based order form for all services which you offer (ie. an order form which has a domain package group set + other package groups) the customer cannot only order a domain name without being forced into having to purchase another package with the domain name due to the way that the wizard and ajax based order form templates work. The only way to prevent this is to use the standard order form template. I have opened a feature request for this issue here: http://www.blesta.com/forums/index.php?/topic/2984-do-not-pre-select-a-package-on-order-form/

Ah, thanks Mike! I searched the forums for a report of this bug already, but forgot to search the dev tracker for this one. Apologies.

I appreciate your input Cody. I agree that PayPal's buttons are not the most aesthetically pleasing! Paulo's suggestion was also to do away with the graphics, so if this topic were to be moved to a feature request, perhaps others from the community could also give their feedback? To be honest, it may well be the best way to go, thereby covering all gateways.
 
However, my opinion is that it doesn't matter that it doesn't mention "PayPal" on the buttons because the user has already chosen, on the previous screen, to pay with PayPal (they are the official PayPal buttons).

I'm in agreement with everyone, the label "date renews" (and its variants) is incredibly confusing for end users, including ourselves. Now that the Blesta team have explained how it works it all makes perfect sense and is good design, but as PauloV said, those not in the know will only get confused. I'm going to take another approach. As Cody has explained that this is the date when the next invoice is due, I'm going to change the language files to say "Next due date" (like competitors do in their control panels). I think that the label is the issue here.
Unfortunately it is quite a few files to alter:
\language\en_us\admin_billing.php \language\en_us\admin_clients.php \language\en_us\admin_search.php \language\en_us\client_services.php \plugins\order\language\en_us\admin_main.php \language\en_us\services.php

Thanks, this has been resolved in CORE-1298 for v3.2.1.