How to Install and Activate WP Block Suite

WP Block Suite installs as four separate Pro plugins. Download and upload each required ZIP. Then activate, license, and test that product.

There is no required suite shell. You can install only the products your site needs.

This guide covers preparation, installation, activation, verification, troubleshooting, staging, Multisite, and documentation.

Know what the purchase includes

• Ultimate Blocks Pro.
• Tableberg Pro.
• Galleryberg Pro.
• Sliderberg Pro.

Each product uses its own plugin package. Treat every ZIP as a separate installation. The plugins overview lists what each one covers.

WP Block Suite costs $299 once. It includes lifetime use, updates, and priority support. We took that apart in standardising WP Block Suite across sites.

The current licence supports unlimited sites. Purchase records and licence details arrive through Freemius.

Prepare before installation

• Administrator access to the intended WordPress site.
• Access to the correct Freemius customer account.
• The required Pro plugin ZIP files.
• Licence details issued for each product.
• A current suitable backup.
• A staging environment when consequence warrants.
• Current hosting and WordPress compatibility information.
• A list of required blocks and workflows.

Do not begin during an important publishing window. Leave time for testing and recovery.

Choose the required components

Install products for defined outcomes. Avoid activating every package merely because the suite includes it.

• Choose Ultimate Blocks Pro for approved broader content needs.
• Choose Tableberg Pro for approved table needs.
• Choose Galleryberg Pro for approved gallery needs.
• Choose Sliderberg Pro for approved slider needs.

One category may justify one standalone product instead. Match the installation to complete requirements.

Confirm administrator access

Sign in to the correct WordPress administration area. Confirm the site address before uploading anything.

Your account needs permission to install plugins. Managed sites may restrict this capability.

Contact the authorised site owner when installation controls are unavailable. Do not bypass organisational restrictions.

Create a suitable backup

Back up files and the database using the site’s approved process. Confirm completion before proceeding.

• Record the backup time.
• Confirm the correct site.
• Verify storage location.
• Check retention.
• Confirm restoration access.
• Know who can authorise recovery.

A backup notification cannot prove restoration. Use tested recovery practices matching the site’s importance.

Use staging when appropriate

Staging reduces production exposure. It is especially useful for established sites, integrations, or custom themes.

• Protect personal and confidential data.
• Prevent real messages or transactions.
• Match important production conditions.
• Keep staging access controlled.
• Define the production deployment route.

Staging cannot reproduce every production condition. Complete a focused check after deployment.

Download the plugin packages

1. Open the authorised Freemius customer account.
2. Locate the relevant WP Block Suite purchase.
3. Identify each required product.
4. Download its current Pro ZIP package.
5. Store it in an approved temporary location.
6. Record its product and version.
7. Preserve the associated purchase evidence.

Use the authorised delivery route. Avoid packages from shared drives without trustworthy provenance.

Verify each ZIP before uploading

• The filename matches the intended product.
• The file came from the authorised account.
• The download completed successfully.
• The package remains a ZIP file.
• The version matches the approved deployment.
• The file is not an unrelated documentation archive.

Do not unzip the plugin package for normal dashboard installation. WordPress expects the installable ZIP.

Install the first Pro plugin

1. Open the WordPress dashboard.
2. Select Plugins.
3. Select Add New Plugin.
4. Select Upload Plugin.
5. Select Choose File.
6. Choose the intended Pro ZIP.
7. Select Install Now.
8. Wait for WordPress to finish.
9. Review the installation result.

Stop if WordPress reports an unexpected package or serious error. Preserve the exact message for diagnosis.

Activate the installed plugin

Select Activate Plugin after successful installation. Alternatively, activate it later from the Plugins screen.

Confirm the correct product appears active. Look for visible errors or unexpected administration behaviour.

Activation proves WordPress loaded the plugin. It does not prove every required block works.

Enter the product licence details

Locate the product’s licence prompt or settings area. The exact route can vary by product version.

1. Open the authorised Freemius account.
2. Locate that product’s licence details.
3. Return to the correct WordPress site.
4. Open the product licence screen.
5. Enter the assigned details accurately.
6. Submit the activation.
7. Confirm the interface reports success.
8. Record the site and activation state.

