Paul

Are you running Blesta in a NAT or reverse proxy? It may be possible that their IP address is seen as your servers for this reason, but not sure why it would sometimes show the correct IP address.

Check your schedule under Settings > Company > Automation. If auto debit is set to run before invoice generation, then it will run before the invoice is generated and thus be unable to auto debit it for that same day.

The only other thing I can think of is that Auto Debit was enabled on the client profile, and that a payment account was set for auto debit. If the answer to both of these is yes, I'm not sure what the issue was unless there is a bug in here someplace.

The cron log seems to indicate that there was nothing to charge. On 12/23/13, was there an invoice due on 12/23/13? When did you manually process it? If the auto debit cron runs after your invoice cron, then it wouldn't try until the next day.

If the payment account was created and then Stripe was changed and "Store card information offsite" was checked or unchecked then the payment account *may* need to be recreated. Also, check the auto debit cron task log under Tools > Logs > Cron to see if there are any errors with processing auto debit. It should display which invoices should be charged and whether they were successful.

Happy New Year! I have a feeling it's going to be a great year!

It was caching it, thanks. Probably should redirect blesta.* to blesta.com, will try to do that soon. Thanks for the heads up.

Hi Larry, Since Blesta didn't create the VPS, it's probably missing the solusvm_vserver_id key in the service_fields table. Search the service_fields for the service_id for this particular service. Among the results should be a key that matches solusvm_vserver_id with a value that matches the id for the server in solusvm. If this row is missing, or wrong, you can add it or update it in MySQL, respectively.

Make sure that the email address as configured in Blesta for your PayPal gateway is the same email address that is set as the "default" email address in PayPal. If they don't match, Blesta will not record the payment.

Yes major.minor.patch ie 3.0.8 So the next minor release is 3.1, then 3.2. Betas are designated like this: 3.1.0-b1 (Or a1 for an alpha 1 release) 3.1 stable will be released in January within the next couple weeks most likely, and then it will be full steam on 3.2.

Tell me you're not a spammer.

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.

Alright, so I know that 3.1 isn't even officially released yet, and the guys are focused on that.. but I've been cranking on markup for 3.2. It's a work in progress, but I think it's coming along nicely, and I thought I'd share and get your feedback. Here's 3 screenshots.. they were taken on.. 1. Macbook Pro 2. iPad Mini Retina 3. iPhone 4s This is just the dashboard, which has the most going on, but pretty much all the client area pages have been created. Bootstrap 3. Tried to stick pretty closely to the current design with improvements wherever possible. So, what do you think?

lol, it's been in there a while, apparently. We need to get the client area conversion to bootstrap done first. Should allow for more flexibility with module management features, and result in a better Onapp implementation.

Thanks Steve! Merry Christmas!

Merry Christmas guys!

Interesting, anyone else experience this on step 2? What module are you using?

The configurable options feature is free, and included in Blesta 3.1 assuming you have support & updates (Everyone on v3 does until at least Aug 14, 2014). With configurable options however, you can charge your customers more for certain options. For example, if you're selling dedicated servers you can have a drop down for the number of IP addresses.. Extra IPs -None- 2 - $3 3 - $5 4 - $6 Etc..

What page/URL are you seeing this error? You can copy/paste the URL and just remove your domain

Hi Swerlo, v3 is a complete rewrite and shares no code in common with previous releases. As such, it is basically new software and it's only been out for 4 months. Regarding feature requests, as you know, we have to prioritize development based on demand. When people request features they are considered, accepted rejected or put on hold, prioritized, and implemented. The core of Blesta will never do everything for everyone -- it would become bloatware, so we have to be thoughtful about the features we implement. The extension system should cover most other cases. I happen to like your feature request, and I think it would be beneficial to the majority. Being that CORE-547 is a similar feature, this can be implemented as part of that task. I've added a note to the task so that fields may be selected for display as read-only within the client area. Thanks

Yeah, I noted that it should work in addition to maxmind, not one or the other.

There is already a task, CORE-547 to hide optional fields from the client area and order pages. It is tentatively scheduled for 3.2, but may be pushed back. I'm not sure if this is exactly what you're asking for though.. this would allow you to set, from optional fields, which ones not to display at all. Are you wanting the fields rather to be displayed only as read-only? Feature requests aren't always answered right away, sometimes we purposely let them run on to gauge support. As we plan future releases, we also revisit the feature request threads on the forums.

CORE-935, thanks for the suggestion! No ETA at the moment, but it's in our system.

That's right, a conversion of the client area and order forms is planned for 3.2. It's undetermined if this initial release will be responsive or not. It may be, or it may be in a subsequent release.

The plan is for a 3.1 beta starting at the end of this week. Betas are open to all direct customers.