Recent Posts

Subscribe to Recent Posts 398 posts found

posted over 1 year ago
distler 100 posts

Forum: Instiki – Topic: Question marks in Instiki page titles?

I can’t think of a reason why question marks in the page name would be a problem. The name is CGI-escaped when forming the URI.

 
posted over 1 year ago
tanzer 36 posts

Forum: Instiki – Topic: Question marks in Instiki page titles?

I recall hearing some advice about avoiding question marks in page titles. Is this well-founded? What are the issues, and what are the workarounds.

One possibility that I could imagine are problems with the question mark in the URL string, leading to invalid http requests. Another is that certain parts of the code, e.g. search, interpret the question mark as part of a regular expression.

 
posted over 1 year ago
distler 100 posts

Forum: Heterotic Beast – Topic: Evaluating HB for Azimuth Forum

Heterotic Beast supports the following hierarchy

Sites ⊃ Forums ⊃ Topics ⊃ Posts

Different Sites have different URLs (virtual hosts, in Apache parlance), and different user-lists. For instance, the LHC Forum is another Site, running under the same Heterotic Beast instance as this one.

The thing closest to Vanilla’s “categories” is Heterotic Beast’s “Forums”. I’m not sure we need both. But we can discuss it.

 
posted over 1 year ago
tanzer 36 posts

edited over 1 year ago

Forum: Heterotic Beast – Topic: Evaluating HB for Azimuth Forum

Also, I’m not evaluating now how important these features are. Once I have a clear picture of what HB can do now, and what it potentially could do without a lot of extra effort, then I’m hoping to adjust our Vanilla-based expectations to the HB.

Regarding categories, for example, we’re very used to it, and take it for granted, but I’m not convinced that it’s a really important feature. For example, although it’s nice to think that I can filter the posts by category, I have never actually done this in practice.

The other uses of categories I mentioned are still valid, though I could probably make a case for workarounds (a separate forum called Technical) or doing without them.

Previewing is just a nice-to-have.

Moreover, we can assess later, now I’m just trying to learn how it works and throw out ideas as they come up.

Thanks

By the way, I meant to change the title of this thread from “Evaluating HB for Azimuth Forum” to “Discussion of HB for Azimuth Forum,” but when I clicked on the Edit link, it takes me right to the Login screen. However, this bug is not present in the instance of HB that we now have running.

 
posted over 1 year ago
tanzer 36 posts

Forum: Heterotic Beast – Topic: Evaluating HB for Azimuth Forum

Our current software supports a categorization scheme for posts. When you submit a post, you choose a category for it. The category shows in the summary line for the post. The categories can be used to filter the list of posts. I believe that Andrew uses this, for example, to view just the posts in the category Technical. Also, the visibility of posts can be controlled at the category level. For instance, the category Strategy can be made readable only to members.

To what extent are such mechanisms supported in HB? We could have separate forums, e.g., one for Technical, but is there a more fine-grained way to classify the posts?

 
posted over 1 year ago
tanzer 36 posts

Forum: Heterotic Beast – Topic: Evaluating HB for Azimuth Forum

Feature Request: ability to preview a post before submitting it.

 
posted over 1 year ago
tanzer 36 posts

Forum: Heterotic Beast – Topic: Evaluating HB for Azimuth Forum

Hi we are currently experimenting with HB, and considering switching over to it. I’m going to use this thread for any feedback, questions or feature requests from the group.

HB provides the essential functionality that we need, which includes Itex and Markdown. So does our current forum software, which is an installation of Vanilla that has been customized by Andrew Stacey to generate MathML and do other good things. We’re happy with the current software, but Andrew is moving on, and we are setting up a new server independently of the nLab. I won’t be able to support this modification of an old version of Vanilla. So we’re motivated to change to a supported package, and Andrew pointed us to the Heterotic Beast.

So the challenge will be to see if I can get the Azimuth group to accept the new package, which is fundamentally similar to what they have now, yet will inevitably differ in form from what they are quite comfortable with now.

I will be posting “feature requests” here that come from that perspective. Please take them with a grain of salt, and don’t do any work on our behalf that you wouldn’t want for yourself – especially because the group might not reach the consensus to make the change. In any case, these feature requests might give you something useful to think about.

 
posted over 1 year ago
tanzer 36 posts

Forum: Heterotic Beast – Topic: Bugs

That a good resolution. Thanks.

 
posted over 1 year ago
distler 100 posts

