The archive at:
http://discussions.gamingoutpost.com/
seems to have some problem for any topic that have any reply to it.
Topic that have 0 replies can be read normally.
For topic that have any reply to it, the below error will be shown:
Fatal error: Allowed memory size of 94371840 bytes exhausted (tried to allocate X bytes) in /home/aresteia/discussions.gamingoutpost.com/sources/classes/bbcode/class_bbcode_core.php on line 902
where X is a variable corresponding to the topic page bytes.
The website below could possibly help to remedy the problem:
http://drupal.org/node/76156
I'm not certain what you mean by this; however, the archives are shut down--posting is not allowed there. If you wish to comment on an archived thread, the best way to do it is to post the link here and comment in the new forums.
If you mean that you can't view threads in which you have previously posted, the best advice anyone can give is log out of that forum and read it as a visitor. All the functions that are available to registered members have been disabled anyway, and visitors are not restricted from reading anything posted there. (I remember that there was a problem that some members could not find some threads on which they had posted if they were logged in, but could if they were not. I don't remember the details.)
If you want me to take a look at the problem you'll have to give me your user name over there; I can't identify your posts without it.
Hope this helps.
--M. J. Young
If you mean that you can't view threads
The above is what I mean. Even as visitor I still get the same error.
Try to read the link below for an example:
http://discussions.gamingoutpost.com/index.php?showtopic=82716&view=getnewpost
That is strange. I get the thread without any problem.
I suppose I should ask your operating system and browser. Other possible fixes include clearing cookies (or manually deleting any from that server)--and that's about the extent of my knowledge on it, but perhaps Aaron will have some advice.
--M. J. Young
I, too, can see the thread just fine without errors. Not being able to reproduce the problem makes fixing it pretty difficult unfortunately.
Other possible fixes include clearing cookies
That fixed it. Thank you.
Glad to help.
--M. J. Young