Jump to content

Squidix Web Hosting

Members
  • Posts

    109
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Squidix Web Hosting

  1. I have this same issue.

     

    Trying to change a hostname, I get "An internal error occurred, or the server did not respond to the request", and in the log I see that with no response, I also see this:

     

    Input

    vps.srvon.com|listtemplates
    a:1:{s:4:"type";N;}

    Output

    vps.srvon.com
    <status>error</status><statusmsg>Type not found</statusmsg>

    In solusvm API log - it does not show hostname call at all.

     

    Blesta log DOES show hostname call.

    |vserver-hostname
    a:2:{s:8:"hostname";s:13:"XXX";s:9:"vserverid";s:2:"48";}
    
  2. Price overrides are a pain when you need to change terms, because you first have to change the package/pricing, whatever you want to call it, then do the override.

     

    Moreover, you can't override to a term that's not available with the package. So if 1 person wants X billing cycle, you have to add a X billing option to the package, which in some cases is not doable.

     

  3. I've done this, pretty roughly.

     

    ./app/models/services.php - add this method 

    +	/**
    +	 * Resends a welcome email.
    +	 *
    +	 * @param int $service_id The ID of the service to resend the welcome email for.
    +	 */
    +	public function resendWelcomeEmail($service_id) {
    +	
    +		extract($this->getRelations($service_id));
    +		
    +		// Resend the service's welcome email.
    +		$this->sendNotificationEmail($service, $package, $service->client_id);
    +		
    +	}
    
    

    Replace in getActions method:

     	public function getActions($current_status = null) {
     		
     		$actions = array(
    +			'resend_welcome_email' => $this->_("Services.getActions.resend_welcome_email"),
     			'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 "resend_welcome_email":
    +								$this->Services->resendWelcomeEmail($service->id, $this->post);
    +								break;
     							case "suspend":
     								$this->Services->suspend($service->id, $this->post);
     								break;
    
    

    ./clients/language/en_us/services.php

    +$lang['Services.getActions.resend_welcome_email'] = "Resend Welcome Email";
     $lang['Services.getActions.suspend'] = "Suspend";
     $lang['Services.getActions.unsuspend'] = "Unsuspend";
     $lang['Services.getActions.cancel'] = "Cancel";
    
    
  4. We are going to improve the staff service management page, likely breaking it up into additional tabs as the default "Basic Options" tab has too much going on with it from features added since 3.0. An "Advanced" tab or similar may be beneficial for these kinds of actions, and possibly some other options not currently available.

     

    I wouldn't necessarily go that far, all I need is the ability to run the basic module commands in the basic options tab without messing with blesta data.

     

    You have abstract methods for all of this on the Module class. A simple passthrough without the extra logic in the service layer would do the trick. No actual new code, I would think.

     

    Strip the extra logic out of the Services model class and it's done. For example termination would just be (roughly) line 1470-1487 of the Services class, plus validation and logging (both already there).

  5. Self explanatory.

     

    This is how WHMCS works. It's intuitive, it's quick, and the only downside is a negligible performance penalty. Account info (domain/username) is either #1 or #2 in search volume for pretty much any hosting company, next to client names/emails.

     

    Also, the first and pretty much only thing I want to see when searching services, service labels, are not even displayed in service search results.

     

  6. I'd like to get some community feedback on this as the devs don't seem interested in doing it.

     

    cPanel usernames are restricted to 8 chars by Blesta. This is crazy. Every single hosting company in the world with more than a handful of customers has at least one cPanel user that was migrated in or something similar with a username of more than 8 chars. cPanel doesn't even enforce this restriction, so resellers constantly go well over 8 chars for their cpanel accts.

     

    This really isn't Blesta's problem to be enforcing. It's cPanel's. If they want to enforce it let them do so, without making it impossible to bring in old data. Pretty much everyone who uses Blesta is going to have to increase this at some point in time with a code change.

  7. Multiple groups would allow more control, but what if on the "Add/Edit" custom field form, the Client Group dropdown had an "All Groups" option? I wonder how difficult it would be for such an option to be observed by the rest of the system. When fetching custom fields for a client group, fetch ones that match all/null/whatever the field is called *and* ones specific to the group.

     

    I need this, preferably in the way you've just described. Let me know if you want Alex to do it and get you a patch.

  8. Looking good, thanks for sharing!  :blesta:

     

    I also like the client # in the header. I believe we have a task to add that in there someplace.

     

    I'm just using $pageTitle and stripping the client number off the other pages (in my opinion it shouldn't be in the title of every page like it is now).

  9. You can clone it, and delete the companies you don't want sure. You'll just have data from the other companies hidden in the database, but if it's all your data, and you aren't selling one of the companies to a 3rd party then I suppose it doesn't matter too much.

     

    I'd need it to be clean.

     

    But presumably everything attaches to a company at some point, even if I have to do join queries to link everything back to the company, I guess I can do it.

  10. There's a lot to consider. We have future plans to implement a Blesta -> Blesta importer for this purpose. This would allow people to move companies between installations, so addon -> standalone, or addon -> addon, or standalone -> addon, just moving companies. It isn't very high on the priority list at the moment though, so I don't have an ETA for you.

     

    Any reason I can't just pull from the database by company ID and make a new database?

     

    Or clone the entire thing, then delete the companies I don't need in each instance.

  11. So is not my road . I always try to find solutions far form the core files .

    But anyway , you can post your modifcations , there are a lot of users has are ready to hack core files to get what they need .

    Thanks for your contribution .

     

    This isn't something you can do without modifying the core files. Coupon logic is hard coded.

     

    Will post shortly.

×
×
  • Create New...