Leaderboard

tio hide it from the client side use my toolbox plugin and : Add Custom css simple pages : client side Markup to set in : head tag CSS To Add : #tax_id {display:none} [for="tax_id"] { display: none;} Save .

I made a spreadsheet showing the extensions supported and their prices for several registrars. It's a few months out of date though. https://docs.google.com/a/michaellawton.co.nz/spreadsheets/d/1N4X--5eBkme8yax36Tk2qJdPWvG85ruXcxM6GA6kyzs/edit?usp=sharing

when the client click the cancel button , 3 option is displayer , the last one Do not cancel . this last one logically should not displayed in activer service , it should be displayed only if the service si set cancel At End of Term .

@MariusB, what version of Blesta are you running? The 3.3.0 official build should include the latest Multicraft module which addressed this issue. Thanks @naja7host

Currently when using the API to create a service with a coupon ID defined it will fail to import. I've managed to identify why and come up with a fix for my scenario. Error example: stdClass Object ( [error] => stdClass Object ( [message] => An unexpected error occured. [response] => SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ''(60)' AND `coupons`.`id` = '1' GROUP BY `coupons`.`id`' at line 1 ) ) Here's an example of my $vars array: Array ( [vars] => Array ( [package_group_id] => 1 [pricing_id] => 178 [client_id] => 4 [status] => active [coupon_id] => 1 [override_price] => [override_currency] => [module_row_id] => 1 [date_canceled] => [date_added] => 2013-08-15 00:00:00 [date_renews] => 2014-11-15 00:00:00 [use_module] => false [quantity] => 1 [ip] => 1.2.3.4 [hostname] => removed.com [configoptions] => Array ( [625] => No [618] => No [619] => No [620] => No [624] => Yes [613] => No [623] => Yes [615] => Yes [622] => No [616] => No [617] => No [621] => No [612] => No ) ) [packages] => 60 ) As you can see, I have coupon_id defined to "1". This generates the following query to MySQL when actually running the API call: SELECT `coupons`.`id`, `coupons`.`code`, `coupons`.`company_id`, `coupons`.`used_qty`, `coupons`.`max_qty`, `coupons`.`start_date`, `coupons`.`end_date`, `coupons`.`status`, `coupons`.`type`, `coupons`.`recurring`, `coupons`.`limit_recurring` FROM `coupons` INNER JOIN `coupon_packages` ON `coupon_packages`.`coupon_id` = `coupons`.`id` WHERE `coupons`.`company_id` = '1' AND `coupons`.`status` = 'active' AND (`coupons`.`max_qty` = '0' OR `coupons`.`max_qty` > `coupons`.`used_qty`) AND (`coupons`.`start_date` <= '2014-10-13 17:32:33' OR `coupons`.`start_date` IS NULL) AND (`coupons`.`end_date` > '2014-10-13 17:32:33' OR `coupons`.`end_date` IS NULL) AND `coupon_packages`.`package_id` IN '60' AND `coupons`.`id` = '1' GROUP BY `coupons`.`id` Now there's one big problem with this query. It will fail because the very last "IN" statement isn't valid. AND `coupon_packages`.`package_id` IN '60' AND `coupons`.`id` = '1' GROUP BY `coupons`.`id` When using IN, the values have to be comma-separated within parentheses. When correcting this last part of the query to this it works: AND `coupon_packages`.`package_id` IN ('60') AND `coupons`.`id` = '1' GROUP BY `coupons`.`id` Now the fix: In your apps/models/coupons.php around line 153: Change if ($packages) { $this->Record->innerJoin("coupon_packages", "coupon_packages.coupon_id", "=", "coupons.id", false)-> where("coupon_packages.package_id", "in", $packages)-> group("coupons.id"); } to if ($packages) { $this->Record->innerJoin("coupon_packages", "coupon_packages.coupon_id", "=", "coupons.id", false)-> where("coupon_packages.package_id", "=", $packages)-> group("coupons.id"); } The change is from "in" to "=" on the 3rd line of this code.

