Cody

Still testing it out, but try the attached file. Upload to /plugins/support_manager/. Your pipe should be similar to: /usr/bin/php /path/to/blesta/plugins/support_manager/pipe.php Note, this file has no hashbang by default. cPanel installs should create the proper hashbang when the pipe is created. Other systems may do the same, but it is always preferable to invoke the pipe using the path to PHP (as in the example above.) pipe.php

The command to pipe messages from your server. What does it look like?

FYI, the current WHMCS migrator doesn't import packages or services. That's still in the works.

Version 3.0.3 is now available. You can download it at https://account.blest...er/client_main/. This is a patch release that corrects issues with 3.0.0. Patching Blesta See Patching Blesta in the User Manual for instructions. Release Notes - Blesta Core - Version 3.0.3 ## Version 3.0.3 2013-09-18 ### Bug * [CORE-206] - All plugin controllers require authentication checks * [CORE-532] - Logicboxes: Cannot add service from admin interface due to error "required Parameter Missing: Customer-Id" * [CORE-555] - PayPal Payflow Pro gateway error: Please enter a valid alphanumeric password * [CORE-632] - Cron: Manually suspended services automatically unsuspend * [CORE-635] - When the cron applies credits to multiple invoices, it may record zero as the amount for the last invoice * [CORE-657] - MyInfo shows Two Factor Authentication fields when "None" is selected * [CORE-686] - Interworx: Invalid credentials produces SOAP parse error * [CORE-688] - Importer: Company Tax ID/VATIN is set for clients when importing v2.5 to v3.0 * [CORE-711] - Plugin email templates missing multiple languages if installed after languages are installed * [CORE-712] - Support Plugin: Using a password with special characters does not work * [CORE-720] - Invoices sometimes remain open when paid due to 4 decimal precision rounding * [CORE-724] - Support Manager {update_ticket_url} tag is not set when email is sent via cron * [CORE-726] - Support Manager: Remove inherited background gradient set on H2 tags in replies * [CORE-727] - Service Suspended template parse error * [CORE-730] - Order Plugin: Successfully redeeming a coupon on the order form does not display a success message * [CORE-733] - Cross company package access violation * [CORE-735] - Undefined offset 1 in client_pay controller * [CORE-738] - Service Suspension email template is never used * [CORE-739] - Invoice delivery log is not limited to the current company * [CORE-740] - Email delivery log is not limited to the current company * [CORE-744] - Tax not applied for states with ISO 3166-2 alpha-numeric subdivision code with 3 characters * [CORE-746] - Order System: Client Registration template displays sign up form again after successful registration * [CORE-748] - Universal Module: Service fields are blank on edit * [CORE-752] - Email templates do not fallback to en_us if the template is not available in the requested language * [CORE-761] - Invoice line items display incorrect service term dates * [CORE-764] - Default Invoice template may incorrectly generate an additional PDF page * [CORE-765] - Universal Module: Input data are not validated against the rules * [CORE-766] - Support Manager: h1, ... h6 tags in ticket responses are styled incorrectly * [CORE-767] - System Requirements: Update to MySQL 5.0.17 * [CORE-769] - Addon Packages set to inactive appear as Available Addons ---

How is your pipe configured?

CORE-715 was resolved in 3.0.2, so I'm closing this thread (again). Any further discussion related directly or indirectly to this topic can be made in the Feature Requests forum.

Copy pipe.php and name is pipe1.php (1 for company ID 1, in the future if/when you add additional companies you can create a pipe2.php, etc.), then make the above changes to pipe1.php. Blesta won't overwrite any files it doesn't itself contain, so there should be no problem there. Also, disclaimer, I haven't verified the above change works though theoretically it should.

Hi, It looks like that is a Spanish payment gateway. Do they have any documentation in English? It also looks like they have developed a gateway for WHMCS included in their example implementations zip. Have you tried contacting them and requesting they create a payment gateway for Blesta?

Yes, I can imagine such a scenario. Users selling services who wish to have addons available via Phone only may have addons: Additional IP Addresses (.) Default Then have a disclaimer "Call to add additional IP addresses". We already have a task to make setting the label for the default addon option configurable. That would then allow users to do the following: Additional IP Addresses (.) 0 - Call to add additional IP addresses 555.555.5555

