Blesta Addons

Dates Another Episode !!!! Service Creation : 05/09/2015 Service Expiration 05/09/2016 We set Schedule Cancellation to end of term in 29-08-2016 , after some days we found the service still active and is Schedule Cancellation is set to 05-09-2017 !!!! the question is what is the meaning of end of term in Blesta ? why Blesta is update the Schedule Cancellation to 1 year plus (maybe is +1 term) is this related to the next invoice generation date ?

it appear you need a custom fields in support manager, that is not supported now .

you mean the badge ? wich plugin you use ? the support manager pro has this option i think . the support manager need the support manager badge plugin to add it ,

السلام عليكم المشكلة من لسيرفر .. اعداداتال php لا تتوافق مع متطلبات السكريبت هل تستخدم cpanel ؟

the same one i have in my system replies ... it use a empty email , the md5 of empty string is "d41d8cd98f00b204e9800998ecf8427e" ... normally it should use the avatar of the email set in department .

not sure, but i think this can be done in language files .

it use i think the email used in the department . if no i think is a good catch here .

i love the Routing system they have , they use Aura . why not blesta use it ?

@Cherry have you checked the pull request ?

Use my plugin support manager badge , it add the box for client part .

cPanel is the most used and most popular , not sur if they are the best in the market, but from my experience the support they has is fantastic , the control panel easy to use for admins and clients . they have so many feature that make it out of the box for hosting panel . and you can complete it with CloudLinux , SO cPanel + CloudLnux they are the best solution in the market , the only thing i find it lock of cPanel is the balancing system or the cluster managed . exist Direct Admin as a simple alternative . if you want a free panel Kloxo, Webmin has some positive feedbacks.

Have you checked the post about the new domain refactor ? what you think about it ?

i didn't see the error log of apache. the page was blank and a not in 500 internal server error .

Sir @Tyson , to be honest , We need to see one of the fallowing Solution in the final v4 : 1 - allow admins to change the package module - the admin take the responsibility for this - 2 - Create a plugin to allow us (admins) Migrate packages between modules . Dropping This Feature was a disaster for us, i will not give a real case, as you can imagine any case that need the package to be changed for a module .

You talking about the core plugin ? i'm talking about the developed plugin . a solution now, is to use Composer\Autoload\ClassLoader() and then register the loader "$loader->register()" .but this solution is only working in the loaded module/plugin, i'm seeking to auto register all the plugin/module that are supporting namespace . as i see as solution (or maybe a small solution) is to search in every plugin/module for a autoload.php file, this file will contain the autoloader class and the register command , that way is possible to register the plugin/module globally . something like $loader = new \Composer\Autoload\ClassLoader(); $loader->addPsr4('Blesta\\Module\\MyModuleOrMyPlugin\\', '/path/to/module_or_plugin/src'); $loader->register(); if we put a file called autoload.php and then the blesta core load all this files in the preAaction , we can use namespace in the available plugin/module .

In v4 , i have noted that it not possible not change a package module when already a service activated with this package ! the question what is the limitation that has blesta added this behavior . i'm as admin , a need the option to change package module even if already services use this package, as i know what i do and i know this will impact the services fields and services relation . in so many case , i'm and some blesta clients use the universal module as a temporary module until we get the module we want , then we change the package module, and we edit every service manually, that way the client services remain the same, as now, we need to create now package, cancel client's services and create new one !!! is possible to remove this lock ?

I was thinking if Blesta can make the magic for Autoloading Pliugins and modules . as now only MassMailer (plugin) and Blesta License (Module) are autoloaded in Blesta . it will be wonderfull from blesta to add some tick to autoload any plugin or module (that is installed) .

+ the PSR standard .

NO, the use a old version of files .

phpseclib has now namespace and new structure and option,is better to update it to the latest version

i have tested the plugin in v4, is working, this related only to v3 .

You call it from the structure.pdt ? Or from other template file ?

@Licensecart what is the exact link that is not working with $this->base_uri

Tag {company.name} = Ok client theme named "FOUR" = Ok admin theme named "FOUR" = Ok

The Ovh/Soyoustart/Kimsufi Module is only for dedicated servers, the Vps module in test mode and has not arrived yet to the selling period, but it will be disponible for public when it has all the feature needed by the client/admin side . The affiliate are not yet done, and is still in development, we need to make a deep look at the new order plugin to see what is added and removed. maybe we can request a sample change to the order form from Blesta team to make fully compatible with the plugin .... (something related to cookies,sessions, store info) .... The License system will be in 2 or 3 type : Yearly License (confirmed), Open Source License (confirmed), Monthly License (not sure at the moment). for the security, we use in our modules the vendor API library , so rarely we create a custom API, and we let the security part managed by Blesta itself. we test our plugins/modules massively , but we are open to any other test or investigations .