Is it occuring every time a non admin posts? Have you checked your error_logs?

this may be related to database or similar
1342161062 is simply the unix timestamp for the error ;-)
Fri, 13 Jul 2012 06:31:02 GMT

my mistake.. that's a bad untrapped php error. try the log for that timestamp above or put php errors = on in htaccess, elgg by itself does not report all the details of the php issue at that time in the elgg exception handler's views.

@Team Webgalli: yes is it occuring every time whit non admin users

I checked error logs in www.domain.com/logs
Repeats the errors:

[Fri Jul 13 02:32:25 2012] [error] [client xxxxxxx] Deprecated in 1.8: register_elgg_event_handler() was deprecated by elgg_register_event_handler() Called from [#5] /home/xxxxx/domains/domain.com/public_html/mod/spam_login_filter/start.php:20, referer: http://www.domain.com/profile/username

[Fri Jul 13 02:32:25 2012] [error] [client xxxxxxx] Deprecated in 1.8: isadminloggedin() is deprecated by elgg_is_admin_logged_in() Called from [#5] /home/xxxxx/domains/domain.com/public_html/mod/spam_login_filter/start.php:27, referer: http://www.domain.com/profile/username

I disabled the plugin spam_login_filter and the error persists

@DhrupDeScoop: What is the path of httaccess to which you refer?

@Ve I have the same problem, I am new to elgg my site is still on test subdomain and did not put on air just becoz of that issue I am having, as an admin i can post but as a normal member nobody can post site gives Fatal Error, I did lots of time fresh installation without installing other plugins but this problem is still there like a nightmare. I tested with 1.8.6, 1.8.7 and these days struggling with 1.8.8 but this fatal error is so annoying I do not like messageboard plugin wanna get rid of that, I want a smiple wall activity feed like facebook has in their main home page and in users profiles :(

Please, someone who can help?

@kisssssss4ever: Use some theme?

You should be able to search your log for the code to see what is causing the exception. Oh, and upgrade to the latest version of Elgg (1.8.8). There was a fix in 1.8.7 for something that should have been a warning but was treated like an exception.

@Cash: Ok, thanks. I'll update to v1.8.8. But keep in mind that @ kisssssss4ever reported the same problem with v1.8.7. and v1.8.8

@Ve : these error_logs are insufficient. Check the log completely and you will see other valuable informations too like failed to connect to DB etc.. Look through other messages in log