Installation
Three ways to install FCHub Stream. Pick one. They all end with video uploads working or your WordPress installation being broken already.
Maintenance suspended indefinitely
Standard WordPress plugin installation. You've done this before. If you haven't, this is about to get educational.
Pick your preferred method below. They all achieve the same result: FCHub Stream installed and ready for configuration. Or broken. Depends on your WordPress setup, really.
The path of least resistance. Works unless your WordPress is already broken.
Requirements:
- Access to WordPress admin panel (shocking, I know)
- PHP upload limits that don't make you cry (check
post_max_sizeandupload_max_filesize) - Permission to install plugins (some hosts disable this for "security")
Steps:
- Download the latest
fchub-stream.zipfrom the GitHub releases page - Navigate to WordPress Admin → Plugins → Add New
- Click Upload Plugin button (top of page, can't miss it)
- Click Choose File and select your ZIP
- Click Install Now
- Wait while WordPress unpacks the plugin (5-30 seconds depending on hosting speed)
- Click Activate
What happens behind the scenes:
When you click "Install Now", WordPress:
- Uploads ZIP to temporary directory (
/wp-content/uploads/usually) - Validates ZIP structure (checks for valid plugin headers)
- Extracts to
/wp-content/plugins/fchub-stream/ - Removes temporary ZIP file
- Registers plugin with WordPress core
On activation:
- Database tables get created (
wp_fchub_stream_videos,wp_fchub_stream_settings) - REST API endpoints register (
/wp-json/fchub-stream/v1/*) - Admin menu items appear in sidebar
- FluentCommunity integration hooks activate
If this fails:
"The uploaded file exceeds the upload_max_filesize directive"
Your PHP upload limit is too small. FCHub Stream ZIP is ~2-5MB. If your limit is 2MB, you're going to have a bad time.
Fix: Ask your host to increase upload_max_filesize in php.ini. Or use Method 2/3 below.
"Could not create directory"
WordPress can't write to /wp-content/plugins/. Permission issue.
Fix: Set directory permissions to 755 or 775. If that doesn't work, your hosting has bigger problems than FCHub Stream.
For when WordPress admin upload fails or you enjoy the nostalgic pain of FTP clients.
Requirements:
- FTP/SFTP credentials (host, username, password/key)
- FTP client (FileZilla, Cyberduck, Transmit, or terminal if you're hardcore)
- Ability to unzip files locally
- Basic understanding that uploading 500+ files takes time
Steps:
- Download the latest
fchub-stream.zipfrom the GitHub releases page - Unzip it locally (you'll get a
fchub-streamfolder) - Connect to your server via FTP/SFTP
- Navigate to
/wp-content/plugins/directory - Upload the entire
fchub-streamfolder (not the ZIP, the folder) - Wait while 500+ files transfer (grab coffee, this takes a while)
- Go to WordPress Admin → Plugins
- Find FCHub Stream in the list
- Click Activate
What happens during upload:
FTP/SFTP transfers every file individually. That's:
- ~500 PHP files
- Asset files (CSS, JS)
- Vendor dependencies (because modern PHP isn't amateur hour)
- README, license files
Total transfer time depends on:
- Your internet upload speed
- Server location (US East → European server = slower)
- Hosting server load (shared hosting at peak hours = pain)
Pro tip: Use SFTP instead of FTP. FTP is unencrypted. It's 2025. Stop using unencrypted protocols.
If this fails:
Files upload but plugin doesn't appear
You uploaded to the wrong directory. Check you uploaded to /wp-content/plugins/fchub-stream/, not /wp-content/plugins/fchub-stream/fchub-stream/ (nested folder mistake).
The fchub-stream.php file should be at /wp-content/plugins/fchub-stream/fchub-stream.php.
"Permission denied" during upload
Your FTP user doesn't have write permissions. Contact your host. Or check if you're accidentally trying to upload to a read-only directory.
For developers who live in the terminal and think GUIs are for amateurs.
Requirements:
- WP-CLI installed on server (get it here if you don't have it)
- SSH access to your server
- Basic command line competence
- Willingness to debug cryptic error messages
Steps:
SSH into your server and run:
# Navigate to WordPress root directory
cd /path/to/wordpress
# Install and activate in one command
wp plugin install /path/to/fchub-stream.zip --activateOr if you prefer doing things in stages:
# Install only
wp plugin install /path/to/fchub-stream.zip
# Verify it installed
wp plugin list | grep fchub-stream
# Activate separately
wp plugin activate fchub-streamWhat WP-CLI does:
Behind the scenes, wp plugin install runs the same WordPress functions as admin upload. But faster. And without browser timeouts. And without clicking through five confirmation screens.
Advantages:
- No PHP upload limits (bypasses web server entirely)
- No browser timeouts for large plugins
- Scriptable (useful if installing on multiple sites)
- Feels professional (even if you're just copying commands from documentation)
If this fails:
"Error: This does not seem to be a WP CLI 'plugin install' command"
You're not in the WordPress root directory. WP-CLI needs to find wp-config.php to work.
Run wp --info to check if WP-CLI can find your WordPress installation.
"Warning: Could not create directory"
Permission issues again. The user running WP-CLI (probably your SSH user) doesn't have write access to /wp-content/plugins/.
Fix: Run with sudo (if you have access) or fix directory permissions:
sudo chown -R www-data:www-data /path/to/wordpress/wp-content/plugins/Replace www-data with whatever user your web server runs as (might be apache, nginx, www, etc.).