CodeCanyon Unlimited Addons - WordPress Plugin

Guide to Setting Up and Safely Using CodeCanyon Unlimited Addons

CodeCanyon Unlimited Addons is best understood not as a single decorative widget, but as a large element library for WPBakery Page Builder. This guide walks through how to approach installation with minimal risk, which settings to review right after activation, how to enable only the add-ons you actually need, how to build a practical section on a page, and how to tell whether the plugin is putting unnecessary load on the site.

This article is written for cases where a short product description already appears above on the page. It does not repeat the product card. Instead, it focuses on real-world usage scenarios, checks, limitations, and troubleshooting. Special attention is given to WPBakery compatibility, user roles, caching, responsiveness, and security, because those are the areas where a large add-on pack most often shifts from being useful to becoming a source of problems.

Facts about what is included in the package were taken from the product page, WordPress.org catalog mirrors, and pages that preserved the plugin description. At the same time, some official product materials are unavailable or outdated, so this guide uses cautious wording where the details are uncertain. If a feature is missing in your copy, rely on the actual interface of the archive you installed and do not blindly carry settings over between versions.

The core idea is simple: check the environment first, enable a minimal set of elements, build one test section, measure the result, and only then move the plugin onto live pages. This approach is especially important for older WPBakery-based projects, where the theme, cache, script optimization, shortcodes, and custom styles all have to work together.

What This Add-on Pack Does and Where It Is Actually Useful

This plugin belongs to the category of extensions for WPBakery Page Builder. Add-ons like this bring new elements, categories, and ready-made building blocks into the builder: banners, tabs, accordions, cards, sliders, team blocks, testimonials, counters, pricing blocks, galleries, buttons, icons, footers, and other visual modules. Unlike small plugins built around a single block, CodeCanyon Unlimited Addons is most useful as a library from which a designer or site administrator can pick the right components for a specific page.

WPBakery already comes with its own elements, templates, and row settings. Unlimited Addons becomes useful when the built-in blocks are not enough, or when you want to assemble repeatable sections faster without hand-coding layouts. For example, an agency might use different service card layouts for landing pages, a site owner might rely on ready-made testimonial and pricing blocks, and a content manager might need visual sections that can be edited directly in the builder interface.

The real value of the pack is not the number of elements, but the ability to make controlled choices. If you enable everything, the editor gets heavier and pages may end up loading extra styles and scripts. But if you keep only the add-ons needed for the current layout, the plugin turns into a practical set of building blocks for fast page design.

Common Use Cases

• Building a WPBakery landing page from ready-made sections without developing a separate template.
• Adding visual blocks to a services page: benefit cards, counters, testimonials, pricing tables, and calls to action.
• Creating content sections for a company website, portfolio, restaurant, studio, local service, or educational project.
• Quickly testing different types of banners, tabs, galleries, and interactive cards without editing theme files.
• Maintaining an older site that already relies on WPBakery and does not have the budget to migrate to another builder.

For a new site built on a WordPress block theme or Elementor, this kind of pack may be unnecessary. It is tied to the WPBakery ecosystem. If the builder is not installed or not in use, the elements themselves will not deliver the expected value. So the first question before installation is not "how many blocks are included," but "does this site actually have a live WPBakery workflow."

Who CodeCanyon Unlimited Addons Is For, and Who Should Take a Different Route

This pack is a good fit for teams that already work with WPBakery and want to expand their visual options without writing a custom shortcode library. It is especially useful for projects where pages are assembled by editors rather than developers. For them, it is much easier to choose a ready-made element, fill in the fields, adjust the colors, and save the page than to ask a front-end developer to build a new block every time.

That said, a large add-on pack is not always the best solution. On a site with strict performance requirements, a tightly controlled design system, or a heavily customized theme, it makes sense to first check how the elements load styles, how they behave in a responsive grid, and whether editor access to importing can be limited. The larger the library, the more important disciplined selection becomes.

When an add-on pack makes sense, and when another option may be better