edited over 1 year ago

Forum: Heterotic Beast – Topic: Bugs

The culprit is

  before_validation :normalize_login_and_email

in app/models/user/validation.rb.

The point is that we don’t want a “David Tanzer”, a “david tanzer” and a “dAvid tanzEr”. The normalize_login_and_email downcases both the login name and email address, associated to an account, to put them in canonical form (before checking the database to see if there is already an account with that name/email).

While downcasing the email address is clearly the right thing to do, it’s not so clear that’s the “right” thing to do for the login name. I’ve fixed it so that we just make a case-insensitive check on uniqueness.

 
posted over 1 year ago
tanzer 36 posts

Forum: Heterotic Beast – Topic: Bugs

Minor: Account names get lowercased. I created an account “David Tanzer” from the signup page, but it gets recorded as “david tanzer.” I find it somewhat unsettling to see proper names in lower case. But its easy enough to workaround by updating the database.

 
posted over 1 year ago
distler 100 posts

Forum: Heterotic Beast – Topic: Can I view the source text for other people's posts?

That might be a worthwhile feature to add.

But, as an Instiki user, you are probably well-familiar with the syntax. Heterotic Beast uses Maruku as its Markdown processor and itex2MML to process equations. It even has the same WYSIWYG SVG editor that Instiki uses. So, except for a few bits of Wiki syntax ([[...]] for wikilinks, [!include ...] to include other wiki pages, etc), it should work exactly the same as what you’re used to.

 
posted over 1 year ago
tanzer 36 posts

Forum: Heterotic Beast – Topic: Can I view the source text for other people's posts?

Hi, is there a way to see a read-only view of source text of other people’s posts, just as it appears when one edits one’s own post? It’s useful for getting ideas from other people, with respect to formulas and formatting.

Thanks,

David Tanzer

Azimuth Project

 
posted 2 years ago
raptastics 1 post

Forum: Instiki – Topic: Debian Init.d Script

Thanks for the awesome wiki!

I couldn’t get the init.d script from the site working on my Debian server. I wrote one form scratch to manage starting and killing the process. It should be fully LSB-compliant and working with update-rc.d.

https://github.com/raptastics/Instiki-Init-Script

Let me know if it does or doesn’t work for you.

 
posted 2 years ago
distler 100 posts

Forum: Instiki – Topic: Debian installation

I love this software so much I’m starting to worry, when are you going to grow tired of maintaining it? Thank you!

My problem is lack of time, not lack of enthusiasm.

 
posted 2 years ago
xabier 8 posts

Forum: Instiki – Topic: Debian installation

Worked as a charm for the development version.

For the current release version (0.19.6) the bundling is successful but when I tried to run instiki this is what I got:

/home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:184:in 'require': cannot load such file -- zip/zip (MissingSourceFile) from /home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:184:in 'require' from /home/xabier/instiki-0.19.6/app/controllers/file_controller.rb:3:in '<top (required)>' from /home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:184:in 'require' from /home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:184:in 'require' from /home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:291:in 'require_or_load' from /home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:250:in 'depend_on' from /home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:162:in 'require_dependency' from /home/xabier/instiki-0.19.6/vendor/rails/railties/lib/initializer.rb:414:in 'block (2 levels) in load_application_classes' from /home/xabier/instiki-0.19.6/vendor/rails/railties/lib/initializer.rb:413:in 'each' from /home/xabier/instiki-0.19.6/vendor/rails/railties/lib/initializer.rb:413:in 'block in load_application_classes' from /home/xabier/instiki-0.19.6/vendor/rails/railties/lib/initializer.rb:411:in 'each' from /home/xabier/instiki-0.19.6/vendor/rails/railties/lib/initializer.rb:411:in 'load_application_classes' from /home/xabier/instiki-0.19.6/vendor/rails/railties/lib/initializer.rb:197:in 'process' from /home/xabier/instiki-0.19.6/vendor/rails/railties/lib/initializer.rb:113:in 'run' from /home/xabier/instiki-0.19.6/config/environment.rb:14:in '<top (required)>' from /home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in 'require' from /home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in 'block in require' from /home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:547:in 'new_constants_in' from /home/xabier/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in 'require' from /home/xabier/instiki-0.19.6/script/server:92:in '<top (required)>' from ./instiki:6:in 'load' from ./instiki:6:in '<main>'

