View Articles

Tiki Wiki CMS is used on several sites that are currently under heavy fire from aggressive, resource-hungry AI crawlers. These bots can overwhelm servers to the point where applications become painfully slow or even completely unavailable, as we discussed in a previous article. The answer cannot be limited to what happens “at the server’s doorstep” (WAF, rate limiting, IP blocking, etc.). It is just as essential to strengthen Tiki Wiki itself by acting on:

• The content the site actually exposes to visitors and bots
• The way queries are built, filtered, and chained
• The detection and control of abnormal memory or CPU consumption
• The data that is queried versus what is actually returned
• The use of Tiki’s own optimisation and performance tools

In the breakneck race to hoover up data, AI models are unleashing armies of bots that crawl the web nonstop—often ignoring rules like robots.txt. The result? Siphoned bandwidth, strained servers, and pages that slow to a crawl or go offline—an abnormal, excessive load that hurts publishers, businesses, and users alike. As The Register notes, more and more voices are calling out bots that send no traffic back yet rack up infrastructure costs and leave teams overwhelmed.

At OpenSource Solutions, we take a clear, measurable approach. We continuously analyze traffic logs to spot overconsumption, correlate signals across multiple servers to tell trustworthy crawlers (search engines) from aggressive AI scrapers, and roll out proactive defenses—quotas, rate limiting, IP allowlists, bot traps, even GeoIP filtering—to protect performance without blocking the indexing that’s essential for SEO. Let’s break it down.

After upgrading your Tiki Wiki CMS Groupware from Tiki 27 to Tiki 29, you might encounter a strange date display bug affecting how date fields are shown in trackeritems, customsearch plugins, and other components. Instead of clear values like 2025-08-21 15:00, you may see garbled text such as -00-yy 15:00.

At OpenSource Solutions, where we provide professional Tiki Wiki support and maintenance, we explored this issue and developed a straightforward workaround for our clients. In this Tiki Wiki Tip article, we’re sharing the steps to resolve the problem and restore correct date formatting across your site.

This comprehensive guide demonstrates how to set up a Debian 12 server with a hosting control panel and install a Tiki Wiki website solution using only open-source software.

Designed for versatility, this proven method leverages an Amazon AWS Lightsail instance but can be easily adapted to most hosting platforms. Follow this step-by-step guide to configure MariaDB, manage PHP versions, install Webmin and Virtualmin, secure your server with SSL certificates, and publish your Tiki Wiki site online—all with expert insights and professional tips to streamline the process.

This tutorial is tailored for intermediate IT administrators or full-stack developers seeking guidance on setting up and publishing websites.

The Tiki 27+ Build System marks a significant evolution in the way Tiki Wiki CMS Groupware handles its development and deployment processes. This article aims to guide you through the essential steps and provide solutions, even as the process continues to stabilize.

Introduced in Tiki 27 and refined in subsequent versions, this build system brings numerous enhancements aimed at improving efficiency, consistency, and ease of maintenance for developers and users alike. However, it requires power users and administrators to familiarize themselves with the new installation method from Gitlab (Version Control System).