sorted by: recent | see : popular

Content Tagged with SWiK-Source + Problems

Thing that often break in SWiK-Source, and why they break. The best way to diagnose problems is to check in the /logs directory. app.errors.log is a good place to look for application errors that occur on page load, app.ajax-errors.log is a good place to look for errors that occur through interactivity with ajax features.

SWiK fails to respond at all or returns a white page.

SWiK assumes a dedicated domain, such as swik.net, or no domain, for use in local host, see localhost install notes. The domain must not have a subdomain. Requests to SWiK are sent to apache through the virtual host setup, and then apache passes the request to swik.php, along with the raw query string. SWiK parses the query string and goes through each major page type, using an inverted control scheme to ask if a page wants to service the request.

This can go wrong because:

• the requests aren’t being sent to swik: a virtual host setting is wrong, or a DNS issue
• an error has been triggered and swik source is configured to hide errors.
• an invalid swik domain has been used.

User and license pages fail to work properly

SWiK-Source does not encode the ’:’ entity in urls such as User:alex. On Unix in Apache 2.0, this is allowed, on Windows OR in Apache 1.0 this is not.

To fix this issue:

• switch to Apache 2.0
• do not host a swik-source wiki on windows
• fix the bug in apache on windows.

Save a wiki page -> no text appears.

This occurs because SWiK execs a ruby textile script to generate the description cache, and it may have difficulty .

This can be because:

• tmp file privileges are improperly set
• ruby is not installed or the path to it is incorrect

check both these things.

RSS feeds do not syndicate properly

RSS feeds are syndicated using a temporary file, and then parsed with MagpieRSS.

If there is an issue with this, it can be because:

• tmp file privileges are improperly set
• the path to swik-configure is improperly set

Icon upload fails

Icon uploads use a two stage system. First the icon is persisted into the database; on the next request the icon is cached into a web directory. This is to ensure a single store for a multi-web-server environment, and cache icons for fast access.

If there is a problem with icon upload, it can be because:

• the swikIcons directory is not created or has bad privs for the server to write to.
• a libpng or libjpg library failure.