OK, I think I see what is going on. As I said components are files. You are referencing a file within a file where the "wrapper" file is really just a URL pointing to a file that then tries to render the file referenced by the "internal" Component URL. Or put another way you are trying to render a webpage inside a webpage. All of which seems awfully complicated. There is no reason to have a Component in a Component, as anyone who has access to the wrapper Component will have access to everything in it.
We have a situation where we want Action Items from all meetings to "roll up" to a project status page. The method we use is below.
- Create a Planner plan* for your action items.
- Create a Project Dashboard/RAID page or skip to step 3 and use sub step 3.
- If using a Planner, use the /planner function to insert in the page.
- If using Tasks or Kanban use those functions.
- Create a Component from the Tasks or Kanban.
- Use the Copy Component function to get a link. Make sure to open the settings to grant permissions as needed. The default is "People who already have access."
- Create a meeting page using the MS template or manually as you desire.
- If using Planner use the /planner function to insert the same plan as above on this page.
- If using the Tasks or Kanban, paste the Component you copied from the Dashboard/RAID page into this meeting page.
- Alternately if you create a meeting page and create a Component of the Action Items list, you can then copy that Component from one meeting to the next.
Keep in mind that when you copy a Component you are always pointing to the same file. Everything from everywhere that Component was "copied" to will be visible and editable any other place you copy it to.
Also, there is a "Share Loop Component" function in the ellipsis menu for pages. Easier than selecting all the contents to make a component, and it works differently, so a Component on a page shared as a Component will work properly. There is also a "Duplicate page" function which is what we use in place of the ability to create custom templates that MS hasn't gotten around to yet.
*Reason being you can't filter the Tasks list in Loop, nor can you sort by status. If you are maintaining a longer running action item list, you can't make the completed tasks go away, they will always be at the top. Also, Tasks does not allow @mentions or even comments as they are not associated with an AD group. The Kanban function in Loop does allow @mentions and comments but when you assign a task it does not sync with To Do, so the user has to go to the Kanban in Loop to see work. Plus, you don't have to copy Plans. Just use the /planner function and pick the plan you want from the list that comes up. No need to remember or go to the page you created it on. But the method above will work with any of the three options.
Yes, I see the irony of writing a novella as a simpler method to your 4 steps.