# Recent Posts

409 posts found

 posted over 1 year ago distler 104 posts 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 …. posted over 1 year ago peter_ljung 2 posts Forum: Instiki – Topic: instiki_session cookie overflows after some editing The instiki_session cookie seems to increase when I edit my Instiki site. After a while I reach the 4kB limit and instiki returns an: Status: 500 Internal Server Error ActionController::Session::CookieStore::CookieOverflow My web server (http://www.lounge.se) is setup as follows: OpenBSD 5.6 ruby 2.0.0p481 passenger-4.0.44 mysql-server-5.1.7 Instiki 1.9.7 When I clear the cookie it start working again for a while until it reached 4k limit agina. Any suggestions of what could be wrong? posted almost 2 years ago distler 104 posts 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. posted almost 2 years ago nkay 8 posts Forum: Instiki – Topic: Instiki hyperlinks failures Thanks for the response. Unfortunately the same error occurs. I have tried many different syntax’s each resulting the same error. 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 and update the code I can get it to not error out. If I create additional folders nested in the ‘files’ folder than it errors back out. I checked permissions on the folders and everything is fine. 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? posted almost 2 years ago tanzer 36 posts Forum: Instiki – Topic: Idle Instiki was using 17% of CPU on a shared host Problems not related. Sysadmins fixed a server problem. Instiki with high CPU usage has not recurred after that one incident. Thanks posted almost 2 years ago distler 104 posts 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. posted almost 2 years ago nkay 8 posts edited almost 2 years ago Forum: Instiki – Topic: Instiki hyperlinks failures I am having an issues with hyperlinks with our WIKI page using the textile markup. Hyperlinks to external webpages work eg. “www.google.com” but any internal html pages within the instiki filesystem end up getting application errors.We have a folder inside the main Web folder called Wiki_files which has many different HTML files but if we link to any of them e.g… “Environment Configuration”:http://acesrep:2500/aces/wiki_files/environments/AcesEnvironments.html) I receive “Internal Error” An application error occurred while processing your request. Looking at the source of the page I get these dumps. (d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/base.rb:1339:in perform_action' d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:617:in call_filters’ d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:638:in block in run_before_filters' d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:206:in call’ d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:206:in block in around_proc' d:/instiki-d:/0.19.6/vendor/rails/activesupport/lib/active_support/callbacks.rb:182:in call’ d:/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/callbacks.rb:182:in evaluate_method' d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:184:in call’ d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:635:in run_before_filters' d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:615:in call_filters’ d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:638:in block in run_before_filters') If I open up the HTML document within the server itself it works fine but not as a link through instiki wiki. posted almost 2 years ago tanzer 36 posts Forum: Instiki – Topic: How do I bulk-clear the Instiki cache Thanks, I did that. It seems to be working fine, but one thing puzzles me. About a day after I cleared everything out as per the above, the full tree under instiki/cache/views/azimuth got repopulated – presumably when the site got crawled. But the storage folder didn’t get repopulated. Or rather, now there is just a single file in it: azimuth-markdownMML-2015-02-12-11-11-03.zip, with a timestamp of yesterday. Before I cleared out storage, there were tons of files it in, it looked something like one file per page of the wiki, though I didn’t look closely. Does this make sense; are there any signs of ill-health here? What is the function of the storage folder? Thanks. posted almost 2 years ago distler 104 posts 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. posted almost 2 years ago tanzer 36 posts Forum: Instiki – Topic: How do I bulk-clear the Instiki cache Can we make the instructions more specific, because I’m cautions about disrupting a structure that I don’t understand. How about: rm instiki/storage/* rm -r instiki/cache/views/azimuth There’s a whole structure of directories and files under the last directory, that’s okay to wipe out? posted almost 2 years ago admin 58 posts Forum: Instiki – Topic: How do I bulk-clear the Instiki cache What is the cleanest / simplest / safest way to purge the entire cache? At the commandline, do an rm -R of the appropriate directory. There isn’t a GUI tool to do it. In addition, the old URL is present in files in the top-level folder “storage.” Those can all be deleted. posted almost 2 years ago tanzer 36 posts Forum: Instiki – Topic: How do I bulk-clear the Instiki cache I did a bulk update in the database to change our forum URL from one location to another. (Updated the field Content in the Revisions table.) Now a large number of entries in the cache are stale. I grepped in the cache directory tree for the old url, and found it present in files in several subdirectories of the cache/views folder for the web in question. I saw it in the subdirectories source, tex, revision, … In addition, the old URL is present in files in the top-level folder “storage.” What is the cleanest / simplest / safest way to purge the entire cache? Thanks! posted almost 2 years ago tanzer 36 posts Forum: Instiki – Topic: Idle Instiki was using 17% of CPU on a shared host Good questions. Thanks. Research pending… posted almost 2 years ago distler 104 posts 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? posted almost 2 years ago tanzer 36 posts Forum: Instiki – Topic: Idle Instiki was using 17% of CPU on a shared host But this isn’t my main concern tonight, which is off-topic: our shared host is crashing everyday, due to too many sleeping processes and not enough memory. They claim that 5G is enough memory, and are promising to fix it… Grr. posted almost 2 years ago tanzer 36 posts Forum: Instiki – Topic: Idle Instiki was using 17% of CPU on a shared host Noticed this, then I touched tmp/restart.txt and usage went down to basically zero. posted almost 2 years ago tanzer 36 posts Forum: Instiki – Topic: Feature Requests Thanks! posted almost 2 years ago distler 104 posts 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. posted almost 2 years ago tanzer 36 posts Forum: Instiki – Topic: Feature Requests Background: The Azimuth wiki is getting consistently hit by a spammer promoting “coffre fort.” I’ll do what I can with keyword blocking, but the guy is creative with words. Main point: The IPs are all in the database at www.stopforumspam.com. Possible feature request: Option to have this web service called when validating an IP address. One question is what the performance hit would be – what is the uptime of this service, and what is its response time. A drawback of doing this is introducing a further dependence through the internet on an external system. posted 2 years ago distler 104 posts 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. posted 2 years ago distler 104 posts 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. posted 2 years ago tanzer 36 posts Forum: Instiki – Topic: Requirements for a server-side Instiki scripting package After considering these requirements, and enumerating the commands that are on the Edit Webs page, let’s take a breath, and then move on to discuss the SQL interpretation of these commands in another discussion thread. Thanks for listening! posted 2 years ago tanzer 36 posts edited 2 years ago Forum: Instiki – Topic: Requirements for a server-side Instiki scripting package Please if anyone sees any problems with these requirements, or has suggestions for simplifications, enhancements or new use cases – do tell! posted 2 years ago tanzer 36 posts Forum: Instiki – Topic: Requirements for a server-side Instiki scripting package I believe that these specifications cover the story I mentioned above, which is to publish from one installation to another based on category:publish. They also cover more. For instance, multiple people could each have their own staging installation, and with these scripting commands, they could publish page sets to a common target installation. posted 2 years ago tanzer 36 posts Forum: Instiki – Topic: Requirements for a server-side Instiki scripting package c) Import a page set P into I’. Options: (1) overwrite existing pages, and clobber their histories, (2) append to the existing histories, (3) fail if the pages already exist. There is a constraint here. If the export contains full histories of pages, it doesn’t make sense to use option (2) to append these histories to an already existing history. So if option 2 is specified, then an error should be generated if the imported data contains full histories and the targets already exist. posted 2 years ago tanzer 36 posts Forum: Instiki – Topic: Requirements for a server-side Instiki scripting package b) Delete the page set for (W,C) from the target installation I’. posted 2 years ago tanzer 36 posts edited 2 years ago Forum: Instiki – Topic: Requirements for a server-side Instiki scripting package Functions to support Use-Case 2. a) Export. Given an Instiki instance I, define a page set by PageSet(W,C), where W is a list of web identifiers and C is a set of categories. This consists of all pages in webs W that fall under one of the categories in C. The export function can be given a list of page-set-specifiers (W1,C1), …, (WN,CN). Allow the wildcard specification * for any of the arguments Wi or Ci. Allow the export to also specify whether the full history should be exported, or just the most recent versions of the pages. Output of the export statement may be based arounda collection of SQL insert statements, which can be applied to the database for another Instiki installation I’. (To keep the levels clear, let’s defer talk about the SQL specifics to a followup thread.) But as the following functions suggest, some more meta-data may be needed. posted 2 years ago tanzer 36 posts Forum: Instiki – Topic: Requirements for a server-side Instiki scripting package Functions to support Use-Case 1. TODO: just read off the functions from the Edit Webs page, and specify them as abstract commands here. posted 2 years ago tanzer 36 posts Forum: Instiki – Topic: Requirements for a server-side Instiki scripting package Use Case 3: Develop new and more powerful methods for manipulating the data that constitutes Instiki webs. This is open-ended, and ideas can grow here as we go along. posted 2 years ago tanzer 36 posts Forum: Instiki – Topic: Requirements for a server-side Instiki scripting package The story behind use-case 2. I maintain one Instiki installation that is competely private, password protected, and not referenced from anywhere on the internet. This is the staging area for Instiki webs that am planning to publish. For some things, I’d rather not think aloud in the open, and would prefer to release when I deem them completed. I will maintain another Instiki installation for the published webs. It’s also a security precaution, to make sure that my staging webs won’t get compromised if the public installation gets hacked, attacked or spammed. Now in the staging webs, I will build a full image of what the published webs will contain. To accomplish this, I will just add the line “category:publish:” to any page in a staging web that I want to get published. So: I’ll want a scripting function that exports all of the data from one installation that is tagged with “publish”, and another one that imports the data into an existing Instiki installation.