# Recent Posts

338 posts found

Forum: Instiki – Topic: instiki without database?

Dear,

is there a possibility to run the latest release without database? like 0.9.2?

I’m running version 0.9.2 on a small thin client and don’t want to bloat the system.

Thx antonio

Forum: Instiki – Topic: Feature Requests

Forum: Instiki – Topic: Feature Requests

Okay, so that was a pretty dubious feature request!

How about this one: if a page exists (meaning, really exists - not just a redirect) then a request to <web>/new/page should redirect either to <web>/edit/page or to <web>/show/page. If the page does exist then the effect of going to <web>/new/page and submitting stuff is the same as submitting an edit except that you don’t get the previous edit in the text box so there’s nothing to show that you’re replacing something already there. The argument for <web>/show/page being that if a page exists and you didn’t know it then you should probably have a good look at what’s already there before writing something new.

(This came up most recently because a Google search for a page led to the /new/ link even though the page exists - Google had clearly found the link somewhere and added it to its list, it does this even if a robots.txt file exists since the link exists on a page that it can read.)

Forum: Instiki – Topic: Windows installation not working

Im trying to migrate an existing wiki running on a old outdated server onto a new 2008 r2 x64 server. I have installed Ruby 1.9.3 onto the new computer and ran the Ruby bundle install –path vendor/bundle command as stated on the website however it looks like im getting a no such file or directory. I have verified that the source.rb file is located in the correct location.

D:\instiki-0.19.6\instiki-0.19.6>ruby bundle install –path vendor/bundle Fetching http://github.com/distler/file_signature.git D:/instiki-0.19.6/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/source.rb:57 8:in “’: No such file or directory - git clone “http://github.com/distler/file_signature.git” “D:/i nstiki-0.19.6/instiki-0.19.6/vendor/bundle/ruby/1.9.1/cache/bundler/git/file_signature-9e3f3d6fbf544 b2242ffca379f5f61bb2971e94e” –bare –no-hardlinks (Errno::ENOENT)

Also If there is any documentation or help on migrating the old wiki to the new server would be great.

Forum: Instiki – Topic: problem running instiki after installation

Probably, those instructions are out-of-date. (Help updating them would be appreciated.)

It would be best to ensure that you have a fully-functioning Ruby (1.9.3 is preferable) installation before proceeding with getting Instiki running. Perhaps these instructions might help.

Forum: Instiki – Topic: problem running instiki after installation

http://golem.ph.utexas.edu/wiki/instiki/show/Installation, the part that talked about ubuntu

Forum: Instiki – Topic: problem running instiki after installation

I followed all the instructions on your installation page for ubuntu.

What page are you talking about?

Forum: Instiki – Topic: problem running instiki after installation

Hi all, first time poster. Sorry if this has been discussed before, but I didn’t find anything on a quick search. I am running ubuntu 10.04, I followed all the instructions on your installation page for ubuntu. Everything seemed to install ok, I did all the apt-get and bundle install, but when I tried to run “./instiki –daemon” I get the following errors, fyi, my version of ruby is 1.8.7, patchlevel 249).

Thanks for your help, Ron

 /usr/lib/ruby/1.8/rubygems/dependency.rb:52:in initialize': Valid types are [:development, :runtime], not nil (ArgumentError) from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:352:in new' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:352:in search' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:346:in gems_size' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:179:in resolve' from /usr/lib/ruby/1.8/rubygems/source_index.rb:95:in sort_by' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:175:in each' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:175:in sort_by' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:175:in resolve' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:160:in start' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:128:in resolve' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:127:in catch' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/resolver.rb:127:in resolve' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:151:in resolve' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:90:in specs' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:135:in specs_for' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:124:in requested_specs' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/environment.rb:23:in requested_specs' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/runtime.rb:11:in setup' from /home/riovine/instiki/instiki-svn/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler.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 

Forum: Instiki – Topic: migration to Rails3.

Here are the steps to follow:

Forum: Instiki – Topic: Feature Requests

It’s been suggested that this is because that is in a div with class name byline.

That seems a pretty thin reed on which to base a request for changing the class names we use.

Forum: Instiki – Topic: Bugs

I am fairly certain that none of my recent updates would affect this scenario..

But I’m happy to hear that it fixed itself.

Forum: Instiki – Topic: Bugs

… and in the time since you asked for clarification, it would appear that you’ve fixed it anyway as it no longer appears having just updated instiki.

Thanks.

Forum: Instiki – Topic: Bugs

Distillation for Distler (sorry, …)

