Main public logs
Appearance
Combined display of all available logs of Costa Sano KB. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).
- 09:13, 18 May 2026 Mngr talk contribs moved page Drupal:Pages/Overlay - floating overlay to Drupal:Overlay/Floating Overlay without leaving a redirect
- 09:12, 18 May 2026 Mngr talk contribs created page Drupal:Overlay (Created page with "= Overlay being heavily used in the webiste, a special chapter is dedicated to it =")
- 08:56, 18 May 2026 Mngr talk contribs created page Drupal:Pages/Overlay- recap sheet (Created page with "= Floating Overlay Box — Recap Sheet = A compact reference for centering a floating overlay box inside an image, with centered text and visible image borders. == 1. Purpose == The Floating Overlay Box is a centered card placed inside an image. It leaves a visible border of the image around it and centers the text inside the box. Ideal for: * heritage captions * exhibition-style labels * centered storytelling cards == 2. Core CSS Pattern == This CSS centers the ove...") Tag: Visual edit: Switched
- 08:52, 18 May 2026 Mngr talk contribs created page Drupal:Pages/Overlay - floating overlay (Created page with "= Floating Overlay Box Component = This component displays a centered overlay box inside an image, leaving a visible border of the picture around it. The overlay box itself is centered, and the text inside the box is also centered with padding. This pattern is ideal for: * heritage captions * exhibition-style labels * centered storytelling cards * emphasis overlays inside photographs == 1. Visual Concept == The overlay does NOT cover the entire image. Instead, it f...")
- 08:41, 18 May 2026 Mngr talk contribs created page Drupal:Pages/Overlay memory sheet (Created page with "= Overlay Engine — Memory Sheet = A compact reference for all overlay components, variants, and integration patterns used across the heritage website. == 1. Core Concept == All overlays follow the same structure: * image + overlay text * hover on desktop * always visible on mobile * accessible (reduced motion, high contrast) * variants applied via CSS classes == 2. Base Twig Macro == <syntaxhighlight lang="twig"> {{ overlay.overlay(img, text, classes) }} </syntaxhigh...")
- 08:36, 18 May 2026 Mngr talk contribs created page Drupal:Pages/Overlay general css (Created page with "= Unified Overlay Engine CSS (overlay.css) = This file defines all styling for the overlay engine used across the heritage website. It includes: * base overlay structure * animation variants * image effect variants * accessibility rules * mobile/touch behavior * carousel compatibility == 1. Base Component Structure == All overlays share this foundation. <syntaxhighlight lang="css"> Root container: .overlay-component { position: relative; overflow...")
- 08:34, 18 May 2026 Mngr talk contribs created page Drupal:Pages/Overlay Developers reference (Created page with "= Overlay Engine Reference (Developer Documentation) = This document describes the internal overlay engine used across the heritage website. It is intended for developers integrating overlays into automatically generated cards, carousels, and content-type templates. == 1. Purpose == The overlay engine provides: * a unified structure for all image overlays * consistent styling across cards, galleries, and carousels * automatic mobile and accessibility handling *...")
- 08:29, 18 May 2026 Mngr talk contribs created page Drupal:Pages/Overlay design blocks (Created page with "= Heritage Website Overlay Design System = This document defines a unified, reusable design system for all image‑based overlays used across the heritage website. It consolidates patterns from previous documents into a coherent, maintainable structure. The goal is to ensure: * visual consistency * accessibility * mobile‑friendly behavior * easy reuse in Twig templates * respectful presentation of historical material = 1. Core Overlay Philosophy = Overlay...")
- 08:20, 18 May 2026 Mngr talk contribs created page Drupal:Pages/Overlay animation (Created page with "= Image Overlay on Hover — Documentation = == Overview == This component displays an image with a text overlay that becomes visible only when the user hovers over the image. It uses Twig for markup and CSS for interaction and animation. Optional enhancements include fade‑in, slide‑in, and blurred‑glass effects. == Twig Markup == The Twig structure is identical for all enhancement variants: <syntaxhighlight lang="twig"> {% if layout == 'overlay' %} <div cla...")
- 17:29, 17 May 2026 Mngr talk contribs created page Drupal:Bootstrap/Layout issues - overlay (Created page with "= Bootstrap Position Utilities – Overlay Cheat Sheet = This page documents how to position text overlays on images using Bootstrap’s position utilities. It focuses on the common pattern: * Parent: <code>position-relative</code> * Overlay: <code>position-absolute</code> + positioning classes == 1. Core concept == To place text on top of an image: <syntaxhighlight lang="html"> <div class="wrapper position-relative"> <img src="image.jpg" class="img-fluid w-100" a...") Tag: Visual edit: Switched
- 17:28, 17 May 2026 Mngr talk contribs created page Drupal:Bootstrap (Created page with "Bootstrap information needed for Barrio and Bootstrap 5") Tag: Visual edit
- 08:29, 17 May 2026 Mngr talk contribs created page Drupal:Pages/Paragraph type text + image (Created page with "= Paragraph Type: Image + Text Frame (Drupal 11.3, Bootstrap 5, Barrio) = This document describes a clean, KISS‑oriented paragraph type that supports: * Image + text beside * Image + text under * Image + text overlay * Image only * Image only with optional link All layouts are handled by a single paragraph type and a single Twig template. == 1. Create the Paragraph Type == Name: '''image_text_frame''' === Fields === ; field_image : Type: Image : Widget: Image : Requ...")
- 16:02, 15 May 2026 Mngr talk contribs created page Drupal:Pages/Homepage 201 (Created page with "= Homepage Publication Assembly Architecture (node/201) = == Introduction == The homepage represented by: <pre> node/201 </pre> became an important architectural evolution inside the publication platform. Initially the platform started with more traditional Drupal page concepts using: * Basic Page content types * Body fields * generic node rendering As the publication architecture matured, the homepage evolved toward: <pre> a Paragraph-driven publication assembly...")
- 12:36, 15 May 2026 Mngr talk contribs created page Maintenance:Drupal/Documenting/Replacing the Default Drupal Node Page With Custom Publication Architecture (Created page with "= Replacing the Default Drupal Node Page With Custom Publication Architecture = == Introduction == One of the most important conceptual steps in understanding Drupal is realizing that: <pre> the default node page is not the final publication architecture </pre> The default page generated by Drupal is primarily: * a generic rendering fallback * a structural default presentation * a content accessibility mechanism It is NOT intended to represent the final publication...")
- 12:26, 15 May 2026 Mngr talk contribs created page Maintenance:Drupal/Documenting/Entity-Driven Publication Architecture Using Chapters, Subchapters, Carousels and Cards (Created page with "= Entity-Driven Publication Architecture Using Chapters, Subchapters, Carousels and Cards = == Introduction == As the publication architecture evolved, an important design decision was made: <pre> publication surfaces should be driven by structured entities </pre> rather than manually duplicated presentation components. The objective is to preserve: * relational coherence * maintainability * publication consistency * navigational continuity * long-term scalability...")
- 12:07, 15 May 2026 Mngr talk contribs created page Maintenance:Drupal/Documenting/Homepage architecture (Created page with "= Drupal Homepage Architecture, Nodes, Routing and Publication Assemblies = == Introduction == One of the initially confusing aspects of Drupal is that a homepage is usually not a single object. Instead, the homepage is typically the result of several Drupal systems collaborating together. These systems may include: * nodes * routing * path aliases * block layouts * Views * Twig templates * Paragraph systems * Bootstrap layouts Understanding these relationships is...")
- 11:59, 15 May 2026 Mngr talk contribs created page Maintenance:Drupal/Documenting/Twig naming (Created page with "= Drupal Twig Template Naming and Rendering Architecture = == Introduction == Drupal uses Twig as its rendering template system. Twig templates define: * HTML structure * rendering organization * component composition * integration with CSS frameworks such as Bootstrap * publication presentation logic Understanding Drupal Twig naming conventions is extremely important because they form one of the central mechanisms of Drupal publication architecture. Twig templates...")
- 19:26, 14 May 2026 Mngr talk contribs created page Wiki:Why (Created page with "= Blueprint for Organising the New MediaWiki Instance = This document provides a structured approach for building a clean, maintainable, successor-friendly MediaWiki installation dedicated to documenting the Drupal platform, the server environment, and operational procedures. The goal is to replace the experimental, Cargo-based wiki with a new, purpose-built documentation system that is clear, predictable, and easy to maintain. == 1. Purpose of the New Wiki == The new...")
- 19:24, 14 May 2026 Mngr talk contribs created page Maintenance:Drupal/Debugging and tracing (Created page with "== Debugging & Logic Tracing == To monitor the internal "order of procedures" and database handshake: {| class="wikitable" ! Method !! Command !! Purpose |- | '''Live Stream''' || <code>./vendor/bin/drush wd-tail</code> || Real-time log of PHP errors, DB queries, and User actions. |- | '''Object Inspection''' || <code>kdf($entity);</code> || (Requires Devel) Formats complex data objects for "ICT-Pro" inspection. |- | '''ECA Workflow Trace''' || ''UI -> Reports ->...")
- 19:22, 14 May 2026 Mngr talk contribs created page Drupal:Config/m-m with IEF and Entity Browser - no custom module (Created page with "= Drupal: Asset selection with Inline Entity Form + Entity Browser (Gin, no custom module) = == Purpose == This page documents the final, working setup for selecting and managing Assets on entity edit forms (e.g. Person → Asset), using: * Inline Entity Form (IEF) – Complex (table display) * Entity Browser (modal picker with search and thumbnails) * Gin admin theme * No custom module * No JavaScript logic * Hardened for AlmaLinux / SELinux The goal was to provide a...")
- 19:16, 14 May 2026 Mngr talk contribs created page Platforms:Timeout issues (Created page with "== Administrator Procedures: Extending Session Timeouts == As a Sysop, you can adjust the server configuration to better support long-term historical research. These changes must be made in the '''LocalSettings.php''' file on the server. === 1. Increasing the Idle Session Window === By default, MediaWiki ends a session after 1 hour of inactivity. For researchers who spend hours drafting, this should be increased to 24 hours. Add or update this line: <syntaxhighlight l...")
- 19:13, 14 May 2026 Mngr talk contribs created page Platforms:AlmaLinux/R-Proxy wiht nginx (Created page with "= Reverse‑Proxy Architecture (nginx → Apache) = This page documents the complete reverse‑proxy setup for the AlmaLinux frontend server. It replaces the former IIS reverse‑proxy and Windows‑based certificate renewal system. The configuration is now fully Linux‑native, stable, and successor‑friendly. == Overview == * Frontend: AlmaLinux + nginx * Backend: Apache (Drupal + MediaWiki) * Certificates: Let’s Encrypt (certbot) * Automatic renewal: systemd timer...")
- 19:11, 14 May 2026 Mngr talk contribs created page Drupal:C-Modules/Tweaks/Removing the view link - better version (Created page with "= Drupal 11 – Removing the “View” link from node save messages = == Context == In the Heritage Project (Drupal 11.3.x), historian users must **not** be redirected to or encouraged to view the node page after saving content. However, Drupal core automatically shows a status message such as: <pre> Article “My title” has been updated. View </pre> The “View” link is part of the default node save status message. A custom module (`heritage_tweaks`) modifies...")
- 19:06, 14 May 2026 Mngr talk contribs created page Project:Data Model/Recursive structure explained (Created page with "= Recursive Structures Explained = This page explains the meaning of the term '''recursive''' as used in the data model documentation. It is written for non-technical readers. No database knowledge is required. == Why this page exists == In several places the entity definitions state that an entity is '''recursive'''. For example: * HeritageObjects are recursive * DigitalAssets are recursive * ResearchChapters are recursive * Places are recursive For readers un...")
- 17:34, 14 May 2026 Mngr talk contribs created page Wiki:Config/Adding new MediaWiki website (Created page with "= Infrastructure Overview and Procedure for Adding a New MediaWiki Instance = This document describes the current three‑VM infrastructure used for hosting Drupal, MediaWiki, and related services. It also explains how to add a new MediaWiki instance (newMW) to the existing environment in a clean, reproducible, and low‑risk manner. == 1. High-Level Architecture == The system is composed of three virtual machines running on Hyper‑V. Each VM has a clearly defined resp...")
- 17:32, 14 May 2026 Mngr talk contribs created page Guides:Workflow/HeritageObject-Procedure (Created page with "= Procedure – Creating a HeritageObject (HO) = This page explains how to create a HeritageObject. A HeritageObject is the central historical or conceptual entity under study. Examples: * building * document * person-related artifact * equipment * archive register * architectural element HeritageObjects anchor all research meaning. == When to create a HeritageObject == Create a HeritageObject whenever: * something is studied or described in the research * mult...")
- 17:30, 14 May 2026 Mngr talk contribs created page Drupal:Content Types/Chapter/Final Chapter Architecture (Created page with "= Final Chapter Architecture = This page documents the final, endorsed structure for CHAPTER, PLACE, and ORGANISATION within the research platform. It reflects the architectural simplification reached after analysis and Excel validation. == 1. CHAPTER Structure (Flat, Non‑Recursive) == The CHAPTER entity is now: * Flat (no recursion) * Non‑hierarchical * Narrative-only * Max. 3 characters * Two families: ** Txx — time‑based narrative chapters ** Xxx — the...")
- 17:26, 14 May 2026 Mngr talk contribs created page Maintenance:Drupal/Drush Commands (Created page with "== Drush: The "Pro" Command-Line Recovery Suite == ''Note: All commands must be run from the Project Root: <code>/var/www/drupal</code>.'' {| class="wikitable" ! Command !! Purpose !! Professional Use Case |- | <code>./vendor/bin/drush cr</code> || '''Cache Rebuild''' || The first step if the UI looks "wrong" or CSS/JS changes don't appear. |- | <code>./vendor/bin/drush uli</code> || '''User Login (Emergency)''' || Generates a one-time secure link to bypass lost passw...")
- 17:24, 14 May 2026 Mngr talk contribs created page Platform:Drupal/Drupal migration (Created page with "== Heritage Project: Drupal 11 Migration Blueprint (AlmaLinux 10.1) == === 1. Infrastructure Architecture === * '''Web Server:''' AlmaLinux 10.1 (Hyper-V VM) - Apache 2.4 / PHP 8.3 * '''Database Server:''' AlmaLinux 10.1 (Hyper-V VM) - MariaDB 10.11+ * '''Proxy:''' IIS ARR (Windows Server) - SSL Offloading & Reverse Proxy === 2. Installation Sequence (Web Server) === On the Web VM, execute the following to establish the "Secure Core": # '''Install Composer:''' #* <cod...")
- 17:23, 14 May 2026 Mngr talk contribs created page Platform:Drupal (Created page with "= Drupal =")
- 17:22, 14 May 2026 Mngr talk contribs created page Maintenance:Drupal/Drupal internals (Created page with "= Drupal Internals for Embedded-System Thinkers = This document provides a behavioral understanding of Drupal 11 by mapping its internal mechanisms to concepts from embedded systems and real-time software engineering. It is designed as a reference for system-level thinking, not as a click-through tutorial. == 1. Embedded Systems ↔ Drupal 11: Behavioral Comparison Table == The following table maps familiar embedded concepts to their Drupal equivalents, focusing on *b...")
- 17:20, 14 May 2026 Mngr talk contribs created page Drupal:Content Types/Place/Leaflet initial centering setting (Created page with "= Setting a Default Center and Zoom for the Leaflet Widget (Drupal 11) = == Overview == When using the Leaflet widget in ''Manage form display'' (e.g., for a PLACE content type), the map may open centered on latitude 0, longitude 0 (the Gulf of Guinea). This happens when no default coordinates are configured. Drupal 11 no longer provides global Leaflet map presets, so the correct place to set the initial map center and zoom is inside the widget settings of the geoloc...")
- 17:18, 14 May 2026 Mngr talk contribs created page Maintenance:Drupal/Standard: Field naming Convention (Created page with "== ICT Standard: Field Naming Conventions == To ensure the '''Heritage Tweaks''' module functions correctly and the database remains organized, all new fields must follow this dual-naming convention. === 1. The Prefix Rule (Namespace) === All field machine names must start with a two-character code representing the '''Content Type'''. * '''Pattern:''' <code>field_xx_fieldname</code> (where <code>xx</code> is the unique prefix). * '''Example:''' <code>field_sa_name</cod...")
- 17:17, 14 May 2026 Mngr talk contribs created page Maintenance:Drupal/Drupal Flow expained (Created page with "= The Drupal flow = If you want to go deeper with Drupal, you should understand how information flows between the system's layers. There are five main layers to consider: == Nodes == alt=Drupal Flow in Layers|thumb|Drupal Flow in Layers At the base of the system is the collection of nodes, the data pool. Before anything can be displayed on the site, it must be input as data. == Modules == The next layer up is where modules live. Module...")
- 17:13, 14 May 2026 Mngr talk contribs created page Maintenance:Drupal/Dead Custom Module Check (Created page with "= Dead Module Checklist (Safe Removal Procedure) = This checklist provides a systematic, successor‑friendly method to determine whether a custom Drupal module is still in use. A module may only be deleted after all checks are completed. == 1. Check for Entity Types == If the module defines any entity types, it is almost certainly still in use. Look inside the module folder: * <pre>src/Entity</pre> * <pre>config/install</pre> If you find: * content entities *...")
- 17:12, 14 May 2026 Mngr talk contribs created page Maintenance:Drupal/Composer Commands (Created page with "{| class="wikitable sortable" ! Command ! Description |- | <code>composer --version</code> | Show the installed Composer version. |- | <code>composer install</code> | Install all dependencies listed in ''composer.json'' (used after cloning a project). |- | <code>composer update</code> | Update all dependencies to the latest allowed versions. |- | <code>composer update drupal/core --with-all-dependencies</code> | Update Drupal core and all related packages. |- | <cod...")
- 17:11, 14 May 2026 Mngr talk contribs created page Drupal:Content Types/Asset/Custom module design for automatic numbering (Created page with "= Automatic numbering of Asset records with custom desing module = == Environment preparation for custom modules == Custom modules live in <pre> /var/www/drupal/web/modules/custom$ </pre> Our custom module is called costasano_asset and as such a directory should be created for this module. Minimum 2 files are necessary for a custom module. <pre> /var/www/drupal/web/modules/custom/costasano_asset costasano_asset.info.yml costasano_asset.module </pre> A first file cos...")
- 17:08, 14 May 2026 Mngr talk contribs created page Drupal:Content Types/Asset/Asset Identifier And Numbering Specification (Draft v1) (Created page with "= Costasano Heritage Project — Asset Identifier & Numbering Specification (Draft v1) = == Purpose == This document formalizes the agreed rules for the automatic identifier generation of '''Asset''' entities in the Costasano Heritage Project Drupal system. The objective is to guarantee: * long-term stability of identifiers * simplicity for users * robustness across exports, URLs, and publications * compatibility with future systems Identifiers must remain valid for...")
- 17:06, 14 May 2026 Mngr talk contribs created page Drupal:C-Modules/Tweaks/Technical Note - Custom tweaks (Created page with "= Drupal 11.3 Technical Note: Heritage Project Custom Tweaks = == Overview == This document outlines the custom module created for the Heritage Project to handle specific user experience (UX) and data integrity requirements that are not met by core Drupal 11.3 configuration. == Features == # '''Status Message Link Removal:''' Replaces the linked node title in "Saved" messages with plain text for Historians, preventing them from leaving their View. # '''Date Format Vali...")
- 17:05, 14 May 2026 Mngr talk contribs moved page Drupal:C-Modules/Tweaks/Day problem dd/mm/yyyy to Drupal:C-Modules/Tweaks/Day problem dd mm yyyy without leaving a redirect
- 17:03, 14 May 2026 Mngr talk contribs created page Drupal:Content Types/General/Creating new entities: content types (Created page with "= Step 1: Creating and configuring the content type = == Initial creation of the content type == # structure/content types # create a new content type # give it a name - example chapter (NO s in the end) # fill n the description # REPLACE the proposed Title field label from Title to Code # Fill in the Explanation or submission guidelines # SAVE == Step 2: Create the fields for this content type == # create a new field and chose the field type # give it a label like "D...")
- 17:02, 14 May 2026 Mngr talk contribs created page Drupal:Content Types/General (Created page with "= General considerations =")
- 17:01, 14 May 2026 Mngr talk contribs created page Drupal:Views/Places/Custom text with URL to openstreetmap (Created page with "= How to use a text field in a view to link to maps (OpenStreetMap + OpenTopoMap) = In the view, make a '''Global: Custom text''' field. This field should be located behind (down) other fields you want to use the fields content of. Look carefully to the '''replacement patterns'''; they tell you what machine fields are available as parameters. Here is an example of the view PLACES: <pre> {{ edit_node }} == Link to edit Content {{ title }} == {{ field_pl_name }} == {...")
- 16:59, 14 May 2026 Mngr talk contribs created page Drupal:Content Types/Asset/Object - Asset many to many implementation (Created page with "= Object–Asset Linking Workflow in Drupal (Conceptual and Editorial Model) = This document explains how the many‑to‑many relationship between '''Objects''' and '''Assets''' is implemented and used in Drupal. It focuses on the '''editorial workflow''' for historians, ensuring that linking multiple Assets to an Object is intuitive, efficient, and conceptually clear. The goal is to provide a successor‑friendly description of: * the conceptual model * the Drupa...")
- 16:57, 14 May 2026 Mngr talk contribs created page Maintenance:Drupal/HowToDo minor updates (Created page with "= How to do a minor Drupal 11 update? = To perform a minor update in Drupal 11 (e.g., from version 11.1 to 11.2), you should use Composer, which is the industry == Preparation == Backup: Always create a full backup of your database and files before proceeding. Maintenance Mode: Enable maintenance mode to prevent users from making changes during the update. <pre> Drush: drush state:set system.maintenance_mode 1 </pre> UI: Navigate to Configuration > Development > Maint...")
- 16:52, 14 May 2026 Mngr talk contribs created page Project:Detailed Data Model/Data Model entity definitions v 5.0 - new (Created page with "= Data Model – Entity Definitions (Version 5.0) = This document defines the '''conceptual meaning''' of all entities in the Costasano Heritage Database. It is the authoritative reference for: * conceptual ER modeling * DBML schema design * Page Schemas and forms * editorial workflows * successor understanding These definitions describe meaning and responsibility, not implementation details. If an entity definition is unclear or disputed, implementation must be pos...")
- 16:49, 14 May 2026 Mngr talk contribs created page Project:Detailed Data Model/Data Conceptual Model v 5.0 - new (Created page with "= Costasano Heritage Database – Conceptual Model (Version 5.0) = This document defines the '''conceptual architecture''' of the Costasano Heritage Database. It is the authoritative reference for: * meaning * responsibilities * boundaries * relationships It must be consulted '''before''' any logical or technical implementation. This version supersedes the v4 conceptual overview and incorporates all conceptual developments reflected in the DBML v5 schema. == Purp...")
- 16:47, 14 May 2026 Mngr talk contribs created page Project:Detailed Data Model/Data Model entity definitions v-5 complete (Created page with "= Data Model – Entity Definitions (Version 5.0) = This document defines the '''conceptual meaning''' of all entities in the Costasano Heritage Database. It is the authoritative reference for: * conceptual ER modeling * DBML schema design * Page Schemas and forms * editorial workflows * successor understanding These definitions describe meaning and responsibility, not implementation details. If an entity definition is unclear or disputed, implementation must be pos...")
- 16:45, 14 May 2026 Mngr talk contribs created page Drupal:Taxonomy/Taxonomy - Vocabulary - Terms use (Created page with "= Using Taxonomy for Keywords and Search in Drupal (Assets, Views, Entity Browser) = == Purpose == This document describes how to use **taxonomy (vocabularies and terms)** in Drupal to: * assign multiple keywords to entities (Assets, Persons, Objects, etc.) * reuse keywords consistently * enable effective searching via **Combined fields filters** in Views and Entity Browser modals * scale to large datasets (1000+ entities) No custom code is required. --- == Concepts...")
- 16:44, 14 May 2026 Mngr talk contribs created page Drupal:Taxonomy (Created page with "= Taxonomy use =")