[Wordpress] Utiliser PHP 7.3


Matériel: PC fixe
Version de YunoHost:
J’ai accès à mon serveur : complet
Êtes-vous dans un contexte particulier ou avez-vous effectué des modificiations particulières sur votre instance ? : non


Mon instance wordpress me dit que PHP n’est pas à jour et me demande de l’upgrade vers la version 7.3. Sauf que j’ai déjà installé PHP 7.3, comment forcer WP à utiliser cette version au lieu de la 7.0 ?


You don’t.

You’re running Debian stretch, which comes with php7.0.
Just be patient.

Excuse me, but i know that php 7.3 is present on my server, here’s the proof

root@stemy:~# systemctl status php7.3-fpm
● php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2020-04-22 08:39:44 CEST; 1 day 11h ago
     Docs: man:php-fpm7.3(8)
 Main PID: 11329 (php-fpm7.3)
   Status: "Processes active: 0, idle: 11, Requests: 4450, slow: 1, Traffic: 0req/sec"
    Tasks: 12 (limit: 4915)
   CGroup: /system.slice/php7.3-fpm.service
           ├─ 9579 php-fpm: pool nextcloud
           ├─ 9591 php-fpm: pool nextcloud
           ├─11329 php-fpm: master process (/etc/php/7.3/fpm/php-fpm.conf)
           ├─12432 php-fpm: pool framaforms__2
           ├─12433 php-fpm: pool framaforms__2
           ├─12437 php-fpm: pool pixelfed
           ├─12438 php-fpm: pool www
           ├─12439 php-fpm: pool www
           ├─13207 php-fpm: pool nextcloud
           ├─15401 php-fpm: pool pixelfed
           ├─18206 php-fpm: pool pixelfed
           └─26304 php-fpm: pool nextcloud

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

I’m not saying that you don’t have php7.3, I’m saying that Debian Stretch comes with php7.0
So, until Debian Buster, YunoHost 4, Wordpress will run with php7.0.

J’ai trouvé une solution de bidouillage, mais c’est pas garanti que ça ne cassera pas quelque chose, donc à prendre avec des pincettes.

il y a deux endroit à prendre en compte :


Et « à la louche », il faudrait que ce soit déplacé vers /etc/php/7.3/fpm/pool.d/ pour ce qui est de la config php de WP et modifié dans /etc/nginx/conf.d/domaine-avec-wp.d/wordpress.conf pour que ça corresponde aux nouveaux chemins ».

Et évidemment redémarrer les 3 services impactés :

    systemctl restart php7.0-fpm.service
    systemctl restart php7.3-fpm.service
    systemctl restart nginx

I have to admit, you can read article about it everywhere on internet that with php7.3, the sky is brighter, the grass greener and your life suddenly so better. Like you’re living in a dream !
I known also, from reliable source, that each time you migrate from php7.0 to php7.3, you save 3 kittens. An unicorn comes to save them.

So, of course I can’t blame you, your life will be so better after that !

But someone told me, not a source as reliable as what I’ve said before, for sure ! But someone told me that if you migrate manually from php7.0 to php7.3, next time you’re going to run any script for your wordpress, it’s going to be an epic fail.

But what to do !?
Believe someone who probably doesn’t know anything about it and be patient until php7.3 comes on its on ?
Or enhance your life, save kittens, see an unicorn and make the world a better place ?


Wordpress me conseille de son côté de mettre à jour vers cette version là pour des raisons de sécurité, donc j’ai plutôt tendance à penser que c’est une source sérieuse, rien à voir donc avec tous les sarcasmes que je lis dans ton message.

Et je trouvais bizarre que wordpress n’utilise pas php 7.3 bien qu’il soit installé.

Under the hood it’s much more complex than that. Just because PHP7.3 is installed doesn’t mean it’s automatically used by Wordpress, and that’s for so many reason it’s difficult to know where to start.

Granted that 7.0 is “outdated” because now there’s 7.3 available in the new Debian Stable (Buster). But that doesn’t mean it’s a critical security vulnerability. It just means that the software running it does not benefit from the improvements in 7.3. However, php7.0 and other packages in Debian Stretch (now oldstable in terms of Debian releases) is still “supported” and will get security updates if needed.

To give you a bit of context: Maniack’s answer is bitter and sarcastic because we as a team are slowly getting bored and tired of having to explain this every day to every people that are either:

  • asking for the super top-notch brand new stuff without realizing that something that already works but is old is better than something new that is broken, not supported or doesn’t exist yet
  • assuming that the fact that there’s a new version means that an older version suddenly becomes a huge security risk and you should absolutely immediately get the new version, otherwise a horde of chinese hacker will suddently be able to get into your server just by snapping their fingers.

To summarize :

  • yes, PHP7.0 is outdated
  • yes, there’s PHP 7.3
  • no, that does not mean having PHP7.0 instead of PHP7.3 is a big drama (if you nevetherless still think it’s a big drama, we can probably find somebody explaining you how their company still run some Debian Squeeze in year 2020)
  • no, having PHP 7.3 installed does not mean it’s automatically used by all PHP apps, it’s more complicated
  • no, you shouldn’t tweak config files manually if you do not no what you are doing. Things will explode.
  • yes, we know Wordpress and Nextcloud and many PHP apps make it sound like a huge drama. It’s not. It’s not broken. Don’t fix what ain’t broken.
  • yes, we know we should move everything to PHP 7.3 on Buster. Yes, it’s on the way. Be patient. Or come help us, and you will soon realize why we are getting tired of answering these. The more people ask for it, the later it will come because we’ll spend even more time doing support or hacky patches to make people happy instead of working on the actual real solution…
  • yes, it’s not your fault, you are just reading what Wordpress tells you. We understand. But if we also tell you that it’s not that important and that you shouldnt tweak stuff manually, you should also consider trusting us. If you don’t, then you’re wasting your time and will waste other people’s time if you later ask for help after not trusting their advice… Remember that it’s a free software project ran exclusively by volunteers. We are willing to make it work more than you are.

Ah une bonne nouvelle que j ai remarqué sur ma mise à jour du “jour”.
Installation php7.3
Merci la team Yunohost @Aleks @Maniack_Crudelis
Vous avancez comme des chefs…serieusement.

Pas trop le temps pro en ces temps particuliers, mais super ravis de revenir tester/dev mon #YUNO

1 Like

Yes, it looks like a good news and may make users happy. But that’s precisely the kind of stuff I was thinking about when talking about “hacky patches”. Under the hood, what it means it that we’re using black magic called sury to be able to install PHP 7.3 in Debian Stretch, which for us dev means more dependency management nightmare and more risk than everything explode, and more time spent fixing this black magic instead of going for the actual real solution …

Like they said :

  • you can have it Cheap
  • you can have Quality
  • you can have it Fast

… but you can only have 2 of those at the same time. Now if I tell you that we’re a free project and that we shipped (some) stuff in PHP 7.3 faster than we should have, I’ll let you guess what this implies ¯\_(ツ)_/¯


Yes, I understood the meaning of your previous answers.
And sometimes your annoyance about the meaning or the choice of such program or not.
Nevertheless I remember that the project continues to progress.
It was my observation that I wanted to share.
Therefore, I would like to support you in this project.
thank you


This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.