Jump to content

velaware

Alpha Developers
  • Posts

    346
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by velaware

  1. When creating an email template and doing something like this:

     

    <table>

    {% for item in items %}

    <tr><td>{item.key}</td></tr>

    {% endfor %}

    </table>

     

    After saving or switching from source to preview, it morphs it to this:

     

    {% for item in items %}

    <table><td><td>{item.key}</td></tr></table>

    [% endfor %}

  2. previously, I have to enter the hostname to the primary domain, but the invoice was written http://domian.com/client/pay/x. when it should http://domian.com /clients/client/pay/x (clients is the subdirectory where I installed blesta)

    I had to enter the subdirectory manually in the email templates.  Seems Blesta doesn't like to play nice with the subdirectory method of installing (which I think they should fix).  Either that, or create a redirect for subdomain.domain.com/client/x to send the user to domain.com/clients/client/pay/x.  This is easy based on the web server you use.

  3. Didn't think about that, I thought a module for a like "download manager" however it has a paypal or something button which after payment returns to the new download manager with a button to download.

    It'd be interesting to modify the download manager plugin to do that, but it would require a bit of a trick.  Might do that though once I get some free time.

  4.  

    Eric is already developing some modules for me :)
    I thought it can be done using the built-in modules.
    Thanks for reply.

     

    Meet people everywhere. :D

     

    As for this being done, not sure.  What you could do is use the license manager once it gets released to the public (I think its only for devs right now?).  I don't think there's any sort of ACL or something for the downloads area, but with the manager you'll be able to have people not be able to use something w/o a valid license.  Its what I do for a few of my works.

  5. While doing work for a client, one of the requests was to make it so the SolusVM module properly (un)suspends a virtual server, instead of shutting down/starting up (which the client could then easily reverse if they wanted via SolusVM CP).  The fix to this is actually pretty simple, so I thought I'd share it!

     

    This assumes you're running Blesta v3.1.1 with no changes made to the module:

     

    Open /path/to/blesta/components/module/solusvm/solusvm.php in your favorite text editor, and look for line 482:

    $this->log($row->meta->host . "|vserver-shutdown", serialize($params), "input", true);
    $response = $this->parseResponse($server_api->shutdown($params), $row);
    

    Now, here we want to edit both references of "shutdown" to "suspend" like so:

    $this->log($row->meta->host . "|vserver-suspend", serialize($params), "input", true);
    $response = $this->parseResponse($server_api->suspend($params), $row);
    

    To unsuspend it we just use go to the unsuspendService function and look for this (around #526):

    $this->log($row->meta->host . "|vserver-boot", serialize($params), "input", true);
    $response = $this->parseResponse($server_api->boot($params), $row);
    

    We want to replace "boot" with "unsuspend":

    $this->log($row->meta->host . "|vserver-unsuspend", serialize($params), "input", true);
    $response = $this->parseResponse($server_api->unsuspend($params), $row);
    

    There you have it.  Suspendable SolusVM containers that clients can't just start back up!

  6. Not sure if bug, or its done by cron.  But, when I create an invoice, even if I have email checked under "Invoice Delievery" it doesn't send (on the client's page it says "unsent").  I have to manually check the invoice and click "Deliever" on the client's profile.

     

    v3.1.1 of Blesta

  7. Is it like this for instance:

     

    1 [hours] [5.00] [0.00] [0.00]

     

    On the order form because it's set to a hour it configures the order form to do:

     

    Number of hours: [ ] 

     

    So if I put in 24 there, it then invoices me 24 x 1 hour = 5.00 x 24 = 120.00

    Yeaup, pretty much.  Most people want an estimate and doing this through a package once you know at least a rough idea, this package saves a lot of headache.

  8. This is more a function of proration than package term. Nobody wants to get an invoice every hour.

     

    I think the way this would work is that you'd enter the hourly price in the package, after hourly billing is enabled through some option there. You'd still have a term of say 1 month, and the customer would be charged hourly rate * 24 * 30 for the month. If they cancel early, a prorata credit refund of the remaining hours could be made.

     

    EDIT: Alternatively, we do nothing different in the configuration, other than to display the pricing on the order form as hourly. So, you'd save the price for the full term, and it would be converted to show the hourly price during checkout.

     

    I always thought this was a bit of a marketing strategy. 25 cents an hour sounds a lot better than $180/mo.

    Well, here's the thought I had regarding this...(and you wouldn't get an invoice every hour)

     

    You create a package with an hourly term.  1 Hour = $15 for example.  Lets say this is for sysadmin work (there are some companies that do charge hourly for sysadmin).

     

    When you create a service, you specify how many hours will be allocated, and the service adjusts based on that.

     

    So, you send the invoice to the client, they pay for that many hours, boom.  Done.

     

    But, in some ways you are right that its a bit of a marketing strategy.   That's why companies may also charge $x/month or $0.00x/hour for cloud instances (Amazon, DigitalOcean, etc...do this).

     

    The idea is more so to accomendate people who don't do monthly work (like me, doing development and charge on the hour not a flat rate fee).  Granted, its up to the staff to make any adjustments, but this does have a viable use and is practical.

  9. Would you say that you can create a package with a monthly term, edit it, add the one time, and remove the monthly to get past this issue? If so, that may be the way around it until we get a fix out.

    That works.  Don't even need to add the one time, just change the type from monthly to one time and it'll edit just fine as well.

×
×
  • Create New...