Leaderboard

Hm... not sure what the problem could be then. The pipe.php file works for me using cPanel. Of course our cPanel account added the hashbang a little differently as #!/usr/local/bin/php -q, but I'm sure that's an OS difference.

I'm surprised no one had mentioned the Universal Module yet. After you figure out how it works, its very powerful. Personally about to launch a companion brand to my web development business that is mostly hosting related: - Domain Names - LogicBoxes Module - Virtual Servers - SolusVM Module - Dedicated Servers - Universal Module I've also set up a bunch of addon services utilizing the Universal Module, such as Server Management, additional IP addresses, Commercial Hosting Control Panels (cPanel, etc.)

Just an update on the plugin I'm working on. The admin section seems to be working fine now. Not making it too fancy or complex. Simple categories with articles in them. I'll modify this post with updated information when I finish a release.

Holy cow! Changing the hashbang did it:

I have it fixed again. This did it for me: pipe1.php if you're using multiple companies copy this into multipe files, pipe2.php, pipe3.php etc and then update $company_id = 1; to whatever company number the pipe corresponds to then forward to the file. #!/usr/local/bin/php -q <?php /** * This files pipes email messages into the system. This is configured to process * messages for only a single company ID. Clone this file and change the * $company_id variable below to add pipe support for additional companies. */ $company_id = 1; try { include(dirname(__FILE__) . DIRECTORY_SEPARATOR . ".." . DIRECTORY_SEPARATOR . ".." . DIRECTORY_SEPARATOR . "lib/init.php"); $_SERVER['REQUEST_URI'] = null; $argv = array( '', 'plugin/support_manager/ticket_pipe/index/' . $company_id ); unset($company_id); // Dispatch the Web request if (!empty($_SERVER['REQUEST_URI'])) Dispatcher::dispatch($_SERVER['REQUEST_URI']); // Dispatch the CLI request else Dispatcher::dispatchCli($argv); } catch (Exception $e) { try { // Attempt to raise any error, gracefully Dispatcher::raiseError($e); } catch (Exception $e) { if (Configure::get("System.debug")) echo $e->getMessage() . " on line <strong>" . $e->getLine() . "</strong> in <strong>" . $e->getFile() . "</strong>\n" . "<br />Printing Stack Trace:<br />" . nl2br($e->getTraceAsString()); else echo $e->getMessage(); } } ?>

A user is a essentially a log in account. Any user type that can log into Blesta is a user (Staff, Clients, etc.). A client is essentially two parts: A user and a contact. The client record simply associates the user and the contact together to produce the client. This type of contact is known as the primary contact. Clients can have any number of non-primary contacts, but only one primary contact. Hopefully that sheds some light on the design.

The license is valid and eligible to transfer. Support & updates good through Aug 14, 2014.

that is exactly what i wanted cheers mate

Hello mate, What your looking for is this: admin/settings/company/currencies/setup/ You then need to untick: Use Package Pricing for New Services Only and tick: Automatically Update Exchange Rates and Allow Client to Set Currency

I'll leave the offer open until the weekend. I'll verify it in a bit, just gotta wait to get home

You can purchase addon companies during checkout for a new license, but cannot order them for an existing license yet. To get an addon company for an existing license just open a ticket and let us how many you need. We'll add them and invoice you. Pricing is $95/each or $350 for 5. It's one time, and can be applied to an owned license only (no monthly options yet). There is no additional yearly maintenance for addon companies.

CORE-639 % discounts for client groups tentatively scheduled for 3.1. It's not completed yet.

Dragging this topic back into the limelight. I don't know how I didn't notice this was added! This is great! The single biggest issue we run into is John Doe signs up for a hosting account, but Jane Smith is the developer. Jane Smith opens a ticket requesting assistance with some obscure PHP thing. When we reply, if the response goes to John Doe, John replies with "what is this, I have no idea what you're talking about etc". It would be nice to have the ability to allow a contact to semi-privately send tickets. Perhaps the tickets would still be accessible to the main client, but the main client wouldn't receive any notifications on them. This way, nothing is hidden from the client, but they also aren't getting bothered by updates to tickets that they don't understand or don't care about. If you want to put icing on the cake, allow the admin to define certain contact types for "transparent tickets". For example, each contact type gets a "direct ticket routing" checkbox. If checked, ticket responses don't go to the main user. That way, a "developer" contact can open tickets without bothering the user, but tickets from a "billing" contact would always cc the user. Finally, updating the docs might be in order here. A quick blurb explaining what the contacts are would be helpful. Also, the current screenshot simply shows "Name" as an example. It might be more helpful to show "Billing" or "Developer" or something like that; otherwise, someone might think they have to manually create name, address, phone, etc fields.

There is an option in the billing section admin -> settings -> company -> billing -> coupons Hope that helps?

This is in v3.0.3.

Haha that url link is the one for another software, Blesta doesn't have one yet. They are going to be doing one which is advanced though.

They do have a HB system and are doing the importer as I'm aware, I remember Cody saying exploit, exploit, exploit Haha.

It also doesn't help that quite a few people purchased licenses with the intent to flip them because they knew the price was going up.

Ok, I think changing it would make more sense but I can understand waiting until granting contacts the ability to login to implement this.

Good observation. I suspect this is the intended behavior for now, but we may want to take a look at this once the ability for contacts to login has been implemented.