Submitted by Gábor Hojtsy on Sun, 08/10/2008 - 16:04.
This is due to temporal problems. We are caching the schedule, and whenever there is a change in the program (someone updates a session node), the cache is regenerated. Since there are multiple dbs, some might still be in syncing, and provide an empty dataset. At least this is my theory. We will watch the issue, and look into how it can be fixed. It is a temporal issue and should be fixed, whenever a new node is updated.
Submitted by mschouten on Mon, 08/11/2008 - 14:44.
Hello there! Can you make the schedule printer friendly?
(because now its only 1 table on 1 page and the rest is not there...). I have copy and paste it into word and then print it...but don't have the nice background now... thanks and Congrats on your wedding!
Submitted by Gábor Hojtsy on Mon, 08/18/2008 - 21:04.
I made the issue even more transient by not caching the program table if the data comes out empty. So it still might come out empty, but will fix itself sooner once reloaded.
known sync problem
This is due to temporal problems. We are caching the schedule, and whenever there is a change in the program (someone updates a session node), the cache is regenerated. Since there are multiple dbs, some might still be in syncing, and provide an empty dataset. At least this is my theory. We will watch the issue, and look into how it can be fixed. It is a temporal issue and should be fixed, whenever a new node is updated.
Schedule print-friendly
Hello there! Can you make the schedule printer friendly?
(because now its only 1 table on 1 page and the rest is not there...). I have copy and paste it into word and then print it...but don't have the nice background now... thanks and Congrats on your wedding!
sure
We are working to have a printer friendly layout of that page. Will see how it goes with different browsers.
please try
Look at this: http://szeged2008.drupalcon.org/blog/compose-and-print-your-own-drupalco...
kind of fixed
I made the issue even more transient by not caching the program table if the data comes out empty. So it still might come out empty, but will fix itself sooner once reloaded.