Une fenêtre de terminal stylisée affiche la commande « ./WP-CLI » en grand texte blanc. À côté, une flèche bleue pointant vers le bas pointe vers une barre horizontale verte, suggérant un téléchargement ou une installation via SSH. L'arrière-plan est gris foncé.

Installer WP-CLI sans accès root ni sudo via SSH sur n’importe quel hébergeur

8 July 202519 mai 2025 by Matt Biscay · Lecture: 3 minutes

Chaque fois qu’un hébergeur n’a pas WP-CLI installé par défaut, je suis déçu : ce puissant outil de gestion WordPress n’est pas disponible ! Heureusement, il est facile d’installer WP-CLI sans accès root ni sudo via SSH.

En suivant cette méthode, vous pourrez utiliser WP-CLI exactement comme s’il avait été installé de manière traditionnelle avec les droits root et placé dans /usr/bin ou /usr/local/bin.

Cet article vous montrera comment installer WP-CLI sur presque toutes les distributions Linux comme CentOS, Debian, Ubuntu, etc., tant que le paquet php-cli est disponible. Tout ce dont vous avez besoin, c’est d’un accès SSH et d’un moyen d’entrer ces commandes, comme le terminal Mac ou PuTTY sous Windows.

Installer WP-CLI sans accès root ni sudo

Nous avons besoin d’un emplacement pour stocker le fichier phar de WP-CLI, créons donc un dossier et entrons dedans :

mkdir -p /tmp/wp-cli
cd /tmp/wp-cli

Téléchargez la dernière version de WP-CLI phar et rendez-la exécutable :

wget -q https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar -O wp
chmod 755 wpCode language: JavaScript (javascript)

Ou bien, téléchargez directement le fichier phar WP-CLI dans votre dossier temporaire :

mkdir -p /tmp/wp-cli
wget -q https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar -O /tmp/wp-cli/wp
chmod 755 /tmp/wpCode language: JavaScript (javascript)

Ou dans n’importe quel dossier de votre choix :

cd /votre_dossier<br />wget -q https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar -O /votre_dossier/wp
chmod 755 /votre_dossier/wpCode language: HTML, XML (xml)

Pour utiliser le WP-CLI que nous venons de télécharger, il faudra ajouter ./ devant wp. Il vous faudra également le chemin d’installation de WordPress.

Nettoyer complètement la base de données WordPress après la désinstallation d’Elementor

15 mai 2025 by Matt Biscay · Lecture: 4 minutes

Lorsque vous désinstallez des plugins WordPress, de nombreux éléments peuvent rester dans la base de données. Cela rend la base de données inutilement volumineuse et peut même ralentir les requêtes.

Il est toujours recommandé de nettoyer votre base de données WordPress après avoir supprimé des plugins. J’ai récemment migré un site d’Elementor vers GenerateBlocks pour améliorer les performances, donc naturellement j’ai dû nettoyer la base de données.

Ce tutoriel concerne le nettoyage post-désinstallation d’Elementor pour supprimer les lignes restantes des tables options, postmeta, usermeta et posts avec WP-CLI.

Dans ce tutoriel, nous allons couvrir les points suivants :

Supprimer les plugins et fichiers Elementor
Supprimer les types de publication Elementor
Supprimer la taxonomie Elementor
Supprimer les meta_keys Elementor des tables usermeta et postmeta
Supprimer les options orphelines Elementor de wp_options

CloudFest Hackathon 2025 main room @ Kronasar Hotel, Europa Park, Germany

CloudFest Hackathon 2025 : the recap

23 avril 2025 by Matt Biscay · Lecture: 8 minutes

I attended CloudFest Hackathon 2025, organised by Carole Olinger, Alain Schlesser and Lucas Radke. It was awesome to meet old friends and make new acquaintances in Europa Park, Germany. Here’s the recap of this 8th edition!

10 projects in competition for #CFHack25

This year, 10 projects were in competition – check out for yourself the diversity of the topics covered:

Peer-to-peer RAG Framework with Wesley Stessens and Franco Lombardo
CMS Freedom with Patricia Brun Torre and Dennis Snell
CMS Health Checks with Oliver Bartsch
WP-CLI as an MCP Host with Pascal Birchler
Federated Community Events with Andreas Heigl and Matthias Pfefferle
Securing the Supply Chain for OSS with Néstor Angulo de Ugarte and John Blackbourn
AIccessiblity Content Updater with Nemanja Cimbaljevic and Anthony Ledesma
CMS Cloud Manager with Markus Kostrzewski and Javier Casares
Accessible Infographics with Anne-Mieke Bovelett and Nina Jameson
WordPress Staging Environment Manager with Tadas Pukas and Paulius Lescinskas

That’s quite broad, isn’t it? I love it when it’s so hard to choose from the list! A few projects particularly piqued my interest: CMS Cloud Manager because it was sysadmin (it would be nice to implement on FastNyx), Accessible Infographics because I would love to work with Anne-Mieke, Peer-to-peer RAG Framework because my friend Wesley is leading the project, and WP-CLI as a MCP Host since it touches WP-CLI with AI.

I finally joined the WP-CLI as a MCP Host table.

What is the Model Context Protocol (MCP)?

The Model Context Protocol (MCP) is a standardised interface designed to enable AI models—like large language models (LLMs) or AI assistants—to interact seamlessly with external systems and applications. Rather than requiring developers or AI systems to manually parse complex documentation or adapt to a wide variety of APIs, MCP provides a unified way for AI to discover available capabilities, call specific functions or tools, and receive structured responses from the target system.

In practical terms, MCP acts as a bridge between AI and software platforms. It allows AI assistants to:

Discover what actions or data are available from a system (such as creating posts, retrieving content, or managing users in WordPress).
Call these capabilities as if they were simple functions, without needing to know the technical details of the underlying APIs.
Receive structured, predictable responses, making integration and automation much easier.

This approach is particularly powerful for developers and organisations looking to integrate AI into their workflows, as it removes much of the friction typically involved in connecting AI models to real-world applications.

MCP in the WordPress Ecosystem

Within the context of WordPress, MCP enables AI-powered interactions with WordPress sites through standardised interfaces. A WordPress MCP Server exposes the site’s REST API endpoints and other capabilities in a way that AI models can easily understand and use. For example, an AI assistant can:

Retrieve the latest posts or comments.
Create or edit content.
Manage users or plugins.
Chain multiple actions together (e.g., summarise GitHub issues and publish them as a blog post).

The WordPress MCP Server handles authentication, endpoint discovery, and request formatting, making it possible for AI models to interact with WordPress securely and efficiently.

Why MCP Matters for Developers

Traditionally, integrating AI with WordPress—especially in local development environments—has been challenging. While REST APIs allow for some AI interactions on live sites, local development workflows lacked seamless AI integration. MCP changes this by providing a protocol that works both locally and remotely, enabling developers to leverage AI for content creation, site management, and automation directly from their command line or development environment, without needing a live site or custom API integrations.

The Vision: a Universal “USB-C Port” for AI

A helpful analogy is to think of MCP as the “USB-C port for AI applications”. Just as USB-C provides a universal connector for hardware devices, MCP aims to standardise how AI models connect and interact with software systems. This universal approach unlocks new possibilities for automation, content generation, and intelligent site management—making advanced AI capabilities accessible to WordPress developers, content creators, and DevOps teams alike.

← Précédent Suivant →