Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Let's end Textpattern support on Apache 1.*
I propose that Apache httpd version 1.x support be officially removed from the Textpattern project from 4.6 onwards.
The most recent (and likely final) release of Apache 1 was in 2010 when 1.3.42 dropped in March 2010, over five years ago.
In addition to some known security vulnerabilities, Apache 1.x is no longer maintained.
Looking at other CMS vendors:
- WordPress requires “the
mod_rewritemodule”, which implies version 2.x - Drupal states “Drupal 7 and 6 will likely work on Apache 1.3.” – the current Drupal version is 8
- Joomla requires “2.x+”
- Concrete5 is “mostly run on Apache 2”
- ModX lists “Apache 2.2.x” as a minimum
In the first instance, if this proposal is agreed, the Textpattern system requirements page should be updated to reflect the changes. Beyond that, the docs need changing and any Apache 1.x-specific code can be assessed for suitability.
Offline
Re: Let's end Textpattern support on Apache 1.*
gaekwad wrote #292030:
I propose that Apache httpd version 1.x support be officially removed from the Textpattern project from 4.6 onwards.
Suits me.
Besides the .htaccess files themselves, there’s nowhere in the code that makes reference to the system requirements beyond linking to the requirements page on .com. The only checks we do internally are to verify the PHP version is up to spec. So it looks like most of the alterations will be ‘soft’ documentation changes only on the periphery, and testing to make sure any .htaccess file tweaks work reliably.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Let's end Textpattern support on Apache 1.*
Makes sense. Practically, the minimum PHP spec will likely make Apache 2.x what’s there anyway. Liking all the “looking forward” energy here on the forum.
Offline
Re: Let's end Textpattern support on Apache 1.*
Bloke wrote #292038:
Besides the
.htaccessfiles themselves, there’s nowhere in the code that makes reference to the system requirements beyond linking to the requirements page on .com. The only checks we do internally are to verify the PHP version is up to spec. So it looks like most of the alterations will be ‘soft’ documentation changes only on the periphery, and testing to make sure any.htaccessfile tweaks work reliably.
On those grounds, I’ve raised this PR: github.com/textpattern/textpattern/pull/488 – presumably we can change the .com sys reqs page after 4.6 hits the streets.
Edit: closed the PR – no code changes at stake.
Last edited by gaekwad (2015-06-28 16:56:49)
Offline