Web beginner here - so forgive the open-ended nature of this question...
We are trying to publish the basics of our season to the website, and getting no content to show up. We don't use TNEW but rather an outside web developer, and they've informed Marketing and I that the web page we're working on is pulled entirely from Tess.
I started with just mimic-ing last year's set up, by adding a 'Display on Website' keyword on the Productions (when I removed this keyword from the old perfs, they came down, so I thought this might be the ticket), Production Season, and Production level, updated the "Publish Web Date" and the same criteria last year on the Content page that are marked as "Use Web API" in System Tables .
Last year's perfs had no Publish to Client or Publish to Web dates plugged in in the Perf pages, but I tried adding today in the Publish to Web section - still no luck.
I know this is fairly custom org to org, but I'm hoping there might be a magic check box I'm just missing... On the Season level?
Any help appreciated!
Frannie
We must have Web MOS on the performance for it to show as well.
From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Frances O'Connell Sent: Monday, October 15, 2012 12:05 PM To: Nicole Keating Subject: [Tessitura Web Forum] Publish Season to Web
You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
I'm afraid without knowing more about the way the custom website is built I can't be sure of how they choose what performances to publish online, but using a keyword is pretty standard. I have a couple of ideas.
First and foremost, always remember that much of the data that flows through the Web API is cached: once it has been initially pulled from the database by the API server, the API server will keep serving up the same information without going back to the database for a certain period of time. This cache period is different for different kinds of data, but I believe keywords are one of the slowest to refresh, maybe 30 minutes, which is a major problem when it comes to using keywords as a publishing mechanism.
You can, of course, make the change and then wait for a while for the API server to refresh before deciding whether or not it's working, or you can force the API server to flush it's cache. There are two ways of doing this: if you have access to the API server methods directly (loading the Tessitura.asmx file in a browser, typically a url like https://[my api server url]/Tessitura.asmx) you can use the "DestroyCache" method. Alternatively, if you have access to the API server files, you can make a minimal change in the API server's Web.config file (i.e. add a space to the end of a line, save, then remove the space, save again). This and change to the timestamp on the Web.config will prompt the API server to dump it's cache.
A less likely possibility is that the web code is somehow looking directly at the keywords attached to the performances and failing to notice that the keyword has been applied at a higher-up production element. If everything else fails you might try attaching the keywords at the performance level. Again, I would be very surprised if that were the issue.
There might also be something that limits the performances it looks for by season id. If you have access you might look at the Web.config file on the _web_ server (not the API server) and see if any of the keys there seem to refer to a particular season or set of seasons.
--Gawain
Oh, yeah, that's also important for us: the right Web modes of sale must be applied _and current_, i.e. the date range on the MOS for that performance includes the current time.
We limit visiblity of our _event_ pages by keyword, and control visibility of the "Buy" button (and ability to select seats on the reservation page) by MOS. This allows us to publish all of our shows at one time, but restrict sales access to users who are granted specific modes of sale (donors, subscribers) for the first couple of weeks before our open onsale.
Thank you Gawain and Nicole. I hadn't checked, but do have active Web MOS and Web Price Types up. Doesn't seem like that's the issue but at least it's one more area to eliminate. It has actually been already about an hour since I added the keyword, so unfortunately it also doesn't seem to be a refresh cache issue. I also have the keywords on every level of Production Element, so that couldn't be it...
I'm going to reach out to the web developers and see if it might be a filter issue in the web.config file wherein it is looking only for last season's ID.
Thanks again for the input!
The other thing I would try is to make sure that the start dates for both the MOS and Web Publish Date are yesterday, not today. I know, it’s odd, but I would still try it. J
From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Frances O'Connell Sent: Monday, October 15, 2012 12:59 PM To: Nicole Keating Subject: RE: [Tessitura Web Forum] Publish Season to Web
From: Gawain Lavers <bounce-gawainlavers9512@tessituranetwork.com> Sent: 10/15/2012 11:17:59 AM
Thanks again Nicole. Still nothing. I'm almost prepared to blame this on the web developers! :)
To follow up - it must have been on the web developer end - I think probably a season parameter that was undetected as after following up our link is working. Thanks again for all the help Gawain and Nicole.