Forum: Instiki – Topic: Dreamhost installation issues

Hmmm. I’m afraid that Maruku no longer supports Ruby 1.8.x (which is EOL). I think you need at least Ruby 1.9.3.

I guess I should update the documentation accordingly …

Forum: Instiki – Topic: HTML/PHP comments?

Short answer: no.

You can try embedding (X)HTML comments in the source, but they get escaped (for a variety of security-related reasons) and hence are “visible” on the page.

Longer answer: Metadata about the page can be placed in a way that does not appear in the rendered output. The syntax is that of email headers (key-value pairs, at the beginning of the page, separated from the main text by a newline):

Author: Me
Subject: My personal musings
Blortnaz: Whatever you want to put here

And now begins the main text ...

This is not quite what you asked for, but it may serve your purpose, depending on what use-case you had in mind.

Forum: Instiki – Topic: instiki_session cookie overflows after some editing

I only replaced the /app folder of my current wiki…

Well, since the changeset that I linked to above also involves changes to vendor/plugins/form_spam_protection/lib/form_tag_helper_extensions.rb , just updating files in /app/* won’t actually work.

Moreover, updating all of the files in /app to the latest version(s) drags in other changes. The particular error that you are seeing is due to this changeset, which introduces a nice feature for wikilinks, but required some changes in /lib as well.

I think I will wait for the 19.8 release on this one. This is not a huge problem.

Currently I am awaiting the release of Passenger 5.0.7, to see whether it resolves some issues with Instiki, or whether changes on the Instiki end are also required. If all goes according to plan, I’ll roll another release sometime in the early summer.

For whatever it’s worth, though, this site runs on the latest development version of Instiki (with Passenger 4.0.59) and is perfectly stable.

If you’re having issues with Instiki 0.19.7, I’d recommend updating now.

Forum: Instiki – Topic: instiki_session cookie overflows after some editing

Try using the latest Development Version. (Grab it either from my BZR Repository, from Github or as a tarball.) There are some changes that should fix the problem.

Someday, I’ll get around to releasing 0.19.8 ….

Forum: Instiki – Topic: Instiki hyperlinks failures

I did figure out that if I tried to upload a file into instiki (which automatically creates a ‘files’ folder in the Webs directory, and moved the html file to the newly created ‘files’ folder …

Oh. I think I misunderstood your problem.

Of course you can’t create an HTML link to some random file in (a random subdirectory of) the instiki directory. That would be stupid and dangerous.

As you can see from URLs for the CSS and javascript files on your Instiki pages, you can link to files in the public directory. You can also link to files in the webs directory (as you can see from the file links that you created).

I guess also a functionality thing I noticed is that if you click on the hyperlink to an local hosted html page. Instiki calls up a download box within the browser and asks the user if they want to save the html file locally, instead of actually opening the page within the browser as an actual webpage. Is this an issue or just how instiki displays local html files?

That’s for security.

You ought to be able to trust that the content of an Instiki page is safe. Thus (for instance) you can’t edit an Instiki page and add malicious javascript to it. This protection would be vitiated, if you could put the malicious javascript in an HTML file that opened in the user’s browser as if it were just another page on the Instiki wiki.

This restriction does not apply to files in the public directory. Those had to have been placed there by the system administrator and are assumed to be safe.

Forum: Instiki – Topic: Instiki hyperlinks failures

How about

"Environment Configuration":/aces/wiki_files/environments/AcesEnvironments.html

?

I don’t know how well Textile handles the “:” in the URL you were using.

Forum: Instiki – Topic: How do I bulk-clear the Instiki cache

How about:

rm instiki/storage/*

That should be fine.

rm -r instiki/cache/views/azimuth

As should that.

There’s a whole structure of directories and files under the last directory, that’s okay to wipe out?

All of those will be recreated, as needed.

Forum: Instiki – Topic: Idle Instiki was using 17% of CPU on a shared host

Hmmm. Both of those sound bad. Are they related?

What version of Passenger are you running?

Forum: Instiki – Topic: Feature Requests

Try adding the entry

'dnsbl.tornevall.org' => 'https://dnsbl.tornevall.org/scan?ip='

to the DNSBLS hash in vendor/plugins/dnsbl_check/lib/dnsbl_check.rb. Apparently, the http://www.stopforumspam.com/ data is shared with that dnsbl list, and hence can be queried with the same kind of dnsbl lookup.

If that works, we can incorporate that in an update to Instiki. If not, we can look into implementing the API.

Forum: Instiki – Topic: Requirements for a server-side Instiki scripting package

You might want to look at this page

% ruby bundle exec rake db:fixtures:export_all
...
% ruby bundle exec rake db:fixtures:import_all

which, mind you, is about exporting a whole Instiki instance (rather than just the pages in a category). But it should give you the general idea.

More generally, it seems that what you want to do is write a few Rake tasks for the sort of administrative functions that you want to perform.

That may be worthwhile, even if you eventually get SSL running properly.

Forum: Instiki – Topic: How to develop an ABC music plugin for Instiki?

The Markdown+Blahtex engine works similarly: shelling out to Blahtex to produce png images for the equations (which are cached on the server.

So you might look closely at the Blahtex Math Extension in (my version of) Maruku.

Forum: Instiki – Topic: How to develop an ABC music plugin for Instiki?

There is a hierarchy of processing of inputs in Instiki

• The chunk handler processes various bits of “Wiki Syntax.” It is extensible, by writing new handlers and including them, by name, in lib/wiki_content.rb.
• A content engine (Markdown, by default, but Textile and RDoc are also available). New content engines can be added in lib/chunks/engines.rb.
• Within one of the Markdown content engines, itextomml handles equations.

Maruku (our Markdown processor) has an extension mechanism. Math support is implemented as an extension. But so is the div syntax, as are fenced codeblocks and citations.

Presumably, what you want is an ABC extension for Maruku. That would be much easier to create, if there were a Rubygem implementation of ABC notation. But there doesn’t seem to be one.

Is there a good library in Python/Perl/… that might be worth porting to Ruby?

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

Well, that was fun…

I think I have instiki now running successfully on

• Ruby 1.8.7
• Ruby 1.9.3
• Ruby 2.0.0

It was quite a juggling act getting it to work on all three. But I think I’ve succeeded.

Let me know if you encounter further problems.

(In an attempt to eat my own dogfood, I have switched this forum and the copy of Instiki running on Golem, to run under Ruby 2.0.0.)

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

I actually had tried the development version, too…

Please try again.

The relevant feature of the development version is that it changes.

(only I was prompted to update Ruby when I first tried to run the bundler; which I did; my current version is 2.0.0)

Oh!

I haven’t tested Instiki on Ruby 2.0. Works fine on 1.9.x, but there may be issues with 2.0.

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

Thanks for the bug report.

The latest development version ( .tar.gz, bzr or git) should fix this problem.

Forum: Instiki – Topic: Bugs

Since I’ve not had much success reproducing your bug, why don’t we see whether implementing your suggestion fixes it for you?

Apply the following patch:

=== modified file 'app/controllers/revision_sweeper.rb'
--- app/controllers/revision_sweeper.rb 2011-09-21 04:46:36 +0000
+++ app/controllers/revision_sweeper.rb 2013-05-30 05:11:33 +0000
@@ -7,15 +7,15 @@
   observe Revision, Page
   
   def before_save(record)
-    if record.is_a?(Revision)
-      expire_cached_page(record.page.web, record.page.name) 
-      expire_cached_revisions(record.page)
+    if record.is_a?(Page)
+      expire_cached_page(record.web, record.name) 
+      expire_cached_revisions(record)
     end
   end
   
   def after_save(record)
-    if record.is_a?(Revision)
-      expire_caches(record.page)
+    if record.is_a?(Page)
+      expire_caches(record)
     end
   end
 

Forum: Instiki – Topic: Bugs

I put 2.9.1 in the Gemfile but I don’t know if that’s the minimum value.

Might as well assume that 2.9.1 is the minimum (since we know that it works). I updated the instructions accordingly.

Interestingly, bundle won’t update to the latest version unless you specify such a minimum.

Correct. If you don’t specify a version, then any version is supposed to suffice.

Forum: Instiki – Topic: Bugs

Poking around, I discovered that my fresh install was using version 2.9.1 of the mysql gem but the live installs were using 2.8.1.

If there’s a minimum version number for the gem that we should be using (no version number is currently specified), then that would be good to know, so that the Gemfile can be updated, accordingly.

Curious, though, that this “cache bug” of yours would seem to have nothing to do with … caching.

Forum: Instiki – Topic: Windows installation not working

So any tips on migrating an already running wiki on a different server?

The advantage of SQLite3 is that the entire database is in a single file, db/production.db.sqlite3 … which makes it easy to transfer.

   bundle exec rake upgrade_instiki

will, among other things, perform the necessary database migrations (assuming the previous one is not too old).

Forum: Instiki – Topic: Windows installation not working

Never had so much trouble for something that is supposed to be so simple.. ugh..

Hopefully, you pain will be someone else’s gain, if the Windows installation instructions can be improved, based on your experience.

However looks like every gem listed on the gem file i have to install manually…

I don’t understand.

bundle install –path vendor/bundle

doesn’t install the gems in in the vendor/bundle/ruby/* ?

Or it does install them, but then Instiki can’t find them?

Forum: Instiki – Topic: Windows installation not working

The sqlite3 rubygem won’t compile without thelibsqlite3 C-library. (Unlike many rubygems, which are pure Ruby, this one contains a C extension that links to the aforementioned library.)

Windows (unlike other operating systems) doesn’t come with that library installed. Some Ruby installers, for Windows, install it; evidently, some don’t. For those, you’ll have to install it yourself.

If you google around, you’ll find plenty of useful advice on this topic. Unfortunately (since i don’t have any familiarity with Windows), I’m not a useful source for such advice. But, yes, as far as I can tell, installing the Windows SQLite3 package is a prerequisite for getting the sqlite3 rubygem installed.

How does this installation work? What i gather you use “GIT” to download all the packages or i think bundles is the term and then ruby installs them on the system?

Bundler lets you manage/install rubygems, without installing them on the system. Instead, they are installed in your application’s vendor/bundle directory.

But that’s not where (as far as I can tell) your problem lies.