Hi,
as far as I can see, you've successfully migrated Learning Locker to Laravel 5.1. My question: Is there any technical reason why your work hasn't been merged with Learning Locker's main Github repository, yet?
The background of my question is: We would like to setup Learning Locker as a LRS for our LMS Moodle and some additional external tools which will use the Tin Can/xAPI. Our Oracle Solaris 11.3 server provides PHP 5.6.x, but explicitly doesn't provide "php-mcrypt". Learning Locker is based on Laravel 4.x which requires php-mcrypt. For this reason, Learning Locker has php-mcrypt as an requirement. As php-mcrypt is based on "libmcrypt" which hasn't been updated for more than 10 years, php-mcrypt itself can eventually be declared as outdated and shouldn't be used anymore.
My question is: Are there any problems left with Learning Locker on Laravel 5.1 or can we use it as is?
Kind Regards,
Steffen
Hi,
as far as I can see, you've successfully migrated Learning Locker to Laravel 5.1. My question: Is there any technical reason why your work hasn't been merged with Learning Locker's main Github repository, yet?
The background of my question is: We would like to setup Learning Locker as a LRS for our LMS Moodle and some additional external tools which will use the Tin Can/xAPI. Our Oracle Solaris 11.3 server provides PHP 5.6.x, but explicitly doesn't provide "php-mcrypt". Learning Locker is based on Laravel 4.x which requires php-mcrypt. For this reason, Learning Locker has php-mcrypt as an requirement. As php-mcrypt is based on "libmcrypt" which hasn't been updated for more than 10 years, php-mcrypt itself can eventually be declared as outdated and shouldn't be used anymore.
My question is: Are there any problems left with Learning Locker on Laravel 5.1 or can we use it as is?
Kind Regards,
Steffen