The Open Guide to London: the free London guide

Please use this page to tell us about any problems you notice with the new OpenGuides software.

• The software allows one to edit the page, but the editing box has to be scrolled horizontally as well as vertically (at least in some browsers). This can be remedied by adding wrap="soft" to the textarea definition. Earle replies: Actually, wrap="virtual" is a bit more reliable across browsers. Thanks for the tip; I've added it to the default templates.

• Anything in quotes ("like so") in the page change comments box gets lost.

Known issues

• Upgrade artefacts - the process of switching from a freeform database to a structured one has left a scattering of misplaced data around the Guide. Please help us out by fixing any instances you notice of the following:
  • Lots of pages have duplicate metadata (address, categories, etc) or it's in the "Content" section rather than the appropriate ones.
  • Locales are now distinct from categories, but there are some instances where pages are referring to locales as if they are categories.
• Rebranding artefacts - the new name and location of the site have caused some similar small issues. Again, please help clean these up if you see them.
  • There are lots of references to "Grubstreet" scattered throughout the Guide.
  • There are images linked to on numerous pages at the location http://grault.net/grubstreet/pictures/ (no longer extant, don't click). These images have now all moved to http://openguides.org/london/pictures/.

• Nested lists - with multiple ** at the start of lines - don't work yet. [See above.] I am working with the author of Text::WikiFormat to sort this out. --Kake

• Fixed format text can be done with <pre> tags, but the first few lines don't seem always to come out properly. See Acton Town Station - I am not quite sure what is happening here --IvorW.

• I'm having trouble setting a username and preferences. I don't know if this is a general problem, or a local one to my browser. It would be useful to have the local cookie requirements written up somewhere. --IvorW