Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/28/2014 in all areas

  1. Download Link: https://dl.dropboxusercontent.com/u/9588244/HostPride/theme-blesta_pride_-_green_amethyst.json
    1 point
  2. Paul

    Quote System

    We are definitely going to add quotes, but it will not be in 3.3. Now may be a good time to get some feedback on the details. We've discussed this internally in some detail, and we've received quite a few requests for the feature but haven't heard much in the way of how you guys would like to see it work with any specificity. ie, when a client accepts a quote and it needs to be invoiced, what options should there be? Invoice all at once, invoice half to start?
    1 point
  3. Paul

    [Order Form] Change Language

    I've added this to CORE-1320. How did all of you beta testers not notice this in 3.2 betas?
    1 point
  4. Shyuan

    Blesta Pride - Adminarea

    I tried using that for a while now (since I created it yesterday upon your request), not bad really Thanks for your words, appreciate it.
    1 point
  5. Michael

    Blesta Pride - Adminarea

    That blue is the my favourite theme to date, it's got the cold feel to it which I like by cold the light blue is like ice will be using this on LC I believe.
    1 point
  6. Do you have any configurable options for daemon_id? See http://docs.blesta.com/display/user/Multicraft I recall running into a similar issue, and Tyson has made some changes to the module that have not been released on the forums, including but not limited to: CORE-1291 CORE-1292 I'd like to see what Tyson thinks after reviewing your report, but also wonder if you have an environment with multiple daemon's we can test in? Our Multicraft dev environment has only 1 daemon.
    1 point
  7. Paul

    Phone Number Issue

    What version of Blesta are you running? Or do you mean on our demo? This sounds like CORE-1240, which was fixed in 3.2.1. The demo has not yet been upgraded to 3.2.1.
    1 point
  8. Shyuan

    Support Manager Pro

    You mean this? http://www.blesta.com/forums/index.php?/topic/2001-support-manager-pro-tickets-delete-merge-spam-multiple-tickets/
    1 point
  9. There is an unofficial Virtualmerchant driver for Omnipay on github. No idea if that one actually works though. If you would like to try it, in short you would need to: Extract the .zip file above to your Blesta installation. Copy the files from the following github repo: https://github.com/zburke/omnipay-virtualmerchant to /vendors/omnipay/virtualmerchant Create a file /components/gateways/nonmerchant/virtualmerchant/virtualmerchant.php with the following contents to make it known to Blesta: <?php require_once(__DIR__."/../../lib/omnipay_nonmerchant_gateway.php"); class Virtualmerchant extends OmnipayNonmerchantGateway { protected $gwname = "VirtualMerchant"; } Backup your existing installation first.
    1 point
  10. Shyuan

    Blesta Pride - Adminarea

    Hehe, here you go, hope you like it. But let me know I wasn't allowed to attach the theme .json file here, so here you go: https://dl.dropboxusercontent.com/u/9588244/HostPride/theme-blue_gem.json
    1 point
  11. this feature will be in my next admin tools plugins .
    1 point
  12. electric

    Easier Order Forms

    It's difficult, because the developers surely want to create an order system that works with lots of different scenarios. However, for us, that vast majority of our customers have very very basic needs and so something that is extremely simple is necessary (critical). 1. Customer searches for domain name. 2. If new domain name, then choose the big "BUY NOW" button. If domain exists, then ask if they own it and want to transfer it. Otherwise, redisplay the search box, and also maybe show suggested names. Repeat as necessary until eventually they have selected a domain name, and we continue. 3. Show all the hosting plans and ask the customer to pick the one they want. Customer chooses the plan, and we continue. 4. Ask the customer what billing cycle they want for the hosting plan. (Monthly, bi-annual, yearly, etc) 5. Done. Press "Pay Now", and complete payment process. NOTES A. All of this should be on ONE page that uses basic AJAX to refresh, and has tally in the top-right area. Each "section" of the order process (domain selection, hosting selection, billing term selection) is displayed as a new area below the previous section. B. If you want to allow addons to be ordered during initial order process, then they can be displayed as part of step 3, depending on the plan they select. Again, keep it all on the same page. Simple is better. (We actually don't even allow customers to pick addons during their intial order, because it was way too confusing for them to see so much stuff they had no idea if they needed or not. It often prevented them from completing the order, which is against basic good business, right? So now, we simply let them pick their domain and hosting plan and that is it. AFTER they complete their order, they can then add addons from within their customer account client area. By then, they already paid, and are "invested" into things, as opposed to being overwhelmed and not completing the order. I hope that helps. If you are looking for some good examples, check out Hostbill's order pages. They have some amazing order screens and processes that we found to be very nice.
    1 point
×
×
  • Create New...