jobplease

I'ld like to make a point about what we (as user) expect from next new major release, but i think that a forum is not a good place to communicate with developers and/or to submit issues.
 
Personally, i lost the "pleasure" to sharing on this forum my opinions, suggestions, doubts, ... because i see that Blesta is going to a great direction, but this is not mine. We're european users and there are so many differences and needs between Blesta's market and our;  i understand that Blesta devs think for their bigger market and i appreciate so much their attempts to come with our needs.
 
In same way i think that Paul & co could share their programs, also if they are a small firm. And i would love to see, before next major release, an action to make order and update documentation and this (or better another) issues repository.
 
Now i wait a response "Blesta works fine for me" or "All you want is in dev.blesta.com", but this is not what i try to say.
 
Thanks and sorry for my tedious thought.
 
Achille
 
P.S.: sorry for my poor english

Thanks guys 
 
 
Lol, the comment about confusion was in jest, it was a poke at the hosting industry in general lol. there was a section where she talked about our packages but i ripped it out cuz she nailed it in a different take and there were some errors in the take i used despite it being the best overall. I'll be incorporating it into a second video later in the week though =]

I like them both. Awesome work !!

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); }

Just wondering if this plugin is safe to use with Blesta ?

The issue is with Xcache and I have disabled it for the domain. Now the mentioned link is working fine.

The issue is with Xcache and I have disabled it for the domain. Now the mentioned link is working fine.

hi there,
 
I am trying to add pop emails for each department.
 
The PHP Mailparse PECL extension is required for parsing email tickets.
 
 

Thank you,.

fixed close please