Project

General

Profile

Actions

Feature proposal #6623

closed

make tags input name unique

Added by krileon almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Low
Assignee:
Target version:
Start date:
01 May 2017
Due date:
% Done:

100%

Estimated time:

Description

currently it's just tags[]. if you've 2 tags usages in the same form they'd conflict. Ensure the tag names are unique to their streams.

Actions #1

Updated by krileon almost 7 years ago

Needs to work in cases of new objects. For example the edit view is activity.0 asset, but after store it becomes activity.32. Currently it's simply using a name of "tags", which isn't unique but isn't dependent on the asset. Maybe a custom asset that for all new entries can be used and those entries will be checked in addition to stream specific? So for new entries use asset activity.0.new then for input names have the below. Could also just automatically handle it this way if the asset ends in ".0".

tags_stream['STREAM_ID'][] = TAGS_ARRAY

If the stream asset ends in .new then it would be the following.

tags_stream['new'][] = TAGS_ARRAY

New would always be parsed.

Actions #2

Updated by krileon almost 7 years ago

  • Status changed from Assigned to Resolved
  • Target version changed from 6.0.0 to 862
  • % Done changed from 0 to 100
Actions #3

Updated by krileon almost 7 years ago

The name is now just an md5 of the asset making input unique per asset. If the streams asset isn't found in the input it'll try to replace the final id with 0 and see if that exists to automatically handle new tags. Examples as follows.

POST: activity.0
STREAM: activity.42

With the above activity.42 won't exist in post so it falls back to activity.0. This will work with any stream asset ending in an id (e.g. gallery.photos.52).

Actions #4

Updated by krileon over 6 years ago

  • Target version changed from 862 to 4.1.0
Actions #5

Updated by krileon over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF