It seems already been attempts to add pgonly attribute to article_custom tag.

It seems already been attempts to add pgonly attribute to article_custom tag.

Sure, including mine, few years ago :-) It didn't get much attention, but I'm not desperate. The aim is to be able to easily count pages or articles (with pageby="1") for informational purposes or for use in pagination plugins.

The initial patch (enable pages count for article_custom) is merged into dev now. The rest of this branch allows for finer custom fields match in article(_custom) and related_articles.

Although I haven't tested it, this seems like a pretty good idea to me. Is it okay to be merged? Any backwards-compatibility issues?

Regarding the item attribute: it assumes comma is the separator. But an earlier commit references pipe also. Should we introduce a separator attribute here, like there is for the if_custom_field tag, so that people are free to delimit their custom fields in any way they see fit? Or is that too confusing?

Thanks @Bloke. I thought we should postpone it to the unlimited custom fields era, also because separator could then become part of custom field definition.

Paging @bloatware – what's the status of this branch / PR from your viewpoint? The branch reports as 20 commits ahead of dev, are those commits worth evaluating for inclusion in dev, or would you prefer it be left open?

@petecooper this branch will be superseded by cf, so eventually including it in dev is only worth considering if dev and cf will not merge in a near future. But I hope they will and would keep this one aside.

Thanks @bloatware – makes perfect sense.