Jump to content

Blesta Addons

Alpha Developers
  • Posts

    4,868
  • Joined

  • Last visited

  • Days Won

    389

Posts posted by Blesta Addons

  1. the blesta has a limit for the service key field, it would better to made a check before sending the fields to the service controller to add add/edit service. i found this in my blesta logs

    PDOException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'key' at row 1 in /home/***********/public_html/vendors/minphp/db/src/PdoConnection.php:196 Stack trace: #0 /home/***********/public_html/vendors/minphp/db/src/PdoConnection.php(196): PDOStatement->execute(Array) #1 /home/***********/public_html/vendors/minphp/record/src/Record.php(275): Minphp\Db\PdoConnection->query('INSERT INTO `se...', Array) #2 /home/***********/public_html/app/models/services.php(3654): Minphp\Record\Record->insert('service_fields', Array, Array) #3 /home/***********/public_html/app/models/services.php(3604): Services->addField('16241', Array) #4 /home/***********/public_html/app/models/services.php(1266): Services->setFields('16241', Array) #5 /home/***********/public_html/app/controllers/admin_clients.php(6053): Services->add(Array, Array, true) #6 /home/***********/public_html/app/controllers/admin_clients.php(5941): AdminClients->createService(Array, Array) #7 /home/***********/public_html/app/controllers/admin_clients.php(4688): AdminClients->processServiceStep('confirm', Object(stdClass), Object(stdClass), Object(stdClass)) #8 /home/***********/public_html/vendors/minphp/bridge/src/Lib/Dispatcher.php(142): AdminClients->addService() #9 /home/***********/public_html/index.php(21): Dispatcher::dispatch('/admin/clients/...') #10 {main} 

    i don't have info about this action, but maybe one of the staff are wanting to add service with long key in the service field .

  2. 3 hours ago, Tyson said:

    I may not have been clear in my last post. I meant to ask if there should be any visual display/text to describe what the limits are when using those buttons? It may be that no text is necessary and the button limits will suffice. 

    we can add a small text to indicate the limits under the input field.

    1 hour ago, Paul said:

    I assume some may prefer this option, but others may prefer a slider. Order form option should we add this? 

    in side side i found that more pro and more simple to work, the slider in some browser and some mobile stuck and freeze . but if you want to add a option when we select the quantity text to select between slider and input well be nice also .

  3. a quick view in the code in editservice() , if the client want to reinstall the vps with the same used template, the action is not token, if he reinstall with a template different from what is in use, the vps is well reinstalled . any one can confirm this ?

     

  4. 4 hours ago, Tyson said:

    What change to the default template do you think should be made?

    not sur, but if the staff suspend a service and they put in the reason fields 'Suspended for security reason', the client should receive the suspension email with the suspended cause, if the suspension was for non payment the reason should be no payment, maybe we should be more precis in the email template to avoid those ticket/emails/phones that ask why my account was suspended . this feature it should be addressed to client not to staff.

    also suspension for non payment is not the same as suspension for violation of TOS . Finally this is not a big deal, it was just enhancement to the email template to be more accurate about the suspension reason .

    also adding suspend by 'Staff id XXX' or by system it would be nice in the service view in admin side .

     

     

  5. 4 hours ago, Tyson said:

    This would be a replacement for the quantity slider, correct?

    How would you suggest handling the limits in this case? For example, if I handle a quantity in the range [0, 500] at increments of 5, should I make those min/max quantities known anywhere? 

    jQuery is our friend here . if you look at the snippet code sample in my post, it include a min/max value, maybe it need some tweak to be more conditional.

  6. i have already requested this feature, the competitor do this from years now, they have pre-events and after-events (hooks) and they look to response to complete the action or return the returned errors.

    i think this behavior a great way to extend the software and give the developers the ability to do more features and staff . the events now in Blesta is just like a notification system about completed actions, and also i think is no sense for look for after-events return as the action is already completed. 

  7. 22 hours ago, Paul said:

    The goal is to remain backwards compatible, so far it's looking like that will be possible. Meaning that existing registrar modules should continue to work, and it shouldn't break when installing the domain manager. However, the domain manager may not be able to recognize pre-existing domain packages and take control over them. A way of conversion may be required to take full advantage of the domain manager with existing domains unless starting fresh for domains going forward.

    What is the Obstacle Now in Domains? in reality the obstacles are now :

    - Multi Price System, This can be fixed with more price fields like Renewal Price, we add more fields , Transfer Price, Restore Price.
    - Better Domain Management, this also can be fixed by adding the functions to the actual modules .
    - Unification Commands, this also can be done by actualizing the actual modules.
    - Privacy, Forwarding & other addons prices, this can be implemented with the actual  system by addons, we need just to tweak the actual modules to support this addons
    - if we want to distinct with domains modules and other modules we can add a new entry in modules to define is a domain module or not (true/false) or something like the order type definition.

    For me what Blesta need is enhancing the actual system  and not reinventing a whole system for domains.  now we have waited years to only hear a something from blesta, creating another system will take other 2 or 3 years, and the quick solution and the simple is to extend the actual exist mechanism to support new features .

  8. On 5/31/2019 at 6:10 PM, Amit Kumar Mishra said:

    may be @Blesta Addons, would be able to make a module/plugin to help us

    i do not see many around with better knowledge?

    we can't do anything, this need a modification in the core files, and we didn't encourage  the core files modification or hacking .

    after the renewal price option, the next step i think is the unification of command in all domains modules, like getNameservers() , setNameservers(array $vars = null), getWhoisContact($type = 'all') ,  getEppCode(), setEppCode($epp) .... something like that .... or the second option that i can think about is to create a new module called for example domain manager, inside the module the option to add registrars and then extend the module command from the registrar class, the same login as modules with their functions, but finally Blesta who decide what is the best .

  9. 6 hours ago, Amit Kumar Mishra said:

    this is because, probably not many of us are reselling domains, or this would be on the priority list

    why not @Paul, we get a vote on this and than may be prioritize it a bit?

    what say all?

    if you search you will find this subject the most wanted and talked. but it seem that the hosting/domain industry is not their priority list .

    13 hours ago, EuroDomenii said:

    I guess that the new feature is " Renewal Price Option - Optionally set a renew price that is different from the new price for services."  Nice!

    yes, this feature is step forward in the domains logic model.

  10. 9 hours ago, Tyson said:

    Interesting. You can extend it by calling the container's ::extend method, e.g.:

    
    $this->container->extend(
        'minphp.constants',
        function ($instance, $c) {
            return array_merge($instance, ['WEBDIR' => $instance['WEBDIR'] . 'fr/']);
        }
    );

    There is an example in Blesta v4.6 that does this to override a few of the services for the application. 

    thank tyson, this only for the upcoming blesta 4.6 ?

    i will test it later,  this will allow us to override it globally in blesta. so anywhere to call $this->base_uri will get the overridden value and not the default one ?  so from the preAction event we can dot it without changing or modifying any blesta files ?

  11. On 5/23/2019 at 4:42 PM, Joseph H said:

    No entirely correct tho, we have solved the issue you raised since May 20th, still we are have the same issue. 

    I really hope you would consider using only the domain for validation. This is already causing a lot of inconvenience for both of us. 

    Hello Sir, it need a fully license reissue to work .

  12. 23 hours ago, Tyson said:

    That's strange. I don't encounter that issue when a space exists before null. Must be something with the context. I'm glad you were able to figure it out though.

    is not a space, is a strange char before null that is not visible and only can be detected by selection .

  13. 23 hours ago, Tyson said:

    I'm curious to know what the reason is behind overriding WEBDIR? Adding a new constant for your case would not suffice? 

    Also, you can override WEBDIR by extending the container. 

    we have some seo practice in our website, nd we need this to do it in our multilanguage plugin that add instance for every language in blesta like /fr/ or /ar/ ...ect

    how we can override only WEBDIR by extending the container?

  14. 5 minutes ago, Tyson said:

    Glad to hear it.

    What error do you receive? null is a valid argument to Date::__construct:

    
    public function __construct(array $formats = null, $timezone_from = null, $timezone_to = null)

     

    Use of undefined constant null - assumed 'null' (this will throw an Error in a future version of PHP) on line 78 

     

  15. 2 hours ago, Tyson said:

    Yes, you should set the timezones after you load the Date helper. It will not set the timezones itself because it is not aware of the timezone of the dates you are working with or what you want to convert them to.

    You could set the timezones on load (via the constructor), or via ::setTimezones.

    
    Loader::loadHelpers($this, ['Date' => [null, 'Africa/Casablanca', 'UTC']]);

    or

    
    Loader::loadHelpers($this, ['Date']);
    $this->Date->setTimezones('Africa/Casablanca', 'UTC');

    Then, you can convert dates:

    
    $this->Date->format('2019-05-01', 'Y-m-d H:i:s');

    It's also useful to include timezone information in the date if it differs from the set timezones:

    
    // Specify the date provided is in UTC
    $this->Date->format('2019-05-01 00:00:00Z', 'Y-m-d H:i:s');
    
    // Specify the date with the full timezone information for the current timestamp
    $this->Date->format(date('c'), 'Y-m-d H:i:s');

     

    Does setting the timezones fix the date issues you were having?

    yes, after we set the timezone the dates not appear correctly .

    just a note the null return error, i have fixed by empty array

    Loader::loadHelpers($this, ['Date' => [[], 'UTC', Configure::get('Blesta.company_timezone')]]);
×
×
  • Create New...