[wp-hackers] Plugins and supporting old versions of WordPress

[Alexander Beutl]

>
> You're really just asking to be hacked. ;)


Call it however you want ;-)
Had my reasons and vanished one of them about a week ago ... ~100$/Month
aren't worth not upgrading since 2.5 is released. 2.3 was no improovement in
any way in my eyes so i didn't vanished my sponsor then...

2008/5/9 Viper007Bond <viper at viper007bond.com>:

> WordPress 2.3 came out over 7 months ago. The majority of plugins have
> updated since then and most of those that haven't have been replaced by
> similar plugins or branched.
>
> You're really just asking to be hacked. ;)
>
> On Fri, May 9, 2008 at 5:26 AM, Alexander Beutl <xel at netgra.de> wrote:
>
> > >
> > > And users of 2.2.x could easily downgrade - right?
> > >>
> > > Not really. The database schema is different.
> >
> > [...]
> > >
> > Pain in the butt, I know.
> > >
> >
> > Yep thats exactly what I wanted to point out - 2.0 until 2k10 is nice but
> > everyone who was such "stupid" as to upgrade until 2.2.x but than lost
> > compatability to 2.3 (remember: Tagging - just as an example) is left
> > without any support... if the one was such "intelligent" as not to
> upgrade
> > (which was recommended as far as I know) he'll be luckily supported...
> > strange way to do things, while I do know it is hard work to keep all
> > branches security fixed...
> >
> > Anyway of course best is to upgrade constantly and fix every
> > incompatabilities... but who has the time to fix others plugins ;-)
> >
> > Anyway I will get my 2.2.3 Blog updated soon - I just need some days to
> > rework everything running on it to not loose anything which matters...
> and
> > to overwork the template which isn't only uncompatible but also unpretty
> -
> > but holds bit too much code which I had better put into plugins -- a week
> > ago I allready dropped the biggest Issue which made an upgrade not only
> > time
> > consuming (for template rework and plugin compatability) but totally
> > impossible...
> >
> > I have 3 other Blogs which are running at current version - and will stay
> > updated forever as far as I am concerned... so I really didn't want *not*
> > to
> > upgrade but when I tried (and did backup of course) everything was broken
> > (and of course, how else could it be) the special chars (umlauts) were
> > broken in that damn backup too - took me two days to get everything back
> > online so I really know why someone might be "update resistant" by
> purpose.
> >
> >
> > 2008/5/9 Jeremy Visser <jeremy.visser at gmail.com>:
> >
> > > On Thu, 2008-05-08 at 15:18 +0200, Alexander Beutl wrote:
> > > > >  2.0 will be maintained until 2010 [1].
> > > > >
> > > > >  [1] http://wordpress.org/download/legacy/
> > > >
> > > > And users of 2.2.x could easily downgrade - right?
> > >
> > > Not really. The database schema is different.
> > >
> > > To do it properly, you would need to go to Manage > Export on the 2.2.x
> > > blog, and download the XML file.
> > >
> > > Then, to import it into a 2.0.x blog, you need the
> > > WordPress-to-WordPress Import plugin, which is capable of reading the
> > > same XML files. You import the XML into the 2.0.x blog after clearing
> > > the database.
> > >
> > > Pain in the butt, I know.
> > >
> > > --
> > > Jeremy Visser
> http://jeremy.visser.name/
> > >
> > > ()                           ascii ribbon campaign — against HTML
> e-mail
> > > /\
> http://asciiribbon.org/
> > >
> > > _______________________________________________
> > > wp-hackers mailing list
> > > wp-hackers at lists.automattic.com
> > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > >
> >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> >
>
>
> --
> Viper007Bond | http://www.viper007bond.com/ | http://www.finalgear.com/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>