Kommentare

Serendipity 1.5-beta1 released

rollenc am um :

The search function did not work as expected. Notice for the administrator of this blog: This may happen because of missing index keys in your database. On MySQL systems your database user account needs to be privileged to execute this query:

CREATE FULLTEXT INDEX entryidx on serendipityentries (title,body,extended)

The specific error returned by the database was:

SELECT e.id, e.authorid, a.realname AS author, e.allowcomments, e.moderatecomments, a.email, e.timestamp, e.comments, e.title, e.body, e.extended, e.trackbacks, e.exflag, e.isdraft, e.last_modified, a.username AS loginname

                  FROM
                        serendipity_entries e
             LEFT JOIN  serendipity_authors a
                    ON  e.authorid = a.authorid
             LEFT JOIN  serendipity_entrycat ec
                    ON  e.id = ec.entryid
                         LEFT OUTER JOIN serendipity_entryproperties ep_access
                                          ON (e.id = ep_access.entryid AND ep_access.property = 'ep_access')

LEFT JOIN serendipityentryproperties epsticky ON (e.id = epsticky.entryid AND epsticky.property = 'epissticky') WHERE (MATCH(title,body,extended) AGAINST('ubuntu*' IN BOOLEAN MODE)) AND isdraft = 'false' AND timestamp

Garvin am um :

Thanks for that bugreport. Sadly this was caused by a last minute change.

Please download this file:

http://svn.berlios.de/viewcvs/checkout/serendipity/trunk/include/functions_entries.inc.php

and overwrite the include/functions_entries.inc.php file with that.

Bectrade am um :

Thanks for your quick reply and fix.

Hanno am um :

Why do you switch to sha1, knowing this is already under attack similar to md5? While it may take some time till sha1-attacks reach a state where this will matter for password storage, it'd be a safety measure to switch to sha256 with salt.

Garvin am um :

It's salted, so we could've even stuck to md5.

mike johnston am um :

Is there any eta on a release candidate or new beta?