×

Notice

The forum is in read only mode.
Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: New paid user - questions on Latest Module

New paid user - questions on Latest Module 8 months 2 weeks ago #35482

  • Uber Pro
  • Uber Pro's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 3
  • Thank you received: 0
Hi there, I just purchased CComment subscription, installed it on my J3.6 development server, and migrated all the comments from JCOmments (about 8,000 comments) into CComments. That went well. Looks like you have put some hard work into this component - I'm excited to use it!

I turned on the latest comments module that comes with CComment and have a few questions:

1. Enabling the module caused the site to stop working - there's a clash with Kunena's latest module of some sort. The error is: Cannot redeclare class BBCodeLexer in /var/www/libraries/kunena/nbbc.nbbc.php (I have the latest Kunena software installed). For now I turned off the Kunena latest module, as I don't HAVE to have it running.

2. The JCOMMENTS latest module (screen capture attached here) allowed me to display the latest comments in a manner that seemed SEO friendly - and in a way that makes sense to me. I was able to display the name of the article the latest comment was made on - I don't see that ability in the CCOMENTS latest module when set to "latest" setting?
My other issue/fear/request is that the URL's the CCOMMENT latest module are showing do not seem SEO friendly like the JCOMMENTS one. Here is an example:

JCOMMENTS Latest: mysite.com/who-plays-what/192-motley-cru...uipment#comment-8079
CCOMENTS Latest: mysite.com/component/comment/?task=comment.gotocomment&id=7794

Notice the JCOMMENTS link uses the SEO URL's for the actual article and at the end it appends the #comment versus the CCOMENTS link which is actually creating a brand new URL (duplicate I guess) that takes the user to the page.

3. Finally, the tooltip that shows up when hovering is showing html code in it - breaks, strong tags etc... That doesn't seem elegant.

I don't want to unfairly/fairly compare you to anyone other product - but I do want to make sure I understand what is going on, and hope you also have an open mind to these comments. There's probably a chance I missed features to address my questions above, so let me know. Thanks much!
Attachments:

New paid user - questions on Latest Module 8 months 2 weeks ago #35489

  • Uber Pro
  • Uber Pro's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 3
  • Thank you received: 0
Additional questions:

4. When I enable the search plugin that comes with CCOMMENT, and I search for some text that I know is in a comment, in the search results, I simply get something like this:
1. Reno Smith
(Comments / Reno Smith)
Reno Smith, Reno Smith
Created on 22 June 2010

I don't see the title of the article that was commented on. I don't see any of the comment's text either.

5. For some reason, all break tags (<br />, <br>) are being displayed in the text of the comments that are displaying on content pages. How can this be set so that break characters actually equate to line breaks?

New paid user - questions on Latest Module 8 months 2 weeks ago #35495

  • Daniel Dimitrov
  • Daniel Dimitrov's Avatar
  • Away
  • Administrator
  • Administrator
  • Posts: 9618
  • Karma: 154
  • Thank you received: 1081
Hi,

1. There is a clash with Kunena, because we use the same library for parsing bbcode. However in our code we are checking for the presence of BBCodeLexer and are not redifining it if it exists. Can you try to have the kunena module first and after that our module?

2. SEO friendly to whom? To your users or to google? For google it shouldn't matter as the url has a 301 redirect. The reason for this urls is pretty simple: performance. You can use the comment module with several components. If I was to try to find the correct joomla SEF url I would have to query the database a lot. That's why I've decided to have a normal redirect url. When clicked we perform the necessary checks to find the correct url and redirect to it
the latest comment module has an option to show a title. It's then shown in the tooltip. If you don't like that design you can make a template override and style the template as you wish.

3. It seems taht the bbcode support is not on?

4. Hm, I haven't tested the search plugin for some time. I'll have to check what we do there.

5. I'll have to look at that.

Regards,
Daniel

New paid user - questions on Latest Module 8 months 2 weeks ago #35497

  • Uber Pro
  • Uber Pro's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 3
  • Thank you received: 0
Thanks for the response Daniel, appreciate it!

Here's my thoughts:

1. I moved Kunena to top and it worked. So, to fully close the loop, this would be a Kunena bug right? I can take it to them if so.

2. For SEO URL's, as long as Google doesn't pick them up as duplicate url's, I'm OK with that. As long as there's a mechanism to prevent that (you are saying you are 301 redirecting them once the user clicks the link and the request goes in to Joomla?).

3 and 5. I have BB codes on inside CComment. I think an issue here is that comments imported from JComment have <br /> tags to represent line breaks. CComment uses BBCode (I don't have much experience with BBCode) which means the html tags that came in via the import mechanism provided by CComment are getting displayed as pure text. If that's true, I'd think there could be some sanitization in the importer functionality that converts <br /> to whatever ccomments needs...... say......what would that be? If you can tell me what <br /> should be replaced with, so that the we get line breaks where <br /> existed, I could try to do an updated of that column in the table.....

4. I'd love it if you took a quick peek at the search plugin. I was able to hack it to show the actual comment text, however it is still using the comment author's name as the title/link and am not sure how to fix that.

Thanks Daniel!
  • Page:
  • 1
Time to create page: 0.110 seconds