Bibliography management

etc · 2020-06-24 14:58:38

Bloke wrote #323978:

Dammit, sorry. <txp:link_name> doesn’t use global escape, so trim doesn’t work. Oleg: Is it easy to retrofit without breaking backwards compatibilty in 4.8.2?

It should work, but   is not trimmed by PHP trim() function. A space would work, or some other symbol (say _) that you can trim with

<txp:link_name trim="_" ... />

Destry · 2020-06-24 15:09:49

etc wrote #323979:

A space would work, or some other symbol (say _) that you can trim with

Noted.

I’ll sit tight for the time being. I’ve plenty of other things to do.

Bloke · 2020-06-24 15:29:59

Oh yeah, sorry, I misread Destry’s post. Didn’t spot that he was using  .

For some reason, I thought we had to pass the tag’s output through txp_escape() to get it to benefit? Cool if we don’t and it works now.

So, Destry, does it work if you use a simple space character as the link_name then escape="trim"? Or use a single underscore or some other character that you don’t use in your regular titles, which you can then remove with trim="YourCharacterHere" prior to it being tested to see if it returns anything.

Bloke · 2020-06-24 17:04:47

etc wrote #323969:

Any reason why?

Also, I just checked it out. Presumably if we didn’t have at least one required field on the Edit Link panel, then you could just click Add Link->Save, Add Link->Save, … and it’d create you a bunch of unnamed links with no content and no fields set beyond the datestamp. Is that okay?

If there was a way of making sure that at least one of the fields was set then we might be able to get away with making the Name optional. But how would we display that requirement for good UX? And what if someone edits a link and blanks out all the content then Saves it?

I think for those reasons and for the ‘default plainlinks Form’ thing I mentioned earlier, we elected to have the Name required. Not saying it’s set in stone, but I think that’s the reason.

Now, one could argue that if you’re making a link, then the URL should be required. But I’ve just worked on a site where that’s not the case. I’m using Links for the list of people that contributed financially to the site’s cause, and not all of them have a website.

I made entries for them all, used the Sort value field as the name of an image I uploaded to represent the contributor’s logo, used the Title for their company name and a description to say how they contributed/thanks. But if they didn’t have a website, they were displayed on the front end without a clickable link.

Thus we can’t really stipulate that a link should contain a URL, although most of the time it would so it’s probably cleaner to do that than make the name required. Dunno. I can hack around it if this was changed using the same trick as above to put in a space as the URL then trimming it and checking it.

jakob · 2020-06-24 20:51:22

I’ve tested the updated plugin now and it should now work ok (a db backup is always a good idea :-)

You can find the multiple field version here

When you install it, it adds five new custom fields but only shows the ones you actually give a name in the Admin › Preferences (just like the regular article custom fields). If you install it over the earlier version:

Flick it off and on again and it will copy over the custom field data you had into the first custom_field and delete the old legacy column from the db.
Go to Admin › Preferences › Link custom fields and give the first custom field and field name.

Your existing tag should now work again, but you can use name="your_field_name" to specify it explicitly (it defaults to the first field if no name is given).

You can use the wraptag, escape and default attributes from txp 4.8 and there’s also a conditional field, e.g.:

<txp:jcr_link_custom name="your_field" wraptag=" (<+>)" />

will output a space and then the value in brackets if a value has been specified (where <+> is a placeholder for the contents).

You can also do:

<txp:jcr_if_link_custom name="image_id">
    <txp:image id='<txp:jcr_link_custom name="image_id" />' limit="1" />
<txp:else />
    <txp:link_name />
</txp:jcr_if_link_custom>

which will output an image only if there is one, otherwise the link_name, or

<txp:jcr_if_link_custom name="status" value="new">
    <txp:link_name /> <span>NEW!!</span>
</txp:jcr_if_link_custom>

and so on…

EDIT: updated GitHub links.

etc · 2020-06-24 21:59:28

Bloke wrote #323983:

If there was a way of making sure that at least one of the fields was set then we might be able to get away with making the Name optional. But how would we display that requirement for good UX? And what if someone edits a link and blanks out all the content then Saves it?

