Wikka Wiki Web Hosting with Free Domain

Frequently Asked Questions

Can I use my own domain with WikkaWiki?

Yes. You can point a registered domain or subdomain to the hosting account and install WikkaWiki in the main document root or a selected directory. Decide the preferred URL before launch because changing it later can affect links, cookies, search indexing, and bookmarks. After setup, verify HTTPS, redirects, email delivery, and any application base-URL or rewrite settings.

How should I test WikkaWiki before launch?

Create a private staging installation and test administrator access, contributor accounts, page creation, editing, histories, search, uploads, permissions, notifications, links, and mobile display. Also verify the selected PHP and database or file-storage configuration, depending on how WikkaWiki stores content. Test a backup restoration and representative extensions or themes before inviting contributors or allowing search engines to index the wiki.

How much storage does a WikkaWiki wiki need?

The application may be small, but storage grows with page histories, uploaded images and documents, search indexes, logs, extensions, themes, and retained backups. Estimate how many contributors will edit content and whether the wiki will host large media files. Choose a plan with room for growth and restoration copies, then monitor disk, inode, and database usage after launch.

What should I check before adding a WikkaWiki extension or theme?

Confirm that it supports the exact WikkaWiki release and current server environment. Review its official source, license, release history, documentation, and security record. Avoid abandoned components that affect authentication, permissions, uploads, or page rendering unless qualified personnel have reviewed the code. Test the component on staging, keep its original package, and create a backup before enabling it on the live wiki.

Can multiple people edit a WikkaWiki wiki?

Yes. Wikis are designed for collaborative editing, but the available roles and permissions differ by platform. Create separate administrator and contributor accounts, grant only the access each person needs, and document page naming and review practices. Test whether readers, editors, and administrators can perform only their intended actions. Public editing requires stronger anti-abuse controls and active moderation.

How can I make WikkaWiki easier to navigate?

Plan a clear page hierarchy, use descriptive titles, link related pages, and create useful landing pages for major subjects. Apply categories, namespaces, groups, indexes, breadcrumbs, or navigation menus where the application supports them. Avoid isolated pages and duplicate titles. Review search terms and broken links periodically, and give contributors a short naming and linking guide so the structure remains consistent.

How can I improve WikkaWiki performance?

Use a supported PHP version, enable only necessary extensions, optimize uploaded images, and manage old logs and caches. Database-backed wikis benefit from appropriate indexes and database maintenance, while file-based wikis need efficient storage and permissions. A CDN can accelerate static assets, but personalized and editing pages require care. Measure response time and resource usage before changing caching or server settings.

What should be reviewed before allowing public editing?

Decide whether visitors may register, edit immediately, upload files, create accounts, or change external links. Configure permissions, spam controls, rate limits, moderation, and revision review before opening access. Publish contribution rules and a contact process for abuse or privacy concerns. Keep administrator accounts separate from everyday editing accounts and verify that unwanted revisions can be identified and reversed.

How do I recover WikkaWiki after a failed update?

Stop further changes and preserve the current files and data before troubleshooting. Restore a matching file-and-data backup to a private location, then verify logins, pages, histories, permissions, uploads, extensions, and themes. Avoid mixing database exports or content directories from different backup times. Once the restored copy works, schedule the production recovery and document the cause before attempting the update again.