Jump to content

Blesta Addons

Alpha Developers
  • Content Count

  • Joined

  • Last visited

  • Days Won


Blesta Addons last won the day on February 4

Blesta Addons had the most liked content!


About Blesta Addons

  • Rank
    Advanced Coder

Profile Information

  • Gender
  • Location
    : \Blesta\Core

Recent Profile Visitors

8,813 profile views
  1. From this mouth (March) all invoices generated for renewal has a date due with the same day of date billed . we have not added any plugin or touched any file from weeks now . also blesta version is the same from a long time ago (we are in 4.5.2) , our case is the fallowing . Invoice Days Before Renewal (10 Days) . ll invoices generated in 2-3-2020 has the billed date 2-3-2020 and due date is 2-3-2020 (normally it should be 12-3-2020). we have this option for so many years and is working as it should be . the issue has begin from first march (1-3-2020) . there are no errors log files . any thing we should look into ?
  2. disabled all core plugins, still the error appear .(disabled crons tach not the cron it self) running the cron with error reporting -1 is showing the error when i run the corn command via ssh .
  3. disabled all plugins/modules cron, still the error appear in the logs.
  4. any ioncube coded file return a line 0 in any error. we have reinstalled the test server, now is a fresh install without any custom plugin/module . the plugins installed is core plugin (support/order/Mass Mailer).
  5. in a test server with 4.8.1 i see alot of this notices in logs E_NOTICE: Undefined property: Cron::$Session {"code":8,"message":"Undefined property: Cron::$Session","file":"/home/xxxxx/public_html/app/app_controller.php","line":0} Uncaught Exception Error: "Call to a member function read() on null" at /home/xxxx/public_html/app/app_controller.php line 0 {"exception":"[object] (Error(code: 0): Call to a member function read() on null at /home/xxxxx/public_html/app/app_controller.php:0)"} php used 7.2
  6. the simplest way is to edit the template PDT file (in view folder).
  7. we are in 4.8 beta, and we are from v3 waiting something for a real hosting market . blesta has added a subdomain feature for cPanel module, from professional view is unused features with that way, companies that sell subdomain with a defined domains can be hosted in cpanel or plesk or vesta or any platform that support subdomains in account creation (almost all panels support this), this feature should be a part of order plugin and not a with cpanel or plesk module, because the client in the first step should select the domain then select the hosting (please make a view in other apps that they have already this done), and of course the check availability should be working for subdomain, i think a simple way is to check if exist record A for the subdomain with a simple php function dns_get_record() . unify functions in registrar modules, like (get name server, set name server, update whois, get whois, get epp, set lock, get lock status, ....ect ) pricing system for domain, now a lock for transfer/restore prices . bundles package, is a trivial features that all hosting companies need it to make offers/promotions . in the end i can say another time Blesta is a good software for almost any thing unless hosting industry .
  8. Extra work for us, mapping and mapping for any service fields that is more than 32 chars. working with the real vars save us a lot of work (loops, searching index ... ) anyway, i'm not expecting anything, there are a very important things that was not implemented for years now, so this small things is not changing anything for us. it was for archiving/remeber purpose only.
  9. the service field length 32 is a small value for a general and all purpose usage . i have already talked in this subject ina old thread that i have not success to get the post. in some module the service fields need more than 32 chars. i will insist again to make it at least 64 chars, and don't know why it was limited to 32 chars only!!! how we can save service fields like this 'dotfrcontactentitybirthplacecountrycode' !!!! we should contact the register to tell him sorry blesta is not supporting more than 32 chars so please change to a less chars !!! and of course if this is working with whmXX, their answer will be a pretty small as change the software to another is already working with our system!!!!
  10. to be sample, i want to allow only admins to upgrade/downgrade packages in ONLY some groups, and do not offer this to clients . for other groups clients can do that from thier client area . the option in the company is applied for all packages if package group has the option allow upgrade/downgrade enabled. if we disable the option in company settings is disabled all the packages in client area . the option should be something like i_n the package group : [X] Allow Upgrades/Downgrades between Packages within this Group. [X] Admin [X] Clients
  11. the package groups has the option to Allow Upgrades/Downgrades between Packages within this Group . we want to see a option to allow this only in admin section, and let it disabled for client side . some products need some manual intervention (docs signed ...ect) to be only changed by admin/staff upon a client request. and we don't want to allow client to change it from their account. it would be nice to add a option to restrict this option to admin side only .
  12. Enable error reporting in blesta config file, then the error will be shown for you.
  • Create New...