View Issue Details

IDProjectCategoryView StatusLast Update
0000366Composrcorepublic2012-05-13 04:09
ReporterChris GrahamAssigned ToChris Graham 
SeverityFeature-request 
Status resolvedResolutionfixed 
Product Version 
Fixed in Version 
Summary0000366: Drop legacy support
DescriptionDrop lots of legacy support...

Anything less than MySQL 5.1
Anything less than IE8 (but no promise of the coolest UI features on anything less than the latest generation of browsers)
Anything less than PHP 5.2
Additional InformationUpdate our coding guidelines, our requirements (on website and docs), tidy up CSS and JS to remove hacks (e.g. setOpacity should not be needed, or the PNG hack, or re-definition of file_get_contents).
TagsRisk: Deprecates functionality
Time estimation (hours)2
Sponsorship open


If users wish to sponsor this issue (optional, some issues are implemented without sponsorship)...
If users wish to sponsor this issue (optional, some issues are implemented without sponsorship)...

Activities

[c4]

2012-01-27 16:13

reporter   ~0000319

Oh Yes!
Drop the dead weight of old technologies.
Right now, the world is changing so fast making the costs of keeping with the old ones prohibitive. IMO developers and admins of modern CMS must make a choice between pleasing all of the potential users or moving forward with exciting innovations supported by modern browsers to attract knowledgeable members and keep websites on the edge of what's invigorating.

BobS

2012-04-17 22:16

reporter   ~0000400

I completely agree with Jean. Even lag-about Microsoft is finally seeing to it that their browser is brought up to modern technologies. I want to see Composr built for the future, not for the past.

maxdamage

2012-04-24 00:45

reporter   ~0000427

Last edited: 2012-04-24 00:52

View 5 revisions

What about support for older versions of Firefox,dev versions of google chrome,etc....?Using this portable version of Google Chrome:16.0.896.0 (Developer Build 103424 Windows)

Chris Graham

2012-04-24 09:51

administrator   ~0000428

The policy has always been to only support the latest versions of browsers other than IE. This is because IE is the only one that does not auto-update, and most other browsers are installed by people by choice (so they know how to keep up to date).

maxdamage

2012-04-30 21:26

reporter   ~0000437

I haven't updated firefox in ages due to the fact that my pc is badly messed up and newer versions have graphical acceleration which my onboard graphics card won't be able to handle.I still use firefox v3.6.16.

I have had to disable a lot of the graphical wizardry just to get my pc to start-up at all. :(

BobS

2012-04-30 22:58

reporter   ~0000438

Unfortunately, time moves on and, so too, must Composr.

BobS

2012-05-12 22:17

reporter   ~0000469

Thanks for your sponsorship, Jean. Just 5 more credits to go till we help Chris move Composr's foundation to a more modern base.

Chris Graham

2012-05-13 04:09

administrator   ~0000476

I have implemented the front-end part of this with the sponsorships here, and put the server-side stuff into another issue. That stuff is less interesting anyway, and easier for us to sort out later too.

Issue History

Date Modified Username Field Change
2016-06-08 00:15 Chris Graham Tag Renamed Deprecates functionality => Risk: Deprecates functionality