Jump to content

MemoryX2

Members
  • Posts

    538
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by MemoryX2

  1. It would be great if invoices would list where a client has made partial payments. 

     

    I realize that when logged int you can see, but it would be really helpful if the invoice would update after payments have been applied and reflect the new amount that is due. That way when it's emailed out it would show updated amount due.

  2. I am occasionally getting infinite ticket loops where I will have like 15,000± tickets created. I need at way / suggestions to keep this from happening.

    More specific:

    Some of my departments do not require the client to be signed in to open a ticket.

    Some random person or bot will attempt to open a ticket with a fake email address.

    Ticket system opens ticket and sends update to fake email.

    Fake email doesn't exist so whatever server emails back to tell me that message could not be delivered to the sender.. Then it happens 15,000 emails.

    What can I do to prevent this from happening? I do not want to make my departments client only.

    Thanks!

  3. Yes it is because they are in their own group.

    Packages should be set into the same group and you should then get a list like this:

     

    monthlyprices.png

     

     

    Mike is right. Packages that are in the same group will appear for upgrades/downgrades.

     

     

     

     

     

    I would really like to see the ability to upgrade a package to a different group. This might should be a feature request..

     

    Here's why, I have hosting for business and hosting for individuals wanting to learn.. Sometimes an individual may want to upgrade to a business class hosting package. Currently I cannot do that very easily.

  4. If you did that you could only use the second route. You'd have to delete the first. Regardless, I would advise against it since it could cause conflicts with the default order plugin routes.

    Okay I won't do that then. Thank you!

  5. I'm not sure if you define how you manage your release cycles anywhere.

    Just some food for thought: The linux kernel used to be released in two branches, the odd decimal point was the beta/unstable version, and the even was production/stable version.

    It is entirely possible you could simply re-package the 3.1 branch of Blesta as the beta/unstable version, then focus on the 3.2 branch as the stable version.

    :-)

    +1 I love this idea!

  6. I'd love to include it in 3.1, but the majority of the work remains to integrate the markup into the existing templates, plugins, and modules. Hoping to get 3.2 out in record time after 3.1, we're definitely going to hit the ground running. Some other features we're planning to add to 3.2 also.

    I was just joking, I know as much as anyone here about the amount of code changes required for it. :)

    I do think the faster it gets implemented the easier it'll be though. Example, all the new modules have to be changed but if it was already done they would have been built on bootstrap.

  7. I was able to duplicate this issue, and it looks like a couple minor issues worked together to cause it.

    • When you assign a server to a server group with the cPanel module, you need to assign it from right to left. If you don't assign a server, the server group uses none, and would be unusable with packages.

    • However, when you create a package, the "Server Group" field is initally "Any", which loads your cPanel server, and sets a valid value for the "cPanel Package" field. When you change to a specific "Server Group", the module options should reload using a server from that specific server group. But due to #1, if you do not have a server assigned to the group, a separate error occurs, preventing the AJAX request from completing. This, then, does not update the module option fields as it should, and so you are allowed to save your package with a "cPanel Package" unavailable to the server group. Because no module is actually being used (none are assigned to the group), you get a "No host defined" error when trying to create a service.

    This is now fixed in CORE-789 for v3.0.8.

    Will this fix carry over to 3.1.0 b2 as well?

    Thanks

  8. ACH works just like credit card payments. The only difference is the user enters their routing and account number instead of their credit card number and expiration date. Everything else is exactly the same.

     

    One thing to keep in mind, as a merchant, is that bank transfers take time to clear and it's not known by the payment processor whether sufficient funds exist prior to the payment being cleared. This means that the bank account number could be invalid, or insufficient funds available, etc.; however the transaction may still be processed successfully. With ACH you'll need to ensure that the funds have cleared before you approve an order.

     

     

    Thanks for the clarification on this. I have been sorta confused / wondering about it as well.

  9. Mostly just fix known issues, if possible, and as CubicWebs mentioned, add several of the features into our cPanel module over time. The cPanel Extended module is not released with Blesta.

     

     

    Cool cool. I haven't been using cPanel extended. I had initial problems with it. I can't wait to see all of this migrated to the Blesta module!

×
×
  • Create New...