Installation
How to download, install, and activate the FCHub Portal Extender plugin on your WordPress site.
Requirements Checklist
Before you begin — and honestly, this bit is mercifully short — confirm that your site meets these requirements:
| Requirement | Details |
|---|---|
| WordPress | Version 6.4 or higher |
| PHP | Version 8.1 or higher |
| FluentCart | Installed and activated |
That's it. No SSL demands, no third-party merchant accounts, no blood sacrifice. Just WordPress, PHP, and FluentCart.
FluentCart Must Be Active
FCHub Portal Extender is an extension for FluentCart's Customer Portal. If FluentCart is not installed and activated, the plugin has nothing to extend and will sit there doing precisely nothing useful. Install FluentCart first.
Download
FCHub Portal Extender is distributed as a WordPress plugin ZIP file. Grab the latest release from the GitHub Releases page:
Download v1.0.3 — download fchub-portal-extender-1.0.3.zip from the GitHub release page.
Installation Steps
Upload the Plugin
Navigate to Plugins > Add New Plugin in your WordPress admin dashboard. Click the Upload Plugin button at the top of the page.
Choose the fchub-portal-extender-1.0.3.zip file you downloaded and click Install Now.
Activate the Plugin
After the upload completes, click Activate Plugin. WordPress will activate FCHub Portal Extender.
If FluentCart is not active at this point, the plugin will activate without complaint but won't actually do anything — it needs FluentCart's portal system to hook into.
Verify It Works
Once both FluentCart and FCHub Portal Extender are active, navigate to FluentCart > Portal Extender in the admin sidebar. You should see the plugin's admin interface where you can create and manage custom portal endpoints.
If you don't see the submenu item, double-check that FluentCart is active and try refreshing the page. The admin menu registers at priority 99, so it appears below FluentCart's own menu items.
What Happens on Activation
When the plugin activates, it registers three things — and none of them are particularly dramatic:
- Portal endpoints register on
initpriority 3 — any endpoints you've configured get registered with FluentCart's Customer Portal - REST API routes register on
rest_api_init— the admin interface needs these to save and manage your endpoint configurations - Admin submenu page registers on
admin_menupriority 99 — adds the "Portal Extender" item under FluentCart in the sidebar
All endpoint configurations are stored in a single wp_options row under the key fchub_portal_endpoints. No custom database tables, no migrations, no existential dread.
What Happens on Deactivation
When you deactivate the plugin:
- Your endpoint configurations are preserved in the database — nothing is deleted
- The endpoints simply stop rendering in the Customer Portal because the registration code no longer runs
- The admin submenu disappears from the sidebar
Settings Are Preserved
Deactivating the plugin does not delete your settings. If you reactivate later, all your custom endpoints will still be there, exactly as you left them. We're not monsters.
What Happens on Uninstall (Deletion)
If you delete the plugin through the WordPress admin, the uninstall.php routine runs and cleans up after itself:
delete_option('fchub_portal_endpoints')removes all your saved endpoint configurations- That's the only piece of data the plugin stores, so this is a full cleanup — no orphaned data left behind
Clean in, clean out. As it should be.
If you prefer uploading via FTP/SFTP like it's 2009:
- Extract fchub-portal-extender-1.0.3.zip on your local machine
- Upload the
fchub-portal-extenderfolder to/wp-content/plugins/ - Go to Plugins in WordPress admin and activate FCHub - Portal Extender
If you have WP-CLI access (and good taste):
# Install from a local ZIP file
wp plugin install /path/to/fchub-portal-extender-1.0.0.zip --activate
# Verify it's active
wp plugin list --name=fchub-portal-extender --fields=name,status,versionNext Steps
FCHub Portal Extender
Custom customer portal endpoints for FluentCart. Add pages, shortcodes, HTML blocks, iframes, and redirects to the portal sidebar — no PHP required.
Content Sources
The six content source types for portal endpoints — WordPress Pages, Shortcodes, HTML, iframes, Redirects, and Custom Post Types. How each one renders and when to use it.