I am having a odd error on my forum with the upgrade that I did went from 1.6.4 to 1.6.6, and the forum is not showing the post content.. In threaded mode it shows the content but not in linear mode.
any ideas?
![[Image: mybberror.jpg]](https://camo.mybb.com/dd5df5c62f75c8d43a658ae5af99bd0a703ae30b/687474703a2f2f6761746f2e7468656d617866696c65732e696e666f2f6d7962626572726f722e6a7067)
this is what I am getting
found another thread with the same issue that has not been answered..
http://community.mybb.com/thread-113106.html
downgraded back to 1.6.4 and said the hell with this upgrading crap.. searched these forums and could not find one answer in regards to my issue..
We can't really help if you just downgrade. If you upgrade again then we can troubleshoot it.
ok I have tired once again to upgrade to 1.6.7 from 1.6.4 and I get this error
Quote:ww www
w
w
w w
wwwwwwwwww
w
this is what I get in threads..
To rule out plugins as a cause of this issue, please try the following:
If you are using MyBB v1.6.4 and newer:
Go to AdminCP >> Configuration >> General configuration >> Disable all plugins >> YES
For all other versions older than MyBB v1.6.4:
In
./inc/init.php, find the code:
define("TIME_NOW", time());
After this code, add this:
define("NO_PLUGINS", 1);
Then save and/or reupload this edited version of the file so the forum will run the new code.
This will stop plugins being run when a page on the forum is loaded; it will not edit, delete or reset any content the plugin has added or changed, it will just temporarily stop the plugins being loaded, so some features on your forum may be temporarily missing or broken whilst this code is in place. When you remove this code, plugins will work again exactly as they were before. This change helps us to see if a plugin is the cause of a problem, without you having to manually deactivate every single plugin, which would mean you may lose data from them.
If your issue is fixed when this code is added, then the cause of your issue is a plugin; please post a list of your plugins and we will try and help you find which one it may be. If the problem still happens with this code added, then it is unlikely a plugin is the cause, in which case we will investigate the issue further.
Thank you.