Hello Bosse,

Is it possible for you to provide us with the FTP access as well so that I can check on this? You can edit your first post to include the ftp access .

By the way, the EasyBlog license that you have seems to be licensed under the domain of http://jarnhall.com/ but you are requesting support for http://www.rolfmunke.se . Have you switched domains?

Hi Mark,

Great!

FTP edited.

Yes, jarnhall.com is where I build my customers sites. Should I edit somewhere that it's moved to rolfmunke.se?

/Bosse

Hello Bosse,

Okay, it seems like there are 2 issues here. On some posts, the "comments" are explicitly disabled. To fix this, you just need to edit the post and set "Allow Comments" to true.

Another issue is because in your settings for post options, it has been disabled explicitly. Take a look at my screen shot here, http://take.ms/sOntz . I have turned this on and it should work fine now for some posts, example, http://www.rolfmunke.se/bloggx/2016-01-06-07-12-55/rolfs-blogg-sa-klarar-du-festen-trots-majonaes-i-smoergastartan

By the way, I have updated the domain for you to rolfmunke.se. Please take note that you can only obtain support for this domain in the future. Should you require support for additional domains, please consider purchasing another license

Hi Mark,

Great! But more!

I did know about these settings, but though they handled EasyBlog in-built comment section.
I could easily just have tested it. Sorry...

Is it possible to position the FB comment section above the post?

Anyway, thanks! You made my day! Been driving me crazy not finding out what the heck it was all about...

Hi Bosse,
You're welcome.
For comments positioning, unfortunately it is not possible configure currently. We appreciate your understanding on this.

Ok. Thanks!

/Bosse

Hey Bosse,

You are most welcome. Glad to hear that your issue has been resolved now.

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry. I will lock and mark this thread as resolved.