Leaderboard

For those comfortable editing their css I have in the mean time done this with: .row .col-md-3 .list-group a[href='/billing/client/main/invoicemethod/'] { display: none; } If you want to hide the auto payment box too you can just change it to: .row .col-md-3 .list-group a[href='/billing/client/main/invoicemethod/'], .row .col-md-3 .list-group a[href='/billing/client/accounts/'] { display: none; } Note: If your Blesta installation is not installed into the billing directory, you will need to change the word "billing" to the name of your installed directory.

A few other applications have a nifty ability to automatically merge template changes which are required for Blesta updates. It would be awesome if Blesta had something similar. I use XenForo and their implentation of such a system is amazing and has always worked flawlessly for me through several major updates with lots of template changes even. https://xenforo.com/community/threads/template-merging-and-history.48846/

I will be showing you a new theme I am working on, I hope this time I can finish it and deliver it to the community.

Just FYI, this field can be disabled in the next release, 3.4 per CORE-547 and CORE-1443

Order #'s are listed in Blesta under Billing > Overview as part of the Orders Widget. If you don't see an "Orders" widget, click "Manage Widgets" on the left, and drag it from the right to the left in the modal box to add it.

Something like the following may work (untested): { "hostname":{ "valid":{ "rule":"isEmpty", "negate":true, "message":"Hostname must not be empty" } }, "configoptions[client_id]":{ "valid":{ "rule":["matches","/^[0-9]{4}$/"], "message":"Please enter a four digit number for the referring client." } } } You will need to change the name of the config option ("configoptions[client_id]") field to the one that you created.

The SolusVM module hasn't changed since v3.2.1. If your SolusVM fields do not load for an old package, it may be that that old package is no longer referencing a valid module row (server). i.e. if you updated the service's package to change the "SolusVM Master Server" to something different, or that server is no longer valid. There could also be a separate error being generated that is causing the fields to not load. You could take a look at the web server logs for more information on any errors. Or you can enable error reporting in Blesta, and if you're familiar with developer tools in your web browser, you can check the AJAX requests on that page to view the response for when those fields were requested, which likely contains more information on the error. To enable error reporting, which will allow errors to appear in the interface, you can update /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1); ...and change it back when you're done.

Ok, I think your support department/ticket issue is related to a transaction lock, which may be because of the missing pricing option in [1] above. The first step would be to fix that and try a new fresh import, things will probably look much better at that point. The importer is trying to import a null price, which means that price is likely null in whmcs and Blesta requires a value. I'll ask Cody or Tyson to take a look at the error and see if they can provide instructions for identifying the record that's causing the issue.

The template that displays that information is used in several places. I think it makes sense that it displays "Contact Information" since the field above it asks whether you want to "Copy Contact Information From" another contact anyway. But if you want to change it, you can update the language definition in the client_contacts file to update it in every location.

The issue appears to be dependant on the timezone. While your fix may work for you, it would be incorrect for other timezones where it may produce invalid results into the past, and so it should not be used either. e.g. from 2014-01-01 00:00:00 to 2013-12-31 23:59:59 Added as CORE-1487 for v3.3.2.

the actual code is public function getAction($plugin_id, $action) { $action = $this->Record->select(array("plugin_id", "action", "uri", "name"))-> from("plugin_actions")->where("plugin_id", "=", $plugin_id)-> where("action", "=", $action)->fetch(); if ($action) { if ($action->options) $action->options = unserialize($action->options); } return $action; } this code always return error about indefined options , because is not included inthe query result . also the $action var is used as var and as result var . the correct one is public function getAction($plugin_id, $action) { $query= $this->Record->select(array("plugin_id", "action", "uri", "name", "options"))-> from("plugin_actions")->where("plugin_id", "=", $plugin_id)-> where("action", "=", $action)->fetch(); if ($query) { if ($query->options) $query->options = unserialize($query->options); } return $query; }

Thanks. This has been fixed in CORE-1486 for v3.3.2.

You can do so with the CSS toolkit so you don't need to keep editing it

true, I wasn't thinking about unlimited for X amount of time. +won

It just means Unlimited uses for a certain time, we do that too Like Black Friday which is coming up soon. +1 maybe a check box.

I was a bit confused by all the stuff happening in that thread as well, but the way I understood it was that in it's current state, the Stripe Module leaves the onus of PCI compliance on you, because it sends card information to the server to be tokenized before passing it along to stripe (since it doesn't use stripe.js). There is a fix/workaround item in progress, looks like it's assigned to 3.5. Core-1085 Blesta does not store the credit card details, but it does send them to the server to be tokenized on the initial charge. The fact that it has to send the card details to the server to tokenize them is the step that requires your server to be PCI Compliant, whereas if we could use stripe.js, you wouldn't have to worry about PCI compliance because stripe would be responsible for it since the card info would never touch the Blesta server. So, once the above task is completed, using stripe.js will be possible.

Hmmmmm ok. I thought it was direct as that's what this post indicated: http://www.blesta.com/forums/index.php?/topic/2055-stripe-payment-gateway-pci-compliance/page-4#entry19419

you have added the code after the installation of the plugin ? try uninstall and then re-install the plugin .. you can also check the plugins_actions table to see if the action has been added to database .

The checkout method doesn't send data directly to Stripe, it sends it to Blesta and then to Stripe. The stripe.js method sends it directly from the users's browser to Stripe.

That is just way too simple and effective, which is probably why I didn't think of it . Good to hear that at least one app is on the way...

What kind of update are you looking for? As mentioned earlier in the thread, it's already been assigned as a future feature: Core-1387, looks like it's scheduled for version 3.5, but that could always change.

Blesta uses the Checkout method. There are some other threads about Stripe and PCI compliance, you might want to search for them.

Just made my day ! Really looking forward to seeing the result.

Totally forgot about this, Fixed. You can find your new IP in the control panel

I found the following http://www.sivann.gr/software/itdb/ http://codecanyon.net/item/inventory-manager-v11/8240513

Packages > Group > Create > Standard type. Packages > Browse > Create > Make 3 packages called Bronze, Silver, Gold. Then do Packages > Group > Create > Addon type > Select the Standard group Packages > Browse > Create > Make extra packages called (Web development, etc)