The ea-Geier WIKI currently (formerly) reachable via http://www.ea-geier.at/wiki.en/ (English version) and http://www.ea-geier.at/wiki.de/ (German version) has been moved successfully to http://en.ea-geier.at and http://de.ea-geier.at. The old links will be forwarded to the new ones.
Sunday, 29 April 2012
rss extension for mediawiki
The rss extension suffers from minor warnings about previously undefined variables, but also from a change in the api of mediawiki on how to access the database, and a change in how dates are formated.
We documented at the discussion page of the extension and on our user page on medawiki itself.
We documented at the discussion page of the extension and on our user page on medawiki itself.
multilang extension for mediawiki
Only minor changes where needed to tweek the multilang extension for the current mediawiki version, which we documented at the discussion page of the extension and on our user page on medawiki itself.
Saturday, 28 April 2012
move of the ea-Geier wiki started
Moving the ea-Geier wiki seems to be a little more difficult due to the age of the old server and the limitations the provider imposed superfluously.
rsync did not work out, the code had to be moved by scp, which copied the complete file for each symbolic link. So all original symbolic links had to be set manually...
A database dump was only possible in an aged MySQL 4.x dialect. Thus all TYPE=... references in the table definitions had to be changed to ENGINE=..., and timestamp(14) had to be adjusted as well.
... finally the transfered code did not run. Due to the limitations mentioned above, we had to use a quite old version of MediaWiki 1.6.10 which was patched only with security updates. Unfortunately this version used Namespace as class, which php5.3.x does not like that much.
However, upgrade to the current version 1.18.3 for the wiki itself was nearly smooth.
The way templates work changed a bit which needed upgrades to the ea-Geier skin.
But all extensions we used stopped working for the new version, none of them are supported any more.
... currently we are working on fixing that ...
rsync did not work out, the code had to be moved by scp, which copied the complete file for each symbolic link. So all original symbolic links had to be set manually...
A database dump was only possible in an aged MySQL 4.x dialect. Thus all TYPE=... references in the table definitions had to be changed to ENGINE=..., and timestamp(14) had to be adjusted as well.
... finally the transfered code did not run. Due to the limitations mentioned above, we had to use a quite old version of MediaWiki 1.6.10 which was patched only with security updates. Unfortunately this version used Namespace as class, which php5.3.x does not like that much.
However, upgrade to the current version 1.18.3 for the wiki itself was nearly smooth.
The way templates work changed a bit which needed upgrades to the ea-Geier skin.
But all extensions we used stopped working for the new version, none of them are supported any more.
... currently we are working on fixing that ...
ea-Geier API cloned
The ea-Geier API currently (formerly) reachable via http://www.ea-geier.at/ea-doc/ has been cloned to http://api.ea-geier.at/. The old link will be forwarded to the new one.
The move was smooth, no problems.
The move was smooth, no problems.
ea-Geier will be back - carbon neutral
After a sabbatical of nearly five years, the ea-Geier will see new life.
While the ea-Geier has been downloaded quite heavily and supposedly used as such, no real problems have appeared, no security issues. Some feature requests could be satisfied using small patches ...
As next big step, the ea-Geier will move to a new server. With new hardware, more space, bandwidth and - best of all - hosted carbon neutral!
While the ea-Geier has been downloaded quite heavily and supposedly used as such, no real problems have appeared, no security issues. Some feature requests could be satisfied using small patches ...
As next big step, the ea-Geier will move to a new server. With new hardware, more space, bandwidth and - best of all - hosted carbon neutral!
Subscribe to:
Posts (Atom)
