Thanks for the update. However I updated the Articles Sharing by installing the com_multisitescontent_V1.0.13.zip via the joomla install system. Then I "Purged the converted files" in the com_multisitescontent. The Master site works fine as is.

As for the Slave site the JFile Error is now gone but, still having issues with the:

---With SEF enabled---

Module Parameters:
1. [Type of link to: (Use Local Links using the Multisites Content...)]
[Master Domain URL: www.slavedomain.com]
(List of News show, no JFile error but, get "500 - View not found", link location on the News article link looks like this [http://www.slavedomain.com/component/multisitescontent/3-article-title?site_id=:master_db:])

2. [Type of link to: (Use Local Links using the Multisites Content...)]
[Master Domain URL: www.masterdomain.com]
(List of News show, no JFile error but, get "500 - View not found", link location on the News article link looks like this [http://www.slavedomain.com/component/multisitescontent/3-article-title?site_id=:master_db:])

3. [Type of link to: (Redirect to other side using full URL)]
[Master Domain URL: www.slavedomain.com]
(List of News show, no JFile error but, get "404" error, link location on the News article link looks like this [http://www.slavedomain.com//news/3-article-title])

4. [Type of link to: (Redirect to other side using full URL)]
[Master Domain URL: www.masterdomain.com]
(List of News show, no JFile error but, goes to Master site instead of staying on Slave site, figured it would do that with this setting. We need it to stay on the Slave domain, link location on the News article link looks like this [http://www.masterdomain.com//news/3-article-title])

Hope this makes sense?

Thanks again for your help in this matter!

The 500 and 404 error are probably due to wrong URL settings.

You must understand that the URL is computed based on the target websites.
So if the target website as the SEF enabled, the URL is computed based on this settings.

So for each case, you have to check the URL produced and verify that the target website understand this URL.
It seems this is not the case.

Before enabling the SEF that is not easy to setup, you should check everything without the SEF enabled. Once this is OK with SEF enabled, you can installed and enable the SEF.
Idem with the 404 that is probably resulting of the SEF.

I went in and disabled SEF on the Slave site.

With the Module Parameters: settings for the Slave site set to:
[Type of link to: (Use Local Links using the Multisites Content...)]
[Master Domain URL: www.masterdomain.com]
(everything seems to work fine as expected. It will not work with the SEF enabled only for the Slave site. As for the Master site it works either way.)

The SEF parameter is always the one of the website where is displayed the articles.

So when you redirect to the full URL, this is the SEF of the target website that is analyzed to compute the URL.
When using the article sharing, this is the reverse. This is the SEF of the current websites.

OK...I think I figured it out. So, far with little testing.

I didn't realize that I needed to build a Multisites Article Menu Item in the Slave Site to link to the Master Site News Categories as well as the Master Site. That was causing the linking issue on the Slave Site. I didn't have a Menu Item that referred to the Master site's News articles, that was why it was giving me 404 and 500 errors.

Plus, the recent change to the Content Modules fixed the JFile error. Thanks

Thanks for your help in this matter. I will let you know if I run into any other issues.

Edit: I did come across something wierd in the way the link is built from the route.php file located at : ../mod_multisiteslatestnews/multisitescontent/helpers/route.php. It was adding an extra "/" to the link (ie. //news/articletitle.html) So, I went into the code on route.php and commented this line of code out to see if that helps:

Lines 82-85 (/mod_multisiteslatestnews/multisitescontent/helpers/route.php):
// Normalize the domain name to be sure it is terminated by a slash
if ( !empty( $domain)) {
$domain = rtrim( $domain, '/') . '/';
}to:
// Normalize the domain name to be sure it is terminated by a slash
// if ( !empty( $domain)) {
// $domain = rtrim( $domain, '/') . '/';
//}That seems to fixed that little issue.

First the fix that we delivered does not concern the modules but the "Article Sharing for JMS" component.

Second, you can not remove the normalization.
You probably have to check the SEF extension.
Sometimes SEF extension does not process correctly the URL and add other info.
We already see that with the standard joomla SEF plugin that does not process correctly all the possible SEF cases and in particular the "form" tags.