Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: megadealhosting on October 02, 2012, 12:50:14 am

Title: Request Widget not displaying the track required
Post by: megadealhosting on October 02, 2012, 12:50:14 am
trying out the request widget in V3 and if the track exists all is good.

However if the track does NOT exist, and email is fired off to me, and its contents are:

A song request has been received from a visitor at CentovaCast Streaming Radio Site.

Song:
Dedication: jane
From: chris (mail@**********)

This request was submitted by a user at the following IP address: 86.135.68.201

As you can see the actual song requested does not get parsed through to the email.

Any ideas, as without this, its pretty impracticable.

CK
Title: Re: Request Widget not displaying the track required
Post by: megadealhosting on October 02, 2012, 09:23:47 am
Also who it was submitted by is missing too

ANy ideas whats happening Steve?
Title: Re: Request Widget not displaying the track required
Post by: megadealhosting on October 02, 2012, 09:37:53 am
no its not, the submitted by info is there i see it now but for some reason the:

Song: {$request.song}

is missing in every instance. Is it a different variable in V3?

Carl.
Title: Re: Request Widget not displaying the track required
Post by: megadealhosting on October 03, 2012, 12:45:38 am
any chance?
Title: Re: Request Widget not displaying the track required
Post by: megadealhosting on October 05, 2012, 12:15:55 am
Obviously no chance of getting a little support from staff, as per usual.

Therefore, have any of Centova's customers currently trialling V3 experiencing this issue too?

It sounds like a very simple issue to fix if only you had a list of variables.

Carl.
Title: Re: Request Widget not displaying the track required
Post by: megadealhosting on October 27, 2012, 05:23:46 am
bump*
Title: Re: Request Widget not displaying the track required
Post by: Centova - Steve B. on October 29, 2012, 11:53:06 am
Obviously no chance of getting a little support from staff, as per usual.
This has already been fixed, but FYI I tend not to bother replying to threads with comments like the above.