alcaeus wrote: BTW, the PM issue is fixed in CVS. It's a problem when obtaining the censored words; a wrong variable is being used ATM so the preg_replace() call fails....
asinshesq wrote:alcaeus wrote:BTW, the PM issue is fixed in CVS. It's a problem when obtaining the censored words; a wrong variable is being used ATM so the preg_replace() call fails....
What problem? Is it different from the code change error that was officially dealt with in the third post of this thread: http://www.phpbb.com/phpBB/viewtopic.php?f=14&t=380687 ? If so, could someone please describe how to notice the problem on our boards and post the cvs fix here? Thanks!
Code: Select all
if ( !($privmsg = $db->sql_fetchrow($result)) )
{
redirect(append_sid("privmsg.$phpEx?folder=$folder", true));
}
$privmsg_subject = preg_replace($orig_word, $replacement_word, $privmsg_subject);
$privmsg_subject = ( ( !preg_match('/^Re:/', $privmsg['privmsgs_subject']) ) ? 'Re: ' : '' ) . $privmsg['privmsgs_subject'];
Code: Select all
if ( !($privmsg = $db->sql_fetchrow($result)) )
{
redirect(append_sid("privmsg.$phpEx?folder=$folder", true));
}
$orig_word = $replacement_word = array();
obtain_word_list($orig_word, $replacement_word);
$privmsg_subject = ( ( !preg_match('/^Re:/', $privmsg['privmsgs_subject']) ) ? 'Re: ' : '' ) . $privmsg['privmsgs_subject'];
$privmsg_subject = preg_replace($orig_word, $replacement_word, $privmsg_subject);
asinshesq wrote: If so, could someone please describe how to notice the problem on our boards
Mr. Sharkey wrote: In many cases, running update_to_latest does nothing more than insert the new version number into the phpbb_config tables. That's not to say that this is the only operation it performs, but unless your database is damaged or the version upgrade requires adjustments or additions to the database structure, no other actions are performed.