Text
Browse by topic
Explore related documentation through its most useful keyword groups.
1438 items
Grouped by Architecture
A named transformation applied to a value inside a template expression.
Explore this clusterA typed event or request exchanged between decoupled Zotonic components through the notifier.
A namespaced interface for retrieving or changing data and invoking operations in Zotonic or browser-side components.
Explore this clusterAn OTP application or site component that adds Zotonic behavior templates data and configuration.
Explore this clusterA server-defined browser action or event binding connected through Zotonic wires.
Explore this clusterA server-side template_compiler document that renders data into HTML text email or another representation.
Explore this clusterA request handler that maps web requests to responses and coordinates authorization rendering or data transfer.
Explore this clusterA route declaration that matches a URL pattern and selects a controller with arguments.
Explore this clusterThe central Zotonic entity that represents content users media categories and other addressable objects.
Explore this clusterDocumentation not covered by the other keyword groups in this split.
Explore this clusterMonitor the user-facing service as well as its processes.
Keep original uploads accessible across deployments and restarts.
Locate the failure in permission, storage, or processing.
Restore into isolation and verify content, media, and access.
Adjust group upload limits and test with an ordinary account.
Run Zotonic under the installation’s service manager.
Prepare translations before making a language visible to visitors.
Find the relevant failure without exposing credentials or personal data.
Trace one message from request to recipient.
Prevent an acceptance workflow from emailing real users.
Use revisions or deleted-page recovery for an editorial mistake.
Set a relay at the correct scope and test a real site message.
Give the next operator enough context to continue safely.
Choose recovery coverage, retention, and an owner.
Align DNS, site selection, and certificate termination.
Recover code and data to a compatible state.
Test version-specific changes and establish a recovery point.
Check media-process isolation and decide whether to run conversions on a separate service.
Request a backup and verify its completion and scope.
Separate node, site, database, and application failures.
Change module activation and verify the affected workflow.
Choose the right configuration layer and verify the effective value.
Start Zotonic in the foreground without an interactive shell.
List configuration files selected for a site.
Run site tests using an isolated test schema.
Install the native tools, prepare PostgreSQL, and build a local checkout.
Check whether global configuration files can be read.
Show node and site state.
Start Zotonic in the foreground with an Erlang shell.
Enter the supplied OTP 28 development shell, prepare PostgreSQL, and build.
Wait until the node answers a ping.
Load changed BEAM files.
Create and check the database used by a native development installation.
Restart one site.
Run selected core test modules.
Remove login methods and permissions without deleting their authored content.
Check a rule change before it affects everyone.
Prepare a site database and schema.
Inspect dispatch rules or trace a URL.
Stop the Zotonic node.
Connect an Erlang shell to the running node.
Print recent lines from a configured log file.
Give an account the permissions required for its work.
Test the configured PostgreSQL connection.
Decrypt a local encrypted backup file.
Start a selected site on the node.
Reset a site rate limiter.
Find obsolete access and verify who can administer the site.
Show a site application directory.
Start Zotonic in the background.
Call an exported Erlang function on the node.
Inspect active Erlang processes.
Restart Zotonic and all sites within the current VM.
Compile, load, flush, and rescan the server.
Stop one site.
Generate gettext translation template files.
Use the right management surface and account.
Flush site caches.
Open the site URL in a browser.
Display a site configuration resolved from files.
Set a global runtime Zotonic value.
Choose roles that exercise the operation's permission boundary: anonymous visitor, limited editor, and administrator. Use separate browser sessions or an…
Choose checks for a change.
Use bin/zotonic setconfig only for a global setting that supports a runtime change. The command changes the running configuration and does not save the value…
Sign in to the local site's admin as an administrator. Open the module management page, find Development (mod_development), and activate it if necessary.
Check the requested path and compare its binary segments with the model callback patterns. Confirm that the callback returns the unused path in the required…
List, create, or restore backups.
First check which file is selected and whether the changed code compiled. Then repeat the request with the relevant cache disabled or flushed.
List selected global configuration files.
Open System → Development and enable live reload. The page also enables separate CSS and JavaScript files when needed.
Open a site in Chromium.
Distinguish global Zotonic configuration, Erlang runtime configuration, site configuration files, and module settings stored for a site. Similar setting names…
Open the Development function tracing tool as the admin user. Enter a module, optionally a function, and a small limit on the number of calls.
Request recompilation on the running node.
Render the changed page with realistic content. Include missing optional fields, a long title, several list items, and a second language when applicable.
Display configuration resolved from files.
Identify where the site's archive files, generated previews, backups, and security files are stored. These have different retention and recovery needs.
Open the Development page's Live dependency graph of templates tool. Start a trace for your session, then load the page or path you want to inspect.
Start with the symptom and use the smallest tool that explains it.
Open Cross-reference check of templates in the Development page and run the check. Read each reported reference with the active module set in mind.
Check whether the resource has an original file and whether its media information describes that file correctly. Then inspect the preview request in the…
Keep development and production settings distinct.
The Development page has an option to enable an API for recompiling and rebuilding Zotonic. The model implements actions for recompiling, flushing caches, and…
Open a site in Chrome.
Create a site application from a skeleton.
Open the Development page's dispatch tools. Inspect the list of active rules, then trace the path that produces an unexpected result.
Open Show an overview of all observers from the Development page. Find the notification and inspect the registered callbacks and their order.
Confirm the hostname, site, and path from the actual request. Use the dispatch trace to see the selected rule and any rewritten path.
Prepare an isolated copy of the previously released application and database. Add representative edited content, then apply the new code and schema changes.
Reproduce one action with the browser console and network panel open. Check for a JavaScript error before the request, a failed request, or a successful…
Open module management for the correct site. Check whether the module is disabled, waiting for a dependency, or failing during startup.
Change a dependency when you can identify the required fix or feature and the affected callers. Read its version constraints and inspect the resulting lockfile…
Measure one representative request and identify whether time is spent in the browser, network, or server. Compare an initial request with a repeated request to…
Run bin/zotonic status to distinguish an unavailable node from a stopped or failing site. Inspect the relevant startup log before repeatedly restarting it.
Enable module#mod_server_storage if the Development page says it is needed for database tracing. On the Development page, enable Trace all database queries for…
Keep domain logic in small functions that accept explicit inputs. Test expected results, boundary values, and meaningful error cases without starting a full…
Check that the module is an Erlang application in a discovered project directory. Confirm the application name, .app.src, main mod_... module, and successful…
Open Dependency graph of all available templates from the Development page. Use the graph to understand inheritance and include relationships before changing a…
Recompile one Erlang source file.
Use compilation for changed Erlang source, loading for changed BEAM files, and an index refresh when new templates or application files are not discovered.