Answers.Body: <p>I figured it out!</p>
  
  <ol>
  <li>In Section settings > Propagation Method, you must choose 'Save entries to all sites enabled for this section', or, if you're using site groups, choose the appropriate group. This basically shares entries across multiple sites.</li>
  <li>If your entries were previously only associated with one site, doing this will cause entries to be resaved.</li>
  <li>When calling entries, do not specific the site from which they are pulled, in other words, do not include site or siteId in the entries query.</li>
  </ol>
  
  <p><code>{% set entries = craft.entries.section('sectionName').limit(10) %}</code></p>
  
  <p>Now your urls will be correct, relative to the current site.</p>
  
  <p>On Site 1: <em>firstSiteDomain.com/news/president-elect-not-sociopath-at-all-billions-rejoice</em></p>
  
  <p>On Site 1: <em>SecondSiteDomain.com/news/post/president-elect-not-sociopath-at-all-billions-rejoice</em></p>
  
  <p>Even though the entries, news in this case, may be intended as "tied to" Site 1, you must 'share' them with Site 2 in order for Site 2 to load them and create <em>entry.url</em> correctly.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-17T16:24:31.240Z
Answers.Text: Aha! Then I completely misunderstood what you tried to do, and was thinking too complex. I thought you wanted to list entries from Site 2 on Site 1, but have them link to the full view on Site 2. Glad you found the solution!
Answers.UserDisplayName: KSP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-16T21:12:40.360Z
Answers.LastActivityDate: 2019-12-16T21:12:40.360Z
Answers.UserDisplayName: 4midori
Answers.Body: <p>I'm guessing a bit here, and I haven't tested it, but I would think once you load the entries in your template, they are entries just like any other, and Craft doesn't keep more track of where they came from.</p>
  
  <p>This would be fine for just listing them, but I guess you want a link to see the full entry? I would guess you would need to keep track of the ones you loaded from the other site, and construct your link URL maunally and accordingly, possibly based on the other sites <code>siteUrl</code>, so for instance:</p>
  
  <pre><code>{% set otherSiteUrl = craft.entries.section('cenicNews').site('cenicOrg').siteUrl %}
  </code></pre>
  
  <p>And then use that to create the links you need.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-14T19:33:44.660Z
Answers.Text: I have considered manually constructing the links, but believe, based on the site settings (under section, per my image), that one should be able to access entry's URL based on the site in which it is loading.
Answers.UserDisplayName: 4midori
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-14T21:15:54.260Z
Answers.Text: I’m pretty sure that this is not stored on the element itself. This is routing that only takes place on the request, given the current site. Once your in the context of one site, that is what it will use, and the entry is “decoupled” from it at this point.
Answers.UserDisplayName: KSP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-14T21:20:16.777Z
Answers.Text: In other words, it will pick the route based on the current site, and add the slug from the entry. If you make links with the other site’s siteUrl and add the entries’ slug, I’m pretty sure you’re good to go.
Answers.UserDisplayName: KSP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-14T21:21:17.330Z
Answers.Text: After all, the {slug} part of your routing is only referring to the slug attribute of your entry.
Answers.UserDisplayName: KSP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-16T21:13:32.943Z
Answers.Text: Thanks @ksp, I took another look at the propagation method for entries, and found the solution, noted below.
Answers.UserDisplayName: 4midori
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-14T17:20:00.460Z
Answers.LastActivityDate: 2019-12-14T17:20:00.460Z
Answers.UserDisplayName: KSP
Body: <p>I've got a bunch of entries in Site 1. I need to display them in Site 2. If I specify the site, I get the entries.</p>
  
  <pre><code>{% set entries = craft.entries.section('cenicNews').site('cenicOrg').limit(10) %}
  </code></pre>
  
  <p>However, they are pointing to Site 1's domain, using Site 1's template:</p>
  
  <p><em>site1.com/news/new-library-initiative</em></p>
  
  <p>I want them to be loaded on Site 2's domain, using Site 2's template:</p>
  
  <p><strong><em>site2.com</strong>/news/new-library-initiative</em></p>
  
  <p>Note, if I remove the <em>site</em> parameter from my query, I get no results.</p>
  
  <p><a href="https://i.sstatic.net/rz2DK.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/rz2DK.png" alt="enter image description here"></a></p>
  
