Welcome to Geeklog Friday, May 24 2013 @ 04:58 PM EDT
The official release version of Geeklog 1.4.1 is now available for download. To recap the new features:
With this release, we're also saying goodbye to the year 2006 as well as the Geeklog 1.3.x branch, for which support has now ended. Geeklog 1.4.1 is a recommended upgrade for all users of previous versions.
Those upgrading from Geeklog 1.4.1rc1 will find a list of all the changed files in the file changed-files in the docs directory. In case you're upgrading from beta 1 or 2, we suggest you replace all of the files.
There were no database changes over the betas or rc1, so there's no need to run the install script again. One theme change that we'd like to point out is for the file preferences/profile.thtml where the input fields for the user's location and homepage were accidentally restricted to 32 characters each. If you're using the Professional theme or a theme based on the 1.4.1 version of the Professional theme, please make sure to pick up this fix.
When upgrading from an earlier version (1.4.0 or 1.3.x), simply follow the upgrading instructions. Please note that there were a lot of theme changes that you may have to apply in case you're using a customized theme. Updated themes for Geeklog 1.4.1 should shortly be available from the usual places, e.g. www.geekdownloads.net
Here's what others have to say about 'Geeklog 1.4.1':
GeekLog 1.4.1 has been released. Both the GL-Util and the FAQ plugin work fine with this new version of GeekLog. [read more]
La version officielle de Geeklog 1.4.1 est maintenant disponible au téléchargement. Les nouveautés sont : * Utilisation possible de serveurs de bases de données Microsoft SQL. * La fonction calendrier est maintenant un plugin. * La possibilité d'avoir un... [read more]
ã¨ã‚Šã‚ãˆãšå¾©æ—§ï½¥ï½¥ï½¥ç–²ã‚ŒãŸ 12æœˆåˆæ—¬ã«ãƒ¡ã‚¤ãƒ³ã®Cobalt RaQãŒæ•…éšœã€ä½•事ã‹ã¨æ€ã„ä¸ã‚’ã‚ã‘ã¦ã¿ãŸã‚‰ã‚³ãƒ³ãƒ‡ãƒ³ã‚µãŒãƒ¢ãƒƒã‚³ãƒªã—ã¦ã¾ã—ãŸã€‚ ã™ãã«äºˆå‚™æ©Ÿã«åˆ‡ã‚Šæ›¿ãˆã‚ˆã†ã¨æ€ã„予備機ã‚ã‘ãŸã‚‰ã“ã¡ã‚‰ã‚‚コンデンサãŒï½¥ï½¥ï½¥orz ãŠã¾ã‘ã«ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆæ©Ÿã«ä½¿ã£ã¦ãŸPCも壊れるã—ã‚‚ã†ãï¼ ã‚„ã‚‹æ°—ãªãã—ã¦ã—ã°ã‚‰ã放置ã—ã¦ãŸã‚“ã§ã™ãŒã‚„ã£ã¨å¾©æ—§ã§ãã¾ã—ãŸã€‚ ã¨æ€ã£ãŸã‚‰Geeklogã€firefoxã§æ€ã„切り文å—化ã‘ã—ã¦ã‚‹ã—・・・ 以下続ã ※追記 一応何ã¨ã‹æ–‡å—化ã‘ã‚‚åŽã¾ã‚ŠåŽæ‹¾ã—ãŸæ¨¡æ§˜... [read more]
The following comments are owned by whomever posted them. This site is not responsible for what they say.
---
Live everyday as if it was your last!
I don't know if it is appropriate to post error report
as an comment to this story but it's convenient for me.
I apologize in advance if it is not good.
I installed geeklog 1.4.1 and experienced an error.
When I posted a comment, I had the following message.
2,mysql_fetch_array(): supplied argument is not a valid MySQL result resource,
/home/takashi/geeklog-1.4.1/system/databases/mysql.class.php,657,Array
I did *clean install* with brand-new database and configuration files.
I also had the same error message when I tried to upgrade from 1.4.0 .
I have one more problem. UTF-8 titles and messages are not displayed correctly,
even if MySQL holds correct UTF-8 strings. I tried to retrieve some articles
from gl_stories with a brief php script with mysql_query and mysql_fetch_array
and confirmed that the table is not corrupted. It seems to be the same problem
as I see bafflegab UTF-8 strings in gl_stories (or other tables) with phpMyAdmin.
I use Debian GNU/Linux etch .
Now I've found that the latter problem (UTF-8 related one) was caused by complex interaction among SET NAMES and server/client default charset.
In geeklog 1.4.0, mysql.class.php didn't care the charset used during the communication between MySQL server and client. Then, in geeklog 1.4.1, mysql.class.php sends SET NAMES just after the beginning of the connection in _connect() method. The problem reported previously was caused by this difference.
I resolved this problem by dumping and restoring the geeklog database by mysqldump. I did some modifications on dump file and my.cnf before/during/after the operation.
Speaking of COM_mail, now that you're heading the UTF-8 way, it's time to implement my UTF-8 mail patch. Without it, none latin letters turn to Gibberish. I'm going to add a "cc"/"bcc" support to the patch.
As for notifications, I really wish you'd add my notification function patch. Then you'd have a central place to control notifications and an admin could even easily add "cc" and "bcc" to them.
Care to explain which problems you see with UTF-8 in emails? If your site is using UTF-8 then emails are sent in UTF-8, too. And that's indicated in the email's Content-type: header.
bye, Dirk
I love Geeklog, but this install has been a nightmare.
---
I have no idea what I'm doing.
And how exactly is your comment going to make things better? Give us some details of the problems you had, please.
bye, Dirk
---
I have no idea what I'm doing.