Abhineet

Hi, I have this theme in my computer about half year, this theme is of a cancelled project and I will not use the theme anymore, for this I will decided share the theme to the community, this can be useful for something.
This theme not will receive updates. If you want a customization you can send me a PM to get a quote.

cloud.zip

Thanks Mike, will try to get in touch with them.

Thanks Mike, will try to get in touch with them.

Ohh.. Thank you for your response though.
Hi Paul,
I am not a reseller for TheSSLStore.  

Have a look at my hack: 
it should work on GoGetSSL just have to rename the text to work on the GoGetSSL, the number should be obvious to people though.
 

Hello Everyone,
 
It's my first post here so I'd like to introduce myself.
 
This is Abhineet a Web Designer and Hosting provider from India.
 
Hope to get best services from Blesta for our business(es).
 
Thank you for reading.
 
Best Regards,
Abhineet

Hi Guys,
 
I think it's one of the most desirable Feature Request which we need in Blesta. I had been told by Paul that there is a plan to add this feature but not sure if it's added to Core yet.
 
It'd be nice if affiliate will have features like :
 
1) They can generate their own coupons [which will give extra discount to the buyer] from their own earnings.
 
2) No promotional links like "aff.php?id=102" as mostly users don't want to join sites using affiliate links and also its not allowed in most money making forums.
 
3) I don't have in my mind yet so any suggestions which will boostup this are "Welcome".
 
Thanks,
Abhineet

This has been fixed in CORE-774 for v3.0.4.
 
To patch yourself, update /app/models/invoices.php (line 885):
 
Replace:
// Increment the used quantity for all coupons used foreach ($coupons as $coupon_id => $coupon) $this->Coupons->incrementUsage($coupon_id); return $invoice_id; With:
// Increment the used quantity for all coupons used foreach ($coupons as $coupon_id => $coupon) $this->Coupons->incrementUsage($coupon_id); // Update invoice totals $this->updateTotals($invoice_id); return $invoice_id;

We have a task to add this feature to the cPanel module. Are you suggesting it be added for a specific module?

Hello,
 
I'm trying the following:
One service costs $ 5.00 incl. tax, that's $4.20 excluding tax. This service is created via package (using Universal Module).
Now I want to offer a coupon for the whole $5.00 amount.
But when the coupon is now applied to the service, it's calculated down to $4.20 - so the client has an invoice about $0.80 instead of free.
(Per order form / api)
 
I also tried setting the coupon to $5.95 - this would be $5.00 + tax. But this one is also calculated down to the $4.20 of the line item.
 
Request:
A. Allow coupons to be taxable. Maybe a checkbox when creating the coupon. This should be applied automatically.
B. (Much better): Apply the coupon to the line item before it is taxed. This would make more sense to me, because nobody has to tax $0.00 - right?
 
Thanks!

You can submit a ticket to invoice you for it. I don't know if there's a order form for it, as I got mine by exchanging a license to a addon license.
 
You only need one license per Blesta installation. Multi-companies are addon licenses which are attached to the main license.
The best I can say is this
 

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.

Most upgrades it will be safe to skip the config directory, but you'll want to compare the original previous version file to see if there are any differences.
 
We are planning to implement easy updates through the interface. (Click to download and upgrade) It'll be a little while for this, but when we do it it's likely it would only overwrite files that have changed.

It would be PERFECT if each client group configured could have it;s OWN customizable Welcome Email. Many of us have different "kinds' of customers and this would greatly improv the customer experience.
 
Bob

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.

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.

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've already said they plan on building a knowledge base module and I'm sure that include everything requested in this thread.
 
It will be interesting to see if the support module and knowledge base module tie into each other like described by CubicWebs.

I would like a coupon tier please in the future, where we can make a coupon just for a month or a year. Or even valid for a month or a year. Maybe a tick box feature with the day, month, year, one time. Or even a auto generator so it pulls what values they are.
 
So maybe one package has this:
 
[  ] 2 day
[  ] 4 month
[  ] 12 month
[  ] 1 year
[  ] one time
 
Because at the moment if a user say wants to buy hosting from you. They find a coupon for 60% off your package. But accidentally clicks on the yearly price. They enter the coupon and BAM they now get 60% off your yearly price. Even though it's not valid for it.
 
Just a little inside of my feature request

CORE-494  for clients resetting cPanel password in the client area. Will take a look at client access to email log.

Contact logins with ACL permissions is actually on our list, CORE-627 and is tentatively schedule for 3.2.
 
We will considered sponsored development for core features, however we will only do those if we already agree that we want to include it. Same really goes for extensions too. We try to prioritize development based on demand, and in all honesty someone willing to part with some cash says a lot about how serious they are about throwing their support behind something. It's possible to have 100 votes for a feature that nobody will really even use but sounds cool. We would rather build the feature that 10 people would actually use than the one 100 people voted for but wont use.

I just wanted to chime in on the module / marketplace discussion. I'll admit that I only read about 75% of the responses, as they were quite lengthy but I think I have a good understanding. If there's anything you want me to clarify, or think I overlooked, please let me know.
 
1. We want to support 3rd party developers as best as we can. We can't build everything for every niche. We are also aware that these developers have a financial incentive to build modules that we won't turn around and build ourselves. We can't guarantee this will never happen, but if there is any question, we encourage developers to ask us. We'll be as honest as possible about our future plans. Using ModulesGarden as an example, it's highly unlikely we'll develop an extended cPanel module anytime soon with the functionality they have built in because a) it already exists at a reasonable price, it fills the demand, and c) there are other areas of demand we can focus our efforts to move forward. Us building a cPanel extended module now would be a lateral move, and take away from much needed forward momentum.
 
2. We have partially built "The Marketplace", which is intended to be a marketplace of extensions for Blesta by 3rd party developers, and, at times, ourselves. When this is ready, 3rd party developers will be able to list their free and paid extensions in the marketplace.
 
3. There are 3 types of extensions we will develop. a) free and included in the core, free and available through the marketplace, and c) paid. We will never take our free modules, and start charging for them on an a-la-cart basis. If they start out included, they will stay that way. (Unless for example the company or panel we've integrated with disappears and we simply remove it altogether.)
 
4. An example of a paid extension that we will be releasing is the Licensing Module / Licensing Manager Plugin combo. This is the same system we use to license Blesta, and we will be releasing it as a paid extension. The reason this will be a paid extension is because it serves a smaller market segment. Not many people need it. There will be other paid extensions like this down the road that either serve a particular niche, segment, or enterprise, but we will not be moving to an everything a-la-cart system. We will also not be moving to a limited feature module, pay more for extended feature model to upsell people.
 
I hope this helps clarify our position.

I'm against this completely.  If I update a ticket I want it going out immediately because I work in a mission critical environment where seconds count.  As far as editing I'm going with Paul on this one... the email would be sent out via email so even if you edited the ticket that would be inconsistent.  Unless an "Edit" email want out to them but then why not just update the ticket again with the correction.
 
The ticketing system is nothing other an a fancy email client.  I treat them like emails because you can't edit emails either.
 
There's my input.

CORE-747, tentatively scheduled for 3.3.