Do not paste licence details into tickets or public documents. Protect them as controlled account information.

Repeat for required products

Install, activate, and license each required package separately. Use the same controlled sequence.

• Verify the product name.
• Verify the ZIP source.
• Upload the correct package.
• Review installation success.
• Activate deliberately.
• Enter that product’s licence details.
• Record the result.

Do not install an unused component for symmetry. Smaller active sets can simplify testing and support.

Verify update access

Open the Plugins screen and review each installed component. Confirm its version and licence state.

Use the site’s normal update check when necessary. Caches can delay newly available information.

• Product appears in the plugin list.
• Installed version matches the plan.
• Licence state appears active.
• Update checks complete without errors.
• Responsible owner receives relevant notices.

Update availability does not remove testing. Add each product to the site’s normal update process.

Configure only approved capabilities

Review product settings after activation. Apply approved choices instead of changing every available option.

• Required blocks or features.
• Role and permission choices.
• Style and responsive settings.
• Performance-related settings.
• Integration values.
• Data handling.
• Cleanup behaviour.

Record important changes. Defaults may differ across versions or sites.

Create a representative test page

Use a private draft or approved staging content. Include realistic examples for every required component.

• Normal text lengths.
• Realistic images.
• Expected table size.
• Responsive layouts.
• Theme styles.
• Adjacent blocks.
• Required editor roles.
• Important integrations.

A placeholder block proves little. Exercise creation, editing, preview, publication, and later maintenance.

Test the editor experience

• Insert each required block.
• Enter representative content.
• Change approved settings.
• Save the draft.
• Reload the editor.
• Duplicate or move content.
• Use relevant patterns.
• Correct a mistake.
• Preview the result.

Repeat with the intended editor role. Administrator success cannot prove editor permissions are correct.

Test the frontend result

• Inspect desktop and narrow layouts.
• Check text and media.
• Use interactive controls.
• Confirm important links.
• Review theme integration.
• Check cached and uncached views.
• Inspect authenticated and public views.
• Verify expected content remains visible.

Test the actual supported browsers and devices. Avoid judging only one wide desktop viewport.

Check accessibility

Use relevant standards and project requirements. Test both authoring controls and published results.

• Keyboard completion.
• Visible focus.
• Semantic headings and structure.
• Meaningful names and labels.
• Reading order.
• Responsive reflow.
• Contrast.
• Motion control.
• Alternative content.

Automated checks remain incomplete. Include qualified manual testing for important user journeys.

Check performance

Measure realistic content with normal theme, caching, optimisation, media, and integrations.

• Editor responsiveness.
• Frontend loading.
• Interaction behaviour.
• Generated asset weight.
• Markup growth.
• Responsive media delivery.
• Cache behaviour.
• Expected content volume.

Compare results against the site’s budget. Investigate the complete page, not one component alone.

Clear relevant caches

Old administration or frontend output can conceal successful changes. Clear only relevant caches through approved controls.

• Browser cache.
• WordPress cache.
• Hosting cache.
• Content delivery cache.
• Optimisation-generated assets.

Cache clearing can increase load temporarily. Follow the site’s operational process.

Troubleshoot an upload-size error

The hosting upload limit may reject a valid ZIP. Preserve the message and confirm package size.

Use the host’s approved method for changing limits. Alternatively, ask authorised hosting support.

Do not weaken broad server controls without review. Restore temporary changes after installation.

Troubleshoot an invalid package

Confirm the file is the installable plugin ZIP. A larger download may contain several nested packages.

• Check the filename.
• Check the authorised source.
• Download again.
• Inspect approved package instructions.
• Select the product ZIP.
• Avoid renaming arbitrary archives.

Never install executable code from an untrusted source. Contact product support when provenance remains uncertain.

Troubleshoot permissions or filesystem errors

WordPress may lack required write access. Hosting configuration or organisational policy can control installation.

Capture the exact error and current environment. Ask the authorised administrator or host.

Do not apply broad permissions as a shortcut. Use least privilege and approved ownership.

Troubleshoot activation failures

Activation can expose runtime, dependency, theme, or plugin conflicts. Protect production before investigation.