Except that it isn't currently called "Cancellation Options", it's called "Cancel Options". I do see your point about "Cancel", though. My original request was to change the button to "Cancellation Options", because I think that "Cancel Options" implies "cancel the options". Edit: By way of illustration: Cancel Package = cancel the package Cancel Service = cancel the service logically, then Cancel Options = cancel the options This is why I'm advocating to change the button text to "Cancellation Options"

You can open a ticket and when the new version is released i will take care of this: https://www.modulesbakery.com/oven/baked/plugin/support_manager/client_tickets/add/1/

Hi There, A new version of our DigitalOcean module will be released this Wednesday: https://twitter.com/ModulesBakery/status/521642951869353984 The next version will include the bug fix and new features added based on some users requests.

how can I transfer domain from admin panel?? Using add service always perform register domain.

.row .col-md-3 .list-group li:first-child {diplay:none;} Should be right. Think you missed the 'li' part

Logicbox -- resell.biz good interm of support and prices , but they have a high prices in some extentions.

Anyway , You can change it from language files

Resolved! I will explain how I fixed these email issues, but first I want to acknowledge that it was ultimately about my server’s configuration, not a problem with Blesta. I also thought I should give a lot of detail here, in case it helps anyone else experiencing these issues. For reference, I’m on a shared hosting reseller account using cPanel. Other systems are likely a bit different. Additionally, Blesta is installed in the webroot of the dev subdomain. Part 1 - Mail piping I think this is more of an issue for people who don’t fully control their server, such as shared hosting resellers, because our options for changing server defaults are limited. As Blesta’s manual states, “The Support Manager requires the MailParse PHP extension in order to parse tickets sent in through email.” Since Mailparse was not available on my server by default, I asked my provider to install Mailparse in my cPanel account and add a custom php.ini file in my dev directory, the path to which I then defined in the Blesta .htaccess file with SuPHP_ConfigPath. SuPHP_ConfigPath /home/username/public_html/dev/ This works fine for anything accessed in a browser, so when I set up a support department to use email, Blesta didn’t give me any errors. However, it doesn’t necessarily work for commands run via the command-line interface (aka CLI), such as the cron automation used for POP/IMAP retrieval, or the pipe.php script used for email piping. This all depends on your server’s PHP configuration. I had seen references to this in other posts, but I don’t recall seeing specific examples of potential solutions. Since I’d never had to deal with this particular issue in my other web applications, I dismissed it as being irrelevant to my situation. Wrong! My provider’s support team finally realized that my custom php.ini, and therefore Mailparse, wasn’t being used by the cron or pipe.php. For the cron job, I was able to rectify this by using php -c path to include the custom php.ini. New cron: /usr/local/bin/php -c /home/username/public_html/dev/myphp.ini -q /home/username/public_html/dev/index.php cron For pipe.php, it was a bit more challenging, because I continued to get a bounce error after I appended -c /home/username/public_html/dev/myphp.ini to the hashbang that cPanel had added to the beginning of the script when I set up the mail forwarder to pipe. Eventually, I found this post, which explained that PHP apparently only allows one argument in the hashbang. I finally got it to work by concatenating -q -c and path into one argument. New pipe.php hashbang: #!/usr/local/bin/php -qc/home/username/public_html/dev/myphp.ini Success with email piping! I had a working system, so I could have stopped there. But, I also wanted to figure out why POP/IMAP still wasn’t working, even though I didn’t really need it because I now had piping. Part 2 - POP/IMAP Retrieval The above cron tweak should have fixed my POP/IMAP retrieval issue, so I was surprised when Blesta still didn’t retrieve email. Again, my provider’s support team found the problem. This time, it was a mail hostname issue that appears to be due to a bug in cPanel. When I created the dev subdomain, cPanel’s mail client configuration page said to use mail.dev.mydomain.com for the incoming server. However, cPanel failed to create the corresponding DNS record, so checking mail using that hostname failed. I didn’t catch this earlier, because I was using a webmail client that accepted my username and password, but didn’t require the server/host name. All I had to do was switch Blesta's support department to use my main domain’s mail hostname (mail.mydomain.com) or the server’s generic one. Problem solved! All Blesta mail is now flowing as it should, whether incoming or outgoing, piped or retrieved via POP/IMAP.