1. Create a page with an apostrophe in the title, say apostrophe's.
2. Edit page.
3. Page magically becomes apostrophe&#x27;s.
4. Edit page, changing its name back to apostrophe's.
5. Page name is now correct.
6. Edit page.
7. Page name is mangled again.

Forum: Instiki – Topic: Feature Requests

Not sure if this is a bug or a feature request …

Google searches now include author information which it tries to glean from the page. It would appear that it uses the “Revised by XYZ” information to do this. It’s been suggested that this is because that is in a div with class name byline. I’m going to try changing this to see if it stops Google from assuming that to be the author. I don’t yet know how to override Google’s ad hoc method (which really does seem ad hoc if it uses a CSS class name as evidence).

I’ll report back on whether or not it works. If it does, consider this a feature request for changing byline to something like revisedby.

Forum: Instiki – Topic: migration to Rails3.

Hi,

I have it working (mostly), today spend some time fixing

• asset pipeline for rails3
• further clean-up
• big issue running with passenger, rvm etc…

so, the test site is running here:

http://test.netxforge.com => This is the front site, which “presents” the wiki pages. http://test.netxforge.com/netxforge/list => The actual wiki

There are a some pending issues, with URL generator, making some links not working.. etc.. so still a bit of work….

Cheers Christophe

Forum: Instiki – Topic: migration to Rails3.

This is extremely interesting.

Porting Instiki to Rails3 has long been on my TODO list. But (as you’ve seen), it’s not a small job. So it keeps getting pushed back in favour of other things. So I’m really happy you’re working on this!

Forum: Instiki – Topic: migration to Rails3.

Ah, found the problem for the issue, I reported earlier. … (took me the better part of the morning grrrr…). Ok, so WikiContent extends ActiveSupport::SafeBuffer. Now this class changed in Rails 3, overriding (Or opening up in Ruby Parlence) with the following code:

def html_safe ActiveSupport::SafeBuffer.new(self) end

So, this produces a different Class type, hence the mixed-in methods get lost! and causes a problem in PageRenderer trying to call this method. Wow, I am happy I found this one.

the file holding this method is called: output_safety.rb in lib/activesupport/kernel. I couldn’t find the alternative for Rails 2.3, to prove my point. but regardless it now works, by commenting out this line in WikiContenr.render!

# self.html_safe

BTW: The teaser screenshot is now shown, in my previous post.

Forum: Instiki – Topic: migration to Rails3.

Hi, (Jacques, I hope you are reading this!)

I am running into a tricky problem in the Rails3 migration. As you likely know, Rails 3 doesn’t load the /lib directory when starting. There are 2 options to auto-load. 1) In application.rb (which is required by Rails 3) put in a config parameter to load. There are some caveats as the names of the files versus the names of the class. 2) there is now a /config/initializers directory, and .rb is executed here.

What I have done now is:

1) config/application.rb

This will load most files, except InstikiErrors and WikiContent as the naming of the files doesn’t fit the rails loading algorithm. To load these I use:

2) config/instiki_init.rb

# Load the Instiki lib

require ‘instiki_errors’ require ‘wiki_content’

(I also had to rename the wiki.rb class in /chunks/wiki as rails would complain, the file should declare the Wiki class ) “Expected /Users/Christophe/Documents/Spaces/netxforge_aptana/com.netxforge.store/lib/chunks/wiki.rb to define Wiki

This /lib classes are loaded, however I run into a problem when saving a page. What happens is that somehow the methods in WikiChunck Module are not available .. so it seems the mixin of this module into the WikiContent class is not working well… I know it’s a fuzzy description but I get for example the following error. You see this occurs in the PageRenderer, when calling ‘update_references’ while prior to that the method ‘render(…)’ is called which creates the variable ‘rendering_result’ correctly created. (Also some of the mixin methods should have been called by then). I am really puzzled about this. I even consider rewritting it, so that mixin is not used. (I actually wonder why a mixin solution was chosen here, it’s not code re-use is it?).

Can you help me fix this?

Here is the error:

NoMethodError in WikiController#save

undefined method find_chunks’ for #<ActiveSupport::SafeBuffer:0x007ff4863dc368>

Rails.root: /Users/Christophe/Documents/Spaces/netxforge_aptana/com.netxforge.store Application Trace | Framework Trace | Full Trace

lib/page_renderer.rb:122:in wiki_links' lib/page_renderer.rb:102:in find_wiki_words’ lib/page_renderer.rb:150:in update_references' lib/page_renderer.rb:141:in render’ lib/page_renderer.rb:29:in display_content' app/models/page.rb:30:in revise’ app/models/wiki.rb:79:in revise_page' app/controllers/wiki_controller.rb:325:in save’

Teaser below :-), Instiki on rails3.

