Closed GoogleCodeExporter closed 9 years ago
The only other field I can think of is 'release date'. Technically that is a
new feature (separate issue) but if it is easier to do it while you are
extending schema... ;)
Original comment by Dade...@gmail.com
on 8 Apr 2014 at 12:16
Possibly field for 3D info (mediainfo field)
Original comment by Guzz...@googlemail.com
on 8 Apr 2014 at 7:34
AMC 4.2+ changes?
Original comment by Guzz...@googlemail.com
on 8 Apr 2014 at 7:38
[deleted comment]
AMC4.2 released:
http://forum.antp.be/phpbb2/viewtopic.php?p=38247#38247
Original comment by Guzz...@googlemail.com
on 21 Apr 2014 at 9:39
Hoe about Votes field - see issue 164
Original comment by Guzz...@googlemail.com
on 20 Jun 2014 at 5:30
Original comment by Guzz...@googlemail.com
on 20 Jun 2014 at 5:30
WIll close this, as all is included, except "Votes" field - we can rise another
issue, if necessary.
Original comment by Guzz...@googlemail.com
on 21 Jun 2014 at 5:18
I noticed you started Docs for 6.2
(http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/17_Extensions/3_Plugins/My_Fil
ms/00_What's_New/Version_6.2) - thanks!
This feature is listed there for 6.2.0 under New catalog fields. Is it in
testmode in 6.1.0?
Docs list Budget, DateReleased, Composer, S3D, Collection, CollectionImage,
CollectionDetails but NOT - AKAS (multi title field), Fanart which the first
comment does. So I am confused (again!)
Original comment by Dade...@gmail.com
on 22 Jun 2014 at 10:58
AKAS and Fanart already WAS in schema - just not yet used by any features.
This issue is not really a "feature", it is more a base to be used by features
- e.g. 3D support -> requires the respective field in schema. Thus we might
remove it from the "what>'s new" page, but I added it there so we remember it
in the future ...
Original comment by Guzz...@googlemail.com
on 22 Jun 2014 at 1:44
Thanks, so I assume one of the next steps is to add skin properties for Budget,
DateReleased, Composer, etc?
Not really sure how to test/verify or document this issue?
Original comment by Dade...@gmail.com
on 22 Jun 2014 at 9:42
you should see the output when enabling debug property logging and having added
such fields to DB - <entry name="PropertyLogging">false</entry>
docs is mostly only adding the respective fields to the skinner property table.
Everything else needs documentation in tghe respective features, when
introduced (e.g. 3D support)
Original comment by Guzz...@googlemail.com
on 22 Jun 2014 at 10:56
Thanks, verified the properties are all there.
However, we don't add all GUI properties to Skin Properties - only those
skinner can/should use (many existing GUI properties are not listed). Please
note the diff between skin properties and GUI properties (which may be used by
internal code but not for skinners)
So I think we should only update the skin properties docs when we add an
issue(s) that supports the new properties/features (i.e. populates them with
data). So I set this issue to Docs Not Req'd
Original comment by Dade...@gmail.com
on 24 Jun 2014 at 2:27
Add "Votes" to the schema, so it is available once we extend the grabber engine
for it.
Original comment by Guzz...@googlemail.com
on 25 Jun 2014 at 12:59
This issue was closed by revision r3056.
Original comment by Guzz...@googlemail.com
on 25 Jun 2014 at 1:00
Verified Votes shows up in property logging in 3056
However it doesn't show up in AMC extended/custom fields yet. But IIRC the
other fields like Composer, 3D, Release Date etc didn't right away either. I'm
not sure when they started to or what I did that enabled that!
Original comment by Dade...@gmail.com
on 25 Jun 2014 at 5:53
Using an existing config will not show them, we add those new fields to the
AMCU config template, so they show up, if you create a new config. I think they
might also, if you "recreate" the config, but not 100% sure.
Original comment by Guzz...@googlemail.com
on 25 Jun 2014 at 8:36
Original issue reported on code.google.com by
Guzz...@googlemail.com
on 6 Apr 2014 at 3:53