-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting FAQ
Run in order:
yarn
yarn bootstrapbootstrap must be run after yarn on a fresh clone. It builds workspace packages (packages/components, packages/components-react) that the main plugin depends on.
Make sure the watch process is running:
yarn start # watches main plugin src/
yarn start:workspace # watches all workspace packagesIf you changed something in packages/components, you need start:workspace.
The Imposter plugin is responsible for re-namespacing vendor dependencies under PrestoPlayer\. If conflicts occur:
composer remove typisttech/imposter-plugin
composer install
composer require typisttech/imposter-pluginwp-env requires Docker Desktop. Install it from docs.docker.com/desktop and ensure it is running before:
yarn wp-env startCheck if something is already on port 3333:
lsof -i :3333Change the port in .wp-env.json or stop the conflicting process.
yarn wp-env start # ensure environment is running first
yarn test:phpThe test suite is installed inside the Docker container — it must be running.
Check .wp-env.json in presto-player/ — it should reference both presto-player and presto-player-pro:
{
"plugins": [".", "../presto-player-pro"]
}Both plugin folders must be siblings in the plugins/ directory.
- Verify
token_auth_keyis set correctly in Presto Player → Settings → BunnyCDN - Confirm token authentication is enabled in Bunny.net dashboard for the library
- Check that the pull zone URL does not have a trailing slash
- Confirm server time is accurate — signed URLs include an expiry timestamp
- Check API key has sufficient permissions (Stream API key, not account key)
- Verify the library ID is correct
- Check server error logs:
WP_DEBUG_LOGinwp-config.php
A past release patched an arbitrary file deletion vulnerability. If you are seeing permission errors on delete endpoints, ensure you are running an up-to-date version and that the user has upload_files capability.
- Ensure the site URL matches what was registered at
my.prestomade.com - Try activation with
https://if the site supports SSL - Check for response code:
s100= new activation,s101= renewal — both are success codes
The license page only appears if Services/License/ is included (standard Pro build). VIP builds exclude the license system by design.
- Check provider is marked as connected: Settings → Email Providers → [Provider]
- Confirm the list/audience ID is set in the email collection preset config
- Enable
WP_DEBUG_LOGand look for API errors from the provider request library - For FluentCRM: it auto-detects connection status based on plugin activity — no API key needed
- Ensure
yarn buildhas been run anddist/is populated - Check browser console for JS errors
- Verify the block class is in
inc/config/app.phpcomponents array - Run
wp-env startand check PHP error logs for block registration errors
Presets are loaded at block insertion time. To apply a changed preset to an existing block, re-select the preset in the block's sidebar panel.
Run the migration manually:
// In wp-cli or a throwaway snippet:
do_action('presto_player_activate');Or deactivate and reactivate the plugin from WP admin.
Enable the purge option: Settings → Analytics → Purge old data. The presto_daily_cron action handles cleanup.
Presto Player | Presto Player Pro | prestoplayer.com | PHP 7.3+ | WordPress 6.3+