Title Builder Beta See instructions

Welcome to Title Builder Beta.

This small piece of kit is designed to make building your Quiz, Crossword or Puzzle question more effective. It should make finding your question easier for others and, the easier it is to find, the more likely someone is to answer it!

To build an easy to find question title simply select the paper and quiz, enter the quiz number if relevant and fill in the Publication Date. Once you’re happy click “Build Title” and the information should populate the Title field. Fill in the final required details of your question as you normally would, and click submit.

As this is a Beta we only have a limited number of papers and quizzes listed. If you think your favourite Quiz, Crossword or Puzzle should be listed here don’t hesitate to contact us.

Remember: You do not have to use the title builder - simply enter the title and question as you normally would and click submit!

Paper & Quiz:

Loading data...

Quiz Number:

Publication Date:

Can't Play The Times Crossword Online.

vetuste_ennemi | 09:28 Sat 25th Jul 2015 | Crosswords

5 Answers

Any of you guys got the same problem?
The message was "TypeError: cannot read/access property crossTword" or some such. Ticked a box to stop this message propagating when I checked to see if the problem reappeared using other crosswords (I was trying to do today's cryptic), so I can't provide the exact text.
Looks like a Java script error message. Is this a programming problem at the website end, or has something changed in my environment? I'm using Chrome running under Windows 8.1

Prize Crossword

Times 26160

Answers

1 to 5 of 5

Best Answer

No best answer has yet been selected by vetuste_ennemi. Once a best answer has been selected, it will be shown here.

For more on marking an answer as the "Best Answer", please visit our FAQ.

4poster

Same here but the fault was rectified later.
Tried on Google and Firefox so it must have been a fault on the site.

vetuste_ennemi

Question Author

Thanks for your reply, 4Poster: I should have been more patient. While I was still having the problem I saw an AB question about 26160, so concluded that the issue was my end. So I did a system recovery from a checkpoint on the 20th to "cure" the problem.