This looks handled in link_save() function:

    if ($linkname === '' && $url === '' && $description === '') {
        link_list(array(gTxt('link_empty'), E_ERROR));

        return;
    }

UX-wise, we could add a bit of JS to ensure at least one of these fields is set client-side, but it’s probably an overkill. Who would ever want to create an ‘empty’ link?

Bloke · 2020-06-24 22:28:18

etc wrote #323989:

UX-wise, we could add a bit of JS to ensure at least one of these fields is set client-side, but it’s probably an overkill. Who would ever want to create an ‘empty’ link?

True, it was hypothetical! I’m happy to knock the required status on the head IF we can:

Display ‘unknown’ or something in the Links panel if the name is empty.
Figure out a better solution for the tpt_link, link_name and linkdesctitle tags. They should not assume that the name exists and instead return gTxt('unknown') (or ‘unset’ or something) if it’s missing.

The trouble at the moment is that those three tags pass the linkname directly to tag() when constructing the anchor. If tag() receives empty content it skips the tag creation. That’s not what we want, is it? Uhhh, is it?

colak · 2020-06-25 04:29:51

etc wrote #323989:

Who would ever want to create an ‘empty’ link?

I would:) I’m using the links panel in creative ways. We discussed this back on 4.7 I think, and I had to add hashes (#) to all my empty links.

etc · 2020-06-25 06:15:46

colak wrote #323994:

I would:) I’m using the links panel in creative ways. We discussed this back on 4.7 I think, and I had to add hashes (#) to all my empty links.

By ‘empty’ I meant ‘no name/URL/description’, which leaves you with id, category and timestamp. You must be too creative to get any use of it :-)

Bloke wrote #323991:

The trouble at the moment is that those three tags pass the linkname directly to tag() when constructing the anchor. If tag() receives empty content it skips the tag creation. That’s not what we want, is it? Uhhh, is it?

We should ask the creative spirits among us what they expect these tags to output when the name is empty. The rest is just code.

Bloke · 2020-06-25 06:43:22

etc wrote #323995:

We should ask the creative spirits among us what they expect these tags to output when the name is empty.

*summons creative spirits*

Ummm:

Skip output of entire link if name empty.
Replace empty name with a fixed string (e.g. unnamed) and display that.
Replace empty name with something ‘invisible’ and display it, so that tag() still renders something.   is tempting but escape="html" will render it verbatim, which is probably not what we want.
Something else…

Cast your votes/ideas please.

gaekwad · 2020-06-25 06:43:52

etc wrote #323995:

You must be too creative to get any use of it :-)

Yiannis is actually a wizard, complete with a mysterious cloak and pointed hat.

colak · 2020-06-25 09:16:30

Bloke wrote #323998:

Something else…

Maybe have the URL? ie equivalent to "$":http://domain.tld with rel="external" if needed.

Textpattern CMS

Textpattern CMS support forum

#25 2020-06-24 14:58:38

Re: Bibliography management

Bloke wrote #323978:

#26 2020-06-24 15:09:49

Re: Bibliography management

etc wrote #323979:

#27 2020-06-24 15:29:59

Re: Bibliography management

#28 2020-06-24 17:04:47

Re: Bibliography management

etc wrote #323969:

#29 2020-06-24 20:51:22

Re: Bibliography management

#30 2020-06-24 21:59:28

Re: Bibliography management

Bloke wrote #323983:

#31 2020-06-24 22:28:18

Re: Bibliography management

etc wrote #323989:

#32 2020-06-25 04:29:51

Re: Bibliography management

etc wrote #323989:

#33 2020-06-25 06:15:46

Re: Bibliography management

colak wrote #323994:

Bloke wrote #323991:

#34 2020-06-25 06:43:22

Re: Bibliography management

etc wrote #323995:

#35 2020-06-25 06:43:52

Re: Bibliography management

etc wrote #323995:

#36 2020-06-25 09:16:30

Re: Bibliography management

Bloke wrote #323998:

Board footer