Hey there smart,
Thanks for your reply, but I'd like you to reconsider. I agree that all modern eShops should increase their support for other related and relevant 3rd party extensions, and I'm sure the redSHOP team would happily integrate JComments support once the code to support it was established. However the team are concentrating at the moment on pertinent bug fixes and other pending feature requests, so I'm trying to help them out by saving them the development and testing time, and I'd appreciate a hand from you since you're much more familiar with how JComments works.
I've taken a look through some of the integration guides for supported 3rd party components (
http://www.joomlatune.com/jcomments-integration-guide.html) and I've noticed a common theme amongst most of the integrations: the code required to establish a connection with JComments from within the component looks generally like this:
global $mainframe;
$comments = $mainframe->getCfg('absolute_path') . '/components/com_jcomments/jcomments.php';
OR
global $mosConfig_absolute_path;
$comments = $mosConfig_absolute_path . '/components/com_jcomments/jcomments.php';
if (file_exists($comments)) {
require_once($comments);
${component_variable} = JComments::showComments({record ID}, '{component name}', {record name});
OR
echo JComments::showComments({record ID}, '{component name}', {record name});
}
Based on the similar instructions across all integration manuals, I'd assume that JComments could be supported within redSHOP with something like this:
global $mosConfig_absolute_path;
$comments = $mosConfig_absolute_path . '/components/com_jcomments/jcomments.php';
if (file_exists($comments)) {
require_once($comments);
$product_reviews = JComments::showComments($product_id, 'com_redshop', $product_name);
}
I've used VM's instructions as a basis, since redSHOP has a very similar design structure. However, I'm not sure which file this should go into: the product details template that the client creates, or one of the model files that control the HTML output used when the {product_reviews} tag is present on the product details template.
If you wouldn't mind, I'd really appreciate your assistance with this, it doesn't look like much is required to get this integration supported, and you seem to be in a better position to tell what goes where. I'll help you how I can, if you'd like me to test anything on my end, just let me know.