An editor can't reference an external link as an "item" in a Collection

joshua_davis commented

2019-09-26 19:36:55 +00:00

(Migrated from gitlab.com)

Operating System

ALL

Browser

ALL

Steps to reproduce

Log in as an editor
Create a collection
Try to add an item that is an external link

What is the current bug behavior?

Only nodes can be referenced as an item.

What is the expected correct behavior?

Reference external links as an item.

Workaround

For list of content that are external links or a mix of external and internal links, use a text field instead.

Work Required

Confirm whether the workaround is a viable approach

## Operating System ALL ## Browser ALL ## Steps to reproduce 1. Log in as an editor 2. Create a collection 3. Try to add an item that is an external link ## What is the current bug behavior? Only nodes can be referenced as an item. ## What is the expected correct behavior? Reference external links as an item. ## Workaround For list of content that are external links or a mix of external and internal links, use a text field instead. ## Work Required * [x] Confirm whether the workaround is a viable approach

joshua_davis commented

2019-09-26 19:53:28 +00:00

(Migrated from gitlab.com)

I know we talked about removing the top list of "Items" so hopefully that will fix this...but as of now I'm unable to save a Collections page unless there is something in that first Item box, so I can't, for instance, have the summary and then a sub-heading and then items, but have to have at least one item before the sub-head.

joshua_davis commented

2019-09-27 15:39:38 +00:00

(Migrated from gitlab.com)

assigned to @mlncn and @FreeScholar

mlncn commented

2019-09-29 17:04:25 +00:00

(Migrated from gitlab.com)

@joshua_davis hmm, external or internal links is a little tricky, because we're trying to display the items in a collection consistently— as teasers (horizontal) or as cards (like on the home page), your choice.

We wouldn't be able to do that with external links.

Given that you already have the Gleaning content type for quick references to external content, would it make sense for collections to reference gleanings that are the links to external content? Or a similar link-only content type— with a new content type we could have it link directly from the teaser/card in the collection to the external link, and get rid of the intermediate page that gleanings have.

@joshua_davis hmm, external or internal links is a little tricky, because we're trying to display the items in a collection consistently— as teasers (horizontal) or as cards (like on the home page), your choice. We wouldn't be able to do that with external links. Given that you already have the Gleaning content type for quick references to external content, would it make sense for collections to reference gleanings that are the links to external content? Or a similar link-only content type— with a new content type we could have it link directly from the teaser/card in the collection to the external link, and get rid of the intermediate page that gleanings have.

FreeScholar commented

2019-09-29 17:14:26 +00:00

(Migrated from gitlab.com)

@mlncn Josh is telling me that @cedewey said we 0could move the current site to our server and launch it until we get the drutopia site in better shape. Is this still an option?

joshua_davis commented

2019-09-29 17:35:22 +00:00

(Migrated from gitlab.com)

Cards would probably display better than the teasers that it's doing
now, but I was thinking something different.

Here's my solution: I'll just use the existing summary box and cut and
paste what we have now into it. I know that's not how it's intended to
be used, but it's the only way I can figure out to get it to display
what it needs to. We apparently want it to do something it's not really
designed to do. So my quick fix is we don't use the items at all and
just do everything in the summary box. I'm sure you'll hate that ;-)

A link-only content type would not, unfortunately, adequately replace
our current Gleanings. While those are usually just snippets and links,
that content type is also used for posting other content that doesn't
fit that description. And I'm not a fan of creating a gleanings page for
every external link in every issue that doesn't have one yet. Seems like
a clunky solution that would also take a lot of time to implement.

Cards would probably display better than the teasers that it's doing now, but I was thinking something different. Here's my solution: I'll just use the existing summary box and cut and paste what we have now into it. I know that's not how it's intended to be used, but it's the only way I can figure out to get it to display what it needs to. We apparently want it to do something it's not really designed to do. So my quick fix is we don't use the items at all and just do everything in the summary box. I'm sure you'll hate that ;-) A link-only content type would not, unfortunately, adequately replace our current Gleanings. While those are usually just snippets and links, that content type is also used for posting other content that doesn't fit that description. And I'm not a fan of creating a gleanings page for every external link in every issue that doesn't have one yet. Seems like a clunky solution that would also take a lot of time to implement.

mlncn commented

2019-09-29 19:50:19 +00:00

(Migrated from gitlab.com)

mentioned in commit 724e4c6d3f

mentioned in commit 724e4c6d3f2855fd1f8c2ce58d28146b1b45fc12

mlncn commented

2019-09-30 13:20:14 +00:00

(Migrated from gitlab.com)

In conversation it turned out the way GEO wants to do collections with the flexibility to make internal and external links, just mixed in a paragraph, not necessarily formatted in any way.

Conclusion: Use a paragraph Text field (not the summary) to mix internal and external links however GEO wants.

To clarify what i was suggesting however it was not to replace Gleanings with a new content type, but rather to use gleanings (or a new content type) to link to external content in a consistently presentable, compatible-with-having-a-defined-collection, way.

In conversation it turned out the way GEO wants to do collections with the flexibility to make internal and external links, just mixed in a paragraph, not necessarily formatted in any way. Conclusion: Use a paragraph Text field (not the summary) to mix internal and external links however GEO wants. To clarify what i was suggesting however it was not to replace Gleanings with a new content type, but rather to *use* gleanings (or a new content type) to link to external content in a consistently presentable, compatible-with-having-a-defined-collection, way.

cedewey commented

2019-09-30 15:18:20 +00:00

(Migrated from gitlab.com)

changed the description

cedewey commented

2019-09-30 15:19:00 +00:00

(Migrated from gitlab.com)

@joshua_davis Does @mlncn suggestion,

Use a paragraph Text field (not the summary) to mix internal and external links however GEO wants.

make sense and work for you?

@joshua_davis Does @mlncn suggestion, > Use a paragraph Text field (not the summary) to mix internal and external links however GEO wants. make sense and work for you?

cedewey commented

2019-09-30 15:19:12 +00:00

(Migrated from gitlab.com)

assigned to @joshua_davis and unassigned @mlncn and @FreeScholar

cedewey commented

2019-09-30 16:23:42 +00:00

(Migrated from gitlab.com)

marked this issue as related to #13

cedewey commented

2019-09-30 16:26:17 +00:00

(Migrated from gitlab.com)

changed title from {-Feedback on the Collections content type-} to {+An editor can't reference an external link as an "item."+}

changed title from **{-Feedback on the Collections content type-}** to **{+An editor can't reference an external link as an "item."+}**

cedewey commented

2019-09-30 16:26:17 +00:00

(Migrated from gitlab.com)

changed the description

cedewey commented

2019-09-30 16:26:44 +00:00

(Migrated from gitlab.com)

changed title from An editor can't reference an external link as an "item{-."-} to An editor can't reference an external link as an "item{+" in a Collection+}

changed title from **An editor can't reference an external link as an "item{-."-}** to **An editor can't reference an external link as an "item{+" in a Collection+}**

mlncn commented

2019-09-30 16:58:27 +00:00

(Migrated from gitlab.com)

@joshua_davis there's now a new "Link" capability (replacing the old) that allows autocompleting internal content or linking to external (it may say 'not found' when entering an external link, but it always still works).

@joshua_davis there's now a new "Link" capability (replacing the old) that allows autocompleting internal content *or* linking to external (it may say 'not found' when entering an external link, but it always still works).

mlncn commented

2019-09-30 19:08:41 +00:00

(Migrated from gitlab.com)

mentioned in issue #13