That's true. But then this turns into a business decision as to whether or not customers should be aware that such an addon group exists prior to placing the order. Some would argue it should still appear, others like yourself disagree. In any case, I don't see this being a bug, but could be a good feature request when configuring an order form: [ ] Hide Addon Group if No Packages Available To User

I believe that's the intended behavior. Couldn't you simply disassociate the addon group from that primary package group? After all, if there is no addon group, no section will be displayed.

I'm unable to duplicate restricted/inactive packages appearing under "Available Add-Ons" during checkout. Are you sure you're running 3.0.2?

Added CORE-769 to address inactive/restricted addon packages appearing as available addons.

I think that can be done simply by modifying pipe.php to include the proper set of parameters (missing from cPanel): #!/usr/bin/php -q <?php try { include(dirname(__FILE__) . DIRECTORY_SEPARATOR . ".." . DIRECTORY_SEPARATOR . ".." . DIRECTORY_SEPARATOR . "lib/init.php"); becomes: #!/usr/bin/php -q <?php try { include(dirname(__FILE__) . DIRECTORY_SEPARATOR . ".." . DIRECTORY_SEPARATOR . ".." . DIRECTORY_SEPARATOR . "lib/init.php"); $argv = array( '/plugin/support_manager/ticket_pipe/index/1' ); But that has to be customized per company and per server (to include or not include /index.php/ in the path).

The issue here that we've seen with cPanel is cPanel's inability to pass parameters along in a pipe request. Because of this, Blesta never receives the company ID that is to be processed for the request and thus can't process the request. We're looking at possible work arounds, and unfortunately so far it looks like this would require a separate pipe script for each and every company you wish to pipe mail for, which is pretty crappy. Would be great if cPanel added support for parameters in pipe requests as that would completely solve the issue without any change required in Blesta.

CORE-727 is fixed for 3.0.3.

Closed as not a bug.

Error validation was only happening immediately before provisioning the service. We've updated the Universal module to do this validation when the form is initially submitted as well. CORE-765 fixed for 3.0.3.

Closed as unable to duplicate.

Until we've investigated and determined steps required to implement this feature, I won't be able to tell you what to change.

Hm... that doesn't seem to make sense. The apahce log error indicates an error with the application (PHP) processing that URL. I would think PHP would log such an error. Unless I'm mistaken, they even log 500 internal errors thrown by PHP itself, as opposed to the script. Not sure what else to try, except maybe searching the PHP changelog or bug tracker for similar issues. It's still entirely possible it's an issue with Blesta, but without an PHP error being captured it's impossible to know for sure.

Don't use notepad. Notepad adds a BOM (byte-order-mark) to any UTF-8 encoded files (which language files must be), and that is unacceptable. I'd recommend Komodo Edit, it's free.

Enable error reporting in php.ini: error_reporting = -1 log_errors = On error_log = /path/to/php/log/error.log

Firstly, I STRONGLY RECOMMEND AGAINST DOING THIS. Adjusting a cron task to run more frequently than once every 5 minutes can be dangerous as it increases the likelihood of a race condition, the results can be unpredictable. Find the ID for the "poll_tickets" key in the cron tasks table (SELECT `id` FROM `cron_tasks` WHERE `key`='poll_tickets') Take the ID from #1, and search for the entry in the cron_task_runs table (SELECT * FROM `cron_task_runs` WHERE `task_id`=TASK_ID) Change the cron_task_runs.interval from 5 to 1. Update line 1983 of /app/controllers/cron.php from: $last_run_date = date("c", floor($this->Date->toTime($last_run->start_date)/(60*5))*(60*5)); to: $last_run_date = date("c", floor($this->Date->toTime($last_run->start_date)/(60*min(5,$cron_task->interval)))*(60*min(5,$cron_task->interval))); Set your configured cron to run once every 1 minute, OR (more preferably) create a new cron task that runs every 1 minute at /usr/bin/php /path/to/blesta/index.php cron/pluginTasks/

It's embedded into the installer.