Situation	Recommendation	What to Check
The site already uses WPBakery and editors actively build pages.	The pack may speed up work and provide more section options.	Availability of the required elements, access permissions, responsiveness, and page speed.
You only need one specific block, such as a carousel or a pricing table.	In some cases, a small specialized plugin is the better choice.	The number of loaded files, theme support, and ease of setup.
The site is built on the modern block editor or another page builder.	Unlimited Addons may become an unnecessary dependency.	Whether WPBakery is needed at all and whether it will complicate future maintenance.
The site has many editors with permission to modify pages.	Use it only after configuring roles and testing import behavior.	Who can import add-ons, upload files, and publish changes.

If the project is small and already uses a theme with built-in WPBakery templates, Unlimited Addons can be tested as a way to expand the section library. If the project is large, define an approved library of elements first: which blocks can be used, which are banned for performance reasons, and which require designer review.

What to Check Before Installing It on WordPress

Preparation matters more than uploading the archive itself. The plugin adds elements to an existing builder, so it depends on the state of WordPress, the WPBakery version, the theme, user permissions, and the site's security policy. On a live site, you should not enable a large pack all at once. It is better to use a staging copy, a test domain, or a private page where you can see how the elements actually behave.

Basic Environment Check

• Make sure WPBakery Page Builder is installed, active, and used on the pages where the new design is planned.
• Check that the theme correctly renders WPBakery rows and columns, especially if it has not been updated in a long time.
• Create a backup of the files and database before installation so you can roll back changes without manually rebuilding sections.
• Create a test page with restricted access or draft status where you can verify the elements before publishing.
• Temporarily disable aggressive minification and script merging during the initial check so it is easier to identify the source of conflicts.

A Separate Security Check

Public vulnerability databases describe a risk related to file import in Unlimited Addons for WPBakery Page Builder versions up to and including 1.0.42. That does not mean every site is necessarily compromised, but it does mean the plugin should not be installed without controlling permissions and verifying the source of the archive.

Before installation, verify the archive version, editor permissions, and whether import is available. If you cannot confirm where the file came from, or you have no way to restrict access to import features, do not enable the plugin on a live site.

At minimum, use a test environment, avoid giving editors access to add-on import unless it is truly needed, do not leave extra archives on the site, monitor security logs, and disable the plugin if it is only needed for legacy pages and is no longer actively used.

Installation and a Safe First Check Before Using It on a Live Page

The installation process is standard for a WordPress plugin: in the admin panel, open Plugins, then Add New, upload the archive, and activate the plugin. But with a large add-on pack, activation itself is less important than what you do immediately afterward. Do not start by publishing a finished page. First, make sure the admin panel opens without errors, WPBakery can see the new elements, and the public-facing site does not run into critical conflicts.

1. Upload the archive through the standard WordPress screen and click Install Now.
2. After installation, click Activate, then go straight to the plugin list and confirm that the plugin is active without warnings.
3. Open the test page in WPBakery mode and click Add Element.
4. Check whether new categories or elements related to Unlimited Addons have appeared.
5. Add one simple element, save the page as a draft, and open the preview.

If the admin panel becomes slow after activation, or if you get a blank screen, a PHP error, or an editor conflict, do not continue setup. Disable the plugin through the extensions list, and if the admin area is inaccessible, use safe server access to temporarily rename the plugin folder. This is not a core hack or a modification of product files. It is a standard way to restore access to WordPress.

A Quick Post-Activation Check

• The WPBakery page opens in the editor without freezing.
• The Add Element button shows new elements or categories.
• A simple added block appears in the preview.
• There are no repeating JavaScript errors in the browser console after saving the page.
• The public-facing site has not lost theme styles, menus, or core interactive elements.

The Element Library: How to Pick the Add-ons You Need Instead of Enabling Everything

Product descriptions often emphasize big numbers for the total count of add-ons and templates. That is useful as a sense of scale, but for a real site, a category map is more practical. The pack includes many types of visual blocks: sliders, banners, tabs, accordions, content cards, testimonials, team blocks, pricing tables, counters, galleries, hover effects, icons, footers, audio, and video blocks. Not all of them belong on a single site.

