By Chris on Sunday, 08 January 2017
Posted in Technical Issues
Likes 0
Views 639
Votes 0
I use the k2 integration and I have a problem showing the avatar and linking to the authors profile in the comments and in the last-comments-module. Could you have a look please?

The link to the image just lacks the author and is just pointing to "http://www.burnyourears.de/autor/" instead of pointing to "http://www.burnyourears.de/autor/chris.html" > that fixed would solve the problem, I guess

Example: "Chris" is a registrated user, it should work with a picture here: http://www.burnyourears.de/alben/45566-nicole-saboune-miman.html#comment-8

Here is the last comment module, on the right side: http://www.burnyourears.de/info/36894-banner.html
The avatars are not showing there either. And the name of unregistered commentator is'n even displayed. And the limitation number of comment length in the modul does not work either... you can see there are shown very long comments – so I guess the modul is broken in some way
Hi Chris,

I use the k2 integration and I have a problem showing the avatar and linking to the authors profile in the comments and in the last-comments-module. Could you have a look please?

I have replicated this on our local and it seems that there are issues on our end. I have issued this to our developer and this fixes will be included on our next release version.

The avatars are not showing there either. And the name of unregistered commentator is'n even displayed. And the limitation number of comment length in the modul does not work either... you can see there are shown very long comments – so I guess the modul is broken in some way

This happened because Komento got issues with K2 components and not integrate properly. I have issued this to our developer also.

Thanks for your understandings
·
Monday, 09 January 2017 10:51
·
0 Likes
·
0 Votes
·
0 Comments
·
Ok, thank you. Is there a release date already for the new version? (Regarding the modul – it's even broken in the backend... see screenshot)
·
Tuesday, 10 January 2017 00:01
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

Is there a release date already for the new version?

Expected date for our new version release is on Jan 13, 2017.

Regarding the modul – it's even broken in the backend... see screenshot)

Can you try to copy attached file to path below and see how it goes.
.../language/en-GB/en-GB.mod_komento_activities.ini
.../language/en-GB/en-GB.mod_komento_comments.ini
·
Tuesday, 10 January 2017 10:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Great, after the update the avatars are shown and the moduls work

But I have one bug left – there is a wrong standard image / error information that an image is missing for guests who comment and are not registered as user. If you can provide me a fast fix or say which line I have to change in the code, that would be cool ... Please see attachment for the bad image, also as an example on this page:

http://www.burnyourears.de/alben/45691-steven-wilson-hand-cannot-erase.html#comment-16,0
·
Saturday, 14 January 2017 01:17
·
0 Likes
·
0 Votes
·
0 Comments
·
Hm, Komento is only retrieving the user's avatar from K2 using the API from K2.

[gist]
K2HelperUtilities::getAvatar();
[/gist]

Can I know how does their avatar appear within K2?
·
Saturday, 14 January 2017 01:30
·
0 Likes
·
0 Votes
·
0 Comments
·
The problem is not with the registered users. The porblem is with guests – there should be a standard image for guests who are not registered and so have no avatar in k2.

Detected another, greater problem: Guest cannot comment. There's a message:

SyntaxError: JSON Parse error: Unexpected identifier "Invalid"

Please try on my page to check the problem
·
Saturday, 14 January 2017 01:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Edit: (Syntax Error: Thought it could be a browser problem. It was not. Problem still exists.)
·
Saturday, 14 January 2017 01:54
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

Can you update your Joomla backend and FTP access at your first post so I can better have a check?

Because I did tried in my locally, it seems work fine and I believe K2 API the way they retrieve the avatar image should return default placeholder avatar image if the user do not have upload any avatar image yet like guest user.

You can refer on my attached screenshot below.
·
Saturday, 14 January 2017 11:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Arlex,

thank you very much for your help. I updates the post with admin and ftp access, please have a look.

Best regards
Chris
·
Saturday, 14 January 2017 17:43
·
0 Likes
·
0 Votes
·
0 Comments
·
You're welcome Chris

Hm, after troubleshoot long hours ago during weekend, I suspect you have turn off "Placeholder image for user if none exists" setting from backend k2 parameter configuration page based on my troubleshooting.

Can you check my attached screenshot below and make sure this setting is turn it on? because I was unable to access your K2 setting from backend page.
·
Sunday, 15 January 2017 12:42
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Arlex,

it was indeed the "Placeholder Image", thank you very much ! So the avatar is working now, but the name of the guest in the comment module is still missing. You can see it in the module with your testcomment.

And the syntax problem still exists – that was a new problem with the komento update on friday, did not have that before.
See image attached -> I tried to post a comment as guest. But after pressing the button, the syntax error comes up (without saving the comment).

Thank you!

Best regards
Chris
·
Sunday, 15 January 2017 17:58
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Chris,

I have applied some fixes on the module and it should display the guest's name now.

As for the error with syntax error, it's most likely that you are getting that error because of the javascript cache on the site which also caches the token. This is the original code, http://take.ms/NOose . On your site it is missing because one of your plugins are probably compiling these scripts into a file.

There is really no way around this unless you do not cache those scripts added on the page.

Please start a new thread if you face other issues instead of replying to this one because we can only link a single issue from our forum to our internal issue tracker.
·
Sunday, 15 January 2017 21:33
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark,

very cool you fixed it, thank you very much – I guess the fix will be part of the next version then?
Concerning the syntax error, I will try to exclude the script from caching. Thank you for the hint ...

All the est,
Chris
·
Sunday, 15 January 2017 21:43
·
0 Likes
·
0 Votes
·
0 Comments
·
Yep, that is correct Chris. The issue will be fixed in our next release. I cannot associate this ticket with our internal issue tracker because this ticket was originally linked to another ticket in our issue tracker. This is why we want you to separate each issues posted on our forums on a different thread

It's easier for our support members to keep track of your issues as well.

Thanks for understanding.
·
Sunday, 15 January 2017 21:46
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post