README

This is a monorepo of a fork of Zend Framework 1, made after it's reached its EOL.

PHP 5.3-8.5 compatible. (see PHP version support for details)

All original framework's components have been split into individual packages, which can be installed separately with composer, e.g.

composer require zf1s/zend-*

where * may be one of: acl, amf, application, auth, barcode, cache, captcha, cloud, codegenerator, config, console-getopt, controller, crypt, currency, date, db, debug, dojo, dom, eventmanager, exception, feed, file, file-transfer, filter, form, gdata, http, json, layout, ldap, loader, locale, log, mail, markup, measure, memory, mime, mobile, navigation, oauth, openid, paginator, pdf, progressbar, queue, reflection, registry, rest, search, search-lucene, serializer, server, service, service-akismet, service-amazon, service-audioscrobbler, service-console, service-delicious, service-ebay, service-flickr, service-livedocx, service-rackspace, service-recaptcha, service-shorturl, service-slideshare, service-strikeiron, service-twitter, service-windowsazure, service-yahoo, session, soap, stdlib, tag, test, text, timesync, tool, translate, uri, validate, version, view, wildfire, xml, xmlrpc.

Alternative installation method

You may also install the whole framework at once, using composer:

composer require zf1s/zf1

to easy up the transition period, but please keep in mind the recommended approach is to identify and install only the packages you need.

Project philosophy

This fork focuses on keeping Zend Framework 1 running on modern PHP versions with minimal changes to the original codebase. We don't modernize the code for the sake of it. The goal is to give legacy projects a chance to run on updated environments. It may also contain fixes for long-standing or newly discovered bugs, and occasional backward-compatible improvements.

That said, zf1s is meant as a bridge, not a destination - the recommended approach is to migrate away from zf1 gradually, one component at a time, and the modularized package structure should allow that. Of course, migrating away requires time and resources and may not always be realistic - we get it, and that's also why this fork exists.

PHP version support

• 1.16.x (current) - supports PHP 7.1-8.5
• 1.15.x - supports PHP 5.3-8.3, may receive backported fixes if time allows

1.15.x can also serve as a stepping stone when coming from older PHP (<7.1): first make sure everything works on your current PHP version with 1.15.x, then upgrade PHP to a commonly supported version (7.1-8.3), then switch to 1.16.x.

This fork has always kept the PHP version requirement as low as possible - all the way down to PHP 5.3 - to keep the barrier to entry low for legacy projects. PHP 8.4 forced a change - supporting both at the same time became unwieldy. See #216 for details and reasoning.

Changelog: here

Original README: click