SPIP

Configuring a feature of your site or a plugin

jack — 2026-02-28T11:11:15Z

Configuring a feature or plugin involves defining values for their various parameters. To do this, you need to define a form and be able to access the parameter values anywhere in your templates.

CVT forms also make it easy to create a configuration page for a feature on your site or for configuring a plugin.

A configuration mode is built into SPIP.

Configuration Form

Suppose you have a ‘thing' feature to configure.

Create a CVT form whose name begins with ‘configure_', with just the HTML file and without the PHP (and therefore without defining the load, verify and process functions) [1].
create a page configure_thing.html in private/squelettes/contenu/, inside your plugin or your skeleton directory. Inside, call the form with simply #FORMULAIRE_CONFIGURER_THING

That's all!

Configuring a plugin

When a plugin has a configuration page, a ‘Configure' option leading to this page automatically appears next to this plugin in the plugin administration page.

This page is defined by the template prive/squelettes/contenu/configurer_prefixeplugin.html and most often uses a configuration form.

Example: for the “mediabox” plugin, the file prive/squelettes/contenu/configurer_mediabox.html contains:

[(#AUTORISER{configurer,mediabox}|oui) <:mediabox:titre_page_configurer_box:>
  #FORMULAIRE_CONFIGURER_MEDIABOX 
 ]

If you want an entry to also appear in the menus in the private area to give you direct access to this configuration page, add a

entry in the paquet.xml file.

Example :

To initialise the value of a configuration (e.g. the in_the_spotlight parameter) when creating or updating the plugin, add the following to the myplugin_upgrade() pipeline:

during creation:

$maj['create'] = array( array('ecrire_config','myplugin/in_the_spotlight', '3'), );

during an update:

$maj['0.1'] = array( array('ecrire_config','myplugin/in_the_spotlight', '3'), );

To clear the value when uninstalling the plugin, add the following to the pipeline: myplugin_vider_tables():

effacer_config("myplugin/in_the_spotlight");

Access configured values

In a template, the value of a configuration can be accessed using the #CONFIG tag (for example #CONFIG{myplugin/in_the_spotlight})

In PHP the values can be accessed in read mode using the lire_config function with lire_config(“myplugin/in_the_spotlight”).

When writing, use the ecrire_config function:
ecrire_config('myplugin/in_the_spotlight', 3)

Autorisations

Not all users have access to the configuration page. By default, only administrators have this option, but you can redefine access rights to your configuration form. To do this, use the php authorise API, as well as the #AUTHORISE tag and the otherwise_deny_access filter for your form template.

Example : [(#AUTORISER{configurer,mediabox}|sinon_interdire_acces)]

Customise treatments

Sometimes, other specific treatments are required when configuration values are changed. In this case, the usual traiter() function from the CVT API must be added, and the common function that handles configuration processing must be called:

function formulaires_configurer_myplugin_traiter_dist() { include_spip('inc/cvt_configurer'); $retours = array(); // The new configuration is saved. $trace = cvtconf_formulaires_configurer_enregistre('configurer_myplugin', array()); // Customised treatments // … $retours['message_ok'] = _T('config_info_enregistree') . $trace; $retours['editable'] = true; return $retours; }

Use another table to store the configured values

By default, the configured values are stored in the spip_meta table, and the entire table is loaded into memory with each hit. However, it is possible to use another table to store the configured values.

For example, to use the meta_myplugin table, add the following line to the configuration form:

Then, to access the values stored in this table, specify the table name prefixed with a / at the beginning of the lire_config argument:

ecrire_config('/meta_myplugin/description', 'blah'); lire_config('/meta_myplugin/argument');

In addition to _meta_table, the name of the table where the configured values are stored, there are three other useful variables to change where or how the configuration is saved:

_meta_casier: name of the ‘casier' in which to serialise (by default, this is the xx from formulaire_configurer_xx)
_meta_prefixe: prefix the meta (alternative to the casier) in the meta table (no default prefix)
_meta_stockage: use an external storage method. None are provided by the core.

[1] To further simplify the creation of this form, you can use the Entries plugin

#VIRTUEL

jack — 2026-02-28T09:34:16Z

This tag returns the value of the redirection field entered for an article (this entry is made in the navigation column of the article editing page).
This option must have been enabled in the ‘Site content' configuration page.

- Tags / BOUCLE(ARTICLES), #VIRTUEL

{virtuel}

jack — 2026-02-24T09:34:00Z

The {virtuel} criterion in an ARTICLES loop allows only virtual articles (which redirect to another URL) to be retained.

Conversely, with {virtuel=''} or {!virtuel}, the loop will only return items that have not been redirected.

See: #VIRTUEL

|wrap

jack — 2026-02-23T13:41:06Z

The |wrap{} filter wraps the tag to which it is applied with the HTML tag specified as a parameter.

Simple examples

[(#BALISE|wrap{})]

will display as HTML source:
blah blah

[(#TITRE|wrap{#TOTAL_BOUCLE|=={1}|?{,
}})]

will display as HTML source if the loop returns only one result:

The Title

but will display:
The Title Another Title
if the loop returns several results.

HTML tag sequences

It is also possible to pass a series of tags as arguments. The final tags will be calculated to produce a correct nesting. The tags specified as filter arguments may include attributes.

Example :

[(#BALISE|wrap{
})]

will display as HTML source:

blah blah

#PRODUIRE

Ricardo Porto — 2025-09-09T16:37:12Z

A tag #PRODUIRE (produzir) gera um ficheiro estático a partir de um template dinâmico de CSS (.css.html) ou de Javascript (.js.html). A partir do SPIP 4, os ficheiros que geram SVG (.svg.html), XML (.xml.html) e JSON (.json.html) também são levados em conta.

#PRODUIRE retorna o nome desse ficheiro estático, o que permite ao Apache servi-lo diretamente, sem passar por spip.php a cada hit.

A sintaxe dos argumentos da tag #PRODUIRE é a mesma de #INCLURE.

O formato do ficheiro é indicado pela pré-extensão do ficheiro: .css.html, .js.html, .xml.html, .json.html, .svg.html. Senão, é HTML.

Pode-se forçar o formato do ficheiro passando como argumento adicional format=css (ou format=js...)..

Nota: o resultado de #PRODUIRE inclui o timestamp do ficheiro template recebido como argumento.

Online Help

jack — 2025-09-01T10:47:18Z

SPIP incorporates an online help system which you can access from the private area of your site.

Table of contents
Help for authors
Can be enhanced by plug-ins
History
Help for authors

SPIP includes online help for authors.
This help documents all the typographical shortcuts that can be used by editors.

This help is available via a plugin-dist ‘help'. The available languages can be seen by their prefix in the directory aide/aide. To add new languages to this file, you must contribute via the SPIP forge.

See Contributing to SPIP development

Can be enhanced by plug-ins

Plug-ins can also enhance this help, as is the case with the ‘Pense-bête' plug-in, for example, using the aide_index pipeline.

History

Previous versions of SPIP up to SPIP 3.2 included online help written on the spip.net website. These help sections are set to disappear from this site as the versions that include them have not been maintained for a long time.

Writing a commit message

jack — 2025-08-09T11:31:53Z

Commit messages in SPIP follow the specifications of Conventional Commits. This facilitates a posteriori review of the code history, as well as PR analysis.

The body of the message must be clear and explanatory: describe the problem addressed and the changes or corrections made.

Table of contents
Structure of a conventional commit
Example of a conventional commit
List of commit types
Further reading
Structure of a conventional commit
First line starting with the type of commit, followed by a colon (:), followed by a message summarising the commit.
The type can optionally be supplemented by a scope in brackets to specify the component or feature that has been modified.
Optionally, one or more additional paragraphs describing the commit in more detail can be added after a blank line. Markdown syntax can be used.
Finally, a last line (separated from the previous ones by a blank line) must contain a reference to the ticket to which the commit is linked. The reference takes the following form: Refs: #XXX, or Fix: #XXX to automatically close the ticket when merging into the destination branch.
Example of a conventional commit

Example of a complete commit log:

fix: repair the link to the GPL licence in the footer of private pages by replacing it with a simple link to the official gnu.org website Fix: #5328
List of commit types

Convention used in SPIP.

Type Meaning

build Modifies a program compilation script or modifies external dependencies. Also indicates a version upgrade.

change Modifies the implementation of a feature — may modify function signatures (≠ refactor)

chore Background work that does not alter the code (release a version, regenerate compiled code)

ci Related to continuous integration

deprecate Deprecate (without removing) a feature

docs Related to documentation (docs, readme, changelog)

feat Adds a feature

fix Fixes a problem

i18n Related to translations and language strings

perf Improves algorithm or programme performance

refactor Rewrites code without changing its API

remove Removes code or functionality (previously deprecated)

revert Reverses a previous change (commit)

security Related to security

style Related to code writing rules (Coding Standard)

test Related to software testing

Further reading

See the websitewww.conventionnalecommits.

Installation mit spip_loader

klaus++ — 2025-06-24T10:05:42Z

„spip_loader” ist ein Skript, mit dem Sie Ihre SPIP-Website automatisch installieren oder aktualisieren können, ohne alle Dateien per FTP übertragen zu müssen.

Table of contents
Verwenden Sie spip_loader, um SPIP automatisch zu installieren
Verwenden Sie spip_loader, um ein Update durchzuführen
Die zur Aktualisierung berechtigten Autoren anpassen
Häufig auftretende Fehler
Was tun, wenn es nicht funktioniert?
Technische Hinweise
Aktuelle Version von spip_loader: 6.2.1

Download

Verwenden Sie spip_loader, um SPIP automatisch zu installieren

spip_loader erfordert mindestens PHP 5.6

Überprüfen Sie die PHP-Kompatibilität Ihres Hosts anhand der folgenden Tabelle: Versions maintenues
Laden Sie das Skript herunter
Speichern Sie diese Datei über SFTP in dem Verzeichnis, in dem Sie SPIP installieren möchten (in der Regel im Stammverzeichnis Ihres Servers oder im Ordner, der die Website enthält, wenn es sich um ein Update handelt).
Achtung: Da das Skript komprimiert ist, müssen Sie bei Verwendung des FTP-Protokolls Ihre Client-Software für diese Übertragung auf Binärmodus einstellen [1].
Rufen Sie das Skript über Ihren Browser auf https://www.adressedevotresite.net/spip_loader.php
Das Skript überprüft, ob Ihr Hosting kompatibel ist. Ist dies der Fall, listet es alle Versionen auf, die Sie installieren können, und schlägt Ihnen standardmäßig die letzte stabile Version vor.
Wählen Sie Ihre Version und starten Sie die automatische Installation.

Skript online lassen
Nach der Installation von SPIP können Sie das Skript spip_loader.php bedenkenlos auf dem Server belassen. Nur autorisierte und authentifizierte Administratoren können darauf zugreifen. Der Vorteil besteht darin, dass Sie Ihr SPIP im Falle einer Warnmeldung sehr einfach aktualisieren können.

Detaillierte Erläuterungen
Der spip_loader erkennt neue Versionen und schlägt vor, diese zu aktualisieren, ohne dass eine FTP-Übertragung erforderlich ist.

Über eine Dropdown-Liste kann die zu installierende Version ausgewählt werden
Wenn kein SPIP installiert ist:
Die Dropdown-Liste wählt die letzte stabile Version aus
Wenn bereits ein SPIP installiert ist:
Die Dropdown-Liste ist standardmäßig auf die letzte Version desselben Zweigs wie die Website eingestellt (sofern diese noch referenziert ist).
Dateien, die nach dem Update veraltet sind (d. h. die zwischen der aktuellen Version der Website und der installierten Version entfernt wurden), werden in einem Verzeichnis fichiers_obsoletes_{date} archiviert, wobei date durch das aktuelle Datum und die aktuelle Uhrzeit ersetzt wird. Dies geschieht nur in den Verzeichnissen: ecrire, prive, squelettes-dist und plugins-dist (sowie im alten Verzeichnis extensions).
In Verbindung mit dem vorherigen Punkt werden Plugins, die im Verzeichnis plugins-dist/ hinzugefügt wurden (und somit nicht zum von SPIP bereitgestellten Zip-Archiv gehören), ebenfalls in dieses Verzeichnis für veraltete Dateien verschoben, es sei denn, sie enthalten eine Datei .spip_loader_keep.
Es ist möglich, eine Konfigurationsdatei zu verwenden, um die Definitionen zu verwalten und sie von einem Update zum nächsten beizubehalten, mit spip_loader_config.php

Ab der Version v5.2.0 ist spip_loader.php ein kompiliertes Skript im komprimierten Binärformat phar, das auch die Übersetzungen enthält. Wenn Sie Definitions verwenden müssen, müssen Sie daher eine Konfigurationsdatei spip_loader_config.php

Ab der Version 6.0.0 sind die Anpassungskonstanten veraltet. Die Konfigurationsdatei spip_loader_config.php muss ein Array zurückgeben, wie im folgenden Beispiel gezeigt.

Verwenden Sie spip_loader, um ein Update durchzuführen

Um ein SPIP zu aktualisieren, gehen Sie wie folgt vor:

Bevor Sie das Skript aufrufen, müssen Sie sich zunächst im privaten Bereich von SPIP anmelden.
Das Skript auf Ihrem Server ablegen, falls es noch nicht vorhanden ist
Das Skript über Ihren Browser aufrufen https://www.monsite.tld/spip_loader.php
Die zu installierende Version auswählen
Den automatischen Installationsvorgang starten

Die zur Aktualisierung berechtigten Autoren anpassen

Standardmäßig kann nur der Autor Nr. 1 dieses Update durchführen.

Wenn Sie weitere Autoren hinzufügen möchten, müssen Sie eine Konfigurationsdatei spip_loader_config.php (im Stammverzeichnis) erstellen, die automatisch eingebunden wird. So bleiben Ihre Einstellungen bei einem Update von spip_loader erhalten.

Beispiel für die Datei spip_loader_config.php:

[5, 6, 8], ];

Häufig auftretende Fehler

Aufgetretener Fehler Lösung

SHA512-Signatur konnte nicht überprüft werden: Signatur defekt.. Sie haben die Datei spip_loader.php nicht korrekt auf Ihren Server übertragen: Sie müssen die Datei im Binärmodus von Ihrer FTP-Software übertragen. Siehe #spip_loader-verwenden-um-SPIP-auto...

403 - File Access Denied Häufig befindet sich am Ende von monsite/spip_loader.php ein Schrägstrich /, der von früheren Verwendungen stammt. Oft reicht es aus, diesen Schrägstrich zu löschen, um den Fehler zu beheben und spip_loader.php seine Arbeit tun zu lassen.

In hartnäckigen Fällen muss der Verlauf der Seite im Browser gelöscht werden

Fehler 403 Sie sind nicht berechtigt, diese Seite anzuzeigen (Installation und Aktion nicht möglich) Überprüfen Sie, ob mod_rewrite aktiviert ist

GuzzleHttp erfordert cURL, die INI-Einstellung allow_url_fopen oder einen benutzerdefinierten HTTP-Handler. Ihr Server erlaubt kein Laden externer Dateien. Sie müssen Ihre php.ini mit dem Befehl allow_url_fopen = On ändern

Deprecated: Usage of ‚_SPIP_LOADER_UPDATE_AUTEURS‘ Ändern Sie die Datei spip_loader_config.php im Stammverzeichnis Ihrer Website wie angegeben.

Was tun, wenn es nicht funktioniert?

Spip_loader kann beim Laden von Dateien fehlschlagen. In der Regel handelt es sich dabei um Probleme mit den Rechten auf dem Server oder mit der PHP-Konfiguration. In diesem Fall müssen Sie Ihr SPIP installieren

entweder durch manuelles Übertragen der Dateien per FTP
oder durch Verwendung von GIT (für erfahrene Benutzer)
Technische Hinweise

Quellen und Entwicklungsbereich von spip_loader
https://git.spip.net/spip-contrib-outils/spip_loader

[1] Siehe File_Transfer_Protocol

SPIP 4.4

jack — 2025-02-18T09:18:46Z

This LTS branch will benefit from extended support until July 2027.

Table of contents
Compatible with PHP 7.4 to 8.4
Changes introduced by SPIP 4.4
Security
Added
Changes
Corrections
Deprecating
Withdrawals
Supported plug-ins
Compatible with PHP 7.4 to 8.4

SPIP 4.4 requires PHP 7.4 or higher, and runs up to PHP 8.4.
It requires the following PHP extensions: sodium, Zlib, Zip and Phar.

Changes introduced by SPIP 4.4

The most striking changes are the fact that SPIP no longer sends passwords in clear text in registration and password reminder emails.

On the technical side, it should be noted that the write, prive and template-dist folders, as well as the security screen, are installed using Composer. This changes nothing for people who use spip_loader. Also worth noting is the introduction of #LAYOUT_PRIVE, #TRAD and #URL_DOCUMENT_FICHIER tags.

There has also been a series of optimisations for image filters.

The #LAYOUT_PRIVE tag replaces #LARGEUR_ECRAN and enables new layouts to be used for pages in the back office:

#LAYOUT_PRIVE{fluide}, the central content adapts according to the presence or absence of content in #extra and #navigation.

#LAYOUT_PRIVE{pleine-largeur}

#LAYOUT_PRIVE{complements-gauche}

#LAYOUT_PRIVE{complements-droite}

#LAYOUT_PRIVE{complements-bas}

#LAYOUT_PRIVE{complements-bas-inverse}

The #TRAD tag avoids writing things like #VAL{module:cle}|_T, for example #TRAD{module:cle, #ARRAY{param, val, ..}, #ARRAY{option, val..}}.

Directories

- The vendor/ directory has been completed, with the arrival of the first spip-league libraries, which will provide an initial gateway to elements of the future SPIP 5.0.
- There is now also a config/spip directory.

This version also brings other improvements and bug fixes.

Security
Cleaning up certain author entries on the author edit form (avoids ending up in logs if verbose logs are activated)
Updating the list of bots & add antennapod (RSS reader) as a legal bot
Added
Not sending passwords in clear text, instead sending links to set your password
copie_locale() passes an action key to the post_edition pipeline
Additional language strings for item lists
#LAYOUT_PRIVE tag
Tag#TRAD{module:key, #ARRAY{param, val, ..}, #ARRAY{option, val..}}
#MIME_TYPE tag calculated
#URL_DOCUMENT_FICHIER tag always returns the file of a document, which allows #URL_DOCUMENT to be used to refer to a web page when desired. Document templates are updated to use this tag.
The add_link and remove_link actions can handle a qualifier
add_menus_args pipeline, in addition to the add_menus pipeline, which passes on the arguments to definir_barre_boutons().
Purging var_nullify variables from the context in traiter_appels_inclusions_ajax.
#PARAM tag to retrieve service container parameters
The |affdate filter accepts a timestamp as input
_image_extensions_logos() function and image_extensions_logos pipeline
cli command to purge cache images that are too old (cache-gd2 and cache-vignettes)
image_oriente_selon_exif() filter to automatically reorient an image according to its exif tag
Changes
The ecrire, prive, squelettes-dist folders are installed with Composer
The security screen is installed with Composer
Updating language strings from trad.spip.net
Use the compter_contributions_auteur pipeline in an author's info box
Ability to customise the singular and plural language strings in the title of all object lists
New layouts for back office (#LAYOUT_PRIVE) : defaut, fluide, pleine-largeur, complements-droite, complements-bas, complements-bas-inverse
Environment values explicitly emptied in ajax are passed through var_nullify to be completely purged.
Allowing ‘new' visitor accounts to be sorted by registration-reminding date
Add the publication time next to the date
Use CSS variables and logical properties in the back office to avoid compiling CSS files
The task control page uses the layout complement-gauche
Using image_extensions_logos() instead of $GLOBALS[‘formats_logos'].
Image filters such as image_recadre reorient the image according to the orientation exif
Corrections
In the back office, avoiding a horizontal scrollbar in certain operating system configurations.
Aligning the content of the en_lignes band with that of the banner.
Better display of object lists on small screens.
No bottom margin on last items in responses
Load autoloader in prive.php file
Avoiding a PHP warning if the logo file is not present
Following medias on inc_vignette_dist which expects a medias parameter
Reestablishing hiding documents viewed in the document block
No longer declaring z-index on columns that are already in flex
Fixing image rotation with convert
Being able to scroll after leaving full-screen mode using the key
Using a value for IMAGETYPE_SVG which does not risk a collision with a future image format addition (19 has been attributed to IMAGETYPE_AVIF in the meantime)
Fixed a fatal error when calling phraser_champs_interieurs().
Using fpassthru() to deliver files directly and avoid a memory limit rather than readfile() which requires the file to be loaded into memory.
Requesting remote files with STREAM_CRYPTO_METHOD_TLS_CLIENT.
Replacing obsolete tt tags with code.
Authors' emails are hidden by default
Sending the number of contributions to articles to the compter_contributions_auteur pipeline
Passing the url to the pass_reset_url language item
For the generic object institution form, test the publierdans authorisation using the parent declared by the parent API
In the generic object institution form, using the same test set for displaying the published status in load and for validation in verify.
Being able to remove the image from the login screen
Being able to change the main logo when there is a hover logo
Missing inclusion in some ajax contexts for bigup
Checking the existence of exif_read_data().
Avoiding warnings on image_oriente_selon_exif() in the absence of an image
Optimising filters image_aplatir(), image_renforcement(), image_flou(), image_sepia(), image_flip_vertical(), image_flip_horizontal(), image_nb(), image_gamma() & image_rotation()
Correction of crop parameter in image_rotation().
Form return message in div instead of p.
The audio/x-m4a mimetype is an alias for audio/mp4a-latm.
Calling to global $formats_logos replaced by _image_extensions_acceptees_en_entree().
Correcting logo duplication (Duplicator plug-in for example) if the tmp/upload folder does not exist
Displaying the document role selector (with the plug-in in question)
Displaying of previews in emb templates
Fixed mediaelements library plug-in path and removed Flash fallback
Added the afficher_config_objet pipeline which was missing on the keywords and keyword_groups pages.
De-double status test in an SQL query.
Support for SPIP 4.4 in the plug-in repository.
Invalidating the cache (even for bots) when a permanent URL is added.
Deprecating
PHP file inclusion via or .
Closing tag .
#LARGEUR_ECRAN tag for private templates to be replaced by #LAYOUT_PRIVE.
From SPIP 5 onwards, calling language strings in templates will be case-sensitive, and there will no longer be automatic conversion to lower case.
Internal function phraser_boucle_placeholder() to be replaced by phraser_placeholder_memoriser() or phraser_placeholder_reinjecter().
Internal function public_generer_boucle_placeholder() to be replaced by public_placeholder_generer().
Language files populating a $GLOBALS are deprecated; return an array directly
Obsolete constant _DIR_IMG_PACK.
Global $traiter_math, $tex_server, fonctions produire_image_math(), traiter_math() et replace_math(), mathjax plug-in should be used instead
Modifying the $formats_logos global is deprecated: using the image_extensions_logos pipeline
Calling the $formats_logos global is deprecated, using the _images_extensions_logos() function.
Depreciation of the _DIR_RESTREINT_ABS constant
|image_typo filter, and rtl_mb_ord(), rtl_reverse(), rtl_visuel(), printWordWrapped(), produire_image_typo() functions, install the plug-in Images typographiques
Withdrawals
verif_butineur(), editer_texte_recolle() functions and _texte_trop_long form environment (unused - used for IE)
Support for the _texte_trop_long form environment (used for IE)
An obsolete and untranslated language file.
Supported plug-ins

As with the previous version, most of the plug-ins are already compatible with SPIP 4.4, which will make upgrading easier.
See: How to upgrade SPIP

Customizing URLs

jack — 2024-08-12T10:29:26Z

Table of contents
Creating a URL
Modifying a URL
Managing URLs
SPIP enables URLs to be managed in a fine-tuned and scalable way. Their format is defined by the webmasters. For technical details, see article Using personalised URLs.

Creating a URL

Each SPIP object can be accessed via a given URL, which depends on the chosen format:

In some formats, the object identifier is used. For example, the "URLs Objects" format will generate a URL of the type article6858.html.
In some formats, other fields are used, such as the title of the object or its section. For example, an article with the title "I Love Pease Pudding" will generate the following "free URLs" I-Love-Pease-Pudding.

URLs are automatically generated when the object is published online.

Here are a few details:

The URLs generated are automatically corrected to comply with the HTML standard (no white spaces, accents, ....).
If a URL is already reserved on the site, SPIP generates an alternative URL (generally by adding the object identifier).

If the "URL editing" option is enabled on the site:

The object's public URL is displayed under the title:

Modifying a URL

Some URL formats allow you to edit URLs, in which case a "Modify" button appears when you hover over the URL.

The form displayed allows you to modify the URL.

The added URL becomes the object's main URL (indicated by a small padlock).
The object's old URLs are retained to avoid 404 errors. People who try to consult the old URLs will automatically be redirected to the main URL (the one with the padlock).

If a URL is no longer useful (and you no longer want a redirect to the main URL), you can delete it (red cross button).

Managing URLs

On sites with a lot of content, hundreds of URLs are generated. This can be problematic if you want to use a specific URL that is already in use.

Fortunately, SPIP offers a page for managing all the URLs on the site, accessible via the Publish → URLs Management menu:

The page displays a list of the site's URLs and associated objects
A search engine can be used to find a specific URL

To unlock a URL, simply delete it from the old object and then assign it to the object you want.

On the Publishing → URL Management page, a button can also be used to force the update of all the URLs on the site.

Type	Meaning
build	Modifies a program compilation script or modifies external dependencies. Also indicates a version upgrade.
change	Modifies the implementation of a feature — may modify function signatures (≠ refactor)
chore	Background work that does not alter the code (release a version, regenerate compiled code)
ci	Related to continuous integration
deprecate	Deprecate (without removing) a feature
docs	Related to documentation (docs, readme, changelog)
feat	Adds a feature
fix	Fixes a problem
i18n	Related to translations and language strings
perf	Improves algorithm or programme performance
refactor	Rewrites code without changing its API
remove	Removes code or functionality (previously deprecated)
revert	Reverses a previous change (commit)
security	Related to security
style	Related to code writing rules (Coding Standard)
test	Related to software testing

Aufgetretener Fehler	Lösung
SHA512-Signatur konnte nicht überprüft werden: Signatur defekt..	Sie haben die Datei spip_loader.php nicht korrekt auf Ihren Server übertragen: Sie müssen die Datei im Binärmodus von Ihrer FTP-Software übertragen. Siehe #spip_loader-verwenden-um-SPIP-auto...
403 - File Access Denied	Häufig befindet sich am Ende von `monsite/spip_loader.php` ein Schrägstrich `/`, der von früheren Verwendungen stammt. Oft reicht es aus, diesen Schrägstrich zu löschen, um den Fehler zu beheben und spip_loader.php seine Arbeit tun zu lassen.
403 - File Access Denied	In hartnäckigen Fällen muss der Verlauf der Seite im Browser gelöscht werden
Fehler 403 Sie sind nicht berechtigt, diese Seite anzuzeigen (Installation und Aktion nicht möglich)	Überprüfen Sie, ob mod_rewrite aktiviert ist
GuzzleHttp erfordert cURL, die INI-Einstellung allow_url_fopen oder einen benutzerdefinierten HTTP-Handler.	Ihr Server erlaubt kein Laden externer Dateien. Sie müssen Ihre `php.ini` mit dem Befehl `allow_url_fopen = On` ändern
Deprecated: Usage of ‚_SPIP_LOADER_UPDATE_AUTEURS‘	Ändern Sie die Datei `spip_loader_config.php` im Stammverzeichnis Ihrer Website wie angegeben.