NewsFeaturesDownloadsDevelopmentSupportAbout Us

Beta testing pLog 1.0.1

The first maintenance release of pLog 1.0 is ready to be tested. pLog 1.0.1 fixes most of the issues that have been found in pLog 1.0 and also adds a few small new features. Even though 1.0.1 is looking much better than 1.0 and there should not be any major issues with it, we will still hold a beta testing round for about 2-3 weeks.

The current 1.0.1 development version is available from svn from the http://devel.plogworld.net/svn/plog/plog/branches/plog-1.0.1 folder (please see our instructions on how to access the pLog subversion repository) and packages are available in tar.gz or tar.bz2 format. Previous packages can be downloaded from the snapshots folder if interested.

Following the trend of pLog maintenance releases, there is no need to run the wizard.php script in order to upgrade your current installation from pLog 1.0 to pLog 1.0.1. Just download the package, unpack the files and upload them to your web server making sure that you are overwriting all of the old files. As soon as the process is complete, you will be running a pLog 1.0.1 installation.

In case you find any bugs or need to report something, please use the project's bug tracking system

For those interested in the issues that have already been addressed in this version, please read on.


< !-- ADS -->

As you can probably see, there are many more issues than we ever hoped for, but we appreciate the patience and efforts of our users who have mananaged to live with these bugs and who have helped to detect and even fix most of them.

394: fonts are too small for chinese (both traditional and simplified)
447: Logout on Dashboard
455: Default custom urls not working with session.use_trans_sid
451: WYSIWYG Editor bug in admin.
446: incorrect variable name in configfilestorage.class.php
445: Rename index.php - broken images
443: the parent id of comments is not being saved in the db
425: XML-RPC Ping hosts are erased from the database
414: Character set in notification emails
329: Issues with PHP's safe_mode
411: link to the blog from admin.php
424: move_uploaded_file doesn't appear to work across partitions
427: Cannot change default_blog_id with admin interface.
385: problems parsing search-engine friendly URLs
415: when a blog uses a locale that a plugin does not provide, en_UK should be used by default
422: using usernames with quotes when posting comments results in an error
417: error inserting descriptions of albums that have quotes (')
412: Core bug in the logging framework
413: Core bug in UsernameValidator
401: templates are not xhtml compliant
407: PrettyRequestGenerator::postUserLink() is generating incorrect links!
404: Forgotten calls to the logging framework in some classes
405: Bug in the resource server when using subdomains
400: Reduction of the amount of data pulled from certain tables
369: Issues and conflicts with custom URLs
397: when "show future posts in the calendar" is enabled, the rss feed loads all the posts

  1. Trackback Trackback: Podcasting directly from pLog
    Posted by 24 May 2005, 06:34
  2. Trackback Trackback: pLog 1.0.1 Beta 測試版釋出了!
    pLog1.0 發表後的第一個維護版本 1.0.1 已經開始測試了。pLog 1.0.1 修復了大部分的 pLog 1.0 中出現的問題,並且加入了一些新功能。不過,即便 1.0.1 看起來要比1.0更好一些,而且沒有任何主要的
    Posted by pLog1.0 發表後的第一個維護版本 1.0.1 已經開始測試了。pLog 1.0.1 修復了大部分的 pLog 1.0 中出現的問題,並且加入了一些新功能。不過,即便 1.0.1 看起來要比1.0更好一些,而且沒有任何主要的 19 May 2005, 19:11
  3. Trackback Trackback: moblogging in pLog
    Now you can create posts and upload images from a cell phone or from any email client.
    Posted by Now you can create posts and upload images from a cell phone or from any email client. 19 May 2005, 06:22
  4. Trackback Trackback: Plog 1.0.1beta开始测试
    plog1.0的第一个维护版本已经开始测试。plog1.0.1修复了大部分的plog1.0中出现的问题,并且加入了一些新功能。不过,即便1.0.1看起来要比1.0更好一些,而且没有任何主要的大毛病,我们也仍然
    Posted by plog1.0的第一个维护版本已经开始测试。plog1.0.1修复了大部分的plog1.0中出现的问题,并且加入了一些新功能。不过,即便1.0.1看起来要比1.0更好一些,而且没有任何主要的大毛病,我们也仍然 10 May 2005, 00:38
  5. Trackback Trackback: Plog 1.0.1beta开始测试
    plog1.0的第一个维护版本已经开始测试。plog1.0.1修复了大部分的plog1.0中出现的问题,并且加入了一些新功能。不过,即便1.0.1看起来要比1.0更好一些,而且没有任何主要的大毛病,我们也仍然
    Posted by plog1.0的第一个维护版本已经开始测试。plog1.0.1修复了大部分的plog1.0中出现的问题,并且加入了一些新功能。不过,即便1.0.1看起来要比1.0更好一些,而且没有任何主要的大毛病,我们也仍然 10 May 2005, 00:36
  6. Trackback Trackback: pLog 1.0.1
    Die Beta-Phase fr pLog, das CMS mit dem die Inhalte dieser Seite verwaltet werden, hat begonnen. Eine bersicht ber die nderungen bietet dieser Art
    Posted by Die Beta-Phase fr pLog, das CMS mit dem die Inhalte dieser Seite verwaltet werden, hat begonnen. Eine bersicht ber die nderungen bietet dieser Art 04 May 2005, 08:53
  1. Comment All fine

    Upgraded, everything seems to work fine.
    Good works guys.

    Posted by Alexander Kaiser 04 May 2005, 06:58
  2. Comment No problems so far

    Updated to V1.0.1 yesterday. No problems so far.

    Posted by vurt 04 May 2005, 08:55
  3. Comment Smarty Memory

    Does this patch remedy the Smarty Template memory problems some people have been having. Couldn't see a specific answer up top (might be blind again though).

    Posted by Erryn 04 May 2005, 15:22
  4. Comment Re: Smarty Memory

    Unfortunately, no. We are still working on it but since it looks like it's going to take a while until we can fix those, we decided to go ahead with 1.0.1 and wait for a potential 1.0.2 or 1.1 to fix the issues with Smarty.

    Posted by oscar 04 May 2005, 17:37
  5. Comment No Subject

    after urgrating, the link "more" does not work with personnal url

    Posted by culturec 05 May 2005, 09:35
  6. Comment CustomField problem

    Trying to use the plugin "secret", I found something weird. It seems that somehow only ONE blog can have the "secret article" function working appropriate. The lastest blog that enables the plugin gets it working.

    After digging the code, I believe there is a logical bug with the following piece of code in the module "customfieldsvalues.class.php" lines 75-78:

    while( $row = $result->FetchRow()) {
    $field = $this->_fillCustomFieldValueInformation( $row );
    $fields[$field->getName()] = $field;
    }

    Because a right outer join is executed before the filling of custom fields, if the fields with NULL produced the outer join appear after the correct fields for the given article, the filling procedure will overwrite the correct values with NULL. I propose to modifiy the code as:

    while( $row = $result->FetchRow()) {
    $field = $this->_fillCustomFieldValueInformation( $row );
    if ( !$field->getValue() ) {
    if ( !$fields[$field->getName()] ) {
    $fields[$field->getName()] = $field;
    }
    }
    else {
    $fields[$field->getName()] = $field;
    }
    }

    I guess such a fix should make sense. Happy pLog!

    Posted by ypchen 03 Jun 2005, 06:36