Jump to content


  • Content Count

  • Joined

  • Last visited

1 Follower

About DigitalSparky

  • Rank
  • Birthday October 10

Contact Methods

  • Website URL
  • Skype

Profile Information

  • Gender
  • Location
    Perth, Western Australia
  • Interests
    PHP, Web Hosting, Domain Names, Security, High Availability, Performance

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'd probably go back to the hosting provider and request the allow it, even if it's just for one profile. It's certainly more performant than having a composer package or something like that handle it (C compiled library vs PHP interpreted). Enabling for individual profiles these days is very simple, as there are user level php.ini's which you can enable/disable modules, and it's exactly what other module enable/disable controls use, so the only thing they really need to do is install it...
  2. Just to quickly add to this one, > /dev/null 2>&1 pipes everything to the abyss, which means you'll even lose errors. you may wish to remove the 2>&1 so you still get emails if there is an error, it may be helpful in the event errors occur, instead of silently failing :). FYI: >/dev/null = Pipe standard out to /dev/null 2>&1 = Pipe standard error to standard out, which in turn pipes to /dev/null so removing 2>&1 means stderr (standard error) will still come through, so you'll get emails in the event of errors, otherwise not. there are other
  3. Hi folks, Couldn't find this reported, however it seems there's a bit of an issue when attempting to install 4.0.0 using PHP 7. It appears there's a syntax error when taking into account MySQL Ports I've configured my development environment to use MySQL on port 13306 and entered the host as Installation works perfectly on PHP 5.6.23 (via FPM & CLI), however via PHP 7.0.18 it throws the following error: SQLSTATE[HY000] [2002] Failed to parse address "" Changing config.php to the host as and port 13306 does not remedy thi
  4. btw, php5.5 and lower are EOL, and 5.6 is security supported only, so I'd personally suggest encouraging people more towards php7+ than anything else for security and continuity of service. That said, it's great that you do support php7, quite a few applications have been very behind on that.
  5. yay thx Paul :). yeah I do read docs... then again I am a dev/systems engineer...
  6. Yup, I just applied that and all is working - the hotfix, unfortunately, is not listed in the README.md... the PHP 5.5 one is though... haha...
  7. Hi folks, I just tried installing Blesta 4.0 with PHP 7.0.17 using the Ioncube loader for PHP 7 and got the following error: Fatal error: The file .../app/models/license.php was encoded by the ionCube Encoder for PHP 5.4 and cannot run under PHP 7.0. Please ask the provider of the script to provide a version encoded with the ionCube Encoder for PHP 5.6. in Unknown on line 0 So even though there is PHP 7 support for Blesta 4, looks like it needs to be re-encoded with the latest version for it to work.
  • Create New...