[geeklog-devel] Geeklog 2.1.0 Release Schedule

Tom websitemaster at cogeco.net
Tue Dec 31 17:43:56 EST 2013

$LANG_ENVCHECK is used by the new Hosting Environment Check page
(/admin/envcheck.php) and is found in both English language files. It
shouldn't be dropped or filtered out.

Thanks for updating the pear packages.


-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: December-31-13 1:10 PM
To: Geeklog Development
Subject: Re: [geeklog-devel] Geeklog 2.1.0 Release Schedule

Quick update:

1) I've fixed the problem with the "lm" script (that updates the language
files) that caused bug #1729 (TOPIC_ALL_OPTION etc. ending up as strings
instead of as constants). That should work now.

In the future, when constants are used in the language files, they need to
be added to lm.php. For now, it only supports constants in the
$LANG_configselects arrays.

That's all in the "lm" directory under

2) I ran the "lm" script again. Everything seems to be working now and all
the language files are up to date. The only differences I'm seeing are in
the Japanese language file. Some are cosmetic (comments, whitespace). And
there's a $LANG_ENVCHECK array that's not used in Geeklog. I guess that is
for a geeklog.jp add-on?

Not sure how to proceed. Should I check in the version that the script
created? It would drop the $LANG_ENVCHECK and change some of the formatting
of the source code (but not the content).

3) I've also updated the PEAR packages that we use. They are in


and are added to the release tarballs automatically. The nightly tarball
already includes the latest updates.

bye, Dirk


geeklog-devel mailing list
geeklog-devel at lists.geeklog.net

More information about the geeklog-devel mailing list