4
PHP/5.2.3
MySql/5
This occurs only with old posts after the upgrade to php5, New posts are fine. I am thinking that it is a db problem.
The data is still there, however it does not propagate from the <{foreach}> loop.
New posts (post upgrade) display fine, absolutely no problems except for the duplicate index keys that occur in sql.
Quote:
Got error 134 from storage engine
As far as I know these are pointless, on my dev site I dropped all of the duplicate keys and the errors in admin stopped.
After doing so, I didn't notice any slow down, as I was led to believe that was the reason there were duplicate index keys defined (for speed/optimization).. However this may differ on larger boards... idk really MySql/5 simply does not like the way the cbb fields are defined.
I have a funny feeling that its just the difference in table structure for me. So yes, "Bug" was the wrong word to use.