Leaderboard

http://freeaccounts.partnersite.myorderbox.com/reseller.php?action=show_signupform But it's a sub reseller so I wouldn't make any test orders without sandbox on else you'd be charged.

If we implement anything with OAUTH it'll work with any system that supports an OAUTH server (not just google).

Added as CORE-687.

Try the following: open /app/models/gateway_manager.php and change (line 244): if (substr($file, 0, 1) != "." && is_dir(COMPONENTDIR . "gateways" . DS . $file . DS . $gateway)) { to: if (substr($gateway, 0, 1) != "." && is_dir(COMPONENTDIR . "gateways" . DS . $file . DS . $gateway)) {

Are you sure there are no hidden files or directories in there anyplace? Files that start with a "."? Typically "." refers to the current directory, and if that's the issue I would expect this to occur under Available Plugins, and Available Modules as well (does this happen there?). You can try editing components/gateways/gateways.php and adding this on line 40.. echo COMPONENTDIR . "gateways" . DS . $type . DS. $gw_file . DS . $gw_file . ".php<br>"; if (!Loader::load(COMPONENTDIR . "gateways" . DS . $type . DS. $gw_file . DS . $gw_file . ".php")) throw new Exception("Gateway '" . $gw_name . "' does not exist"); Then reload, and post what was output

We've got to start someplace. All these others will be coming, prior to a 4.0. This is a bit of a tangent, but related to time based billing. If manually creating an invoice, you can enter the hourly rate in the amount box, and enter a fractional or decimal quantity. For example, if you charge $95/hr and are billing an item for 3hrs and 50 minutes, you can enter 95 for the amount, and 3 50/60 for the quantity and it will do the math for you.

That's not really necessary, though it might make things clearer for those wondering if it's supported.

Thanks for the reminder, I've made a note.. we should get those added back in!

Were there any other details, like a stack trace? EDIT: Also, can you list all the files that are in your components/gateways/ and components/gateways/merchant/ and components/gateways/nonmerchant/ directories?

It is supported now. See http://docs.blesta.com/display/user/Logging+In scroll down for the section on Yubikey. Make sure you have another full rights admin account you can login and remove the TOTP settings in case things go sideways, but I did test this with our Yubikey and it was working just fine.

Thanks, it's intentional. I've seen some people complain that Blesta looks "too slim", but we did that on purpose. While we will be adding in additional support for a lot of things, or goal is to keep everything simple. The fact is that the multi-level, super long nav that our competitors have contains things most people never need. The way we implemented the plugin system, and designed things overall, reduces the number of links to those actually necessary and settings and things that aren't needed on a frequent basis are hidden away. The problem for us I think, is that people are use to the clutter, but I'm hopeful that once they spend enough time in Blesta they will come to appreciate the way we handled the UI.

This happens when adding a new service? It sounds like your Plesk server is complaining about the data type it received for the webspace/subscription ID. We've tested this on Plesk v11.5 and haven't experienced this issue, so I wonder why Plesk complains about the data type for an empty string now. If you're familiar with php, you can edit /components/modules/plesk/plesk.php and change: $data = array('id' => $webspace_id); to $data = array('id' => (empty($webspace_id) ? null : $webspace_id)); and let us know if that resolves your issue.

Invoice padding wasn't ready for 3.0.0, so should have been removed during beta. CORE-681 fixed for 3.0.1 removes these settings. Will be added back in when the feature is fully supported.

CORE-680 fixed in 3.0.1.

In all likelihood it would be completely provider agnostic. You'd simply enter the authentication URL for each of the providers you wish to support, or perhaps check boxes from a set of supported (e.g. tested) ones.

Although I would consider it "nice to have" if the user could authenticate with Facebook or LinkedIn, for clients and staff we need an email in the account, so email providers would serve not only as authenticators but also to gather an active and trusted email address and link the account to that, so I would focus on Google, Gmail with > 600 M users and Google Apps with > 5 M companies. If you are planning to add it for any OAuth service provider, I would suggest then to have settings to allow or disallow each one from a list of providers supported. I would personally leave it only for Google and Hotmail, in that case, maybe Yahoo! when it gets to OAuth 2.0.

That is good news. I'm in the process of switching to resell.biz but I still have to manage these domains for the time being. I have to complimemt you guys on how clean the system is right now. I hope it never gets bloated and cluttered like some of the competitors.

We'll need the developer team then mate to help you solve this they might need a login. Edit: Fixed your issue for you, it was your acl_acl was broken which gave you no permissions, and the order system plugin didn't have the databases for some reason, I added them manually, and uninstalled the plugin. After I re-installed it and everything works.

I think I'm more excited about Blesta 4.0 than anything lol, hopefully then there will be enom, a knowledgebase, project management, proxmox module, expanded portal plugin so that custom pages can be created and managed from within Blesta..

Ok, I see a task, CORE-439, to correct invoice padding.

OpenSRS is planned immediately following an Enom module, which is more highly requested. We met with some of the OpenSRS guys at HostingCon in Austin, and have everything we need to start development.

I think that this would probably be the best way to go about it.

I'll get one up for you now mate. Video completed: http://screencast.com/t/jQm2aqmdAECn

/components/gateways/nonmerchant/offline

Can you please go to: /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1); Then try again as that shows the errors if there is anything.

Great yeah as your on a reseller your username comes before the package name. Glad you have got it working mate.

Both licenses will remain active, though most people probably won't use v2.5 after they finish migrating. We are working on an importer for you.

If someone on the company end thinks that a ticket is solved, and marks it as solved, and the client still has an issue, they should be able to re-open the ticket, instead of having to open a new ticket. I believe Zendesk has a "Solved" state for up to 3-4 days, where tickets can still be reopened, and then they have a "Closed" state, where tickets can no longer be opened, and users can only create follow up tickets. Here's a post on how that works: https://support.zend...-Closed-ticket- And also having an option to create a follow up ticket for closed tickets, so that the new ticket contains a reference/link to the original ticket, would be an awesome option as well.

Custom fields are assigned to CORE-450, and they can be optionally stored encrypted. These fields will be by department, so you can have different fields for different departments, with whichever ones you want encrypted encrypted.