• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Stop Plesk from checking for updates for non-existant / moved wordpress installs

iwbyte

New Pleskian
I have a number of sites where I set up wordpress using the application install feature in Plesk 11/12, but then moved them to a new directory. For example, the site was set up in /new/ as we got it going, then moved it to the root directory when we were ready.

The problem is that for some reason Plesk still thinks there's an install in /new/ and keeps sending me emails to update the wordpress software.

I know I can disable the notifications, but I WANT the notifications for other sites on this server - just not the non-existant/moved installations.

I don't want to 'remove' wordpress from these installs because then it may (will?) delete the database, which in Wordpress circles is usually seen as a Bad Thing (tm).

Is there a command-line..uhm, command to tell plesk to stop checking the /new/ directory (which is empty or doesn't exist?). Or do I need to put a fake wordpress install in there, leave it in overnight so plesk sees its up to date and then delete it and it will leave me alone?

Thanks for any suggestions
 
Back
Top