Squidix Web Hosting

This is yet another thing that I have to dig in the database to do and can't delegate to my staff. Just was reminded to post by having to do it for a client.

And despite all of that, WHMCS is the industry leader. Blesta would be wise to take as many cues as possible from WHMCS. > See the big picture, maybe Microsoft should copy Sony because more people like the PS4. Well, yeah.

Ridiculous. They should do it by hand. A little long division never hurt anybody. GO TO THE ANT, O SLUGGARD; CONSIDER HER WAYS, AND BE WISE. WITHOUT HAVING ANY CHIEF, OFFICER, OR RULER, SHE PREPARES HER BREAD IN SUMMER AND GATHERS HER FOOD IN HARVEST. HOW LONG WILL YOU LIE THERE, O SLUGGARD? WHEN WILL YOU ARISE FROM YOUR SLEEP? A LITTLE SLEEP, A LITTLE SLUMBER, A LITTLE FOLDING OF THE HANDS TO REST, AND POVERTY WILL COME UPON YOU LIKE A ROBBER, AND WANT LIKE AN ARMED MAN. PROVERBS 6:6-11 MAY YOU BURN FOR ETERNITY

We should just carve each package's details into a stone. When someone comes to the site, they fill in their address and pay $11 to have the stones shipped (thank god for USPS flat rate). Then they can pick one and carve in the configurable options and send it back.

Okay let me clarify. I think we need a "hidden" type that DOES show up in admin menus but can't be ordered - inactive could be dropped from admin menus. Or leave "inactive" as is (basically like hidden) but add the soft delete option that will hide it even the admin (but still let you edit services).

I think soft delete would be more like regular delete, to the user. Inactive would basically just mean "unorderable" like it does now. I like #2. Don't like the setting idea. Changing the meaning of an entity property based on a setting, doesn't feel right.

Would like the ability to turn an unpaid invoice back into a draft.

That's fine, it should just be available. I'm in a very competitive market and we have hundreds of clients paying different rates, some higher than package some lower. I can count on one hand the number of times we've been approached about it.

> Maybe have a poll? Any poll done here is not going to be representative of the general public. We're all early adopters and tinkerers, just look at this thread. > Prices have been going down over the years, and if we didn't extend that to existing customers they would think we are screwing them over, and act accordingly. No, in the real world 95% of people won't say a word. But let's not turn this into an argument about how companies should and should not operate in order to work within the confines of the software in its current state. There is a very valid case for this type of flexibility, and the fact that every other system makes this easy speaks for itself.

> alot of providers update prices for all if the product remain with the same conditions and tem and caracteristiques . Out of the blue? I don't know who you're dealing with. I never see this. It happens with renewals. But that's not arbitrary. Many of the big companies (godaddy, bluehost, etc) get you on board at a few dollars a month, and bump it up to ~8.99 after first cycle. This should be done with a coupon. Not a package pricing change. It's an entirely different concept and it has nothing to do with what I'm talking about. I have NEVER had a hosting company come to me out of the blue and say "hey, we're changing your pricing". Despite multiple pricing changes for their packages. > and what about if a client find the price for package X in your website is Z and he is paying other amount for it ? what will be your answer ? That has nothing to do with the technical request I'm making. That's a business question which is my problem. I'm not adapting my business to work around the software. You're arguing a business case which for us (and many others) the fact that we will have to deal with this is a foregone conclusion. > the proffetional way is to create another product/package if you want to play with turnover . It's not another package, conceptually, it's the same exact thing at a different price. It also screws up my reporting and junks up the system with needless packages. Not an option for us. If I want to do a bulk pricing change, that should be the manual action. Blesta has the edge case mixed up with the normal behavior.

99% of companies will not change pricing on old customers. Talk about a way to increase turnover... And yes, this is a very moderate way to do it, and it's one of the solutions I had in mind. When updating the package, choose whether or not to update pricing for pre-existing services.

Yeah, I don't use software to prove to the world how cool and non-lazy I am. This is a joke of an argument, give it a rest. I understand based on prior arguments that you enjoy sitting around copying and pasting things but most of us don't. The culture around here is strange to say the least.

Because it makes wayyy more sense than the current setup? Go survey 100 hosting companies and ask them how many times they change package pricing vs how many times they arbitrarily change prices on their existing customers. Who does that? Nobody, that's who. 99 to 1, if you're lucky. Not sure where you guys came up with this but it definitely wasn't from asking hosting companies.

If it's not right there on the manage page, it defeats the purpose. In this case I might as well just copy and paste the password and email it out, since I have to navigate to the plugin. Can't stress enough that this should be core.

I don't want to wind up with some ridiculous number of packages. If two clients are on the same package, I want them to be on the same package. There is a reason that virtually no other system works like this. To be frank, this way of doing things is crazy.

That still doesn't do it. The bulk of orders are not placed by admins. As to the latter, that's 1000x rarer than the reverse. If anything, that should be the thing that requires manual intervention. What web hosting company does this? I've never seen it. Not once.

This really should be core functionality if you ask me.

That was actually my first instinct but I figured that'd be more work than just having a setting to show the PDF.

Yep, should be default. I'd say [Ticket ID: number] SUBJECT -hash-

Very much self explanatory.

Having these things force download is a huge pain. This has been discussed - http://www.blesta.com/forums/index.php?/topic/1131-view-pdf-invoices-from-within-browser/ Cody suggested a setting to accommodate the fact that this may cause issues with some browsers.

This discount type would override the price of any package to a predefined price. Opening this thread to gauge interest, patch is already submitted. One common use case is $X trial periods that apply to multiple packages.

"1 year for 1 @" should probably be something like "1x 1 year @". Maybe with the "1x" omitted if quantity is actually 1.

Holding off on word from Blesta devs to see if we can get this included.

Termination would go something like this. COMPLETELY UNTESTED. DO NOT TRY AT HOME. ./app/models/services.php - add this method + /** + * Terminates a service. + * + * @param int $service_id The ID of the service to terminate. + */ + public function terminate($service_id, array $vars = array()) { + + extract($this->getRelations($service_id)); + + // Terminate the service. + + if (!isset($this->ModuleManager)) + Loader::loadModels($this, array("ModuleManager")); + + $module_data = $this->getModuleClassByPricingId($service->pricing_id); + + if ($module_data) { + $module = $this->ModuleManager->initModule($module_data->id, Configure::get("Blesta.company_id")); + + if ($module) { + // Set the module row used for this service + $module->setModuleRow($module->getModuleRow($service->module_row_id)); + + $service_info = $module->cancelService($package, $service, $parent_package, $parent_service); + + if (($errors = $module->errors())) { + $this->Input->setErrors($errors); + return; + } + + } + + } + + } Replace in getActions method: public function getActions($current_status = null) { $actions = array( + 'terminate' => $this->_("Services.getActions.terminate"), 'suspend' => $this->_("Services.getActions.suspend"), 'unsuspend' => $this->_("Services.getActions.unsuspend"), 'cancel' => $this->_("Services.getActions.cancel"), ./app/controllers/admin_clients.php switch ($this->post['section']) { case "action": switch ($this->post['action']) { + case "terminate": + $this->Services->terminate($service->id, $this->post); + break; case "suspend": $this->Services->suspend($service->id, $this->post); break; ./clients/language/en_us/services.php +$lang['Services.getActions.terminate'] = "Terminate"; $lang['Services.getActions.suspend'] = "Suspend"; $lang['Services.getActions.unsuspend'] = "Unsuspend"; $lang['Services.getActions.cancel'] = "Cancel";