INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Buliding own TrackInfo Page - Limitations  (Read 1491 times)

Nick-S

  • Guest
Buliding own TrackInfo Page - Limitations
« on: December 30, 2003, 12:21:41 pm »
Hi,

I'm trying to build my own TrackInfo Page. Why couldn't I use the phrase TRACKINFO_INSERT_COMPOSER or any by me created field like TRACKINFO_INSERT_MEDIUM in the HTML-Document? MC then just displays TRACKINFO_INSERT_COMPOSER  and not the info, which is "behind" it. Can I just use the "standard" informations like Artist, Album, Year, Genre, Lyrics???

Thank you very much for your help,

regards,

Nick
Logged

JaWe

  • Regular Member
  • World Citizen
  • ***
  • Posts: 100
Re:Buliding own TrackInfo Page - Limitations
« Reply #1 on: December 30, 2003, 12:58:45 pm »
Try: TrackInfo_Insert(Composer), TrackInfo_Insert(Medium)...
Logged

Nick-S

  • Guest
Re:Buliding own TrackInfo Page - Limitations
« Reply #2 on: December 31, 2003, 02:07:23 am »
Hallo,

that's working BUT I've got a custom field called "Interpret(en)" and one called "Komponist(en)" (German for artist in singular and plural  ;) ) I know that there are the fiels artist and composer but my custom fields are data fields, with the entries divided by semicolons. The Advantage is that now, if a song has e.g. four different artists everyone is seperately listed in the view sheme.  ;D

But with these fields it is not working, i think because of the brackets.

Is there another trick?
Logged

Nick-S

  • Guest
Re:Buliding own TrackInfo Page - Limitations
« Reply #3 on: January 02, 2004, 10:13:44 am »
No chance for a solution?  ?
Logged

EpF

  • Citizen of the Universe
  • *****
  • Posts: 649
Re:Buliding own TrackInfo Page - Limitations
« Reply #4 on: February 04, 2004, 05:48:41 pm »
Hi Nick - I'm a tenderfoot too, I haven't tried to build a trackinfo page yet, and I guess you have already tried double brackets, eg (Komponist(en)).  But possibly using quotes around the custom field name, eg ("Komponist(en)") would work...  From having done a primer with javascript and customising a PlayingNow skin I would suggest experimenting with square brackets and single quotes and anything else that might isolate your field name within the external brackets.  I might be totally off, but as no one else has replied I thought I'd give you my best guess...  ::)
Logged

Drowbe

  • Guest
Re:Buliding own TrackInfo Page - Limitations
« Reply #5 on: February 05, 2004, 04:06:19 am »
Sorry pal, all you can do is keep bumping it and hope someone responds.
Logged

DJ_Hazelwood

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 294
Re:Buliding own TrackInfo Page - Limitations
« Reply #6 on: February 05, 2004, 04:43:23 am »
Quote from: Nick-S on December 31, 2003, 02:07:23 am
But with these fields it is not working, i think because of the brackets.

I've tested it and i think you are right.
It seems to be because of the brackets.

I would use other names for the custom-fields (without brackets), then it will work.

Logged
Pages: [1]   Go Up
« previous next »