1. Record the exact failure.
2. Confirm the affected site.
3. Check recent changes.
4. Inspect approved logs.
5. Reproduce safely on staging.
6. Test supported combinations.
7. Contact support with evidence.
8. Recover through the approved route.

Avoid random production deactivation. It can disrupt unrelated content or services.

Troubleshoot licence activation

• Confirm the correct product.
• Confirm the correct customer account.
• Re-enter assigned details carefully.
• Check the site’s current address.
• Check outbound connectivity.
• Review relevant security restrictions.
• Clear stale administration caches.
• Capture the exact response.

Staging and production addresses may appear separately. Record assignments and remove obsolete environments responsibly.

Contact authorised support when activation remains unsuccessful. Share only necessary diagnostic information.

Troubleshoot missing blocks

• Confirm the correct plugin is active.
• Confirm the intended block belongs to it.
• Review enabled capabilities.
• Check editor role restrictions.
• Clear relevant caches.
• Reload the editor.
• Check browser errors.
• Test a clean representative draft.

Block visibility and frontend output are separate checks. Test both before approving installation.

Troubleshoot visual conflicts

The theme or optimisation layer may change presentation. Identify the smallest reproducible case.

• Compare editor and frontend.
• Test the active theme safely.
• Inspect custom styles.
• Review optimisation settings.
• Check responsive breakpoints.
• Capture screenshots and markup.

Do not overwrite broad theme styles impulsively. Fix ownership at the correct system layer.

Install on WordPress Multisite carefully

Multisite introduces network administration and activation choices. Confirm the intended scope before installation.

• Identify the network owner.
• Confirm package installation authority.
• Choose network or site activation deliberately.
• Test representative subsites.
• Review theme differences.
• Record licence assignments.
• Plan network-wide recovery.

Network activation affects every subsite. Use it only when requirements and testing support that scope.

Move from staging to production

Repeat controlled installation on production or use the site’s approved deployment system. Avoid copying stale environments blindly.

1. Approve staging evidence.
2. Choose the production window.
3. Confirm a current backup.
4. Notify relevant owners.
5. Deploy authorised packages.
6. Apply approved configuration.
7. Confirm licence state.
8. Clear relevant caches.
9. Run focused production tests.
10. Monitor important outcomes.

Record differences between environments. Production URLs, services, caches, and data can change results.

Document the finished installation

• Site and environment.
• Installed products.
• Installed versions.
• Installation date.
• Licence state and owner.
• Configuration profile.
• Required blocks.
• Test evidence.
• Known exceptions.
• Update owner.
• Support route.
• Backup and recovery route.

Do not record licence secrets in broad documentation. Reference their controlled storage location.

Add the products to ongoing operations

• Monitor available updates.
• Review meaningful release changes.
• Test representative workflows.
• Deploy through approved stages.
• Watch for errors.
• Maintain backups.
• Keep account recovery current.
• Review unused components.

Installation is one event. Safe ownership continues through updates, incidents, handoff, and eventual replacement.

Remove a component cautiously

Deactivation, uninstallation, and data removal can have different effects. Test representative content before proceeding.

1. Identify content using the component.
2. Inspect stored data and settings.
3. Export anything required.
4. Create a current backup.
5. Test deactivation on staging.
6. Inspect editor and frontend output.
7. Plan content conversion.
8. Confirm data-removal behaviour.
9. Remove only with approval.
10. Validate and document completion.

Do not delete a plugin to solve an unexplained incident. Preserve evidence and assess dependent content.

Use the installation checklist

1. Confirm required suite products.
2. Confirm administrator access.
3. Create a suitable backup.
4. Choose staging where appropriate.
5. Download authorised Pro ZIP files.
6. Verify each package.
7. Upload the first ZIP.
8. Install and activate it.
9. Enter its licence details.
10. Repeat for required products.
11. Verify update access.
12. Apply approved configuration.
13. Create representative content.
14. Test editor workflows.
15. Test frontend output.
16. Check accessibility.
17. Check performance.
18. Deploy to production safely.
19. Document ownership and recovery.
20. Add products to ongoing operations.

Frequently asked questions

The verdict

Prepare before uploading. Get WP Block Suite with four lifetime Pro plugins.