Of course I’m more than happy to run the development version. I’ve copied this chunk of code just in case you wanted to know the outcome.

I love this software so much I’m starting to worry, when are you going to grow tired of maintaining it? Thank you!

 
posted 2 years ago
distler 100 posts

Forum: Instiki – Topic: Debian installation

Sorry.

You can try replacing

gem "mongrel", ">=1.2.0.pre2"

with

gem "thin"

in the Gemfile and see if that allows a successful bundle install.

 
posted 2 years ago
xabier 8 posts

Forum: Instiki – Topic: Debian installation

I’m afraid I need more dumb-proof directions… or maybe I need to convince myself that I shouldn’t be trying this installation without knowing some Ruby basics.

 
posted 2 years ago
distler 100 posts

Forum: Instiki – Topic: Debian installation

Hmm.

Well, I’m thinking of ditching mongrel in favour of thin, which is being maintained.

You might try changing that line in the Gemfile and seeing if that fixes your error. It would be one more motivation for making the switch.

 
posted 2 years ago
xabier 8 posts

Forum: Instiki – Topic: Debian installation

I’m trying to install Instiki (both current and development versions) on a machine that runs Linux Mint Debian Edition LMDE 201403. This distribution is based on Debian, so I guess I’m running into Debian-based errors too. This is part of the output of the bundling command I get:

Installing mongrel (1.2.0.pre2) with native extensions /usr/lib/ruby/1.9.1/rubygems/installer.rb:562:in 'rescue in block in build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError) /usr/bin/ruby1.9.1 extconf.rb checking for main() in -lc... yes creating Makefile make compiling http11.c http11.c: In function ‘http_field’: http11.c:193:3: error: format not a string literal and no format arguments [-Werror=format-security] VALIDATE_MAX_LENGTH(flen, FIELD_NAME); ^ http11.c:194:3: error: format not a string literal and no format arguments [-Werror=format-security] VALIDATE_MAX_LENGTH(vlen, FIELD_VALUE); ^ http11.c: In function ‘request_uri’: http11.c:235:3: error: format not a string literal and no format arguments [-Werror=format-security] VALIDATE_MAX_LENGTH(length, REQUEST_URI); ^ http11.c: In function ‘fragment’: http11.c:246:3: error: format not a string literal and no format arguments [-Werror=format-security] VALIDATE_MAX_LENGTH(length, FRAGMENT); ^ http11.c: In function ‘request_path’: http11.c:257:3: error: format not a string literal and no format arguments [-Werror=format-security] VALIDATE_MAX_LENGTH(length, REQUEST_PATH); ^ http11.c: In function ‘query_string’: http11.c:268:3: error: format not a string literal and no format arguments [-Werror=format-security] VALIDATE_MAX_LENGTH(length, QUERY_STRING); ^ http11.c: In function ‘HttpParser_execute’: http11.c:439:5: error: format not a string literal and no format arguments [-Werror=format-security] VALIDATE_MAX_LENGTH(http_parser_nread(http), HEADER); ^ cc1: some warnings being treated as errors make: *** [http11.o] Error 1

I understand that there are issues with Debian’s Ruby packaging. Or at least there were the last time this webpage was updated, but that was long ago. Any updating on this? Is it a stupid error? Thanks a lot.

 
posted 2 years ago
sykstan 3 posts

Forum: Instiki – Topic: installation problems (mac osx lion)

Thank you for your help, it works now!! Ruby 2.0.0-p353 is the version of Ruby I got, and then everything ran smoothly as promised on the website, in stark contrast to previous attempts. I was even contemplating learning Ruby to try and understand what was going on.

As you can probably tell, I have been attacking this problem in my spare time, so the replies are a bit distant in between.

 
posted 2 years ago
admin 58 posts

Forum: Instiki – Topic: installation problems (mac osx lion)

Googling around, that sounds like an antiquated version of RubyGems. If so,

gem update --system

should fix it.

On the other hand, since you have JewelryBox, you could just use it to install Ruby 2.0 or 2.1 (both of which should work with the development version of Instiki), which come pre-installed with a more modern version of RubyGems.

 
posted 2 years ago
sykstan 3 posts

Forum: Instiki – Topic: installation problems (mac osx lion)

Hello,

Sorry for getting back so late, only just had time to come back to this.

