This morning, I added some references to a working project and they were not updated properly. Diving inside, it was trying to make new downloaded records in Refs, and reporting "rule not found". When I tried to document the problem, I by the way opened another preview page and the problem went away. It was something about that particular preview session.
Just now, I opened a preview on another page and got all kinds of weird reports about how the project did not exist; that it was making the preview directory (even after it had made it); that it was making the preview directory (in the middle of the page, after it had displayed other (empty) files); that it could not find the make log (even after it had displayed the (empty) target file). These files aren't supposed to be empty, but WW is showing them that way.
I should mention also that this preview directory took minutes to "make". Maybe in this case it's timing out while trying to make the preview directory (which should be different from the other case, unless I forgot to DNC Refs).
Just went through the whole process again, and had the same problem. Which means I can't work, but I can leave it for you.
http://lalashan.mcmaster.ca/theobio/circumcision/index.php?title=FGC/recode&action=submit
Preview session key is 16815012.
But I can't really leave it for you, because my example seems to depend on stuff that I didn't save!
Very confused.
OK, saved and previewed again. Still waiting, after minutes.
You will probably want to diagnose this, but I think I will probably try to rebuild the project. It's insanely twisted, and maybe unreasonably big.
New Preview session key is 1789846224
Anonymous
And of course it's not showing the right pathology. Although sets.var should not be empty (and was not empty in the saved version).
The problem here was that DHS data tables was not clicked DNC (and it's giant). There probably is some weirdness for you to diagnose, but I've unclicked it for now. You could probably experiment with gigantic previews on your own, if it somehow rises to the top of your priority list.
Glad you found this. Very sorry for the trouble.
I'll keep this open until I can have a look at whether it's timing out
or what. The comet notification framework is likely to help with
problems like this, by letting you see what it copies when and notice
when it's taking a long time.