serge

I hereby award thee     Best Post of the Day 

There is no email template for canceled services, so no email about a canceled service would be sent. There is a task to add an email template for services scheduled to be canceled, but perhaps one for cancelling a service would be good as well.
 
Your scenario is a little bit different, however. You want to include a message in the email template about the cancellation of a specific service, but an email template we create would be generalized and not dependent on the service being canceled. A separate partial email may need to exist to handle the behavior you expect, similar to the Package Welcome Email (e.g. Package Cancel email).

Thanks for the advice.
 
Looks better.

Number 1 but the user information on the left.

In my case, it's more about get paid service activated quick, my cron is 2 mins frequency by the way.

Hi all,
 
Just sharing an approach that can be used in a custom module to check whether a service field value is unique or already in use (e.g. to enforce unique domain names).
public function validateService($package, array $vars=null, $edit=false) { if ($package) $module_row_id = $package->module_row; else $module_row_id = isset($vars['module_row']) ? $vars['module_row'] : null; $row = $this->getModuleRow($module_row_id); //get the service id using a known and guaranteed unique field. this is needed to perform a unique validation of service fields without having the same service that may already have the field to cause validation to fail (e.g. when activating a pending service). $service_id = $this->getServiceIDUsingUniqueServiceField('myUniqueServiceUID', $params['myUniqueServiceUID']); $rules = array( 'domain' => array( 'unique' => array( 'final' => true, 'rule' => array(array($this, "checkUniqueDomain"), $service_id), 'negate' => true, 'message' => Language::_("ModuleName.!error.domain_valid.unique", true) ) ) ); $this->Input->setRules($rules); return $this->Input->validates($params); } // check any service field value exists private function checkServiceFieldValueExists($key, $value, $service_id = null) { Loader::loadComponents($this, array("Record")); $exists = false; if (is_null($service_id)) { $service_id = -1; } $this->Record->select() ->from("service_fields") ->where("service_fields.key", "=", $key) ->where("service_fields.value", "=", $value) ->where("service_fields.service_id", "!=", $service_id); if($this->Record->numResults() > 0) { $exists = true; } $this->Record->reset(); return $exists; } // check domain is unique public function checkUniqueDomain($value, $service_id = null) { return $this->checkServiceFieldValueExists('domain', $value, $service_id); }

No problem mate, yeah it's there when the support manager is installed but if the upload folder permissions or location isn't correct or done after it gets missed.

+1 on naja7host view

package per extension , yes , you can have control of price of every extension .
 
but can you set a different price for renew , transfer , registration ? you can't .
can you offer free domain (extention) + hosting ? and the same extention is paid when it is alone (no hosting)
 
nowadays a lot of new extension in the market , so for me a package per extension can lead to more than 100 package .... so that is a lot for maintain the package under control .

Mujahed graciously signed over the rights of the code to us. We will be going through it to ensure we don't have any concerns over the code base and committing it to Github as a free module. This will include the Tasty cPanel, Tasty Interworx, and DigitalOcean modules.
 
This will allow the community to also help maintain the modules and submit pull requests to us for new features, fixes, or improvements.
 
We may also bring in some of the advanced management functionality into our official modules, and we *may* completely take over and fully support and maintain the digital ocean module.

I ever renamed a payment gateway label, it's had to be done from direct change in database, certainlly in table like gateway

get an new option for client custom field:
 
Get unique custom field string value accross all customer, so when this option is enabled, the custom field form reject an update if this client custom field value ever exist with an other customer.

the instruction typo error you found is from payment gateway website
 
 
for the upload at your blesta:
 
1/ open the unziped archive, go up to : /paymentwall-for-blesta/upload/
 
2/ next upload "components" folder  to the root of your blesta install

at blesta admin panel, check:
 
- enabled currencies at your order form
- enabled currencies at each gateway: /settings/company/gateways/
 
Both Must match

get an new option for client custom field:
 
Get unique custom field string value accross all customer, so when this option is enabled, the custom field form reject an update if this client custom field value ever exist with an other customer.

Agreed also wanna say A Hosting billing not perfect without Advance Domain Manager/management.

greate news, going to test .
 
 
if they ask me what they should do , i will suggest make some new modules wanted by the community .  investing times in modules will bring new clients .

A plugin was developed that allows for services to have their packages reassigned to a package within a different package group. Typically services can only be upgraded/downgraded to another package in the same group, this allows it to be assigned to a package of a different group. The plugin will be included, but not installed by default, starting with 3.6.0 BETA 2. 
 
To install:
Download reassign_pricing.zip Unzip, and upload the reassign_pricing directory to /plugins/ Go to Settings > Company > Plugins > Available and click to Install This will add a new item under "Account Actions" on a client profile page called "Reassign Pricing".
 
Please report any issues or suggestions in the beta forums. Thanks!

the standard ISO is correct .
 
blesta is merging between states and cities in some countries like morocco and italy .

and also, clear blesta cache + clear internet browser cache

we have talked about this subject so many times  ago and we think is the time to talk about it now . i have made a plan to make something special for my need and provide it to the cmmunity , but i have stack with some limitation and some lock of professional advanced skill and lock of time . so what i have do , first i have decided to make the domain manager as a module , and add the registrar as a components inside the module .
 
the registrar wil have a :
- json file to identify the name ,description, version ect ...
- folder for API class
- module.php (that file has the fields that will be used in the addrow in module + the rules validation )
- manager.php (that file will have the available functions for this registrar )
- package.php (that file will include the fields that will be shown in the package creation )
- maybe we can add more files for other uses .
 
 
in the module manager , we add registrar as  a row (addrow) , in the add row , it list all the registrar exist in components folder as a list , when we select a registrar it load the returned fields in module.php .
in the package creation , when we select domain manager , it list the available registrar , when selecting the chosed registrar it can load the required fields by package.php (optional ) .
 
in the client/admin side , we will have a standard function like , name-server, contacts, dns, forwarding , emails ... ect ... the tabs has a relation with the actions available in the registrar or simply if not available show a message of unavailability .
 
so the idea is simple 
 
clients/admins tabs --- communicate with the module , the module forward the call to the registrar module . the registrar module return the response , the module show the response (success or errors) .
 
with this way we have a centralized domain management, and we can maintain 1 module rather than multiple modules .we can add the registrars as we want and we can improves them without touching the module it self .
 
the logic is nearly the same used in the gateways , we laod the gateway class inside the gateway model  .
 
 
 
 
 
 
 
 
 
 

is a bad news, but if mujahed need help in anything we are here .
 
what i suggest is blesta staff negoce with mujahed to get the source code of their plugins, as others can fix/update the code if needed like the cpanel extended .
 
but why is closing ? is the blesta market is not rentable anymore ? or there are some new road of business ?
 
@sixwishlist , the real lesson here if for blesta team , no dev can support blesta for long term  if they not change the target market . the HOSTING industry is the only market that can help blesta grow and grow , for so months ago we request blesta team to take care about hosting market like the domain management , the order form for hosting also . competitor has grow not by the core software , but the module/plugins they have by them or third party , another example is PauloV, it was so happy with the core code and has and still providing plugins/modules for free , like me , just to provide more option to the clients and encourage them switching/using blesta , now is less active , because the main feature he/and me and so others need it not exist after so many months , a better domain management and a good order form for hosting industry . i'm not against blesta ,  but blesta should learn what other say about them , and do what the people need (other can call it cloning functions from others , i call it add the defaults futures  ) .

Thanks for the information. In terms of OpenSRS, there is already a community developed module which you can grab here.
 
In terms of other modules, there are several good developers on the forum here including PauloV, Naja7host, and ModulesBakery (www.modulesbakery.com) that may be able to help.
 
I was looking into Asterisk integration a bit yesterday, I'd love to have it myself, but I don't think the MG Asterisk integration does provisioning does it?
 
In terms of HHVM, PHP 7 (Out in Nov) is probably going to end up effectively replacing it. Still, I will say, you may be able to run Blesta on HHVM in the near future. 

Just to update this topic.
 
Development is still going on. Expect the first public release in October.

I think it's same way:  http://www.blesta.com/forums/index.php?/topic/4117-prevent-loop-blesta-behind-loadbalancer-with-ssl-termination/?hl=termination