fatal error with composer
By steven moore on Monday, 02 May 2016
Posted in Technical Issues
Replies 10
Likes 0
Views 834
Votes 0
So, I jsut upgraded my easyblog installation to the newest from 3.9 i believe...

when I try to write a post, i get this error...

Fatal error: Call to a member function hasCustomFields() on a non-object in /home/ascens81/public_html/stevetmoore.me/administrator/components/com_easyblog/includes/composer/composer.php on line 295

what do I do? I cannot write.
You are getting this error most likely because:

1. You did not have a default category. Go to the categories at the back end of EasyBlog and ensure that at least 1 category is set as default.

2. Your default category is unpublished. Make sure that the category is published.
Mark
·
Tuesday, 03 May 2016 00:10
·
0 Likes
·
0 Votes
·
0 Comments
·
did both of those things... and still not working.
steven moore
·
Tuesday, 03 May 2016 02:44
·
0 Likes
·
0 Votes
·
0 Comments
·
and its public
steven moore
·
Tuesday, 03 May 2016 02:46
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Steven,

I tried to access the back end of your site with the user account which you provided but it is not working. Can you please set the user with super administrator privileges so that I can check on your issues?
Mark
·
Tuesday, 03 May 2016 11:01
·
0 Likes
·
0 Votes
·
0 Comments
·
sorry bout that, the account is a superuser now.
steven moore
·
Wednesday, 04 May 2016 00:23
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Steven,

I don't seem to hit any errors and the composer is loading up fine without hitting any errors for me as you can see here, http://screencast.com/t/twLN5cps

Am I missing anything?
Mark
·
Wednesday, 04 May 2016 00:34
·
0 Likes
·
0 Votes
·
0 Comments
·
I had this same problem. (5.0.34)

My client deleted the "Uncategorized" default category, leaving no default category.

Setting a new 'default' category worked!

Thanks for the solution!
Tim
·
Thursday, 05 May 2016 22:09
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating Tim, glad that your issues are resolved now
Mark
·
Friday, 06 May 2016 00:41
·
0 Likes
·
0 Votes
·
0 Comments
·
yeah, I just realized it is user specific... only my account. So I made a new admin account, and it works fine.
steven moore
·
Friday, 06 May 2016 02:24
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Steven,

May i know your issue is it resolved? Because I've tried to open composer from backend, it seems work fine.
Arlex Wong
·
Friday, 06 May 2016 10:19
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post