Paul is this enought ++1 ?

hi,

let say i have package X with 10$ , i want to make it 8$ for just some clients . the acual solution is to make duplicated package and pass the orderlink just for this client . or we should give him discount coupon . the probleme with this , if the client give the coupon to other he can go with , or if the client pass the url to other he can order this service . also we need some sort of transparency in our order form , order page for all , only if the client is logged the price change . yes is maybe complexe , or it maybe ned ajust a some sort of reflexion and making the right way todo it with some few lines .

You can try my workaround to this issue at using Universal Module for dedicated servers for instance (you need to let the user know what's their IP address, assigned after the order is done) [blesta 3.2.1] Universal Module Workaround: Show Service Fields At Client Panel [blesta 3.2.1/3.3] Universal Module Workaround 2: Hide Certain Service Fields From Being Shown On Order Page Both should work with blesta 3.3

I think add API Key password (encrypted) and IP allow option Thank you

Thanks for clarifying. I think the issue has to do with a pro forma invoice being paid (and converted to an invoice) before it is sent, which ends up removing it from the list of invoices to deliver. I'll take a look at fixing this as apart of CORE-1465.

No , i have stopped publishing released for the reloaded module until v3.3 or maybe until the new domain module ; i get some free time to make a search in this , as we also need it , i have arrived to a working solution , now in the admin area you can select register or transfer , then the auth-code box will appear ,the tweak is the fallowing , change the getAdminAddFields function with this one public function getAdminAddFields($package, $vars=null) { // Handle universal domain name if (isset($vars->domain)) $vars->{'domain-name'} = $vars->domain; if ($package->meta->type == "domain") { // Set default name servers if (!isset($vars->ns1) && isset($package->meta->ns)) { $i=1; foreach ($package->meta->ns as $ns) { $vars->{"ns" . $i++} = $ns; } } // Handle transfer request if (isset($vars->transfer) || isset($vars->{'auth-code'})) { return $this->arrayToModuleFields(Configure::get("Logicboxes.transfer_fields"), null, $vars); } // Handle domain registration else { $fields = array( 'transfer' => array( 'label' => "Domain Action", 'type' => "radio", 'value' => "1", 'options' => array( '1' => "Register", '2' => "Transfer", ) ), 'domain-name' => array( 'label' => Language::_("Logicboxes.transfer.domain-name", true), 'type' => "text" ), 'auth-code' => array( 'label' => Language::_("Logicboxes.transfer.auth-code", true), 'type' => "text" ) ); $module_fields = $this->arrayToModuleFields(array_merge($fields, Configure::get("Logicboxes.nameserver_fields")), null, $vars); if (isset($vars->{'domain-name'})) { $tld = $this->getTld($vars->{'domain-name'}); if ($tld) { $extension_fields = array_merge((array)Configure::get("Logicboxes.domain_fields" . $tld), (array)Configure::get("Logicboxes.contact_fields" . $tld)); if ($extension_fields) $module_fields = $this->arrayToModuleFields($extension_fields, $module_fields, $vars); } } $module_fields->setHtml(" <script type=\"text/javascript\"> $(document).ready(function() { // Set whether to show or hide the ACL option $('#auth-code_id').closest('li').hide(); if ($('input[name=\"transfer\"]:checked').val() == '2') $('#auth-code_id').closest('li').show(); $('input[name=\"transfer\"]').change(function() { if ($(this).val() == '2') $('#auth-code_id').closest('li').show(); else $('#auth-code_id').closest('li').hide(); }); }); </script> "); return $module_fields; } } else { return new ModuleFields(); } } is the same almost for all other registrar modules , just change the language to your own use .

Thanks mike . i have re-assigned the ACl and re-saved the group staff and the support departement and support staff . worked now . i think the admin (full admin) should by default have access to all without permission

i think all blesta people need to have all options/functions of both support manager native and pro combined into one and have options settings all configurable so if people dont like something they may disable/enable if they want to