Bug#366892: phpwiki: unserialize errors
Zed Pobre wrote: > Okay, I'll fire off a few shortly. Thanks, I'll respond over the next couple of days. > There is no such button at the bottom of the PhpWikiAdministration > page on either of my wikis. There is a "Purge Markup Cache" button, > which I pressed, but it did not solve the problem. (In fact, the > serialize error message showed up on the page saying that the cache > had been purged). Hmm, another PHPwiki gremlin strikes. Currently when you upgrade to a new version the "default" (pgsrc) pages are not updated as upstream has not yet added the necessary functionality to do so without potentially overwriting local changes. This is listed as a known problem in their upgrade path so I should have realised you would hit it sorry. Your PhpWikiAdministration page is almost certainly still using the 1.3.7 (or possibly even earlier) source which doesn't have the necessary actions in it. There are two options here. 1) Manually copy the content of /usr/share/phpwiki/pgsrc/PhpWikiAdministration into the PhpWikiAdministration page source field while logged into the wiki as the Administrator. or for a smaller change 2) Add the following code to the end of PhpWikiAdministration !! Convert cached_html to new SQL column This is only needed on SQL or ADODB if you didn't do action=upgrade, but created the new page.cached_html field seperately, and now you want to move this data from page.pagedata over to page.cached_html. Once you've got the convert button, hopefully you'll be able to solve the source of the errors. It looks like I'm going to have to code up a little helper script to solve this problem for other upgrading users. Cheers -- Matt Brown [EMAIL PROTECTED] Mob +64 21 611 544 www.mattb.net.nz signature.asc Description: OpenPGP digital signature
Bug#366892: phpwiki: unserialize errors
Hi Zed, Zed Pobre wrote: > I accidentally upgraded an old 1.3.7 install of PHPWiki. This broke > all of my wikis, in case you were unaware that the automatic upgrades > still aren't working, but that's not what this bug is about, as I > managed to massage that part back into shape. I'm not aware of any upgrade issues other than the one reported in #361337 which I'm waiting to hear back from the reporter for more info on. If you have some specific issues could you please file bugs on them so that I can look into it? Thanks. > Unfortunately, I am still getting the following errors at the bottom > of each page: > > lib/WikiDB/backend/PearDB_pgsql.php:134: Notice: unserialize(): Error at > offset 0 of 192 bytes (...repeated 4 times) > > lib/WikiDB/backend/PearDB_pgsql.php (In template 'browse-footer'):134: > Notice: unserialize(): Error at offset 0 of 196 bytes > > lib/WikiDB/backend/PearDB_pgsql.php (In template 'browse-footer'):134: > Notice: unserialize(): Error at offset 0 of 268 bytes > > > This doesn't actually seem to prevent the wiki from working in any way > that I've noticed, but it is unsightly, and a quick perusal of the > section involved makes me think that it is trying to unserialize data > that wasn't serialized to begin with, which may be a sign of a much > larger problem. Hmm, I have a theory. The package bypasses the upgrade.php mechanism that upstream recommends you use when switching between new versions because I've found it too be too buggy and reliable. But I may have missed a step. Older versions of PHPwiki sometimes stored cached_html as a page property, this has now be moved to its own column in the page table. This may not be happening in your case. Please go to PhpWikiAdministration and click the Convert cached_html button at the bottom of the page. Does this fix the problem? Thanks for your help. -- Matt Brown [EMAIL PROTECTED] Mob +64 21 611 544 www.mattb.net.nz signature.asc Description: OpenPGP digital signature
Bug#366892: phpwiki: unserialize errors
Package: phpwiki Version: 1.3.12p2-1 Severity: normal I accidentally upgraded an old 1.3.7 install of PHPWiki. This broke all of my wikis, in case you were unaware that the automatic upgrades still aren't working, but that's not what this bug is about, as I managed to massage that part back into shape. Unfortunately, I am still getting the following errors at the bottom of each page: lib/WikiDB/backend/PearDB_pgsql.php:134: Notice: unserialize(): Error at offset 0 of 192 bytes (...repeated 4 times) lib/WikiDB/backend/PearDB_pgsql.php (In template 'browse-footer'):134: Notice: unserialize(): Error at offset 0 of 196 bytes lib/WikiDB/backend/PearDB_pgsql.php (In template 'browse-footer'):134: Notice: unserialize(): Error at offset 0 of 268 bytes This doesn't actually seem to prevent the wiki from working in any way that I've noticed, but it is unsightly, and a quick perusal of the section involved makes me think that it is trying to unserialize data that wasn't serialized to begin with, which may be a sign of a much larger problem. I run two wikis in parallel on this machine, both off of PostgreSQL. Both display the errors. The errors are displayed whether or not you have authenticated. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.13.1.erdos Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Versions of packages phpwiki depends on: ii apache [httpd]1.3.33-6sarge1 versatile, high-performance HTTP s ii debconf 1.5.0 Debian configuration management sy ii php4 4:4.3.10-16server-side, HTML-embedded scripti ii php4-pear 4:4.3.10-16PEAR - PHP Extension and Applicati ii php4-sqlite 1.0.2-7PHP4 bindings to SQLite, a file-ba ii sqlite2.8.16-1 command line interface for SQLite ii ucf 1.17 Update Configuration File: preserv -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
