Cody
-
Posts
1,574 -
Joined
-
Last visited
-
Days Won
74
Posts posted by Cody
-
-
The command to pipe messages from your server. What does it look like?
-
-
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 ---- teefrircuniot and Michael
-
2
-
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.
-
I am using one company at the moment so if that will work I'm will to sacrifice the multi company functionality.
The question for me is, what is I create a new php file like pipemod.php that won't be overwritten on every update and put the exact same code in it as pipe.php along with the mentioned code changes then I send all of my emails to pipemod.php will that work?
The goal here is for it work before and after an update. If its not multi company I don't care I just need it to work and not worry about it.
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.
-
-
The question is, can you imagine a single solitary use case where having a pre-filled single radio button labeled "Default" under the "Available Add-Ons" section with no available add-ons is useful? Moreover, can you imagine a case where it isn't confusing for the end-user? I can't. If not, you're adding extra development and configuration to create that [ ] option when nobody has a use for it.
Furthermore, this does not make the customer aware of what add-on groups exist. As an end-user, I would have no indication of anything other than unnecessary elements in the ordering system. I can't imagine an agument that this is a worthwhile portion of the checkout under these circumstances.
In conclusion, it seems to me that a static boolean check to see whether any add-ons are marked active before outputting the "Available Add-Ons" checkout section in question would suffice to solve this issue.
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
-
I could be wrong, but wouldn't this limit us from easily adding it as a recurring add-on to their service on the admin-end? Even though it is hidden from the checkout, we use this to sell to customers whom call or email in for add-ons which Blesta can't yet quite handle they way we would like.
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
-
Just to be clear, I don't think the inactive/restricted addon packages appear available. If they are restricted, the correlated options do not appear on the configure page. Problem is, the "Available Add-Ons" section still appears with a lone "Default" radio button option. The section is completely useless and confusing without active add-ons in addition to the "Default" option.
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.
-
Could we create a .php file, that contains a configurable option for the company ID in the file? We'll default this to "1" for the primary company. If users want to pipe email into multiple companies, they could copy the file, change the company ID, and pipe their mail into the cloned file.
We'll continue to support the other option by passing as parameters, but anyone that has trouble with that can use the alternative method.
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.
-
-
Closed as unable to duplicate.
-
-
PHP error logging is enabled. It has nothing related to Blesta in it, only an entirely unrelated script in different directory.
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.End of script output before headers: index.php, referer: https://fullambit.net/portal/admin/packages/index/inactive/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.
-
I want to use Notepad to translate the files. But the yet not translated English definitions are not included in the Hungarian language files.
This is the problem.
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/
-
Dam haha woops is there a v3 one mate?
It's embedded into the installer.
Email Piping
in Support
Posted
Still testing it out, but try the attached file. Upload to /plugins/support_manager/. Your pipe should be similar to:
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