build: Remove outdated sphinx-contentui package

[sarina]

Remove sphinx-contentui package

See openedx/docs.openedx.org#1417

This is an outdated package that was included in the docs cookie cutter. It can cause build errors and doesn't seem to be used.

Add php file security

Resolves test failures like this:

This is a WordPress security standard enforced by many plugin review tools (like the WordPress Plugin Checker). Here's what's going on:

The problem

The file openedx-commerce-public-display.php is a PHP partial — it's meant to be included by another PHP file, not accessed directly via a URL. But without a guard, someone could potentially navigate to it directly in a browser, like:

https://yoursite.com/wp-content/plugins/openedx-commerce/public/partials/openedx-commerce-public-display.php

Accessing a partial directly could expose PHP errors, partial HTML output, or unintended behavior.

What ABSPATH is

ABSPATH is a WordPress constant defined early in WordPress's bootstrap process (wp-load.php). It holds the absolute filesystem path to the WordPress installation root.

If a file is loaded through the normal WordPress request lifecycle, ABSPATH will already be defined. If someone hits the file directly, WordPress never bootstrapped, so ABSPATH is not defined.

The fix

Add this at the very top of the file (line 1, before any HTML or PHP output):

<?php
if ( ! defined( 'ABSPATH' ) ) {
    exit;
}

This says: "If WordPress hasn't loaded yet, stop execution immediately."

Where exactly to add it

Looking at [that file on GitHub](https://github.com/openedx/openedx-wordpress-ecommerce/blob/main/public/partials/openedx-commerce-public-display.php), it likely opens with a PHP tag or HTML. The guard should go at the very top, before anything else renders.

This is a low-effort, high-value security hardening step — it's a best practice for any PHP file in a WordPress plugin that isn't meant to be a standalone entry point.

[github-actions]

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.

---

🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check

[sarina]

@feanil trying to remove this package everywhere but I think there's deeper issues here (it's saying I'm upgrading from Py 3.8 -> Py 3.12) - should I just close this until the packages are upgraded?

[feanil]

Python is only used for the docs in this repo so it should be safe to upgrade to python 3.12, you just need to also update the .readthedocs.yml file to match the new version.

[sarina]

wasted some tokens to get validation from claude 🥲

[MaferMazu]

Thanks for this change @sarina ✨ Btw, loving your prompts 😅