Cody

There are a number of things to consider if we were to allow multiple prices per term and period through the order system. I think that it's something that can technically be done, but there are also a lot of potential issues.
Obviously, the more people that want this the more likely it is we'll take time away from other tasks to tackle those issues.

Sure you can request a feature for this -- though I'm leaning more towards not allowing language definitions at all in config.json files for modules, gateways, and plugins. 99% of modules and gateways are named the same in every language. For example, PayPal is "PayPal" everywhere in the world.

Updates to the WHMCS migrator are coming in 3.3.0. These include client passwords, price overrides, options when importing client credits, and more.

There are a number of things to consider if we were to allow multiple prices per term and period through the order system. I think that it's something that can technically be done, but there are also a lot of potential issues.
Obviously, the more people that want this the more likely it is we'll take time away from other tasks to tackle those issues.

Updates to the WHMCS migrator are coming in 3.3.0. These include client passwords, price overrides, options when importing client credits, and more.

I don't even know who I would hire to do this (electrician?, network tech?), so I guess I had no choice Haha.

Fixed in CORE-1368.

Phase 2 will be running electrical to the network closet so I can install a switch, router, and other equipment.

I've spent the last few months wiring my house, so I thought I'd share my experience and the process.
 
The Goal
My house was built in the 60's, so had no structured wiring of any kind. The telephone wires were 4 untwisted pair, which predated CAT3 by about 20 years. Lukily, just about every room in the house had a telephone drop, so I figured I could replace each drop with CAT6.
 
Thinking about it some more, since I didn't already have cable to each room I figured I might as well bundle that in as well. The goal for phase one was to add 6 drops, each with 2 CAT6 and 1 RG6. Each drop was to terminate in the coat closet due to its central location in the house. This would become my network closet.
 
