Rocketz

Ah that's easy
 

I am using piping
But I don't want to have 12 google apps accounts. I want 1. Along with 12 aliases on it. 
admin@domain.com is the main account. info@, sales@, whatever@ are the aliases. I forward the aliases to the blesta domain. 
Alias1@google-apps.com forwards to alias1@blesta-install.com, alias2 forwards to alias 2 and so on
However, if I sent an email to alias1@google-apps.com, it forwards the email to blesta, my server has logs of it. However, Blesta doesn't pipe in the ticket. It sends the "Ticket Bounce" error message template. So it actually reaches Blesta, but Blesta rejects creating a ticket for it. Departments are set to accept all emails, not just customers. 
However, if i email alias1@blesta-install.com directly, the ticket is piped in just fine.
That's what I want to know. What's going on in Blesta to refuse creating a ticket the first way. 

Only reason is SLA's. Up to 5 minutes before a ticket is seen equals up to 50% of the reaction time for certain SLA segments in my case. 
Piping only takes about 30 seconds to a minute, so that helps a lot when it comes to response and reaction times. 
If only it were so simple to use IMAP in my case  

The import from Wordpress was useful in that it converted all of our posts into Markdown files that I was able to import into the project. The posts required some tweaking to work properly, but the import saved a ton of time. We built the theme using Bootstrap, SASS, and Gulp, and converted it into a Hugo theme. So, most of the work was building the new site, creating the Hugo theme. Importing Wordpress posts was really the easiest part.
I did have to create some shortcodes for displaying Vimeo videos in posts, responsive images, and buttons. They include some shortcodes already, like code highlighting that was very useful. So, posts consist of largely markdown content, and some shortcodes to avoid the use of HTML in the post content.

paul, how did you find the conversion from wordpress to hugo went? Were you able to re-use any elements, or it had to be completely designed from scratch? 

Your host really needs to help you out on this. 
 
That error usually happens because your account/domain is set to receive mails on another email server. You're piping to a local email that's set to refuse incoming email. 

We use this tag in our email titles: 
Licensecart {ticket.department_name} - #{ticket.code} has been {% if ticket.reply_date_added == ticket.date_added %}opened{% else %}updated.{% endif %} [{ticket_hash_code}]

Client goes through checkout process for mydomain.com. Invoice is created, pending account is created. Doesn't pay.
 
Client comes back, goes through checkout process for mydomain.com. Invoice is created, pending account is created. Pays.
 
Goes back to account, applies credits to last invoice. After 5 minutes, account is provisioned.
 
Client sees unpaid invoice and pending account from previous checkout. Keeps receiving outstanding invoice notifications. Goes in and tries to cancel pending service.
 
Because first invoice went unpaid and account was not actually provisioned, Blesta stores same WHM username for both pending account and now active account. When user goes to cancel the pending account, Blesta instructs WHM to delete associated account from WHM, even though account was never created. But, because username is the same as the now active account, WHM deletes the now active account.
 
The result?
 
In Blesta, client sees one active service, one cancelled service, one closed invoice, one open invoice, and they have no active services in WHM.
 
This is all due to the fact that Blesta is creating pending accounts and invoices for clients prior to receiving payment. It also does not allow clients to void invoices and for some reason, allows them to cancel pending accounts that haven't even been created.
 
This is all very strange, atypical, and buggy behavior. I've now manually had to go in and hack the 'Manage' link out from non-active services to prevent this from happening. And I'm still going to have to go in and manually void outstanding invoices.

Can't there be an account dropdown on the top right once they're logged in? 
 
I.e : If you have 4 actual accounts, at the top right or wherever makes the most sense, you can an account dropdown and can select it there. That's how we managed permissions with designers who had access to multiple customer accounts at my previous company. 

That's a setting in WHM you can toggle on or off. It's under "password strength configuration"
 
If you don't want to turn it off, you'll probably need to provide random passwords to your customers rather than letting them choose their own. 

I suspected this on some level but couldn't find the error until hours later. It was a syntax error inside php.ini with regard to mailparse. 
 
Everything works as expected for now Thanks all! 

I suspected this on some level but couldn't find the error until hours later. It was a syntax error inside php.ini with regard to mailparse. 
 
Everything works as expected for now Thanks all! 

That's a setting in WHM you can toggle on or off. It's under "password strength configuration"
 
If you don't want to turn it off, you'll probably need to provide random passwords to your customers rather than letting them choose their own. 

There's a few departments that should not have an auto-reply to them. For example, vendor notices that go into a certain queue, if there is an auto-reply, it creates an endless loop of auto replies. 
 
How do I remove auto-reply per department? 

That's completely irrelevant to the thread. It's up to Blesta to make their own business decisions regarding how licensing works. That's entirely their business and we aren't privy to any details. 
 
I'd rather keep this thread fairly on topic. We're still waiting for 4.0 / 4.1, and I'm anxious to see if Blesta incorporates any suggestions from this thread and other places in the forum. 

The way he said it is totally inappropriate and lacks respect, but shunning him for an opinion isn't right  
 
