So, I have been working heavily in React, TypeScript / Python and various others stacks inside WP/WC and wanted to create a better usage of the tables for large data sets. Trying to not go headless yet ….

But the native tables are just way to slow for any scale with ACP. In working with completely open no paywall license models, we wanted to create a connection to use an as you scroll progressive loading React / Python / Vue / Vite table model, there must be a better way than using these built in super outdated slow table models that are native to the framework.

We have built my own table models in React +++ and they work for even millions of records in seconds, so I know it can work, but the feature set can’t compare and to fork this app into my own is just not worth the efforts just to manage data.

We can’t be the only one for this need? We have looked into decoupling this plugin and seems like I would be forced into a fork at this time to use my own table manager.

Thoughts?

Kinda my idea >

<?php

declare(strict_types=1);

namespace ACP\Custom;

final class ModeResolver
{

    public const MODE_STANDARD = 'standard';

    public const MODE_ENTERPRISE = 'enterprise';

    public static function resolve(): string
    {
        // Emergency override to keep ACP on default behavior.
        if (defined('ACP_FORCE_STANDARD_MODE') && ACP_FORCE_STANDARD_MODE) {
            return self::MODE_STANDARD;
        }

        $mode = defined('ACP_MODE')
            ? (string)ACP_MODE
            : (string)get_option('acp_mode', self::MODE_STANDARD);

        $mode = strtolower(trim($mode));

        return in_array($mode, [self::MODE_STANDARD, self::MODE_ENTERPRISE], true)
            ? $mode
            : self::MODE_STANDARD;
    }
}

Standard mode keeps native ACP behavior. Enterprise mode enables Custom fork logic.