Forum: Instiki – Topic: migration to Rails3.

Hi,

I am using Instiki, as a sort of content backend for my website. It’s a base for the website application, which needs additional functionality, which I would like to build on the latest rails 3.x. So I rolled up my sleeves and started to migrate Instiki to Rails 3, which is now almost complete. The approach is pragmatic, fixing things when they break in Rails3. I have recorded all the adaptation, and this could be a check list to ‘replay’.

So here is the thought. I would like to share this experience and help out if there is a interrest to push the original instiki to Rails3. I would however need some help from the original developers.

I can clone the original, but then would like to push it back to the original git, of course in another branch, and when all ok, that could become the new official version… what do you say?

Cheers Christophe

Forum: Instiki – Topic: Bugs

Fixed. Thanks!

Forum: Instiki – Topic: Bugs

Pandoc is clearly weird. But you have uncovered a regression in Maruku. I’ve fixed that bug in the latest version in my repository on Github.

  ruby bundle update

will fix the problem.

Forum: Instiki – Topic: Bugs

In the process of migrating my wiki from Textile to Markdown I think I found a bug:

The following snippet of text: punto!). was converted by pandoc as punto![]().. The latter text blows the editing page with the error “NameError in WikiController#save”. Step to reproduce

1. create a new empty page
2. write punto![](). (without apexes)
3. save hitting the “Submit” button

Forum: Instiki – Topic: Migration from Textile

Thanks for your quick reply, you gave me a good idea. Actually I didn’t think about the history, and luckily I don’t need to keep it. I’m the only user of my wiki, but since it was started long ago, the pages format wasn’t fully coherent, so a completely automated migration wasn’t possible, I also needed the old wiki running, as a reference. So in the end this is what I did:

1. exported as you suggested the whole wiki, the result is a convenient “file per page”
2. converted the files with the command pandoc file.textile -o file.markdown in a BASH for cycle
3. moved existing installation from ~/instiki to ~/instikiold
4. installed a new, empty, instance in ~/instiki
5. launched the two instances together, on different ports
6. opened all files in jedit to correct in a single shot all repetitive errors
7. imported every page from file, one by one (starting with the smaller files!)

It took a lot of time to clean everything up, but in the end all the pages were moved successfully.

Forum: itex2MML – Topic: itex and other languages

Sounds good to me!! Heye Andrew Can you provide little information about your Extension Via PM.

cheers

Forum: Instiki – Topic: Migration from Textile

Interesting question!

I guess the first question is: do you want to convert the whole history (ie all previous revisions of each page) to Markdown, or just the current version?

If you just need the current version converted, you can go to the “Export” tab, and click on “Markup” to create a zip archive containing the (Textile) markup of each page.

If you want to convert the previous revisions, too, then you should look at the rake tasks described on this page. Those instructions are geared towards migrating from one database (e.g. sqlite) to another (e.g. MySQL). But they would also be useful in converting the content of the revisions table, without changing database engines.

• The db:fixtures:export_all rake task dumps your database to a (series of) YAML file(s).
• db:fixtures:import_all imports them to a (new) database.

In between, you’d run a conversion on the dump/fixtures/revisions.yml` file.

Forum: Instiki – Topic: Migration from Textile

I have an installation of Instiki, installed very long ago, and always kept up to date. I find it very useful because it runs completely in the user home, so it can be easily synced across several computers. I don’t need to write formulas to the wiki, just text and snippets of code.

Since the beginning the chosen markup was Textile (maybe was the default back then…), now I see on the web that Textile is almost unused and I wish to migrate to Markdown.

Is it there a best practice for this kind migration? Was it tested before?

Do I need to write a script that reads the sqlite database and feeds the pages to pandoc and then back to the database before changing the markup setup in “edit web”, or it’s safe to switch from one markup dialect to the other?

Forum: Instiki – Topic: Instiki website

Ok, I’ve stumbled upon it while I was looking for informations about textile, but let me open another post, it’s a completely different topic.

Forum: Instiki – Topic: Bugs

I’m sorry.

Could you please distill that long and rambling discussion in to a set of steps by which one might reproduce the bug?

Forum: Instiki – Topic: Bugs

There would appear to be a bug on pages with apostrophes in their names. See http://nforum.mathforge.org/discussion/4757/apostrophes-in-page-titles-lead-to-weird-behaviour for details.

Forum: Instiki – Topic: Instiki website

The instiki.org website is a hopeless mess, on many levels. Alas, I don’t control it, so I can’t do much about it (except to send the occasional plaintive email message to Matthias, which he ignores).

Instead, point your browser at my website, which contains both up-to-date information and (as best as I am able to assure) is spam-free.