The Materials
1000' CAT6 1000' RG6 quad sheild CCS (this was a mistake, more on that below) 100' RG6 dual shield pure copper 100' CAT5e 10 pack of 4-slot keystone wall plates 200 pack of CAT6 connectors and matching boots 25 pack of CAT6 keystones 8 pack of RG6 keystones 10 pack of blank keystones 10 pack of low voltage wall inserts Hinged 4U wall mount rack 24-port CAT5e patch panel 24-port CAT6 patch panel 2 desk grommets (2 3/8") 1 RG6 4-port splitter 1 RG6 8port directv splitter RG6 external enclosure Tools: Punch down tool RG6 compression tool RG6 cutter RG6 stripper Wire strippers (only needed to strip the CAT5e to connect to the telephone NID) Philips head screwdriver  
The Process
I planned the following drops:
Master bedroom Bedroom 1 Bedroom 2 Bedroom 3 Kitchen Living Room I would also neet the following utility drops:
Network closet to external enclosure for CATV and SATV utilities Network closet to Telephone NID This is what I was replacing at each drop:

 
I estimated the distance between the drop location and the network closet, then added 5 to 10 feet to ensure excess, and in some cases, avoid electrical lines in the attic.
 
I cut the RG6 and CAT6 from their spool and labeled each, then attached to the existing telephone line and climbed in the attic to pull through.

 
Lucky for me, the following was true:
In the 60's low voltage wires did not have to be stapled down. 2 CAT6 and 1 RG6 is just thin enough to fit through the 1/2" opening already drilled in the joist. Due to the sloe in the roof it would have been impossible to increase the diameter of these holes Punched down

 
Compression fitting

 
RG6 quad shield CCS was a bad choice for a couple reasons. First, Directv requires pure copper for the SWIM. That's why I had to get another 100' of RG6. Second, manipulating quad shield CCS is super difficult. That stuff is rigid. I wasn't able to pull RG6 through Bedroom 1 because that drop went down and made a 90 degree turn through a stud. The quad shield couldn't handle it.
 
While RG6 CCS is fine for video, it sucks for pulling, and has the added limitation of more resistance than pure copper. If I did this again I would have gone pure copper dual shield.
 
The finished product

 
Next I drilled two 2 and 3/8" holes to drop into the network closet. I inserted the rubberized desk grommets to prevent insulation from falling out of the ceiling, and pulled through.
 

The CAT5e is gray. I daisy chained this across the first 8 ports of the CAT5e patch panel. This allows me to patch through telephone to any one of my drops. Each telephone port supports up to 4 lines.
 

 
You can see here I'm patching the phone into my office.
 
After running the CAT5e for the telephone (and my internet). My speed changed from 7.26 Mbps / 0.92 Mbps to 7.28 Mbps / 2.20 Mbps.

I've spent the last few months wiring my house, so I thought I'd share my experience and the process.
 
The Goal
My house was built in the 60's, so had no structured wiring of any kind. The telephone wires were 4 untwisted pair, which predated CAT3 by about 20 years. Lukily, just about every room in the house had a telephone drop, so I figured I could replace each drop with CAT6.
 
Thinking about it some more, since I didn't already have cable to each room I figured I might as well bundle that in as well. The goal for phase one was to add 6 drops, each with 2 CAT6 and 1 RG6. Each drop was to terminate in the coat closet due to its central location in the house. This would become my network closet.
 
The Materials
1000' CAT6 1000' RG6 quad sheild CCS (this was a mistake, more on that below) 100' RG6 dual shield pure copper 100' CAT5e 10 pack of 4-slot keystone wall plates 200 pack of CAT6 connectors and matching boots 25 pack of CAT6 keystones 8 pack of RG6 keystones 10 pack of blank keystones 10 pack of low voltage wall inserts Hinged 4U wall mount rack 24-port CAT5e patch panel 24-port CAT6 patch panel 2 desk grommets (2 3/8") 1 RG6 4-port splitter 1 RG6 8port directv splitter RG6 external enclosure Tools: Punch down tool RG6 compression tool RG6 cutter RG6 stripper Wire strippers (only needed to strip the CAT5e to connect to the telephone NID) Philips head screwdriver  
The Process
I planned the following drops:
Master bedroom Bedroom 1 Bedroom 2 Bedroom 3 Kitchen Living Room I would also neet the following utility drops:
Network closet to external enclosure for CATV and SATV utilities Network closet to Telephone NID This is what I was replacing at each drop:

 
I estimated the distance between the drop location and the network closet, then added 5 to 10 feet to ensure excess, and in some cases, avoid electrical lines in the attic.
 
I cut the RG6 and CAT6 from their spool and labeled each, then attached to the existing telephone line and climbed in the attic to pull through.

 
Lucky for me, the following was true:
In the 60's low voltage wires did not have to be stapled down. 2 CAT6 and 1 RG6 is just thin enough to fit through the 1/2" opening already drilled in the joist. Due to the sloe in the roof it would have been impossible to increase the diameter of these holes Punched down

 
Compression fitting

 
RG6 quad shield CCS was a bad choice for a couple reasons. First, Directv requires pure copper for the SWIM. That's why I had to get another 100' of RG6. Second, manipulating quad shield CCS is super difficult. That stuff is rigid. I wasn't able to pull RG6 through Bedroom 1 because that drop went down and made a 90 degree turn through a stud. The quad shield couldn't handle it.
 
While RG6 CCS is fine for video, it sucks for pulling, and has the added limitation of more resistance than pure copper. If I did this again I would have gone pure copper dual shield.
 
The finished product

 
Next I drilled two 2 and 3/8" holes to drop into the network closet. I inserted the rubberized desk grommets to prevent insulation from falling out of the ceiling, and pulled through.
 

The CAT5e is gray. I daisy chained this across the first 8 ports of the CAT5e patch panel. This allows me to patch through telephone to any one of my drops. Each telephone port supports up to 4 lines.
 

 
You can see here I'm patching the phone into my office.
 
After running the CAT5e for the telephone (and my internet). My speed changed from 7.26 Mbps / 0.92 Mbps to 7.28 Mbps / 2.20 Mbps.

I've spent the last few months wiring my house, so I thought I'd share my experience and the process.
 
The Goal
My house was built in the 60's, so had no structured wiring of any kind. The telephone wires were 4 untwisted pair, which predated CAT3 by about 20 years. Lukily, just about every room in the house had a telephone drop, so I figured I could replace each drop with CAT6.
 
Thinking about it some more, since I didn't already have cable to each room I figured I might as well bundle that in as well. The goal for phase one was to add 6 drops, each with 2 CAT6 and 1 RG6. Each drop was to terminate in the coat closet due to its central location in the house. This would become my network closet.
 
The Materials
1000' CAT6 1000' RG6 quad sheild CCS (this was a mistake, more on that below) 100' RG6 dual shield pure copper 100' CAT5e 10 pack of 4-slot keystone wall plates 200 pack of CAT6 connectors and matching boots 25 pack of CAT6 keystones 8 pack of RG6 keystones 10 pack of blank keystones 10 pack of low voltage wall inserts Hinged 4U wall mount rack 24-port CAT5e patch panel 24-port CAT6 patch panel 2 desk grommets (2 3/8") 1 RG6 4-port splitter 1 RG6 8port directv splitter RG6 external enclosure Tools: Punch down tool RG6 compression tool RG6 cutter RG6 stripper Wire strippers (only needed to strip the CAT5e to connect to the telephone NID) Philips head screwdriver  
The Process
I planned the following drops:
Master bedroom Bedroom 1 Bedroom 2 Bedroom 3 Kitchen Living Room I would also neet the following utility drops:
Network closet to external enclosure for CATV and SATV utilities Network closet to Telephone NID This is what I was replacing at each drop:

 
I estimated the distance between the drop location and the network closet, then added 5 to 10 feet to ensure excess, and in some cases, avoid electrical lines in the attic.
 
I cut the RG6 and CAT6 from their spool and labeled each, then attached to the existing telephone line and climbed in the attic to pull through.

 
Lucky for me, the following was true:
In the 60's low voltage wires did not have to be stapled down. 2 CAT6 and 1 RG6 is just thin enough to fit through the 1/2" opening already drilled in the joist. Due to the sloe in the roof it would have been impossible to increase the diameter of these holes Punched down

 
Compression fitting

 
RG6 quad shield CCS was a bad choice for a couple reasons. First, Directv requires pure copper for the SWIM. That's why I had to get another 100' of RG6. Second, manipulating quad shield CCS is super difficult. That stuff is rigid. I wasn't able to pull RG6 through Bedroom 1 because that drop went down and made a 90 degree turn through a stud. The quad shield couldn't handle it.
 
While RG6 CCS is fine for video, it sucks for pulling, and has the added limitation of more resistance than pure copper. If I did this again I would have gone pure copper dual shield.
 
The finished product

 
Next I drilled two 2 and 3/8" holes to drop into the network closet. I inserted the rubberized desk grommets to prevent insulation from falling out of the ceiling, and pulled through.
 

The CAT5e is gray. I daisy chained this across the first 8 ports of the CAT5e patch panel. This allows me to patch through telephone to any one of my drops. Each telephone port supports up to 4 lines.
 

 
You can see here I'm patching the phone into my office.
 
After running the CAT5e for the telephone (and my internet). My speed changed from 7.26 Mbps / 0.92 Mbps to 7.28 Mbps / 2.20 Mbps.

I've spent the last few months wiring my house, so I thought I'd share my experience and the process.
 
The Goal
My house was built in the 60's, so had no structured wiring of any kind. The telephone wires were 4 untwisted pair, which predated CAT3 by about 20 years. Lukily, just about every room in the house had a telephone drop, so I figured I could replace each drop with CAT6.
 
Thinking about it some more, since I didn't already have cable to each room I figured I might as well bundle that in as well. The goal for phase one was to add 6 drops, each with 2 CAT6 and 1 RG6. Each drop was to terminate in the coat closet due to its central location in the house. This would become my network closet.
 
The Materials
1000' CAT6 1000' RG6 quad sheild CCS (this was a mistake, more on that below) 100' RG6 dual shield pure copper 100' CAT5e 10 pack of 4-slot keystone wall plates 200 pack of CAT6 connectors and matching boots 25 pack of CAT6 keystones 8 pack of RG6 keystones 10 pack of blank keystones 10 pack of low voltage wall inserts Hinged 4U wall mount rack 24-port CAT5e patch panel 24-port CAT6 patch panel 2 desk grommets (2 3/8") 1 RG6 4-port splitter 1 RG6 8port directv splitter RG6 external enclosure Tools: Punch down tool RG6 compression tool RG6 cutter RG6 stripper Wire strippers (only needed to strip the CAT5e to connect to the telephone NID) Philips head screwdriver  
The Process
I planned the following drops:
Master bedroom Bedroom 1 Bedroom 2 Bedroom 3 Kitchen Living Room I would also neet the following utility drops:
Network closet to external enclosure for CATV and SATV utilities Network closet to Telephone NID This is what I was replacing at each drop:

 
I estimated the distance between the drop location and the network closet, then added 5 to 10 feet to ensure excess, and in some cases, avoid electrical lines in the attic.
 
I cut the RG6 and CAT6 from their spool and labeled each, then attached to the existing telephone line and climbed in the attic to pull through.

 
Lucky for me, the following was true:
In the 60's low voltage wires did not have to be stapled down. 2 CAT6 and 1 RG6 is just thin enough to fit through the 1/2" opening already drilled in the joist. Due to the sloe in the roof it would have been impossible to increase the diameter of these holes Punched down

 
Compression fitting

 
RG6 quad shield CCS was a bad choice for a couple reasons. First, Directv requires pure copper for the SWIM. That's why I had to get another 100' of RG6. Second, manipulating quad shield CCS is super difficult. That stuff is rigid. I wasn't able to pull RG6 through Bedroom 1 because that drop went down and made a 90 degree turn through a stud. The quad shield couldn't handle it.
 
While RG6 CCS is fine for video, it sucks for pulling, and has the added limitation of more resistance than pure copper. If I did this again I would have gone pure copper dual shield.
 
The finished product

 
Next I drilled two 2 and 3/8" holes to drop into the network closet. I inserted the rubberized desk grommets to prevent insulation from falling out of the ceiling, and pulled through.
 

The CAT5e is gray. I daisy chained this across the first 8 ports of the CAT5e patch panel. This allows me to patch through telephone to any one of my drops. Each telephone port supports up to 4 lines.
 

 
You can see here I'm patching the phone into my office.
 
After running the CAT5e for the telephone (and my internet). My speed changed from 7.26 Mbps / 0.92 Mbps to 7.28 Mbps / 2.20 Mbps.

See the updated CORE-1371. With this event, plugins are able to inject arbitrary markup into the head, top of the body, and bottom of the body, as well as set variables into the structure that could be used in conjunction with changes to the structure file.
 
 
There's really no difference. A hook is simply a poor man's event. By the way, there's already an event that is triggered on every page load: Appcontroller.preAction. CORE-1371 improves on that event.

See the updated CORE-1371. With this event, plugins are able to inject arbitrary markup into the head, top of the body, and bottom of the body, as well as set variables into the structure that could be used in conjunction with changes to the structure file.
 
 
There's really no difference. A hook is simply a poor man's event. By the way, there's already an event that is triggered on every page load: Appcontroller.preAction. CORE-1371 improves on that event.

See the updated CORE-1371. With this event, plugins are able to inject arbitrary markup into the head, top of the body, and bottom of the body, as well as set variables into the structure that could be used in conjunction with changes to the structure file.
 
 
There's really no difference. A hook is simply a poor man's event. By the way, there's already an event that is triggered on every page load: Appcontroller.preAction. CORE-1371 improves on that event.

A number of users have requested the ability to download invoice PDFs using the API. I've always said how easy it is to build a plugin to do this, so here it is.
 
Actually, I took it a few steps further and made it more abstract than that. This plugin allows you to invoke any component in Blesta using the API, so it's quite powerful. Invoices are offered for download and stream through the browser using the InvoiceDelivery component.
 
Documentation for this plugin can be found here..
component_api.zip

Maybe the client could rely the information to the developer and developer's boss? Whose to say that the content of the ticket may not contain confidential information that the client doesn't wish to share with the developer? It could then be easy to accidentally send confidential information to third parties!
 

No, I'm not kidding. It would be trivial to create an email that CC'd 10,000 people. Now you want Blesta to log all 10,000 CC addresses and email each one whenever the ticket is updated? That would clearly cause a denial of service that could effect not only your server, but also your mail service.
 
 
It's a security concern because it allows a multitude of users to reply to a single ticket. Blesta verifies the integrity of a ticket reply by evaluating the subject line. Allowing multiple people to reply to the same ticket can be a security concern as the reply is associated with the client and may not have necessarily come from the client.
 

Maybe a feature request to allow ticket replies to be CC'd to other contacts that are already set for the client account?
 

I wouldn't say this is an incredibly simple feature. Like I said, it has inherit problems. Those could probably be dealt with in some way to mitigate their effects. I don't know.
 

There are a lot of things in Kayako that Blesta doesn't do, but it's easy to use Kayako with Blesta.

Maybe the client could rely the information to the developer and developer's boss? Whose to say that the content of the ticket may not contain confidential information that the client doesn't wish to share with the developer? It could then be easy to accidentally send confidential information to third parties!
 

No, I'm not kidding. It would be trivial to create an email that CC'd 10,000 people. Now you want Blesta to log all 10,000 CC addresses and email each one whenever the ticket is updated? That would clearly cause a denial of service that could effect not only your server, but also your mail service.
 
 
It's a security concern because it allows a multitude of users to reply to a single ticket. Blesta verifies the integrity of a ticket reply by evaluating the subject line. Allowing multiple people to reply to the same ticket can be a security concern as the reply is associated with the client and may not have necessarily come from the client.
 

Maybe a feature request to allow ticket replies to be CC'd to other contacts that are already set for the client account?
 

I wouldn't say this is an incredibly simple feature. Like I said, it has inherit problems. Those could probably be dealt with in some way to mitigate their effects. I don't know.
 

There are a lot of things in Kayako that Blesta doesn't do, but it's easy to use Kayako with Blesta.

Blesta is not going to keep track of every CC address attached to an incoming email and reply back to all of them. That could easily produce a denial of service. Tickets are one-to-one. They come from one address, and are received at one address.
 
Moreover, you suggest anyone CC'd should be able to reply to the ticket. That's a security concern.
 
The ticket system isn't a mailing list, so I don't think it should necessarily act like one.

I don't understand. You can view all emails a client has received under their account, or view the mail log under [Tools] > [Logs].
 
You mean select multiple tickets and reply with the same response all at one time? I don't know about that, since there's no way to know what the last response is for every ticket selected, since that's not listed on the ticket listing page.

Version 3.2.2 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.2.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.2.2.

See all Change Logs.

Are you sure you overwrote all of the necessary files? Specifically the files affected by CORE-1349 are in /components/invoice_templates/. What would happen before CORE-1349 was that PDF invoices would send headers and output the PDF document, but execution would continue. This would result in additional headers being sent which produced an error of "cannot send headers, headers already sent".
 
As of CORE-1349, all invoice templates shipped with Blesta (default and quickbooks) now terminate execution immediately after the PDF is output, which completely prevents additional headers from being attempted. Moreover, no headers are sent prior to PDF output, so if CORE-1349 doesn't resolve the issue for you, the issue must be with either custom changes, or outside the control of Blesta (e.g. server related).

Version 3.2.2 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.2.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.2.2.

See all Change Logs.

Version 3.2.2 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.2.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.2.2.

See all Change Logs.

Version 3.2.2 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.2.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.2.2.

See all Change Logs.