Fix | Conflicts between AWS SDK in this plugin and others

[sksaju]

Description of the Change

This PR implements Strauss dependency prefixing to namespace the AWS SDK, preventing conflicts with other WordPress plugins that may use the same AWS SDK package. The implementation creates a completely isolated version of the AWS SDK under the ClassifaiVendor\ namespace.

Closes #822

How to test the Change

First, let's get everything installed and built:

# Navigate to the plugin directory and install dependencies
composer install
npm install
npm run build

Check That Strauss Did Its Job

Strauss should have created a vendor-prefixed directory with our namespaced AWS SDK. Let's verify:

# See if the prefixed directory exists
ls -la vendor-prefixed/aws/

# Check that classes are properly namespaced
grep -r "ClassifaiVendor" vendor-prefixed/aws/

You should see something like this:

vendor-prefixed/aws/
├── aws-sdk-php/
│   ├── src/
│   │   ├── Aws/
│   │   │   ├── Polly/
│   │   │   └── ... (other AWS services)
│   └── autoload.php

Test the AWS Polly Feature

Now let's make sure our text-to-speech functionality still works:

1. Head to your WordPress admin panel
2. Navigate to ClassifAI → Text to Speech
3. Enter your AWS credentials:
   • Access Key ID
   • Secret Access Key
   • AWS Region (like us-east-1)
4. Try generating speech from a post - you should get an audio file back

The Real Test - Conflict Prevention

This is where we see if Strauss actually prevents conflicts:

1. Install another plugin that uses AWS SDK (WooCommerce with AWS extensions works well)
2. Activate both plugins at the same time
3. Check for any PHP errors in your error logs
4. Test both plugins to make sure they still work properly

If everything's working, you shouldn't see any "class already exists" or similar errors!

Test the Build Process

Let's make sure our build process works correctly:

# Run the archive command
npm run archive

# Check what's in the release directory
ls -la release/

Changelog Entry

Added - Implement Strauss dependency prefixing for AWS SDK to prevent conflicts with other plugins

Credits

Props @username, @username2, ...

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added Critical Flows, Test Cases, and/or End-to-End Tests to cover my change.
• All new and existing tests pass.

[dkotter]

So currently this function will return true if the autoload file is loaded properly. Now that we are introducing another autoload file, I think we'll need additional changes here to ensure both are loaded properly and show an error message if not.

Something like this (untested):

function classifai_autoload() {
	$loaded = false;

	// Load the prefixed vendor autoloader (contains AWS SDK and all other dependencies)
	if ( file_exists( CLASSIFAI_PLUGIN_DIR . '/vendor-prefixed/autoload.php' ) ) {
		require_once CLASSIFAI_PLUGIN_DIR . '/vendor-prefixed/autoload.php';
		$loaded = true;
	}

	// Load the main vendor autoloader (contains plugin classes and other dependencies)
	if ( $loaded && file_exists( CLASSIFAI_PLUGIN_DIR . '/vendor/autoload.php' ) ) {
		require_once CLASSIFAI_PLUGIN_DIR . '/vendor/autoload.php';
	} else {
		$loaded = false;
	}

	if ( ! $loaded ) {
		error_log( // phpcs:ignore WordPress.PHP.DevelopmentFunctions.error_log_error_log
			sprintf( 'Warning: Composer not setup in %s', CLASSIFAI_PLUGIN_DIR )
		);

		return false;
	}

	return true;
}

[dkotter]

Is this needed? Looking at the changes in composer.json, we run this same command on the post-install-cmd hook which I think means this will automatically run after the step above

[dkotter]

One other thing that needs fixed here. If running composer install locally, you'll need to ensure your environment is running PHP 7.4 (which is our minimum for this plugin). If you're running PHP 8+, composer will set PHP 8.1 as our minimum which breaks things (you can see this in some of our failing GitHub Actions on this PR). So you'll want to install PHP 7.4 locally, run composer install and then commit the composer.lock file

[github-actions]

@sksaju thanks for the PR! Could you please rebase your PR on top of the latest changes in the base branch?

[jeffpaul]

@dkotter @peterwilsoncc we'll likely need to pick this one up to finish it off, to give us a bit more time I'm moving this out a release