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.
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.
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!
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.
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.
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.
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.
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.
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…
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.)
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.
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!
In this case the bundle gets installed (…). But when I tried to run instiki I got this: /Users/Xabier/Documents/Trabajo/Investigacion/instiki-svn/vendor/rails/railties/lib/rails/gem_dependency.rb:21:in ‘add_frozen_gem_path’: undefined method ‘source_index’ for Gem:Module (NoMethodError)…
I’m running into the same error with Ruby 1.9.3-p448 and the development version of instiki.
Thank you Jacques! I actually had tried the development version, too, but I didn’t remember the outcome -only that it didn’t work either. In this case the bundle gets installed (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). But when I tried to run instiki I got this: /Users/Xabier/Documents/Trabajo/Investigacion/instiki-svn/vendor/rails/railties/lib/rails/gem_dependency.rb:21:in 'add_frozen_gem_path': undefined method 'source_index' for Gem:Module (NoMethodError)
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-svn/config/boot.rb:47:in 'load_initializer'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-svn/config/boot.rb:111:in 'run'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-svn/config/boot.rb:11:in 'boot!'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-svn/config/boot.rb:124:in '<top (required)>'
from /Users/Xabier/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in 'require'
from /Users/Xabier/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in 'require'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-svn/script/server:3:in '<top (required)>'
from ./instiki:6:in 'load'
from ./instiki:6:in '<main>' I’m afraid I don’t understand what is going on here. Sorry for my illiteracy, I’m just a devoted Instiki final user …
Hi, I’m running into problems when trying to install Instiki on my Mac (OS X Lion). Ruby version seems to be 1.8.7. A previous version of Instiki (I think it was 0.19.4) worked fine. This problem appeared when I re-installed the developer tools from the App Store, but this might as well be a coincidence. I’m trying the three last versions and in every case I get this output when I try to run ruby bundle install --path vendor bundle:
Fetching http://github.com/distler/file_signature.git
remote: Counting objects: 339, done.
remote: Compressing objects: 100% (241/241), done.
remote: Total 339 (delta 128), reused 279 (delta 68)
Receiving objects: 100% (339/339), 218.79 KiB | 289 KiB/s, done.
Resolving deltas: 100% (128/128), done.
Fetching http://github.com/distler/maruku.git
remote: Counting objects: 6916, done.
remote: Compressing objects: 100% (3505/3505), done.
remote: Total 6916 (delta 3472), reused 6758 (delta 3331)
Receiving objects: 100% (6916/6916), 2.37 MiB | 330 KiB/s, done.
Resolving deltas: 100% (3472/3472), done.
Fetching source index for http://rubygems.org//Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/source.rb:253:in ‘fetch_all_remote_specs’: undefined method ‘list’ for #Gem::SpecFetcher:0x10dff3b98 (NoMethodError)from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/source.rb:234:in 'remote_specs'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/source.rb:231:in 'each'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/source.rb:231:in 'remote_specs'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/source.rb:165:in 'fetch_specs'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/source.rb:70:in 'specs'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:159:in 'index'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:158:in 'each'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:158:in 'index'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/index.rb:7:in 'build'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:157:in 'index'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:151:in 'resolve'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:90:in 'specs'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/definition.rb:85:in 'resolve_remotely!'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/installer.rb:43:in 'run'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/installer.rb:8:in 'install'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/cli.rb:220:in 'install'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/vendor/thor/task.rb:22:in 'send'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/vendor/thor/task.rb:22:in 'run'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/vendor/thor/invocation.rb:118:in 'invoke_task'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/vendor/thor.rb:263:in 'dispatch'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/lib/bundler/vendor/thor/base.rb:386:in 'start'
from /Users/Xabier/Documents/Trabajo/Investigacion/instiki-0.19.6/vendor/plugins/bundler/gems/bundler-1.0.18/bin/bundle:13
from bundle:21:in 'load'
from bundle:21
With the above changes, then expire_caches triggers an error when renaming a page. I think it is due to expiring pages that redirect to the given page. This is called in expire_caches in after_save. If the page name has changed, then the function self.pages_redirected_to in wiki_references.rb is called with the old name but that no longer exists in the database. So the page = web.page(page_name) returns null. I’ve put in a conditional to test for this which at least removes the error but I don’t know if there are some caches that aren’t now being expired that ought to be - I’ll check the logs to trace this.
def self.pages_redirected_to(web, page_name)
names = []
redirected_pages = []
if web.has_page?(page_name)
page = web.page(page_name)
redirected_pages.concat page.redirects
redirected_pages.concat Thread.current[:page_redirects][page] if
Thread.current[:page_redirects] && Thread.current[:page_redirects][page]
end
redirected_pages.uniq.each { |name| names.concat self.pages_that_reference(web, name) }
names.uniq
end
I’ve put those changes in place and will keep an eye on what happens.
Incidentally, when manually clearing out the cache I note that / in page names gets translated into subfolders. So a page name Sandbox/Set creates a folder Sandbox with a file Set.cache. Should the page name be completely sanitised under such circumstances?
564 posts found