Recursion in embeds, backlinks, and other references
complete
N
Nicolas Bosshardt
In some cases, referencing an object in a page creates an unwanted recursion (or infinite re-referencing of a page in itself).
Examples have been discussed on Discord for:
- Tag embeds infinitely re-referencing the page they are on: https://discord.com/channels/940596022344843336/1001364765051994132/1145673249997467668 look also at the screenshot attached: the page called “Music MOC test 2” is embedded several times (and we can see it is indented each time it is referenced again)
- Backlinks and Block referenced repeatedly because a page contains several links to aanother page or block: https://discord.com/channels/940596022344843336/1124628550100725760/1124637313654333530
Note: there may still be use cases for having the page it is embedded on show up (use cases to be described by those who need it) but avoiding an infinite loop => Perhaps there should be an easy filter option to filter out current object.
Log In
Steffen Bleher
complete
Solved with the latest update.
P
Pavel Kinev
Vaguely related, but since we're are in tags context:
shouldn't tag filters be
includes
, doesn't include
instead of is
, is not
?as "tags" is a list..
Steffen Bleher
Pavel Kinev: agree! Very technical term. We'll improve this.
michael_v_h
Merged in a post:
Embedded tag collection includes the parent page
P
Pavel Kinev
see the attached image
Steps
:- I have 2 weblinks with a tag "tvshow"
- Create a page and add tag collection for this tag
- Switch it to embed view
Expected
:Should be 2 entries only
Actual
:The page where I've added the tag collection to is also there in the list.
It happens with any embedding and any tag amount.
_____
Is it a bug? or intended?
As it's highly confusing, since it adds this tag to the page where it shouldn't be, since the page just shows the db-table based on this tag.
_____
Edit:
I assume the page could be included in the table if that tag was explicitly added to the page (header or inline)
P
Pavel Kinev
Found the issue already:
Steffen Bleher
in progress
Steffen Bleher
Thanks for compressing this discussion. Currently, the best way to handle it is to set a filter "Where Title is not equal <reference-page-title>".
We'll think about it but often embedded pages are explicitly wanted.
v
vision assemblies
Steffen Bleher: thx for weighing in + caring, Steffen!
– can you maybe give an example here? I still look out for really solid use cases (or positive user voices) for this 'standard' use of self-recursive entries... 🤔♻️🐉
an idea
💭: maybe it´s an idea to put a toggle somewhere for people to decide (case-by-case)? – at least the need for a rough-edged filter working on titles doesn´t really feel comfortable / appropriate, given the systematicity of the problem (like in the case of MOCs, given in the forums).
Steffen Bleher
vision assemblies: For tags it might be a bit different but imagine you have projects that you mention as central pillars in some pages as embeds (so you can work on them there). You'd want to see where you mentioned these projects.
What about hiding for tags only?
v
vision assemblies
Steffen Bleher: sounds fabulously on point to me, Steffen!
yes, it was indeed the tag-scenario where it occured to me. and, if I am right, the other good folks reporting in on that basically had such a tag / MOC-like scenario at hand too!
I would hope anyone else, esp. Nicolas Bosshardt, @PKM Beth, @boonikad9300, and @Chris Prad, ... who might have additional / different observations, will weigh in...
– but to my ears this sounds like a very good 'solution'...!
N
Nicolas Bosshardt
Steffen Bleher: tags is indeed the most problematic area because it can cause infinite recursion, I don't think it's the case for other types of reference. What you descibe about page embeds makes sense, so the solution to 'hide for tags only' seems the way to go 👍