Check the current supported PHP requirements and plan a backup of all content and configuration files. A SQL-only backup does not protect a PluXml site.

Use the project's current supported release information and the requirements shown for the package you select. If Softaculous offers an older or unsuitable build, follow the current vendor installation process or ask us to confirm a suitable environment. Do not enable an unsupported PHP runtime simply to reproduce an old tutorial.

1. Back up any existing site at the destination. Choose an empty directory or a separate staging hostname for a new installation; never approve overwriting a working site without a migration plan.
2. Open Softaculous where your hosting service includes it. In cPanel, search for Softaculous Apps Installer. In SiteWorx, use Hosting Features > Softaculous where that integration is enabled.
3. Find PluXml and review the package and requirements before selecting Install. Select the correct HTTPS domain. Leave In Directory empty only when the empty domain root is the intended destination.
4. Complete the application-specific fields and a strong administrator credential stored in a password manager. Supply a reachable administrative email where requested. Review file-backup and update choices. Include the actual content, media and configuration files for this file-based application; a database-only backup is not sufficient.
5. Start installation once and wait for the completion result. Record the public and administration URLs. Where this application needs the publisher's own deployment process, complete that process instead of forcing an outdated installer package.

Set the blog URL and author information, then configure categories, static pages and comment preferences. Review themes and plugins against the selected release.

Publish a test post containing a title such as Café news and community updates, an image, a category and a short paragraph. Check the article page, category listing and feed before and after copying the site into an isolated restore location.

The title should retain its accented character, the image should load, and the feed should still be readable. Include a static page and any comment data you use in the same recovery check. If punctuation or characters become damaged, preserve the original XML files and compare the transfer or import encoding before editing the live content.

This is a file-content recovery test. A hosting SQL export cannot replace the XML, media and configuration files that make up the publishing site.

Publish a test article, upload an image and check a static page and feed. Validate accented or multilingual text in the content you expect to publish.

If a transfer damages XML or changes encoding, preserve the source files and inspect the import process. Avoid editing many content files blindly in production before restoring a known-good copy.

Keep files and data together in your recovery plan, test application updates in a copy when practical, and review logs after deployment. If installation fails, record the exact error, selected application/PHP versions and destination path before retrying.

• Choosing and managing applications with Softaculous
• Migrating an older blog to WordPress or a current publishing platform
• Creating Web Hosting backups and planning a restore
• Changing PHP versions, extensions and application limits
• Installing Serendipity and checking the first setup

• Softaculous installation workflow
• Softaculous blogs catalogue