StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POYShout 5: Function Unserialize Error
primarykey
Id
17652310
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-15T10:41:28.267
FavoriteCount
0
LastActivityDate
2014-01-28T14:33:11.673
LastEditDate
2013-07-15T10:52:16.440
LastEditorUserId
2027231
OwnerUserId
2027231
ParentId
0
PostTypeId
1
Score
0
ViewCount
114
LastEditorDisplayName
text
Body
Bought YShout and have been running on my webserver for some time now. Support isn't answering any emails in a long time. I keep getting unserialize errors that kill the chat box. Error: There appears to be a problem: unserialize() Error at offset 65537 of 86434 bytes. File: filestorage.class.php Line 36. Here is the function with line 36 in it. <pre><code>function load() { if (($contents = $this->read($this->path)) == null) return $this->resetArray(); return unserialize($contents);///////////line 36 } </code></pre> here seems to be the line in the log file that is generating the error message, 65537 seems to be located right at the "a" in "uia:2:" in the string. <pre><code>i:251;a:6:{s:8:"nickname";s:7:"TestUser";s:7:"message";s:30:"when he's online ask him";s:9:"timestamp";d:1373857811.6403610706329345703125;s:5:"admin";b:0;s:3:"uia:2:{s:4:"info";a:1:{s:15:"latestTimestamp";i:-1;}s:5:"posts";a:0:{}}ip";s:12:"76.174.54.75";}} </code></pre> Not really sure how YShout works, but I'm getting this error more than once a day now. I have to delete the log file, then YShout creates a new log from scratch and all is well. But until I delete the log causing problems no one can use the chat window. Ideal solution would be to fix this and figure out whats going on. Secondary solution would be to rename the log file causing the error. This would cause YShout to create a new log file to use and we would have a history of the log that contained the error message.
Tags
<php><serialization>
Title
YShout 5: Function Unserialize Error
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USuser2027231
UserOwnerUserId
1. USuser2027231
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.