# Start a new discussion

## Not signed in

Want to take part in these discussions? Sign in if you have an account, or apply for one below

## Site Tag Cloud

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

• CommentRowNumber1.
• CommentAuthorMike Shulman
• CommentTimeJan 17th 2019

Created page, to fill a hole in the table.

• CommentRowNumber2.
• CommentAuthorMike Shulman
• CommentTimeJan 17th 2019

Something is wrong with the parsing of this page, but I can’t tell what.

1. Having a look.

2. Fixed. For some reason the combination of Maruku and the new renderer when it comes to lists inside the new theorem environments is a bit fragile. There needs to be a blank line between the end of the list and anything else. I’ve been putting off fixing this, because, as with several things, it will be resolved once we get rid of Maruku, which is a high priority.

• CommentRowNumber5.
• CommentAuthorMike Shulman
• CommentTimeJan 17th 2019

Thanks! I’ll try to remember that.

• CommentRowNumber6.
• CommentAuthorMike Shulman
• CommentTimeJan 17th 2019

Now I’m trying to fix the include on this page (I mistakenly typed includes instead of include) and I’m getting

uninitialized constant Page::Open3

• CommentRowNumber7.
• CommentAuthorMike Shulman
• CommentTimeJan 17th 2019

I’m getting that error editing other pages too. Maybe it’s system-wide?

3. Yes, I restarted the server when making the spam update, and this has broken editing. No idea why, am trying to look into it.

• CommentRowNumber9.
• CommentAuthorMike Shulman
• CommentTimeJan 17th 2019

Thanks!

• CommentRowNumber10.
• CommentAuthorRichard Williamson
• CommentTimeJan 17th 2019
• (edited Jan 17th 2019)

OK, think it is fixed now. The cause seems to have been the most bizarre thing: for half a year, the Ruby code in a certain file in Instiki had worked fine, and suddenly now it decided that an explicit import was required! I don’t know exactly how Rails’ dependency mechanism works; if the Ruby version was somehow bumped without my knowing it, this would explain it, but I can’t believe that things would be set up to automatically bump something like that!

I have been installing a few things on the server recently, and I suppose this might have bumped the Ruby version, but the nLab is running in a Rails virtual environment, and I would have thought would be unaffected. Oh well, hopefully nothing else has been broken by this!

• CommentRowNumber11.
• CommentAuthorMike Shulman
• CommentTimeJan 17th 2019

Weird. Thanks for fixing!