I have a fairly large commitment towards Blesta (addon companies), but I can't actually use Blesta for what I need it to do. Do I want to use Blesta? YES. But right now, I'm stuck using WHMCS because of core components that Blesta will not get to until 4.1 at least.
 
The reason I can't use Blesta? Because it would take a lot more money to customize it and bring it up to speed, than it would be to simply use a competing product. And even then, it wouldn't be 100%
 
Let's be honest here guys, the development of Blesta is pretty slow. I'm not sure if the hope was that 3rd party developers would take up the slack, but there's been a really big mis-read on what your customers are using Blesta for, and what you think they should be using Blesta for.
 
I think WHMCS got their act together security-wise, finally. But I don't like their company, I don't like how cPanel runs things either (but use them for server software... because cPanel).
 
I really like Blesta, I met the Blesta guys at multiple Hostingcons, great guys, but Blesta needs to kick it up a notch if it wants to grow and put a dent in competitors' market-share. 
 
I'm still rooting for Blesta, i haven't sold my license, and still pay for updates even if I don't use it. But I wish Blesta would really start focusing on what customers want to use Blesta for, how they use it, how many clicks it takes to get to something, intuitiveness, along with a whole bunch of other things, and start moving development resources towards those pain points first, and worrying a lot less about ancillary stuff.
 
Maybe even provide smaller, quicker updates. When a new feature is built and tested, ship it out. Stop waiting 3+ months to make bigger splashes with releases. You're a smaller company, who should be much nimbler than your bigger competitors. Use that to your advantage. You have the ability to pivot quickly and release things nearly as fast. I don't know why you don't do it. 
 
Like someone once told me, it's fine to give out ideas and roadmaps about where you're going. It's the execution that counts, and few people can do that part well.  

The way he said it is totally inappropriate and lacks respect, but shunning him for an opinion isn't right  
 
I have a fairly large commitment towards Blesta (addon companies), but I can't actually use Blesta for what I need it to do. Do I want to use Blesta? YES. But right now, I'm stuck using WHMCS because of core components that Blesta will not get to until 4.1 at least.
 
The reason I can't use Blesta? Because it would take a lot more money to customize it and bring it up to speed, than it would be to simply use a competing product. And even then, it wouldn't be 100%
 
Let's be honest here guys, the development of Blesta is pretty slow. I'm not sure if the hope was that 3rd party developers would take up the slack, but there's been a really big mis-read on what your customers are using Blesta for, and what you think they should be using Blesta for.
 
I think WHMCS got their act together security-wise, finally. But I don't like their company, I don't like how cPanel runs things either (but use them for server software... because cPanel).
 
I really like Blesta, I met the Blesta guys at multiple Hostingcons, great guys, but Blesta needs to kick it up a notch if it wants to grow and put a dent in competitors' market-share. 
 
I'm still rooting for Blesta, i haven't sold my license, and still pay for updates even if I don't use it. But I wish Blesta would really start focusing on what customers want to use Blesta for, how they use it, how many clicks it takes to get to something, intuitiveness, along with a whole bunch of other things, and start moving development resources towards those pain points first, and worrying a lot less about ancillary stuff.
 
Maybe even provide smaller, quicker updates. When a new feature is built and tested, ship it out. Stop waiting 3+ months to make bigger splashes with releases. You're a smaller company, who should be much nimbler than your bigger competitors. Use that to your advantage. You have the ability to pivot quickly and release things nearly as fast. I don't know why you don't do it. 
 
Like someone once told me, it's fine to give out ideas and roadmaps about where you're going. It's the execution that counts, and few people can do that part well.  

The way he said it is totally inappropriate and lacks respect, but shunning him for an opinion isn't right  
 
I have a fairly large commitment towards Blesta (addon companies), but I can't actually use Blesta for what I need it to do. Do I want to use Blesta? YES. But right now, I'm stuck using WHMCS because of core components that Blesta will not get to until 4.1 at least.
 
The reason I can't use Blesta? Because it would take a lot more money to customize it and bring it up to speed, than it would be to simply use a competing product. And even then, it wouldn't be 100%
 
Let's be honest here guys, the development of Blesta is pretty slow. I'm not sure if the hope was that 3rd party developers would take up the slack, but there's been a really big mis-read on what your customers are using Blesta for, and what you think they should be using Blesta for.
 
I think WHMCS got their act together security-wise, finally. But I don't like their company, I don't like how cPanel runs things either (but use them for server software... because cPanel).
 
I really like Blesta, I met the Blesta guys at multiple Hostingcons, great guys, but Blesta needs to kick it up a notch if it wants to grow and put a dent in competitors' market-share. 
 
I'm still rooting for Blesta, i haven't sold my license, and still pay for updates even if I don't use it. But I wish Blesta would really start focusing on what customers want to use Blesta for, how they use it, how many clicks it takes to get to something, intuitiveness, along with a whole bunch of other things, and start moving development resources towards those pain points first, and worrying a lot less about ancillary stuff.
 
