Eclipse 1.4.0 is now available, bringing improvements to theme customization, mobile navigation, accessibility, and overall reliability.
Built as a modern, responsive child theme of Denim, Eclipse provides a customizable interface while preserving Geeklog's native functionality and plugin integration.
Theme Studio: More reliable settings, custom palettes, footer management, and configuration restoration.
Mobile navigation: Improved responsive menus, keyboard accessibility, and Escape key support.
Administration: Refined responsive styling and advanced search forms.
Stability: Safer configuration storage, cache handling, and theme update rollback.
Compatibility: Successfully tested with Geeklog 2.2.2, PHP 8.3.36, and PHP 5.6.40.
The release has also been tested with the Static Pages, Downloads, and Menu plugins.
Eclipse requires Geeklog 2.2.2 or later and the Denim parent theme.
You can download Eclipse 1.4.0 from either location:
Feedback and contributions from the Geeklog community are welcome.
Posted November 5, 2026 | 6:03 pmSearchRank 1.3.0 is now available for Geeklog, bringing a redesigned administration interface, detailed search analytics, daily activity charts, CSV exports, and improved automatic data retention.
This update helps site administrators understand what visitors are searching for within their websites, identify popular topics, and analyze search activity over time. It also introduces a French translation and updated PHP compatibility checks.
The new version is available from the official SearchRank 1.3.0 release on GitHub.
SearchRank 1.3.0 significantly improves the administration and reporting experience while maintaining the plugin's original purpose: recording and ranking internal website searches.
The administration interface has been redesigned with responsive layouts and consistent navigation between the dashboard, search log, analytics, configuration, and help sections.
Administrators can review frequently searched expressions, browse recorded searches, and access built-in guidance more easily. A French (France) UTF-8 translation is also included.
A new analytics section provides a clearer view of how visitors use the website's internal search functionality.
CSV filenames include the website hostname and export timestamp, making reports easier to identify when managing multiple Geeklog installations.
SearchRank measures searches performed within the Geeklog website. It does not track search engine impressions from Google or Bing.
SearchRank now integrates its cleanup process with Geeklog's scheduled-task mechanism. Expired daily search records are removed according to the configured retention period, while expressions with more recent activity are preserved.
New installations default to 365 days of data retention. Existing installations retain their previously configured retention settings when upgraded.
Analytics periods are automatically limited by the retention configuration, and comparisons are suppressed when the configured history cannot cover two complete periods.
This release includes additional administration safeguards, improved output escaping, basic filtering of potentially sensitive search expressions, and safer CSV exports.
The declared minimum requirements are Geeklog 2.1.3 and PHP 5.6.40, with a MySQL-compatible database. Automated PHP syntax checks cover PHP 5.6, 8.1, and 8.3. PostgreSQL is no longer supported.
A fresh installation has been tested successfully on Geeklog 2.2.2. Additional regression testing is still recommended for older Geeklog installations and legacy database upgrades.
Before updating an existing installation, back up the Geeklog database, SearchRank tables, and plugin files.
Use Geeklog's plugin upgrade mechanism rather than uninstalling the existing plugin, as uninstalling may remove previously recorded search history.
Upgrade paths from earlier SearchRank versions, including 1.0.0, are included, but migrations from very old installations should be tested on a staging site before production use.
The official release includes the installable archive searchrank_1.3.0_2.1.3.zip.
For source code, documentation, release notes, and issue reporting, visit the official SearchRank repository.
Feedback and testing reports from the Geeklog community are welcome, particularly concerning upgrades from older versions and compatibility across supported hosting environments.
Posted October 17, 2026 | 9:44 pmI'm pleased to introduce Revisions 0.2.5, the first public pre-release of a new content versioning plugin for Geeklog.
The idea is simple: when you update a page, wouldn't it be useful to keep its previous version, compare the changes, and recover the original content if needed?
This initial version demonstrates that concept with automatic version tracking for Static Pages, a revision history interface, and a safe visual preview of archived content. The plugin is available for testing and feedback from the Geeklog community.
Once installed, Revisions automatically starts tracking eligible Static Pages. There is no need to select individual pages or manually activate tracking for each one.
When a tracked page is modified and saved through the supported Geeklog save process, its previous editorial content is stored in the revision history.
Administrators can then browse pages with archived revisions, select an earlier version, and examine the changes.
Revisions is still an experimental plugin. Version 0.2.5 focuses on demonstrating the history and comparison features.
Automatic restoration is not yet available. For now, administrators can recover archived HTML manually through the Static Pages editor.
Future development will focus on safe restoration, improved handling of concurrent edits, and extending revision history to Geeklog stories and potentially other content types.
This pre-release does not support PHP-based or template-based Static Pages, and it cannot reconstruct changes made before tracking was initialized. It should not be treated as a replacement for regular database and file backups.
Revisions 0.2.5 requires Geeklog 2.2.2 or later and PHP 5.6.40 or later.
The plugin has been tested on a Geeklog 2.2.2 installation, and GitHub Actions checks its PHP syntax with PHP 5.6, 8.1, and 8.3.
Revisions official GitHub repository
As this is a pre-release, testing on a development installation with a database backup is recommended.
This is an early step toward bringing content version history and recovery capabilities to Geeklog.
I'd be interested in hearing from other Geeklog users and developers. Does this approach meet your needs? Which content types should be supported next? What would make revision history most useful in your daily workflow?
Please share your suggestions, report issues, or contribute through the GitHub issue tracker.
Thanks to everyone helping improve Geeklog!
Posted October 17, 2026 | 7:00 pmEclipse 1.3.0 is now available for Geeklog! This new release brings a refreshed administration experience, an improved article editor, and further enhancements to the built-in Theme Studio.
Designed as a responsive child theme of Denim, Eclipse combines modern public-facing layouts with a more comfortable editorial workflow, while preserving Geeklog's native permissions, templates, and plugin integration.
Eclipse 1.3.0 requires Geeklog 2.2.2 or later and is available from the official GitHub release page.
This release focuses on making Geeklog easier to manage, more pleasant to use, and more consistent across public pages and administration screens.
Eclipse provides a redesigned administration workspace with improved navigation, responsive layouts, and a dashboard that brings useful information together.
The modern interface continues to respect Geeklog's existing permissions and administrative functionality.
The article editor has received particular attention in this release. Its reorganized layout makes better use of the available screen space and provides clearer access to frequently used settings.
Improvements include a full-width title field, more compact article details, SEO assistance, draft recovery, focus mode, and protection against accidentally leaving an article with unsaved changes.
Eclipse includes Theme Studio, an administration interface for customizing the appearance of the website.
Administrators can adjust color palettes, navigation styles, layout preferences, and footer content. Theme Studio also provides live previews, configuration history, and rollback capabilities.
Theme updates can be installed using the official ZIP archive, with package validation and safety backups to help protect existing installations.
Eclipse 1.3.0 also refines the public-facing theme with improved typography, responsive navigation, cleaner article previews, and more consistent layouts.
Article summaries have been simplified, and administrators can optionally display a heading for topic index pages. The theme continues to rely on Geeklog's native content and template mechanisms.
Geeklog 2.2.2 or later is required. Compatibility with Geeklog 2.1.1 is no longer maintained.
Eclipse uses Denim as its parent theme, so Denim must remain installed. The theme maintains PHP 5.6 syntax compatibility, although a currently supported PHP version is recommended for production websites.
Eclipse 1.3.0 is available as a free, open-source theme under the GNU General Public License.
Download Eclipse 1.3.0 from GitHub Releases
For a new installation, download the official eclipse-1.3.0.zip archive and install the Eclipse theme directory in your Geeklog layout directory. Keep Denim installed as the parent theme.
For an existing Eclipse installation, the archive can also be uploaded through Theme Studio's update interface. Backing up your site before upgrading is recommended.
Eclipse is an open-source project, and feedback from the Geeklog community is welcome.
If you encounter a problem, have an improvement suggestion, or would like to contribute, visit the Eclipse GitHub repository or open an issue using the GitHub issue tracker.
Thank you to the Geeklog community for its continued support and contributions!
Posted October 17, 2026 | 6:23 pmThe Open Graph Protocol (OGP) plugin 2.1.0 is now available for Geeklog. This release improves social metadata generation, SEO title handling, and support for rewritten topic URLs.
OGP helps websites generate Open Graph and Twitter/X Card metadata for sharing content on social networks. Version 2.1.0 also introduces cleaner article descriptions while maintaining backward compatibility with existing installations.
This release introduces several improvements:
OGP 2.1.0 requires Geeklog 1.6.0 or newer and PHP 5.6.4 or newer. The release has been tested with Geeklog 2.2.2.
Upgrading from OGP 2.0.0 is supported through Geeklog's standard plugin upgrade process. No database schema changes or configuration migration are required.
The new release is available from the official Geeklog Plugins repository on GitHub.
Developers can also explore the source code and contribute to future improvements through the OGP GitHub repository.
Posted October 16, 2026 | 4:56 pmA new version of the Monitor plugin for Geeklog is now available.
Monitor 1.5.0 continues the modernization work started with version 1.4.0, with a strong focus on reliability, diagnostics, safer administration, plugin compatibility checks and multilingual support.
The new version is available from the official Geeklog Plugins repository:
https://github.com/Geeklog-Plugins/monitor
Monitor is evolving into a dedicated site-health and diagnostic plugin rather than a collection of unrelated administration tools.
Its guiding principle remains simple:
Observe -> Diagnose -> Alert -> Recommend -> Act only when explicitly requested
By default, Monitor is read-only. It reports problems, provides context and recommends actions without silently changing site configuration, plugin code or security state.
The administration interface focuses on four main areas:
Monitor 1.5.0 targets:
Several compatibility improvements have been made around Geeklog's native Configuration system.
Monitor now uses the expected Geeklog configuration structure, provides native configuration help tooltips and can repair malformed configuration metadata from earlier development builds without requiring an artificial version increase.
Existing administrator values are preserved during these repairs.
One of the most visible improvements in Monitor 1.5.0 concerns plugin monitoring.
The plugin catalog now provides clearer information about:
The Discover plugins list is now sorted alphabetically, making larger plugin repositories easier to browse.
Monitor also distinguishes between the newest release available upstream and the newest release that can actually be installed on the current site.
This is particularly useful for administrators maintaining older Geeklog installations.
Monitor uses GitHub metadata to discover plugin versions and compatibility information.
Version metadata caching has been refined in 1.5.0:
An optional read-only GitHub token can therefore provide both a larger API quota and fresher version information.
The log tools have also received significant improvements.
Monitor provides bounded and escaped log viewing, explicit CSRF-protected log clearing and daily log archiving.
Archives are kept outside the public web directory and active logs are truncated only after the archive copy has been successfully created.
The archive interface provides sortable lists and dedicated previews without exposing raw filesystem paths.
Monitor can create lightweight snapshots of the current site state and compare them over time.
The comparison can highlight changes such as:
This provides administrators with a quick way to understand what changed between two checks.
Monitor 1.5.0 also continues the removal of old or risky mechanisms inherited from historical releases.
Among the changes introduced during the 1.4/1.5 modernization work are:
sleep(60) request blocking;Monitor is not intended to replace the dedicated Geeklog Ban plugin.
Instead, Monitor observes suspicious activity and reports security information while Ban remains responsible for persistent blocking rules and enforcement when installed.
Monitor 1.5.0 also introduces a clearer interoperability model.
It exposes read-only capabilities such as:
monitor.healthmonitor.diagnosticsmonitor.logs.summarymonitor.plugins.statusdashboard.summaryOther Geeklog components such as Agent, Eclipse or Hub can consume these services without directly accessing Monitor's internal files or storage.
This keeps Monitor responsible for calculating and owning its diagnostic data while allowing other plugins and themes to reuse it safely.
This release also greatly expands Monitor's multilingual support.
Monitor 1.5.0 now includes UTF-8 translations for:
English remains the canonical language file.
Automated CI checks now verify that translated files contain the same keys and compatible placeholders such as %s and %d, helping
MediaGallery 1.9.0 is now available from the official Geeklog Plugins repository.
This new version continues the modernization work started with MediaGallery 1.8.0 while keeping an important goal intact: existing Geeklog websites should be able to adopt the improved plugin without being forced to upgrade their entire CMS stack first.
MediaGallery 1.9.0 therefore continues to support Geeklog 2.1.1 and newer, including Geeklog 2.2.2, while keeping PHP 5.6-compatible syntax and being validated against PHP 5.6, 7.4, 8.1 and 8.3.
The source code and installable package are available here:
https://github.com/Geeklog-Plugins/mediagallery
One of the main goals of MediaGallery 1.9.0 is to complete the remaining PHP 8 runtime hardening.
Older MediaGallery installations may contain records created by previous releases, imports or migrations where some optional media metadata is not present. Newer PHP versions are much less forgiving when code accesses missing array keys.
MediaGallery 1.9.0 now normalizes optional media metadata before it reaches the rendering layer. This includes values related to media resolution, display resolution, remote media and remote URLs.
This prevents PHP 8 warnings when older or imported media records are displayed and completes the remaining compatibility work associated with issue #11 in the MediaGallery issue tracker.
The release branch is automatically checked against PHP 5.6, PHP 7.4, PHP 8.1 and PHP 8.3.
MediaGallery 1.9.0 also expands the SEO work introduced during the previous modernization cycle.
Album pages can now expose Schema.org CollectionPage structured data together with an ItemList representing the media displayed on the current page.
Individual media pages continue to expose content-specific structured data using appropriate Schema.org types such as:
ImageObjectVideoObjectAudioObjectMedia URLs used in structured data are normalized into absolute public URLs where appropriate.
Albums and individual media pages also receive improved meta-description fallbacks. When a dedicated description exists, MediaGallery can provide content-specific metadata instead of relying only on the generic site description.
The result is cleaner metadata for search engines and other consumers without changing the editorial workflow for site administrators.
MediaGallery can now cooperate with the OGP plugin when it is installed.
If an active OGP plugin exposes the expected social metadata API, MediaGallery can delegate Open Graph and Twitter/X metadata to it.
Albums can provide their title, description, canonical URL and a representative image. Individual media pages can provide similar information together with media-specific metadata.
This integration remains optional.
MediaGallery does not require OGP, and websites without the plugin continue to receive standalone Open Graph and Twitter/X metadata generated by MediaGallery itself.
MediaGallery also remains authoritative for its canonical URLs, descriptions and Schema.org structured data.
A major part of the recent MediaGallery modernization has been making the plugin easier for the rest of the Geeklog ecosystem to work with.
Historically, another plugin wanting information about MediaGallery albums or media could be tempted to query MediaGallery's private database tables directly. That creates tight coupling between plugins and makes future changes more difficult.
MediaGallery instead exposes bounded services and standard Geeklog Plugin API information.
For example, other Geeklog components can request a permission-filtered album tree through PLG_invokeService() instead of knowing anything about MediaGallery's internal mg_* tables.
MediaGallery also reports album and media changes through Geeklog's normal lifecycle mechanisms.
This allows plugins and services such as IndexNow, XML Sitemap, Hub and future integrations to react to MediaGallery content without MediaGallery containing consumer-specific code.
The same interoperability work makes MediaGallery more suitable for newer Geeklog tools such as Agent, Hub and modern administration dashboards.
MediaGallery continues to use the persistent storage architecture introduced with version 1.8.0.
User media is stored outside the replaceable public_html/mediagallery/ plugin directory and instead uses Geeklog's configured image storage location.
This is particularly important when updating a plugin through Geeklog's ZIP installer because plugin files can safely be replaced without treating user media as part of the application code.
The storage paths are derived from Geeklog configuration rather than hard-coded locations, which also makes the design suitable for shared-code multisite installations.
Each site can keep its own MediaGallery content even when several Geeklog sites share the same plugin source files.
MediaGallery 1.9.0 carries forward the security improvements introduced during the 1.8 modernization.
These include protections around:
Image processing also checks that the configured Geeklog image backend is actually available before attempting resize, conversion, rotation or watermark operations.
Supported configurations include GD, ImageMagick and NetPBM according to the Geeklog site configuration.
The maintained MediaGallery interface has also moved away from several technologies and assumptions inherited from much older web applications.
The current templates provide responsive album and media layouts, improved semantic markup and accessibility, modern lightbox and slideshow behavior, and HTML5 audio/video playback.
Legacy Flash and ActiveX playback paths are no longer part of the active playback experience.
Album thumbnails and portrait-image rendering have also received improvements, including the use of better source images when generating visual representations.
MediaGallery 1.9.0 significantly expands its maintained language coverage.
The current English files are used as the structural reference, and the release includes updated or newly synchronized UTF-8 translations for:
The language files follow the same functional key structure as the English reference and are included directly in the MediaGallery 1.9.0 distribution.
This should make the plugin much easier to deploy on multilingual Geeklog sites and within the international Geeklog community.
MediaGallery 1.9.0 also improves how the plugin identifies itself to Geeklog.
Release and minimum Geeklog compatibility information are now centralized in a canonical version.php file.
The plugin runtime, installer and upgrade logic therefore share the same authoritative release metadata.
The static plugin.json manifest remains available for repository and administration tools, and the distribution workflow validates that its compatibility information remains synchronized with the installer metadata.
This avoids situations where the version reported by the running plugin, the installer and the package metadata can accidentally diverge.
MediaGallery 1.9.0 supports:
Automated syntax validation currently covers PHP 5.6, 7.4, 8.1 and 8.3.
Keeping Geeklog 2.1.1 compatibility is deliberate. It gives administrators the option to modernize important plugins before, during or after a staged migration of the Geeklog core itself.
Existing MediaGallery 1.8.0 installations can upgrade directly to MediaGallery 1.9.0.
No additional database schema migration is required beyond the existing 1.8.0 state.
As always, administrators should keep a current database and media backup before updating a production website.
Sites still running MediaGallery 1.7.x require one additional precaution.
Those installations may still store user media inside:
public_html/mediagallery/mediaobjects/
Because Geeklog's plugin ZIP updater replaces the plugin public directory, legacy media must first be migrated to the persistent storage location introduced with MediaGallery 1.8.0.
MediaGallery includes a migration tool for this purpose. The tool copies and verifies the media while deliberately leaving the original source files untouched.
Administrators upgrading from 1.7.x should complete this migration successfully before replacing the plugin through the Geeklog ZIP installer.
MediaGallery 1.9.0 source code, documentation and the validated installable archive are available from the official Geeklog Plugins repository:
https://github.com/Geeklog-Plugins/mediagallery
The installable package is:
mediagallery_1.9.0_2.1.1.zip
MediaGallery 1.9.0 is another step toward keeping one of Geeklog's long-standing content plugins useful on both existing and modernized Geeklog installations, with stronger PHP compatibility, cleaner interoperability, improved SEO and much broader language coverage.
Posted October 4, 2026 | 7:11 pmIf you are still running an old glFusion, WordPress, or legacy Geeklog website, moving to a clean and modern Geeklog installation can now be much easier.
The new Migrator 1.0.0 plugin has been created specifically to help recover content from legacy CMS database dumps and import it into a fresh Geeklog 2.2.2 installation.
Migrator is available here:
https://github.com/Geeklog-Plugins/migrator
Rather than trying to upgrade an aging installation through years of intermediate versions, Migrator takes a different approach: start with a clean Geeklog installation and bring your valuable content with you.
Maintaining a Geeklog website that has been online for many years can become increasingly difficult.
The site may have gone through several PHP versions, database upgrades, theme changes, plugin updates, and server migrations. In some cases, the installation may be so old that performing a traditional step-by-step upgrade is no longer practical.
Migrator provides another option.
You can install a completely fresh copy of Geeklog 2.2.2, install the current versions of the plugins you need, and then use Migrator to recover compatible content from the database of the old website.
Depending on the source installation, Migrator can recover core content such as:
Where possible, existing IDs are preserved so relationships between imported content remain intact.
This approach can be particularly useful when moving from a very old Geeklog installation to a clean server with a current PHP and database environment.
glFusion originated as a fork of Geeklog, which means that many of its core database structures remain closely related to Geeklog.
That makes glFusion an especially interesting migration source.
Migrator can recover compatible glFusion core content and also includes dedicated support for some of the most important glFusion plugins.
Migrator can recover compatible Forum data including:
One of the more difficult areas of a CMS migration is dealing with old Forum attachments.
Migrator can convert legacy glFusion Forum attachment records into MediaGallery downloadable media items. Migrated Forum posts can then reference those files through MediaGallery download autotags.
This provides a practical bridge between an old glFusion Forum installation and the current Geeklog plugin ecosystem.
Migrator also supports migration of compatible glFusion MediaGallery data.
This includes information such as:
Some compatibility differences between old glFusion versions and current MediaGallery releases are handled automatically during migration.
Physical media files themselves are deliberately not copied automatically. Migrator instead reports the paths required for the administrator to copy them manually.
This keeps the database migration safe and predictable while avoiding potentially dangerous automatic manipulation of large media directories.
Migrator is not limited to Geeklog-derived platforms.
It also provides a migration path from WordPress to Geeklog.
A WordPress migration can currently recover several important types of content.
WordPress categories are converted into Geeklog topics, posts become Geeklog stories, and pages can be imported as Static Pages.
Migrator also handles:
This makes Migrator particularly useful for website owners who want to leave WordPress but keep their existing editorial content.
There are intentionally some limitations.
WordPress plugin-specific content is not migrated, and WordPress password hashes are not imported. Migrated WordPress users therefore need to set a new Geeklog password.
Tags, featured-image metadata, pingbacks, trackbacks, and some attachment metadata are also outside the current migration scope.
The objective is not to reproduce every internal WordPress feature. The goal is to recover the important content needed to rebuild the website cleanly in Geeklog.
One of the most important design decisions behind Migrator is that it does not need to work directly against your production database.
Instead, you export the source database and upload the resulting SQL dump to Migrator.
The plugin currently accepts:
.sql;.sql.gz;.zip containing a single SQL file.Migrator then recreates the source tables using isolated staging table names.
This means the source database structure can be inspected and analyzed without executing its original table names against the Geeklog destination database.
The workflow is deliberately cautious.
First the database is staged. Then Migrator detects the source CMS and analyzes the available content. The administrator can review the results and perform a dry run before starting the actual migration.
Migrator is not intended to merge arbitrary websites into an already populated Geeklog site.
It deliberately expects a fresh Geeklog 2.2.2 installation.
Before writing content, the plugin checks the destination installation and refuses the migration if it no longer resembles the expected fresh-install baseline.
This restriction is intentional.
Content migration becomes much safer when the destination is predictable. It also reduces the risk of overwriting users, articles, topics, or other existing content.
A typical migration therefore looks like this:
A migration is also a good opportunity to reconsider everything that has accumulated over the years.
Instead of carrying old PHP files, abandoned plugins, obsolete themes, outdated configuration entries, and years of technical debt into another upgrade, a clean Geeklog installation gives you a much simpler starting point.
You can install only the plugins you still use, deploy a current theme, review permissions, reorganize topics, and remove content that no longer needs to be published.
Migrator focuses on recovering the data that matters while allowing the new Geeklog installation itself to remain clean.
Database records and physical files are intentionally treated separately.
For MediaGallery migrations and recovered Forum attachments, Migrator creates the required database records and reports where the corresponding files must be placed.
With MediaGallery 1.9.0 on a standard Geeklog 2.2.2 installation, persistent media storage is located under:
public_html/images/mediagallery/
Administrators using customized image paths can use their configured MediaGallery storage location instead.
This separation is particularly useful when migrating large websites, because files can be transferred independently using SSH, SCP, rsync, FTP, or another server-side method.
Migrating an old CMS database is inherently sensitive, so Migrator includes several safeguards.
Uploaded SQL dumps are stored outside the public web root. Source tables are staged under isolated names. Potentially dangerous or unrelated SQL statements are not executed as part of the migration workflow.
Migrator also keeps migration jobs, ID mappings, and logs so that administrators can understand what happened during the import.
There is also a reset mechanism for imported database content when a migration needs to be restarted.
As with any CMS migration, however, you should always keep complete backups of both the source website and the destination environment.
Migrator 1.0.0 is the first public release of this new migration tool.
It currently targets Geeklog 2.2.2 and supports three important migration scenarios:
Legacy Geeklog → Geeklog 2.2.2
A practical way to rebuild a very old Geeklog website on a completely fresh installation.
glFusion → Geeklog 2.2.2
Including compatible Forum and MediaGallery data.
WordPress → Geeklog 2.2.2
For site owners who want to move their editorial content away from WordPress and into Geeklog.
Migrator is available from the Geeklog Plugins organization on GitHub:
https://github.com/Geeklog-Plugins/migrator
If you still maintain an old Geeklog, glFusion, or WordPress website, this may be a good time to give that content a fresh start with Geeklog.
Posted October 4, 2026 | 6:50 pmGeeklog language files are receiving a significant update, covering both the core CMS and several bundled plugins.
Over the past few weeks, I have been reviewing the existing translations, completing missing strings, adding missing language files, fixing placeholders, and improving consistency between languages.
The goal is simple: provide a more complete and reliable multilingual experience for Geeklog users and make future language maintenance easier.
A first series of pull requests has been submitted to the official Geeklog repository for the main Geeklog language files.
The work currently covers:
The updates focus on missing or untranslated strings, wording consistency, UTF-8 support, and compatibility with the current Geeklog language structure.
Each language is handled separately so that changes can be reviewed and merged independently.
The same work is now being applied to the plugins distributed with Geeklog.
Pull requests have already been submitted for:
For these plugins, the language packs are being aligned with the same set of languages whenever possible.
This includes not only updating existing translations, but also adding language files that were previously missing.
This work is not limited to translating strings.
I have also been using automated checks to detect common problems such as:
%s and %d;This makes it possible to validate a language pack before submitting it upstream and reduces the risk of introducing broken interface strings.
For the most recently completed plugins, the objective is to reach full coverage with no missing keys, placeholder errors, or remaining translation review items.
The pull requests are currently being reviewed in the official Geeklog repository.
If accepted, these updated translations should become part of Geeklog and be available directly in a future update.
There is no need to wait for the merges if you want to test them today.
The current development versions of the language files are available from the lang branch of my hostellerie/geeklog-2.2.2 repository on GitHub.
This branch contains the ongoing language modernization work before the changes are separated into individual pull requests for the official Geeklog repository.
Automated checks can detect structural problems, but they cannot replace native speakers.
If you use Geeklog in one of these languages, feedback is particularly useful for:
The objective is not simply to translate every English string, but to provide language files that are practical and comfortable to use on real Geeklog websites.
More plugin language updates are planned as this work continues.
Posted October 1, 2026 | 5:07 pmEclipse 1.2.0 is now available for Geeklog.
This release is an important milestone for the project. Eclipse started as a modern, responsive child theme based on Denim, but version 1.2.0 goes much further. It improves the administration experience, strengthens compatibility with Geeklog 2.2.2, introduces better interoperability with plugins, expands Menu integration and makes theme updates safer.
The project is available on GitHub:
https://github.com/hostellerie/eclipse
The stable 1.2.0 release is available here:
https://github.com/hostellerie/eclipse/releases/tag/v1.2.0
One of the main goals of Eclipse is to improve the daily experience of managing a Geeklog site without replacing Geeklog's own permission and plugin systems.
Eclipse 1.2.0 continues this work with a more complete Modern workspace, while still keeping the Classic Eclipse administration interface available.
The administration dashboard can now receive structured information from plugins through declared capabilities.
For example, a plugin can expose:
Eclipse displays this information without directly querying the plugin's private database tables.
This is important because it keeps responsibilities clearly separated: the plugin owns its data and business logic, while Eclipse is responsible for presentation.
Documents and Videos are already reference implementations of this approach, and other plugins can follow the same model.
Navigation has also received significant improvements.
Eclipse 1.2.0 can now work with independent Menu plugin locations for:
This gives site administrators much more freedom when building the structure of a site.
The theme also handles administration and public navigation separately. Secondary public navigation is no longer injected into administration pages, while the traditional primary navigation remains available when using Classic
Posted October 1, 2026 | 9:00 am