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
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