I''ve been out of the Instiki world for a while now, so I apologize if
these questions have been answered elsewhere.
I built up a good amount of content using the packaged MacOS X version
of Instiki 0.10.2 and now need to move that conent to a new system.
However, I have the known problem with 0.10.2 not being able to
export.
So, I''m trying to get 0.11.0 up and running on MacOS X 10.4.7.
I''ve
properly installed all requirements through DarwinPorts, and am able
to run Instiki.
Two problems:
First, I can''t create a new web. When I try to do so, I get the
following error:
"NoMethodError in Admin#create_system
undefined method `files_path'' for nil:NilClass"
Secondly, I can''t migrate my old database:
"$ ruby script/import_storage -t /Users/ttate/Library/Application\
Support/Instiki/2500 -i /Users/ttate/Desktop/instiki-0.11.0/ -d sqlite
-o instiki_import.sql
script/import_storage:97:in `require'': no such file to load --
wiki_service (LoadError)
from script/import_storage:97"
The above error is dying on "require ''wiki_service''"
in the
import_storage script.
Any ideas?
Thanks,
Tyson Tate
Tyson Tate wrote:> undefined method `files_path'' for nil:NilClass"Hi Tyson, This error is almost certainly that the SWIG library is missing. When SWIG isn''t present, sqlite3-ruby reverts to a broken pure Ruby implementation. Does ''port installed'' show the swig port is present? If so, then you might try reinstalling the sqlite3-ruby gem. Give that a try; sorting out the SWIG issues will definitely sort out not being able to run and work with Instiki 0.11.0. I expect it will also fix the migration tool''s problems as well. -- John
Hi Tyson,
It''s a pretty easy to fix the export problem in 0.10.2
In your instiki 0.10.2 directory:
1. go to the app/controllers subdirectory.
2. find the file application.rb and open it in a text editor.
3. goto about line 66.
4. find this section:
def send_file(file, options = {})
options[:type] ||= (FILE_TYPES[File.extname(file)] ||
''application/octet-stream'')
super(file, options)
end
and add the line "options[:stream] = false" so that the section looks
like this:
def send_file(file, options = {})
options[:type] ||= (FILE_TYPES[File.extname(file)] ||
''application/octet-stream'')
options[:stream] = false # add this line here!!
super(file, options)
end
After making that change you should be able to export from 0.10.2.
Tom
On 6/28/06, Tyson Tate <tysontate at gmail.com>
wrote:> I''ve been out of the Instiki world for a while now, so I apologize
if
> these questions have been answered elsewhere.
>
> I built up a good amount of content using the packaged MacOS X version
> of Instiki 0.10.2 and now need to move that conent to a new system.
> However, I have the known problem with 0.10.2 not being able to
> export.
>
> So, I''m trying to get 0.11.0 up and running on MacOS X 10.4.7.
I''ve
> properly installed all requirements through DarwinPorts, and am able
> to run Instiki.
>
> Two problems:
>
> First, I can''t create a new web. When I try to do so, I get the
following error:
>
> "NoMethodError in Admin#create_system
>
> undefined method `files_path'' for nil:NilClass"
>
> Secondly, I can''t migrate my old database:
>
> "$ ruby script/import_storage -t /Users/ttate/Library/Application\
> Support/Instiki/2500 -i /Users/ttate/Desktop/instiki-0.11.0/ -d sqlite
> -o instiki_import.sql
> script/import_storage:97:in `require'': no such file to load --
> wiki_service (LoadError)
> from script/import_storage:97"
>
> The above error is dying on "require
''wiki_service''" in the
> import_storage script.
>
> Any ideas?
>
> Thanks,
> Tyson Tate
> _______________________________________________
> Instiki-users mailing list
> Instiki-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/instiki-users
>
Thanks to both John and Tom for your help. I''m on my way to work right now to give these ideas a shot. I may end up sticking with Instiki, knowing that it''s still under development (or at least somewhat). My work needed a nice Wiki solution for our in-house documentation and such, but the only other decent wiki I could find was MediaWiki, which is a bit overkill four our needs. I wasn''t going to go with Instiki, knowing about the export problems and such, but it looks like 0.11.0 should fix the worst of my worries. Are there any other outstanding issues I should worry about before making Instiki our standard platform for internal wikis? Thanks! -Tyson
Ignore this e-mail - I have no idea why it took 4 hours to reach the list. :) I''ve replied in the other thread because installing SWIG didn''t help and fixing the code in 0.10.0 didn''t fix the export problem. -Tyson On Jun 29, 2006, at 9:59 AM, Tyson Tate wrote:> Thanks to both John and Tom for your help. I''m on my way to work > right now to give these ideas a shot. > > I may end up sticking with Instiki, knowing that it''s still under > development (or at least somewhat). My work needed a nice Wiki > solution for our in-house documentation and such, but the only other > decent wiki I could find was MediaWiki, which is a bit overkill four > our needs. I wasn''t going to go with Instiki, knowing about the > export problems and such, but it looks like 0.11.0 should fix the > worst of my worries. > > Are there any other outstanding issues I should worry about before > making Instiki our standard platform for internal wikis? > > Thanks! > -Tyson > _______________________________________________ > Instiki-users mailing list > Instiki-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/instiki-users