Tags: <entries><multi-site>
Title: Displaying one site's content in another site (Craft 3 Multi-site)
ThreadText: # Displaying one site's content in another site (Craft 3 Multi-site)
  
  (Asked by: username_0 on 2019-12-12)
  
  I've got a bunch of entries in Site 1. I need to display them in Site 2. If I specify the site, I get the entries.
  
  ```
  {% set entries = craft.entries.section('cenicNews').site('cenicOrg').limit(10) %}
  
  ```
  
  However, they are pointing to Site 1's domain, using Site 1's template:
  
  *site1.com/news/new-library-initiative*
  
  I want them to be loaded on Site 2's domain, using Site 2's template:
  
  ***site2.com***/news/new-library-initiative
  
  Note, if I remove the *site* parameter from my query, I get no results.
  
  [![enter image description here](https://i.sstatic.net/rz2DK.png)](https://i.sstatic.net/rz2DK.png)
  
  **Tags:** entries, multi-site
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2019-12-16. Score: 4 | Accepted answer
  
  I figured it out!
  
  1. In Section settings > Propagation Method, you must choose 'Save entries to all sites enabled for this section', or, if you're using site groups, choose the appropriate group. This basically shares entries across multiple sites.
  2. If your entries were previously only associated with one site, doing this will cause entries to be resaved.
  3. When calling entries, do not specific the site from which they are pulled, in other words, do not include site or siteId in the entries query.
  
  `{% set entries = craft.entries.section('sectionName').limit(10) %}`
  
  Now your urls will be correct, relative to the current site.
  
  On Site 1: *firstSiteDomain.com/news/president-elect-not-sociopath-at-all-billions-rejoice*
  
  On Site 1: *SecondSiteDomain.com/news/post/president-elect-not-sociopath-at-all-billions-rejoice*
  
  Even though the entries, news in this case, may be intended as "tied to" Site 1, you must 'share' them with Site 2 in order for Site 2 to load them and create *entry.url* correctly.
  
  > **Comments:**
  > **username_1**: Aha! Then I completely misunderstood what you tried to do, and was thinking too complex. I thought you wanted to list entries from Site 2 on Site 1, but have them link to the full view on Site 2. Glad you found the solution!  
  
  ---
  
  ### Answer by username_1 on 2019-12-14. Score: 2
  
  I'm guessing a bit here, and I haven't tested it, but I would think once you load the entries in your template, they are entries just like any other, and Craft doesn't keep more track of where they came from.
  
  This would be fine for just listing them, but I guess you want a link to see the full entry? I would guess you would need to keep track of the ones you loaded from the other site, and construct your link URL maunally and accordingly, possibly based on the other sites `siteUrl`, so for instance:
  
  ```
  {% set otherSiteUrl = craft.entries.section('cenicNews').site('cenicOrg').siteUrl %}
  
  ```
  
  And then use that to create the links you need.
  
  > **Comments:**
  > **username_0**: I have considered manually constructing the links, but believe, based on the site settings (under section, per my image), that one should be able to access entry's URL based on the site in which it is loading.  
  > **username_1**: I’m pretty sure that this is not stored on the element itself. This is routing that only takes place on the request, given the current site. Once your in the context of one site, that is what it will use, and the entry is “decoupled” from it at this point.  
  > **username_1**: In other words, it will pick the route based on the current site, and add the slug from the entry. If you make links with the other site’s siteUrl and add the entries’ slug, I’m pretty sure you’re good to go.  
  > **username_1**: After all, the {slug} part of your routing is only referring to the slug attribute of your entry.  
  > **username_0**: Thanks @ksp, I took another look at the propagation method for entries, and found the solution, noted below.  
  
  ---
  
  