I have been going nuts over this for 3 weeks now. I cannot figure out what is causing my problem.

I have MT 3.2 installed on an Apache server running freebsd. I use Berkeley DB (although I was trying to upgrade to MySQL when I discovered another problem). I have three blogs currently, and more planned. There are currently 112 posts in the 3 blogs.

Perl version is 5.6.1, CGI 2.78, DB_File 1.811

I get a 500 error on the 3rd blog when I attempt to publish a new post, or mark a draft post as publish. I also get the same error when I attempt to save the published post after editing.

Despite the error, the individual archive appears to be published correctly, and when I refresh the entry list the entry is marked as published. Sometimes the index templates do not get published correctly, but they can be rebuilt individually without errors. If I fiddle with the entry each time I post, I can make it work. However, my other authors are not computer literate enough to do this.

I have tried reinstalling all the MT files, plugins, etc... in ASCII mode, just in case I missed one. I have also checked the permissions on every cgi script, and changed all the perl scripts to 755 at the same time. Just in case, I have also changed the mt-config.cgi settings to:



I have tried reverting to the standard templates, re-installing archive templates that I don't need, and even starting a fourth blog with the default templates. The problem continues to occur on the new blog. However, the problem has never occured on the first two blogs.

I thought it might be a timeout error, howerver the entries in the third blog are quite short and the first two blogs have far longer entries.

I thought it might be one of my entries in the problematic blog, so I created the 4th blog with no entries and default templates. The problem is still there.

I thought it might be disk quota limit from my ISP, but I am only at half quota.

I don't know if this might be a Berkeley limitation, so I have looked into switching to MySQL, but another problem has arisen there (reported in another post).

Everything was working so well, until I upgraded to MT 3.2.

Any help would be greatly appreciated,

Nick

Thanks to Lisa from Sixapart, I have been able to resolve one of the problems. I have been able to complete the transition to MySQL. The 500 error does not occur when I use the MySQL database, so I infer that the Berkeley DB is the problem. i.e. it is not my templates or my entries that are the problem. It might be limits within Berkeley, or it could be the ISP has improperly installed it. Or, there might be an incompatibility between MT 3.2 and Berkeley DB. Or conceivably, there is another cause that I cannot identify.

Whatever it is, I hope this problem doesn't arise for anyone else. If you can, upgrade to the MySQL database.

Nick