I followed the instructions of copying 2.0.5 patch onto my 2.0.3 installed site. I get many errors such as:

criteria = null, $id_as_key = false) { $ret = array(); $limit = $start = 0; $sql = 'SELECT * FROM '.$this->db->prefix('modules'); if (isset($criteria) && is_subclass_of($criteria, 'criteriaelement')) { $sql .= ' '.$criteria->renderWhere(); $sql .= ' ORDER BY weight '.$criteria->getOrder().', mid ASC'; $limit = $criteria->getLimit(); $start = $criteria->getStart(); } $result = $this->db->query($sql, $limit, $start); if (!$result) { return $ret; } while ($myrow = $this->db->fetchArray($result)) { $module = new XoopsModule(); $module->assignVars($myrow); if (!$id_as_key) { $ret[] =& $module; } else { $ret[$myrow['mid']] =& $module; } unset($module); } return $ret; } /** * Count some modules * * @param object $criteria {@link CriteriaElement} * @return int **/ function getCount($criteria = null) { $sql = 'SELECT COUNT(*) FROM '.$this->db->prefix('modules'); if (isset($criteria) && is_subclass_of($criteria, 'criteriaelement')) { $sql .= ' '.$criteria->renderWhere(); } if (!$result =& $this->db->query($sql)) { return 0; } list($count) = $this->db->fetchRow($result); return $count; } /** * returns an array of module names * * @param bool $criteria * @param boolean $dirname_as_key * if true, array keys will be module directory names * if false, array keys will be module id * @return array **/ function &getList($criteria = null, $dirname_as_key = false) { $ret = array(); $modules =& $this->getObjects($criteria, true); foreach (array_keys($modules) as $i) { if (!$dirname_as_key) { $ret[$i] =& $modules[$i]->getVar('name'); } else { $ret[$modules[$i]->getVar('dirname')] =& $modules[$i]->getVar('name'); } } return $ret; } } ?>

On the top of the page. Any ideas how this might be fixed?

...mark

samidiabmd.com

Mark:

I did a test tonight and used the complete package 2.0.5 for the update. No errors whatsoever....

Please try this and let us know what happened!

try re-uploading /kernel/module.php from the update package to your webserver.

Hello all,

I still have no idea what caused the problem. Here's what it took to fix it though.

I did a complete unistall of my site (deleted all files on the server).

I upgraded a backup version on my local pc. Then uploaded the new site to the server. Now it works.

I guess I should be happy that the problem's gone...

But I wish I knew what caused it. btw. another feature of the bug was that it sent email messages to one of my webmaster accounts (but not all). The email messages contained the dumps that looked like that posted earlier.