Maybe even provide smaller, quicker updates. When a new feature is built and tested, ship it out. Stop waiting 3+ months to make bigger splashes with releases. You're a smaller company, who should be much nimbler than your bigger competitors. Use that to your advantage. You have the ability to pivot quickly and release things nearly as fast. I don't know why you don't do it. 
 
Like someone once told me, it's fine to give out ideas and roadmaps about where you're going. It's the execution that counts, and few people can do that part well.  

The way he said it is totally inappropriate and lacks respect, but shunning him for an opinion isn't right  
 
I have a fairly large commitment towards Blesta (addon companies), but I can't actually use Blesta for what I need it to do. Do I want to use Blesta? YES. But right now, I'm stuck using WHMCS because of core components that Blesta will not get to until 4.1 at least.
 
The reason I can't use Blesta? Because it would take a lot more money to customize it and bring it up to speed, than it would be to simply use a competing product. And even then, it wouldn't be 100%
 
Let's be honest here guys, the development of Blesta is pretty slow. I'm not sure if the hope was that 3rd party developers would take up the slack, but there's been a really big mis-read on what your customers are using Blesta for, and what you think they should be using Blesta for.
 
I think WHMCS got their act together security-wise, finally. But I don't like their company, I don't like how cPanel runs things either (but use them for server software... because cPanel).
 
I really like Blesta, I met the Blesta guys at multiple Hostingcons, great guys, but Blesta needs to kick it up a notch if it wants to grow and put a dent in competitors' market-share. 
 
I'm still rooting for Blesta, i haven't sold my license, and still pay for updates even if I don't use it. But I wish Blesta would really start focusing on what customers want to use Blesta for, how they use it, how many clicks it takes to get to something, intuitiveness, along with a whole bunch of other things, and start moving development resources towards those pain points first, and worrying a lot less about ancillary stuff.
 
Maybe even provide smaller, quicker updates. When a new feature is built and tested, ship it out. Stop waiting 3+ months to make bigger splashes with releases. You're a smaller company, who should be much nimbler than your bigger competitors. Use that to your advantage. You have the ability to pivot quickly and release things nearly as fast. I don't know why you don't do it. 
 
Like someone once told me, it's fine to give out ideas and roadmaps about where you're going. It's the execution that counts, and few people can do that part well.  

The way he said it is totally inappropriate and lacks respect, but shunning him for an opinion isn't right  
 
I have a fairly large commitment towards Blesta (addon companies), but I can't actually use Blesta for what I need it to do. Do I want to use Blesta? YES. But right now, I'm stuck using WHMCS because of core components that Blesta will not get to until 4.1 at least.
 
The reason I can't use Blesta? Because it would take a lot more money to customize it and bring it up to speed, than it would be to simply use a competing product. And even then, it wouldn't be 100%
 
Let's be honest here guys, the development of Blesta is pretty slow. I'm not sure if the hope was that 3rd party developers would take up the slack, but there's been a really big mis-read on what your customers are using Blesta for, and what you think they should be using Blesta for.
 
I think WHMCS got their act together security-wise, finally. But I don't like their company, I don't like how cPanel runs things either (but use them for server software... because cPanel).
 
I really like Blesta, I met the Blesta guys at multiple Hostingcons, great guys, but Blesta needs to kick it up a notch if it wants to grow and put a dent in competitors' market-share. 
 
I'm still rooting for Blesta, i haven't sold my license, and still pay for updates even if I don't use it. But I wish Blesta would really start focusing on what customers want to use Blesta for, how they use it, how many clicks it takes to get to something, intuitiveness, along with a whole bunch of other things, and start moving development resources towards those pain points first, and worrying a lot less about ancillary stuff.
 
Maybe even provide smaller, quicker updates. When a new feature is built and tested, ship it out. Stop waiting 3+ months to make bigger splashes with releases. You're a smaller company, who should be much nimbler than your bigger competitors. Use that to your advantage. You have the ability to pivot quickly and release things nearly as fast. I don't know why you don't do it. 
 
Like someone once told me, it's fine to give out ideas and roadmaps about where you're going. It's the execution that counts, and few people can do that part well.  

You're the man. You're 100% right, that's the bit I missed. 

See you have missed one important bit I believe... In my opinion and experience it sounds like you have the domain group twice not this:

I want to offer a service addon that is a % of the main package value
 
For example, I have 5 products that are different pricing. Let's say 10 dollars, 20, 30, 40 and 50
 
I want to create 1 option, which would be a % for each. So let's say I want it to be 10% of the main package pricing, the option, if selected with a product would be 1 dollar, 2 dollars, 3-4-5 and so on. 
 
This would avoid creating an option for each product, which gets tedious and hard to manage. 
 
I'm not seeing how to do this right now. Any help?  

thanks guys. I sent a request in to Ken and we'll go from there. 
 
I'm looking for custom themes. I don't want my portals to look like Blesta or WHMCS. 

See: http://www.blesta.com/forums/index.php?/topic/592-display-prices-on-your-website/?hl=display+prices