Leaderboard

We are installing Blesta 4.0.0 and notice that during the installation process an alert was issued saying that our cache directory was not writable. This was strange to us because in our environment, the user who runs PHP has write access (we use suPHP for security reasons). Upon closer look we notice that Blesta 4.0.0 does not ship with an empty cache directory (as defined by CACHEDIR). Rather, the code assumes that the cache directory already exists. You can see this below: app/controllers/install.php 807 'cache_writable' => [ 808 'message' => Language::_('SystemRequirements.!warning.cache_writable.recommended', true, CACHEDIR), 809 'req' => true, 810 'cur' => is_writable(CACHEDIR) 811 ], // To cache view files for performance The PHP function is_writable does two things: checks if the user can write AND if the file exists. Since Blesta does not ship with an empty CACHEDIR (nor was anything mentioned to create one in the README), we get an error for no reason. Below is a patch for a proposed fix. It checks to see if a file exists, if it does, then performs the is_writable test. Otherwise, attempt to create a directory and check if we can write to it The second test is probably pointless cause if you can create a directory you should be able to write to it, but edge cases can be tricky if parent folder has sticky bits enable, etc. -Adam diff --git a/app/controllers/install.php b/app/controllers/install.php index a6c462e..414d3a8 100644 --- a/app/controllers/install.php +++ b/app/controllers/install.php @@ -807,7 +807,7 @@ class Install extends Controller 'cache_writable' => [ 'message' => Language::_('SystemRequirements.!warning.cache_writable.recommended', true, CACHEDIR), 'req' => true, - 'cur' => is_writable(CACHEDIR) + 'cur' => (file_exists(CACHEDIR)) ? is_writable(CACHEDIR) : (mkdir(CACHEDIR, 0755) && is_writable(CACHEDIR)) ? true : false ], // To cache view files for performance 'ext-simplexml' => [ 'message' => Language::_('SystemRequirements.!warning.simplexml.recommended', true),

Currently the page https://www.whmcs.com/price-change-faq/ states Yet email went out (accidentally) to some resellers informing them of a price rise as of today's date. Due to the email that was accidentally sent out to some resellers, WHMCS has now stated reseller pricing will rise as of July 1st. From what I have read the resellers buying price will be based on the amount of clients their clients have.

Looks like I am a bit behind the times lol

Can't wait some of their clients got it on the 20th March mate: https://www.lowendtalk.com/discussion/109083/whmcs-introducing-tier-based-pricing-on-reseller-program

The new The SSL Store module does support configurable options, mostly for Additional SANs, which only apply to some certificates. If you have the module import all the certificates as packages, it will create the config options. If you don't want to sell all certs, I'd suggest doing this on a trial or dev install to see what the config options look like but looking at one.. Name: additional_san Type: Quantity Client can Add (Client CAN NOT Edit) Min: 0 Max: 198 Term: 12, 24 months