How to Build a Practical Element Set

Start with the page's job. A services landing page usually needs a hero block, benefit cards, a process section, testimonials, pricing, and a final call to action. A portfolio page needs grids, filters, a gallery, and project cards. A restaurant site benefits from menus, hours, a gallery, reviews, and contact details. If a category is not relevant to the current scenario, it is better not to import it or expose it to editors.

The One-Page Rule

For the first test, choose no more than three element types. For example: service cards, testimonials, and a counter. That gives you a faster way to understand how the plugin works with the theme, how styles are loaded, how much time editing takes, and where conflicts appear. After that, you can expand the set.

The Single Visual Language Rule

The danger of a large library is how easy it becomes to mix several different styles on the same page. One block may use shadows, another bright gradients, and a third a completely different typographic style. The result is a site that looks like a random set of demos. Before publishing, define limits for border radius, button color, heading size, spacing, and animation style.

Good Unlimited Addons setup does not begin with finding the prettiest element. It begins with selecting the blocks that actually support the purpose of the page.

Post-Installation Setup: Roles, Import, Styles, and Responsiveness

After installation, you need to work through four areas: user access, importing selected add-ons, element styling, and responsiveness. Even if your version has a different interface, the logic is the same: limit risk first, then choose the elements, then align them with the site's design, and finally test them across screen widths.

Access Permissions and Editors

WPBakery has its own logic for roles and access to builder features. That matters even more with a large add-on pack. An editor may only need permission to place approved elements on a page, but should not necessarily be allowed to import new blocks, upload files, or change system settings. If several content managers work on the site, create a separate test role or check permissions on a non-public page first.

A practical approach looks like this: the administrator selects and tests the library, the designer defines which elements are allowed, and the editor works only with the approved set. That lowers the risk of accidental imports, broken layouts, and heavy blocks appearing on important pages.

Import Only the Add-ons You Actually Need

The product description specifically mentions the ability to import only selected add-ons. If that feature exists in your version, treat it as the default mode. Do not import the entire pack for hypothetical future tasks. A large element set makes navigation harder, increases the chance of someone using the wrong block by mistake, and makes the editor less intuitive.

A Minimal Set for a Typical Services Website

• A banner or hero block for the first screen of the page.
• Benefit cards or content blocks for explaining the service.
• Testimonials or a trust block, if the site has real verified reviews.
• A pricing block or comparison section, if prices and packages genuinely belong on the page.
• A call to action with a button leading to a form, contact point, or the relevant section.

Design and Safe CSS Tweaks

WPBakery supports extra classes and element design settings. That makes it possible to bring different add-ons into a consistent visual style without editing plugin files. The safe approach is to add your own class in the Extra class name field, then place the styles in a child theme or in Additional CSS. That code is easy to remove, and it will not disappear during a plugin update.

The example below does not change the plugin's logic. It simply lines up cards within the selected section if the specific element supports an additional class.

.ua-guide-cards {
  display: grid;
  gap: 24px;
}

.ua-guide-cards .wpb_content_element {
  margin-bottom: 0;
}

After adding the CSS, check the page in preview, then open it in tablet and phone views. If an element becomes too narrow or breaks the spacing, remove the class from that block or temporarily comment out the CSS. Do not edit plugin files for small visual adjustments.

Responsiveness and the WPBakery Grid

The official WPBakery documentation describes responsive row and column settings, including how the grid behaves on different devices. This is critical for add-ons: a block that looks great on a wide screen may feel overloaded on a phone. Check column widths, block order, whether secondary decorative elements should be hidden, and whether buttons remain easy to read and tap.

For a complex section, use a simple rule: build a working desktop structure first, then check the tablet layout, then the phone layout. If a block depends on a hover effect, make sure its meaning is not lost on devices without hover support.

Practical Example: Building a Services Section in WPBakery

