I want to create a php application that can be used by many users, As laravel 4 requries 5.3.7 i am confused weather to use it or not because many of the users may not have the php version supported as they will be using shared hosting.
How to overcome this ? Is it by using older version of laravel or some other solution please help me. I am really intersted in using laravel cause of its robust nature.
To be honest, depending on what your application is, it's probably enough to think that most users are either already going to be on PHP 5.3.7+ or they will be willing to upgrade to the latest version or a more recent version of PHP.
When PHP 5.3.20 was released, there was an extremely public announcement that PHP 5.3 was going to be EOL'd after March 2013.
It's now obviously past March 2013.
People should have moved to PHP 5.4 by now. If your application is a one of a kind, or the best in it's class, then you should not need to worry about what version of PHP is being operated on, as people should either
be running PHP version > 5.3.20
be able to upgrade to a PHP version > 5.3.20
The Laravel dependancy on PHP 5.3 is a nice one, and to be honest, with all of the new features and general code style of Laravel being introduced, I would not be surprised if the version requirement is increased to PHP 5.4 "soon" (in say the next 6-12 months).
If you want to create an application used by many users, simply advise them that there is a minimum requirement for PHP 5.3.7. This is not too unusual for web applications.
For example, a very popular PHP forum phpBB has required PHP 5.3.3 since March 2012.
Related
I am using Lucene 3.5.0 for index creation. Zend-Framework-1.8.2 with PHP-7.1.12 is being used to search index.
I have upgraded Lucene from 3.5.0 to 8.4.1. The indexes are now created with Lucene 8.4.1. But searching index gives error. I believe I need to upgrade Zend-Framework and PHP.
So, could anyone please provide the pointers on which Zend-Framework and PHP version is compatible to use with Lucene 8.4.1 indexes?
Well ... bad news for you.
The Zend Search component concerning Lucene is not maintained since years and has been archived a long time ago. Even on Packagist the package is marked as This package is abandoned and no longer maintained. No replacement package was suggested.
Same goes for Zend Framework. Even Zend Framework 3 is not maintained anymore. The follow up is the Laminas Framework.
My suggestion would be that you switch to Laminas, the successor to Zend Framework. Most components of the Laminas Framework are already PHP 8.1 compatible. Say goodbye to the ZendSearch component. This component is not developed further and will prevent you from using current PHP versions in the future. PHP 7.3 has reached an end of life already. PHP 7.4 is in a security fixes only state since december 2021 and will reach an end of life by end of this year. Zend Framework and ZendSearch will not work for the foreseeable future, if they should work now.
Just use one of the following alternatives:
Elasticsearch
Pucene
Solr
Sphinx
Guys I am planning to use moodle 2.7 as the lms in my organization..could you please let me know if there are any know vulnerabilities which could grant a user a higher order privilege?? if yes then how do I make sure I fix it...I have to use moodle 2.7 only..cannot upgrade that
Moodle 2.7 is out of support in about 6 weeks. It's patched (security wise) as of this point in time, but if someone discovers something 3 months from now, it won't be fixed and you'll have to upgrade anyway. It's a really, really bad idea to use it for a new site when you might as well use 3.1 (LTS) or 3.2
Since the TYPO3 forum seems a bit dead, I thought I'll try my luck here. If anyone knows a different place to ask, be sure to name it and I'll delete this post.
I recently acquired a project with TYPO3 webistes that I need to migrate from 6.2 to 7.6. I will probably need to rewrite a lot of customized extensions and I want to start with the login system. The main site uses shibboleth_auth (which is discontinued) that has been partially rewritten to fetch login data from different endpoint.
Now, what is the current alternative for this extension? And how do I "extend" an extension so that It can still be upgraded, but also uses my methods? ( in this case, the custom endpoints for login verifications ).
I know that the University of Austria and Munich are currently working on a shibboleth authentication plugin that will work with 7.6. They asked a couple of weeks ago about feature requests and funding.
Our agency is maintaining a friendly fork of EXT:shibboleth_auth, it can be found at GitHub and Packagist. It is currently compatible with TYPO3 8.7 CMS and a version for TYPO3 10.4 LTS will follow shortly.
I can not find any link related with 2.1.5 from SourceForge. I wonder whether I can still use this version as a third party component in my product.
Any comment would be appreciated very much!
Sure you can. Search the web and you will find that version easily (e.g. here or here) It is a different question however whether you should still use that version. It is quite old and lots of bugs have been fixed and new functionality has been added. So do the following:
check the license restrictions (LGPL vs. AGPL)
if you don't have a problem with a GPL based license then use the latest 5.X version
if you can't use APGL buy a commercial license or use at least version 2.1.7
if you go the 2.1.7 route do some testing - in many cases it will do its job still fine. If not you'll probably have to fix it by yourself
Update: I would now use openPDF which is a maintained fork based on 2.1.7.
I have a problem here. My Zend_Forms do not render in view script.
Via FirePHP i have spotted a lot of "Need PHP 5.3 to get value"
Could someone confirm?
What should i do if i have PHP 5.2.11?
Thanks!
Yes. They are compatible. I am not aware of any features that would require 5.3.
Install XDebug or Zend Debugger to see what's wrong.
They weren't supposed to be using anything that would require PHP 5.3 until ZF2.0 (which, if you read the blogs, is due soon). Did you download the framework manually, or are you tracking it via an svn:external? If you are, you may want to do it differently as from here on in we're likely to see new code requiring 5.3 being checked in.