populateArticleData() custom field handling about textpattern

From [email protected] on September 08, 2009 15:18:18

Another solution would be to use the actual table column names (custom_1) instead of
the user-defined labels for those columns. If you want to sort on custom fields, you
have to use those table column names anyway and it solves problems with labels as
shown below, not to mention the fact that it would get rid of some ugly hacks to
actually get the labels working properly on the public side:

'custom_1' => "spaces, i haz 'em"

<txp:article custom_1="something" /> (OK)
<txp:article spaces, i haz 'em="something" /> (FAIL)

From stefdawson on September 23, 2010 06:37:54

On the radar. Will defer this topic to TXP 5 when custom fields are revisited as part of a wider enhancement.

Status: Confirmed

From stefdawson on October 15, 2012 05:13:00

Roll in as part of the Key/Value store (see Issue 275 and Issue 277 ).

Subtext: custom field key names to be sanitized so they can be used in txp:article_custom, provided the names don't clash with existing attributes or table columns. A well-known prefix would do.

Possible option to enhance article_custom to use custom_n= attributes as well, depending on the way the key store is implemented.

Either would be a boon for multi-lingual implementations.

Summary: populateArticleData() custom field handling
Status: Assigned
Owner: stefdawson
Cc: r.wetzlmayr
Labels: Milestone-4.6

[petecooper]

Should be covered by #456 in real terms, so closing for the moment.