Jump to content

Blesta Addons

Alpha Developers
  • Posts

    4,868
  • Joined

  • Last visited

  • Days Won

    390

Posts posted by Blesta Addons

  1. On 2/15/2017 at 5:38 PM, Tyson said:

    I'd recommend using an acronym. These keys are meant to be short and concise. 64 characters isn't very short

     

    On 2/15/2017 at 6:25 PM, Licensecart said:

    like paypal_custom_1 small and you know what it is

    i can even use pc1 and is done !!!

    the request is not how i want to use my settings , the request was to make the KEY support more than 32 chars , that is .

    also the maximum key to 64 will not affect any aspect of blesta working, it help other devs to make their own key settings as they want .

     

     

  2. the plugin cancel unpaid order has a option to delete from database the unpaid service . you can set it and is safe .

    also exist another plugin called delete voided invoice http://blesta-addons.com/plugin/store/main/item/8/ .   this plugin has a option to delete from database a voided invoice, also you can mass delete invoices with some old days ; you can use it is also safe, just make sure  that your country law doesn't prohibit it .

     

  3. 33 minutes ago, Paul said:

    We are planning to maintain it for v4 forward. Keeping that in mind, feel free to submit pull requests on Github, the extension is open source.

    i have sent the request pull for the local edit .

    now i found that the response from placeFullOrder() is not returning the domain to add it in the service field .

  4. i have added the fucntion to allow local edit, it can be added to the module for next release .

     

        /**
         * Returns all fields to display to an admin attempting to edit a service with the module
         *
         * @param stdClass $package A stdClass object representing the selected package
         * @param $vars stdClass A stdClass object representing a set of post fields
         * @return ModuleFields A ModuleFields object, containg the fields to render as
         *  well as any additional HTML markup to include
         */
        public function getAdminEditFields($package, $vars = null)
        {
            Loader::loadHelpers($this, ['Html']);
    
            $fields = new ModuleFields();
    
            // Create domain label
            $thesslstore_fqdn = $fields->label(Language::_('ThesslstoreModule.tab_client_cert_details.domains', true), 'thesslstore_fqdn');
            // Create domain field and attach to domain label
            $thesslstore_fqdn->attach(
                $fields->fieldText('thesslstore_fqdn', $this->Html->ifSet($vars->thesslstore_fqdn), ['id'=>'thesslstore_fqdn'])
            );
            // Set the label as a field
            $fields->setField($thesslstore_fqdn);
    
            // Create order id label
            $thesslstore_order_id = $fields->label(Language::_('ThesslstoreModule.tab_client_cert_details.store_order_id', true), 'thesslstore_order_id');
            // Create order id field and attach to order id label
            $thesslstore_order_id->attach(
                $fields->fieldText('thesslstore_order_id', $this->Html->ifSet($vars->thesslstore_order_id), ['id'=>'thesslstore_order_id'])
            );
            // Set the label as a field
            $fields->setField($thesslstore_order_id);
    
            // Create token label
            $thesslstore_token = $fields->label(Language::_('ThesslstoreModule.tab_client_cert_details.token', true), 'thesslstore_token');
            // Create token field and attach to token label
            $thesslstore_token->attach(
                $fields->fieldText('thesslstore_token', $this->Html->ifSet($vars->thesslstore_token), ['id'=>'thesslstore_token'])
            );
            // Set the label as a field
            $fields->setField($thesslstore_token);
    
            return $fields;
        }
    	
        /**
         * Edits the service on the remote server. Sets Input errors on failure,
         * preventing the service from being edited.
         *
         * @param stdClass $package A stdClass object representing the current package
         * @param stdClass $service A stdClass object representing the current service
         * @param array $vars An array of user supplied info to satisfy the request
         * @param stdClass $parent_package A stdClass object representing the parent
         *  service's selected package (if the current service is an addon service)
         * @param stdClass $parent_service A stdClass object representing the parent
         *  service of the service being edited (if the current service is an addon service)
         * @return array A numerically indexed array of meta fields to be stored for this service containing:
         *  - key The key for this meta field
         *  - value The value for this key
         *  - encrypted Whether or not this field should be encrypted (default 0, not encrypted)
         * @see Module::getModule()
         * @see Module::getModuleRow()
         */
        public function editService($package, $service, array $vars = null, $parent_package = null, $parent_service = null)
        {
            // Set fields to update locally
            $service_fields = ['thesslstore_token', 'thesslstore_order_id', 'thesslstore_fqdn'];
            foreach ($service_fields as $field) {			
    			// check if the field is set and is not empty
    			if (isset($vars[$field]) && $vars[$field] != '') {
    				$service_fields[$field] = trim($vars[$field]);
    			}
            }
    		
    		$fields = []; 
            foreach ($service_fields as $key => $value) {
                $fields[] = ['key' => $key, 'value' => $value];
            }
    
            return $fields;
        }

     

  5. i have made a look at the module code,  i found that the domain is set in the service fields but after the client is completing the ssl generation process successfully, but in the live mod is not set , maybe it's a bug , some client has completed the ssl process feneration and is active now , but the thesslstore_fqdn is empty .

    the module has a email template in his code, but i cant see it in the package !!! not sure why .

    note i use the module in v 3.6 .

  6. the new ssl store module is wonderful . but we have some observation in it that is really important to improve .

    1 - the service name_key is always "new" as it defined in the confg.json .it must show the domain tht the ssl was activated for .

    2 - there are no option for admins to edit the services_fields, is important if we want to add a license manually then attach it to a active order in the thesslstore website .

    3 - the reminder email should include the domain name for the ssl .

    3 - a good welcome email template sample :)

    as we have a lot of ssl for client we can't locate wich ssl we should go in it, we need to enter to every ssl to see the domain of the certificate .

  7. 3 hours ago, Licensecart said:

    I'm not sure if we get this too, but say if I have a service expiring on the 3/3/2016 and I cancel it on the 6/3/2016 when the renewal date is 1/4/2016 (when it will be invoiced again), will that schedule the cancellation on the 1/4/2016 or 1/5/2016?

    that is the case ; the service is canceled on 1/5/2016.

  8. 19 hours ago, Tyson said:

    Canceling a service at the 'end of term' will set the cancel date to the service's renew date. The service wouldn't be renewed, and instead will be updated by the cron to be canceled on that date.

    I'm not aware of the cancelation date getting updated automatically anywhere in the system. Is it possible the cancelation date was changed manually or updated via the API from custom code/extensions?

    i'm totally sur we don't have any custom plugin that touch the renew date . but i will make a test and see again.

    what we have stated , that the service is not renewed , but the cancellation date was prolonged to +1 term .

     

  9. when we set Scheduled Cancellation to end of term . in almost all our service, the cancel date is changed to the next renewal date .  a sample .

    the service created  in 31/1/2015.

    we set Scheduled Cancellation to end of term (31/1/2016) , after a couple of days we found the Scheduled Cancellation is set to 31/1/2017 .

    this case is not only related to a service, is almost all of our service .

    any one can reproduce the behavior ?

  10. On 1/27/2017 at 4:17 PM, Licensecart said:

    Looks awesome mate :D

     

    On 1/27/2017 at 4:36 PM, Paul said:

    Very nice, looks great! :blesta: 

    Thanks .

    On 1/28/2017 at 2:36 PM, ariq01 said:

    hi @Blesta Addons, can i request another logicboxes module?

    i mean resellerclub. Resellerclub provide domains, shared hosting, vps, codeguard, website builder, etc as their products. So will you create another resellerclub module which provide reseller to sell all of their products? not domains only.

    We are working in some logicboxes staff for our internal use . we have in our TODO list the logicboxes for hosting and vps . once we finish the xtream codes module and ovh vps module we will begin the work in one lmogicboxes module , not sure who will be first Hosting or Vps module .

  11. In your template file, search the li of the nav and add the fallwing code to your template, you need to edit links and navigation names

     

    <li class="dropdown">
    	<a href="#" class="dropdown-toggle" data-toggle="dropdown">
    		<i class=""></i>Link 1<b class="caret"></b>
    	</a>
    	<ul class="dropdown-menu">
    		<li><a href="http://URL_HERE/"><i class=""></i> Sub Link 1</a></li>
    		<li><a href="http://URL_HERE/"><i class=""></i> Sub Link 2</a></li>
    	</ul>
    </li>

     

  12. Hello All Again .

    Logicboxes Resellers Manager

    this plugin allow you to manage your sub-resellers of logicboxes, and you can centralize your work wittout leaving blesta admin side ..

    with this plugin you can:

    1 - Create, Edit and View  Sub-reseller

    2 - Add Funds to subresellers

    3 - List all your subresellers.

    4 - Check wich subreseller has a matched account in your blesta .

    Add Funds For Sub-resellers

    You can add funds for any subreseller, registered in blesta or not , you can also add invoice with charged amount  to the client or any client id .

    Create Sub Reseller

    from client profile, you can create sub reseller account for him with a simple click .

    Create Widget, Admin Widget

    in client side and admin client profile, and if the client has a sub-reseller account, a new widget added to thier dashboard, showing the available amount with the last transactions .

    the plugin is PAID with a small fee of 19.99$ yearly .

    Order Link

    Plugin page

    Screen Shoot .

    Sub resellers list view

    242

    Client Profile Admin widget

    239

    Admin Add funds page

    241

    Client Widget Dashboard

    240

     

    Best Regards

  13. 11 hours ago, Paul said:

    Identifying the service and applying the transaction to an open invoice linked to that service is a good idea. It's also possible that we could look for open invoices that are for the same amount of the transaction, but this would be less reliable. Does PayPal allow for this kind of meta data to be set up with the subscription?

    i have not made a profound look in this with metadata . but i suspect it can related to the "custom" metadata .

    identify the payment with the invoice amount is not a good idea . but it can be a second option maybe .

  14. On 14/01/2017 at 0:29 AM, Tyson said:

    It would be good to have some steps to duplicate the issue, but I think your last post illustrates the problem--the currency has to be the same for the service/options otherwise they can't be represented on an invoice.

     

    On 08/01/2017 at 0:33 AM, Blesta Addons said:

    EDIT :

    we have not made any change , and it show now the total if the currency is identical with service term and config options . so i think is resolved .

     

     

  15.  

    1 - Option to select where Configurable Option should be ordered (Order Form, Client Area, Both)

    2 - Configurable Option with onetime term should appear in all package term .

    3 - Option to allow order config option for multiple times .

    4 - default selected option for Configurable Options.

    for the first case , some options can be ordered only if the service is active , not during the service creation .

    for the second , some config should be purshased one time even if the package term is monthly or yearly , like the installation serice,

    for the third case, some service allow slots, o semilar thing, the client want to order the option first time, then he would add the same config another time or multiple time .

     

    https://requests.blesta.com/topic/configurable-options-enhancement

×
×
  • Create New...