The latest development version does not make a difference, exact same error message. I’ve tried git pull https://github.com/parasew/instiki.git, downloading the tarball linked, and also from the Instiki website. None have worked so far. The ruby bundle install --path vendor/bundle command worked fine, but running ./instiki spits back the above message.

Any ideas?

 
posted 2 years ago
distler 100 posts

edited 2 years ago

Forum: Heterotic Beast – Topic: Rails 3.1.0

Heterotic Beast is now a Rails 3.2 application. (There’s an updated acts_as_state_machine gem, among other things which make this transition smooth.)

This forum is currently running on Rails 3.2.16.

 
posted 2 years ago
distler 100 posts

Forum: Instiki – Topic: Ruby 2.0 and 2.1

The current development version of Instiki runs (and the next release will run) just fine on Ruby 2.0 and 2.1.

This is important for (among others) MacOSX Mountain Lion users, whose default version of Ruby is 2.0.

 
posted 2 years ago
admin 58 posts

Forum: Instiki – Topic: Bugs

I’m working on updating my branch of Maruku, to incorporate various improvements from trunk. In particular, there are improvements to the table code. So you should check it out…

 
posted 2 years ago
Andrew Stacey 118 posts

Forum: Instiki – Topic: Bugs

There’s a bug with maruku’s table handling: it doesn’t like whitespace at the end of the line (a previous version did, and it would seem to me that whitespace here should be fine). This causes tables that used to render to no longer do so.

The fix is to modify the regexp for splitting cells: line 515 of lib/maruku/input/parse_block.rb should read:


if (/^[|].*[|]\s*$/ =~ s)

(I notice that this isn’t the same as the version of maruku on github, so don’t know if this would be superseded by updating to the latest version from there.)

 
posted 2 years ago
admin 58 posts

Forum: Instiki – Topic: installation problems (mac osx lion)

You need the latest development version ( .tar.gz, bzr or git).

 
posted 2 years ago
sykstan 3 posts

Forum: Instiki – Topic: installation problems (mac osx lion)

Hello there, I’m having the same problem with my installation. The default Ruby that came with my iMac is 1.8.7, but the gem nokogiri needed >=1.9.2, so I got Ruby 1.9.3p484 using JewelryBox. This time the bundler installed, but running ./instiki comes back with

/Users/tans/Downloads/instiki/vendor/rails/railties/lib/rails/gem_dependency.rb:21:in add_frozen_gem_path’: undefined method source_index' for Gem:Module (NoMethodError) from /Users/tans/Downloads/instiki/config/boot.rb:62:in load_initializer’ from /Users/tans/Downloads/instiki/config/boot.rb:126:in run' from /Users/tans/Downloads/instiki/config/boot.rb:26:in boot!’ from /Users/tans/Downloads/instiki/config/boot.rb:139:in <top (required)>' from /Users/tans/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in require’ from /Users/tans/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in require' from /Users/tans/Downloads/instiki/script/server:3:in <top>' from ./instiki:6:in `load' from ./instiki:6:in `<main>' `</main></top>

How did you manage to get it up and running? Thank you.

 
posted 2 years ago
admin 58 posts

Forum: Instiki – Topic: Windows 8 and Instiki

Installation instructions.

 
posted 2 years ago
slym 1 post

Forum: Instiki – Topic: Windows 8 and Instiki

I followed the instructions given on the instiki.org and this is what I get:

C:\instiki-0.19.6>ruby instiki C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/source. rb:571:in load_spec_files': http://github.com/distler/file_signature.git (at ma ster) is not checked out. Please run bundle install (Bundler::GitError) from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/source.rb:385:in local_specs’ from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/source.rb:554:in specs' from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/definition.rb:356:in converge_locked_specs’ from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/definition.rb:345:in each' from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/definition.rb:345:in converge_locked_specs’ from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/definition.rb:143:in resolve' from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/definition.rb:90:in specs’ from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/definition.rb:135:in specs_for' from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/definition.rb:124:in requested_specs’ from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/environment.rb:23:in requested_specs' from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler/runtime.rb:11:in setup’ from C:/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bu ndler.rb:107:in setup' from ./config/../config/preinitializer.rb:18 from ./config/boot.rb:28:in load’ from ./config/boot.rb:28:in preinitialize' from ./config/boot.rb:10:in boot!’ from ./config/boot.rb:124 from ./script/server:3:in require' from ./script/server:3 from instiki:6:in load’ from instiki:6

I tried different versions of Ruby but with no success. Please help!