MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"lecontinue": "20260917131158|599",
"continue": "-||"
},
"query": {
"logevents": [
{
"logid": 609,
"ns": 0,
"title": "Platform:Drupal/Tracing Drupal Storage",
"pageid": 430,
"logpage": 430,
"revid": 1402,
"params": {},
"type": "create",
"action": "create",
"user": "Mngr",
"timestamp": "2026-09-20T18:21:46Z",
"comment": "Created page with \"= Tracing Drupal Storage \u2014 From File to Physical Disk = == Purpose == This document explains how to trace a Drupal file through the different storage layers of the Costa Sano infrastructure: <code>Drupal file \u2193 Linux filesystem \u2193 Linux block device \u2193 Hyper-V virtual disk \u2193 VHDX file \u2193 Windows storage volume \u2193 physical disk</code> The important concept is that '''each layer hides the implementation details of the layer b...\""
},
{
"logid": 608,
"ns": 3002,
"title": "Platforms:Drupal/Drupal storage migration - \u00e9nd vdisk",
"pageid": 0,
"logpage": 429,
"revid": 1401,
"params": {
"target_ns": 3002,
"target_title": "Platforms:Drupal/Drupal storage migration - 2nd vdisk",
"suppressredirect": ""
},
"type": "move",
"action": "move",
"user": "Mngr",
"timestamp": "2026-09-20T16:38:06Z",
"comment": ""
},
{
"logid": 607,
"ns": 3002,
"title": "Platforms:Drupal/Drupal storage migration - \u00e9nd vdisk",
"pageid": 0,
"logpage": 429,
"revid": 1400,
"params": {},
"type": "create",
"action": "create",
"user": "Mngr",
"timestamp": "2026-09-20T16:37:31Z",
"comment": "Created page with \"= Drupal Media Storage Migration \u2014 Separate Hyper-V VHDX = == Purpose == This document describes a safe way to move the Drupal media storage from the Drupal VM's existing filesystem onto a separate Hyper-V virtual disk (VHDX). The objective is to obtain: * simple local storage from Drupal's point of view; * separation between the Drupal application/system disk and large media storage; * easy future expansion of the media storage; * no dependency on NFS or remote fil...\""
},
{
"logid": 606,
"ns": 3002,
"title": "Platforms:Drupal/To Synology",
"pageid": 0,
"logpage": 428,
"revid": 1396,
"params": {
"target_ns": 3002,
"target_title": "Platforms:Drupal/Using Private Storage space",
"suppressredirect": ""
},
"type": "move",
"action": "move",
"user": "Mngr",
"timestamp": "2026-09-20T15:15:53Z",
"comment": ""
},
{
"logid": 605,
"ns": 3002,
"title": "Platforms:Drupal/To Synology",
"pageid": 0,
"logpage": 428,
"revid": 1394,
"params": {},
"type": "create",
"action": "create",
"user": "Mngr",
"timestamp": "2026-09-18T14:03:40Z",
"comment": "Created page with \"= Drupal Media Storage on Synology NAS via NFS = This document explains how to relocate Drupal\u2019s <code>public://</code> media directory to a Synology NAS using NFS. This approach provides stable, scalable storage for large archives (500 GB+) while keeping the Drupal VM lightweight and maintainable. ---- == 1. Overview == Drupal stores uploaded media in <code>sites/default/files</code>, mapped internally as <code>public://</code>. For large archives, it is recommended...\""
},
{
"logid": 604,
"ns": 3014,
"title": "Project:PubModel/mozilla pdf.js viewer user guide",
"pageid": 427,
"logpage": 427,
"revid": 1392,
"params": {},
"type": "create",
"action": "create",
"user": "Mngr",
"timestamp": "2026-09-18T07:41:29Z",
"comment": "Created page with \"= PDF.js Viewer \u2013 Simple User Guide for Historians = The Mozilla PDF.js viewer is the built\u2011in PDF reader used in Firefox and available as a standalone viewer (viewer.html). This guide explains only the practical functions historians need when reading archival PDFs, without developer jargon. == 1. Opening a PDF == * Click the '''Menu icon''' (top right) \u2192 '''Open File'''. * Or simply '''drag and drop''' a PDF into the viewer window. == 2. Navigating Pages == *...\""
},
{
"logid": 603,
"ns": 3014,
"title": "Project:THE skin/mybarrio.theme system dynamics",
"pageid": 0,
"logpage": 426,
"revid": 1388,
"params": {
"target_ns": 3014,
"target_title": "Project:THE skin/mybarrio.theme rendering dynamics",
"suppressredirect": ""
},
"type": "move",
"action": "move",
"user": "Mngr",
"timestamp": "2026-09-17T16:33:22Z",
"comment": ""
},
{
"logid": 602,
"ns": 3014,
"title": "Project:THE skin/mybarrio.theme system dynamics",
"pageid": 0,
"logpage": 426,
"revid": 1387,
"params": {},
"type": "create",
"action": "create",
"user": "Mngr",
"timestamp": "2026-09-17T16:32:59Z",
"comment": "Created page with \"= Drupal Rendering Dynamics = == How <code>mybarrio.theme</code> Participates in Page Rendering == === Companion document to === '''<code>mybarrio.theme \u2014 Code Structure and Operation</code>''' ---- = 1. Why this document exists = Understanding the individual functions in <code>mybarrio.theme</code> is only half of the story. To understand why the code works, it is necessary to understand '''when Drupal calls those functions and what is being rendered at that momen...\""
},
{
"logid": 601,
"ns": 3014,
"title": "Project:THE skin/mybarrio.theme cleaned by gemini",
"pageid": 425,
"logpage": 425,
"revid": 1380,
"params": {},
"type": "create",
"action": "create",
"user": "Mngr",
"timestamp": "2026-09-17T15:37:12Z",
"comment": "Created page with \"__NOTOC__ = Drupal Theme Optimization: mybarrio.theme = This document details the refactoring and optimization of the custom code inside the '''mybarrio''' theme's preprocess hooks. The refactoring successfully removed approximately 100 lines of redundant and deeply nested logic, resulting in a cleaner, faster, and more maintainable codebase. == Optimized Source Code == Place this updated code into your local <tt>mybarrio.theme</tt> file: <syntaxhighlight lang=\"php\">...\""
},
{
"logid": 600,
"ns": 3014,
"title": "Project:PubModel/Field order in forms",
"pageid": 424,
"logpage": 424,
"revid": 1379,
"params": {},
"type": "create",
"action": "create",
"user": "Mngr",
"timestamp": "2026-09-17T14:00:36Z",
"comment": "Created page with \"= Field Order = == Purpose == This document defines the suggested standard order for fields in the Costa Sano historian-facing forms. The objective is not to force every content type or card to have the same fields. Instead, fields should appear in a '''predictable practical sequence''', so that a historian can work through a form without having to search for related information. The two main parts of a form are: # '''Archive part''' \u2014 information about the histori...\""
}
]
}
}