Let's walk through a specific scenario: you need to add a "Services and Benefits" section to a company page without changing the theme template. The goal is to create a clean block with three cards, a short explanation, a results counter, and a button linking to a form. This kind of example works well for a local service business, studio, agency, or B2B website.

Goal and Preparation

Before you start, WordPress, WPBakery, and CodeCanyon Unlimited Addons should already be active. The page should be a draft or a copy of a live page. Prepare short pieces of content: the section heading, three benefits, one number for the counter, and a link to the form. Do not use placeholder copy from demo templates, because it often gets left on the site after publication.

Setup Steps

1. Open the page in the WPBakery editor and add a new row through Add Element or the row add button.
2. Split the row into three columns if you want the benefit cards to appear in one line on a wide screen.
3. Add your chosen card, content block, or icon element from the add-on library into each column.
4. Fill in the headings, short descriptions, and icons. Do not place long paragraphs inside cards, because they work poorly in a grid.
5. Below that, add a counter or a small trust block if the number is real and does not feel arbitrary.
6. Add a button leading to the form, contact section, or another target point on the page.
7. For each card, check spacing, background color, text color, and the hover state if one exists.
8. Save the page as a draft and open the preview in a separate tab.

Checking the Result

On desktop, the cards should line up cleanly and have equal height, or at least not look uneven and scattered. On tablet, a 2 + 1 layout can work, but the third card should ideally be centered or the grid should be rebuilt. On phone, each card should span the full width, the button should remain visible, and the text should not overlap the icon.

Check more than just how it looks. Click the button, make sure the link goes where it should, and verify that the section does not overlap the menu, form, or floating theme elements.

What Can Go Wrong

If the cards appear without styles, a CSS optimization conflict is likely, or the required add-on file may not be loading. If animation is not working, check the browser console and temporarily disable JavaScript merging. If everything looks correct in the editor but not on the public page, clear the site cache, browser cache, and CDN cache if one is being used.

Performance, SEO, and Supporting Older Pages

Visual add-ons affect a site in more ways than appearance alone. They may load styles, scripts, fonts, galleries, animations, and images. That is not inherently bad, but it does require control. The more elements a page contains, the higher the chance the page becomes heavier and editing becomes slower. For SEO, what matters is not the plugin's promises, but the actual speed, clean content structure, proper headings, and accessibility of interactive blocks.

How to Avoid Overloading the Page

• Use one animation style per section instead of a different effect on every card.
• Do not add a slider when a simple three-card grid does the job better.
• Compress images using the site's built-in tools or an optimizer, but do not replace text with images.
• Check the page after caching and minification are enabled, not only in admin mode.
• Remove unused test sections from the page instead of simply hiding them visually.

What to Do With Older WPBakery Pages

If the site has been running on WPBakery for a long time, Unlimited Addons may end up being used on older pages that cannot be moved quickly to another editor. In that case, the goal is not to rebuild everything, but to stabilize the existing sections. Make a list of the pages where the pack's elements are used, check which blocks are still genuinely needed, and document the settings before updating the theme or WordPress.

On an older page, the best outcome is not the maximum number of new effects, but predictable rendering and straightforward maintenance. If a block still works but looks dated, first try bringing it closer to the theme style through classes and design settings. A full element replacement is only necessary when it breaks responsiveness, conflicts with scripts, or is no longer supported.

Troubleshooting: Symptoms, Causes, and Safe Fixes

Most problems with add-on packs like this happen where the builder, theme, and optimization stack meet. There is no need to immediately remove the plugin or start editing files. First, determine exactly where the chain is breaking: import, editor, page save, front-end output, styles, scripts, or user permissions.

Common Issues When Working With WPBakery Add-ons

