Joomla Templates Club 406,261 posts

[Andrew Winkler Friend Andrew WinklerJoin date: September 2014Posts: 725Downloads:206Uploads:31 Thanks: 291 Thanked: 34 times in 2 posts]

#192487

When clicking on any of the sidebar menu category links, which display a ‘wall’ of articles in the selected article category, the kunena discuss plugin form is displayed underneath every article preview, even if frontpage and blog layout are disabled in the kunena discuss plugin settings.

For site page example: http://therebel.org/news/editorial/

For kunena discuss plugin settings see attached screenshot

---

Attachments:

1. 

[phong nam Friend phong namJoin date: May 2015Posts: 3779Downloads:1Uploads:587 Thanks: 499 Thanked: 974 times in 888 posts]

#513342

Hi andrewwinkler,

For now, all the categories page’s links on sidebar are invalid on your site so I can not check out the issue you had mentioned.

However, the Content-Kunena Discuss plugin will display automatically its form at the afterDisplayContent position defined in blog item layout when enabling the plugin settings. In this case, I’d like to suggest you to try these steps to solve your issue:

– Open templatesja_wallhtmlcom_contentcategoryblog_item.php file, remove or comment line:

<?php echo $this->item->event->afterDisplayContent; ?>

– Clear System cache after updating changes.

1 user says Thank You to phong nam for this useful post

1. Andrew Winkler

[Andrew Winkler Friend Andrew WinklerJoin date: September 2014Posts: 725Downloads:206Uploads:31 Thanks: 291 Thanked: 34 times in 2 posts]

#513406

Thanks for the quick response. I think what’s happening here is having the Kunena discuss form being displayed for every blog layout item causes the SQL engine being pushed to the wall (sorry about the pun). Let’s hope your suggestion will do the trick.

[Andrew Winkler Friend Andrew WinklerJoin date: September 2014Posts: 725Downloads:206Uploads:31 Thanks: 291 Thanked: 34 times in 2 posts]

#513498

Yes, it fixed it. The broken category links issue was unrelated. It was caused by a misconfiguration in the SEF URL plugin.

1 user says Thank You to Andrew Winkler for this useful post

1. phong nam

[Author]

Posts