Symptom	Likely Cause	What to Do
New elements are not visible in Add Element.	WPBakery is not active, the add-ons were not imported, or the user role is restricted.	Check that WPBakery is active, review role settings, and confirm that the required element category is available.
The page saves, but the block appears on the site without styling.	CSS did not load, the cache is serving an older version, or the optimizer merged files incorrectly.	Clear the cache, temporarily disable CSS merging, and check the page in incognito mode.
JavaScript breaks after adding a slider or gallery.	A library conflict, duplicate script loading, or overly aggressive JavaScript deferral.	Disable deferred loading for that page, check the browser console, and test a different element.
On phones, the cards are too narrow or overlap each other.	WPBakery responsive columns are not configured, or the element has a fixed width.	Check Responsive Options, column widths, and any custom CSS.
The editor became slow after importing a large set.	Too many elements in the library, or the server is too weak for a heavy editor.	Keep only the required elements, disable unnecessary plugins in testing, and review server limits.
PHP warnings appear in the admin panel.	An older plugin version may conflict with the current PHP or WordPress version.	Check the error log, test on a site copy, and do not move the plugin to production without verification.

When It Is Better to Roll Back

A rollback makes sense if the problem repeats after clearing cache and disabling optimization, if the issue affects the entire site, if the element would require editing plugin files, or if you cannot confirm the safety of the installed version. In cases like that, it is easier to remove the specific block, restore the page from backup, or replace the element with a standard WPBakery block.

Questions Worth Asking Before Publishing the Page

Can the plugin be used without WPBakery Page Builder?

There is very little practical value in doing that. Unlimited Addons is built to work with WPBakery, so without the builder being active, the elements will not be used the way they were intended. If the site does not run on WPBakery, it is better to look for extensions designed for your actual editor.

Do I need to import the entire add-on set at once?

No. If your version lets you import only selected add-ons, start with the minimum set needed for a specific page. That makes it easier to test speed, responsiveness, and errors. A full import adds noise to the editor and increases the chance of someone using unnecessary blocks by accident.

Why do the elements look different from the demo?

Appearance is influenced by the theme, global typography, WPBakery CSS, cache, optimizers, and custom styles. The demo shows one design context, while your site may use different container widths, fonts, and spacing. Start by checking the theme and the class settings of the specific element.

Can editors be given access to import add-ons?

In most cases, that access should not be granted by default. Editors usually only need to work with approved elements on the page. Import and system settings should remain with an administrator or technical specialist, especially given the public reports of issues in older versions.

Will the pack affect site speed?

It can, especially if the page contains many heavy blocks, galleries, animations, and sliders. Check the actual page after caching is enabled instead of judging the plugin only by its description. If a simple grid solves the problem, there is no reason to replace it with a more complex interactive element.

What should I do if PHP warnings appear after activation?

Do not treat hiding the warnings as the only solution. First, check the PHP version, error log, and theme and plugin compatibility on a site copy. If the warnings are tied to an older product version and interfere with normal operation, it is better to roll back the installation or replace the element with another solution.

Is the plugin suitable for a new WordPress site?

Only if you are intentionally choosing WPBakery as the main builder. For a new project using a block theme, Elementor, or another editor, adding WPBakery just for one add-on pack is usually not practical because it creates an extra dependency.

When CodeCanyon Unlimited Addons Is a Good Choice

CodeCanyon Unlimited Addons makes sense if your site is already built on WPBakery, you need a large library of visual blocks, and the team is ready to work with discipline: choosing only the elements it really needs, checking responsiveness, controlling roles, and avoiding effect-heavy pages. In that kind of workflow, the pack can speed up the creation of landing pages, services pages, portfolios, and repeatable commercial sections.

If you have a new site without WPBakery, strict performance requirements, or no reliable way to verify the archive's source and version, it is better not to rush. Compare more compact alternatives first, evaluate the editor you already use, and decide whether this dependency is actually necessary. The best outcome here comes not from installing "the biggest pack available," but from carefully introducing tested elements into a clear workflow.

Before publishing, run a final check: the backup exists, the test page works, unnecessary add-ons have not been imported, roles are restricted, the mobile version is readable, the cache has been cleared, and the target buttons lead where they should. Once that is done, the plugin can be used as a working WPBakery library rather than a random bundle of visual effects.