CodeCanyon Projectify - WordPress Plugin

A Guide to Setting Up and Using CodeCanyon Projectify in Elementor

CodeCanyon Projectify is useful when your site already has substantial content but needs a clear, manageable way to showcase it. That might mean a studio portfolio, a collection of completed projects, a case study catalog, a work gallery, a resource page, or an archive of a custom post type. This guide isn’t about building a new site from scratch. It focuses on connecting existing WordPress content, widget settings, and a clear result on a published page.

Projectify has one important characteristic to understand before you install it. According to the author’s description, the add-on displays existing WordPress content: standard posts, pages, portfolio entries, galleries, and other custom post types, if your theme or site has them. That means the quality of the showcase depends on more than the grid layout you choose. First, organize your content, images, links, and taxonomy terms. Then choose a layout.

This guide covers preparation and installation, source and taxonomy settings, display options, a practical portfolio example, checks on the published page, safe updates, and troubleshooting. Field names may vary slightly between Projectify and Elementor versions, so each section explains both what to do and how to tell whether it worked.

What the Add-On Does and Who It’s For

Think of Projectify as a tool for the public-facing part of your site, not as a standalone project database, client portal, or task management tool. It helps you select existing posts and display them in a portfolio, fullscreen, circular, grid, or slider layout. The official product listing draws a clear distinction between Projectify and Modulify: Projectify works with your site’s posts, while Modulify uses a set of standalone items that you enter manually.

This approach works especially well when your editorial team already publishes content in the usual way. For example, a designer creates a separate post for each case study, adds a featured image, writes a title and description, and then an editor assembles those posts into a collection on the home page or a services page. Each post remains the source of truth: updating its title, image, or link doesn’t require tracking down a second copy of that information in a separate grid.

Good fits for Projectify

The add-on is a good fit for a site with a regularly updated collection that visitors need to browse quickly. Typical examples include an architecture firm showcasing completed projects, an agency grouping case studies by service, a photographer organizing shoots by genre, a company presenting news and service pages in a more visual format, or a developer turning a custom post type into a project showcase.

In each case, the value comes from more than the animation. Visitors first see clear images and titles, then narrow down the selection or open a detailed post. Projectify lets you build that experience in Elementor without manually duplicating the same set of cards on every page.

When another approach may work better

Projectify may not be a good fit if the content doesn’t already exist as WordPress posts. Suppose you need six one-off promotional cards on a specific page, each with a different link, and you won’t use them anywhere else. Projectify’s content model may be more than you need, since you’d have to create posts just to fill a single block. In that case, standalone Elementor elements or a product designed for manually entered modules may be more convenient.

Projectify also doesn’t replace a product catalog with price, inventory, and advanced attribute filters or a checkout flow. If your showcase needs to manage store products, don’t substitute a display of general posts for a product catalog. And if your site doesn’t use Elementor, this add-on won’t solve the problem on its own: the official product listing identifies Elementor as its compatible platform.

A useful rule of thumb: Choose Projectify when you already have quality WordPress posts and want to present a collection of them in a designed Elementor block. If you need standalone cards, don’t make your content model imitate a project catalog.

The Key Decision: Use Existing Content or Create Items Manually?

Many setup problems start here, before you get to the design settings. An editor opens an Elementor page, adds Projectify, and tries to build a polished showcase before deciding which posts should appear in it. The page ends up showing recent news, unrelated pages, or duplicate content, and the editor tries to fix the problem with colors, spacing, and animation.

Projectify works the other way around: you start by choosing the source. The official description lists posts, pages, portfolio entries, galleries, and other custom post types. For each widget, answer four questions: Which post type will it display? Which posts should be included? How should they be grouped? In what order should visitors see them?

Using standard posts as the source

Standard posts work well for a blog, news, project stories, or a series of publications. WordPress already gives them a date, author, categories, tags, featured image, and permalink. The downside is just as clear: if the same post type mixes company news, technical notes, and case studies, a broad query might show the wrong content. To avoid that, create a dedicated category or taxonomy term for the showcase and make sure it’s assigned to every post you want to include.

Don’t select posts based on a word that happens to appear in the title. Titles can change for editorial clarity, while taxonomy terms identify a post’s purpose. For an agency, for example, using a case-study term or a dedicated case study category is more reliable than expecting every title to include the word "project."

Using a custom post type

A custom post type is useful when projects need their own fields and editorial workflow. It might be called portfolio, works, or something else registered by your theme or another plugin. Projectify doesn’t necessarily create that post type; its job is to display content available from the source. Before you configure the widget, open the post type in the admin area and make sure it contains publishable work, not just test entries.

Check the permalinks for at least three posts. A card can look great and still lead to a draft, an empty template, or an error page. Your showcase should strengthen the site’s navigation, not hide its flaws behind a visual layer.

Using a manually entered set of items

This is a good point to pause and reconsider your approach. You could technically create several standard pages and select them in Projectify, but maintaining the collection may be awkward if those cards aren’t full-fledged posts. The author’s official comparison with Modulify explains the difference: with Modulify, you manage each item’s image, title, subtitle, and link. Projectify is designed to work with existing posts.

So don’t judge the product only by how its demo looks. Ask yourself where an editor will update a project title three months from now. If the answer is "in a standard WordPress post," Projectify keeps things organized. If the answer is "in one card on one page," another tool may be a better fit.

Prepare Your Project Posts Before Opening Elementor

Before installing the widget or adding it to a page, put together a working collection of six to eight items. A single test project won’t show how the grid, filters, long titles, and different image proportions will behave. You don’t need a huge collection either: the goal is to cover typical cases, not fill the site with demo content.

What each post needs

Each post should have a clear title, a permalink, a suitable featured image, a short introduction, and at least one term that groups it with similar work. If your theme or another site component uses a custom field for the main image instead of the standard featured image, check that separately. Don’t assume every Projectify layout will automatically read a custom field. Start by checking the output with a real post.

• Title should explain the work without relying on a caption embedded in the image. "Website for a museum" is more useful than an internal label like "Item 07."
• Image should have a consistent level of visual quality. The aspect ratios don’t have to match, but a haphazard mix of portrait screenshots, tiny logos, and dark photos can make even a well-built layout feel uneven.
• Link should lead to a published page that visitors can access without signing in. Check it in a separate browser window, not only while logged in as an administrator.
• Taxonomy term should represent one clear category, such as industry, type of work, service, or format. Don’t mix roles, cities, years, and publication status in one filter.

Good preparation also makes troubleshooting easier. If the widget includes unwanted items, check the query rules. If some cards look wrong, open the corresponding posts and fix their content. When the source data is disorganized, it’s hard to tell whether to change Projectify’s settings or the content itself.

Use taxonomies to help visitors navigate

A taxonomy is useful to visitors only if it helps them make a decision. A studio site might group work into "Branding," "Websites," and "Packaging." An architect’s site might use "Residential," "Public Spaces," and "Interiors." A developer might use "Integrations," "Stores," and "Client Portals." These terms help visitors understand what they’ll find before opening a card.

A poor approach is to create dozens of one-off terms, each for a single piece of work. The filter can end up longer than the showcase. If a category contains just one item and doesn’t support consistent navigation, it may be better to describe that characteristic in the post itself.

Check your preparation

In the admin area, open the list of posts you plan to use and filter it with WordPress’s built-in controls. You should see exactly the items you want to show visitors. Then open two posts from different terms and the post with the longest title. If each reads well as a standalone page and the images look appropriate, your source is ready to connect.

What to Check Before Installing and Publishing

Checking your setup doesn’t have to turn into an exhaustive technical audit. For Projectify, focus on a few things that directly affect what visitors see: WordPress and Elementor are available, you can edit the intended page, permalinks work, images load, and you have a safe place to test. The official product listing identifies Elementor as a compatible product, so there’s no point proceeding without an active Elementor installation.

Make sure the editor is working

In WordPress, make sure the user who will configure the block can edit the page and the relevant posts. Then open a test page in Elementor. If the editor itself won’t load, installing another widget won’t fix the underlying problem. Elementor’s official documentation recommends first checking that WordPress, your theme, and your plugins are up to date, and temporarily ruling out plugin conflicts on a staging site or backup.

Be especially careful in environments with several Elementor add-ons, a script optimizer, and aggressive caching. That doesn’t mean they’ll necessarily conflict with Projectify. But if something does go wrong, troubleshooting is faster when you know which components are active and how to clear the cache.

Back up the site and create a test page

Make a current backup before changing live pages or updating plugins. This is a recommendation from WordPress’s plugin management documentation, not just a formality. The next safe step is to create a draft page, such as "Showcase Test," and build your first block there. This lets you check the source, layout, container width, and links without changing the home page right away.

Once you’ve checked the block, you can recreate it on the live page or save the Elementor page as a template if that fits your workflow. Don’t move every experimental design choice to the home page at once. Start with one working version, then make sure visitors can tell where each card leads.

Caching and resource optimization

Caching doesn’t cause every problem, but it can make a saved change look like it didn’t take effect. After changing the sort order, filter, or page text, first update the page in Elementor, then refresh it normally in your browser, and only then clear the cache for your optimizer or host. This sequence helps you distinguish an unsaved change from an older cached copy of the page.

Don’t disable all plugins on a live site without preparation. If you need to diagnose a conflict, do it on a copy or disable one component at a time while recording the original state. Good troubleshooting is reversible.

Install Safely and Confirm the Widget Is Active

For a purchased add-on, use the original archive from your Envato account. The official Projectify listing says to unpack the full download archive, find projectify.zip, and install it through the WordPress plugins area. Don’t upload the entire download archive if it also contains documentation and other files. WordPress expects the installation ZIP for the specific plugin.

1. Back up the site and make sure Elementor is active.
2. In the admin area, go to Plugins > Add New and select Upload Plugin.
3. Choose the installation archive, projectify.zip, not the full archive containing all the purchased files.
4. Click Install Now, wait for the success message, then activate the add-on by clicking Activate Plugin.
5. Open a page in Elementor and search for Projectify in the widget panel. The category name, icon, or exact label may vary, so look for the product name rather than relying on a screenshot from an older guide.

After activation, don’t start by configuring every option. Add the widget to a test page, save it, and check that the editor doesn’t show a critical error. Then open the public page in a separate browser window. The basic signs of a successful installation are that the widget is available in Elementor and you can open, save, and publish a regular page without issues.

If the widget doesn’t appear in the panel

First, refresh the Elementor page and search in the widget panel. Elementor’s documentation confirms that the search filters available elements by name. If Projectify still doesn’t appear, check Plugins > Installed Plugins: the add-on should be active, and Elementor shouldn’t be disabled. Then check whether the admin panel is showing stale cached content or the editor has an error.

Don’t edit plugin files through the WordPress editor or upload the archive over an active installation before you understand the cause. Start with the basics: confirm that both components are active, check that you have the correct original archive, review WordPress’s installation message, and make sure Elementor works without the new block.

Why you shouldn’t edit code right away

We couldn’t find public official documentation for specific Projectify hooks, filters, or CSS class names. Adding random PHP code from someone else’s article could cause an error after an update or change a page the code wasn’t meant to affect. For your first setup, stick to the built-in WordPress and Elementor controls. If you later need to customize the appearance, first inspect the specific block’s HTML in your browser, make a backup, and apply a minimal, reversible rule through the method your site uses.

One Widget, Several Display Styles

Projectify’s changelog notes that its separate widgets were combined into one. For users, this means you can start with one main widget and select the right display style in its settings instead of looking for separate elements for a grid, slider, or other layout. This doesn’t guarantee that every version has the same fields. Look for the general sequence of "source, selection, order, display" instead of memorizing where a button was in an old video.

A practical setup order in Elementor

Open a test page in Elementor and add the Projectify widget to the canvas. Elementor’s documentation groups widget settings under the Content, Style, and Advanced tabs. Start with Content, since that’s where the source and items for the block are usually configured. Adjust the design only after the preview shows the right posts.

First, choose an available source type. Then, if your version offers the option, limit the selection to the relevant taxonomy or category. Set the number of items and their order only if those fields are available. The official product listing includes sorting by ID, author, title, name, random order, comment count, and page order. Choose an option that fits the content, not one that just looks impressive.

• Sort by title for an alphabetical catalog where visitors look for a specific name.
• Use page order when an editor can explicitly control the sequence of posts in the source.
• Use random order with care. It may work for an inspiration gallery, but it makes the showcase harder to check and makes it more difficult for visitors to find an item again.
• Filter by author only when the author is genuinely part of the navigation, as in a collaborative portfolio.

After each change, look beyond the first card. Scroll through the list, select each filter term, check the longest title, and inspect the last card. A layout may look tidy with three items but break down with nine, so test it with your actual collection.

Keep content and styling separate

Use the Style tab to adjust contrast, text size, spacing, and hover states within the options available in your installed widget. Don’t use decorative settings to hide a problem with the source. If a title is cut off, first decide whether the editorial title can be shortened. If some projects have no image, add a featured image to those posts. If a card should link to a case study, check the post itself, not just the hover effect.

The Advanced tab is for general Elementor options such as margin, positioning, responsive visibility, and other properties. Use it when the issue concerns the block’s placement on the page rather than its Projectify content. For example, if the container is too narrow, adjust the Elementor section or container instead of shrinking the card text over and over.

Taxonomies, Filters, and the All Button

Taxonomies are more than a minor detail in Projectify. The author’s changelog records a shift from the old category inclusion behavior to taxonomy support for all post types, along with faster taxonomy search. That matters because you can’t assume that custom post types use standard WordPress categories. Find out which terms are registered for your source and which ones visitors need.

Build each filter around one question

Each group of filters should answer the same question. On a work showcase, visitors might ask, "What type of work is this?" They can then choose between design, development, and strategy. On a real estate showcase, they might ask, "What type of property is this?" and choose among apartments, houses, and commercial spaces. If the first option is about type, the second about city, the third about year, and the fourth about status, visitors won’t know what to expect when they make a selection.

Start with a small set of terms, assign them to several posts, and then add them to the widget if it offers that option. After saving, click each filter on the published page. Write down the expected number of items in advance. For example, if you’ve assigned four posts to "Websites," selecting that filter shouldn’t leave six. This simple check catches incorrectly assigned terms faster than inspecting styles or scripts.

Why the All label matters

Projectify’s changelog specifically mentions an option to change the All label in the masonry layout. This can make the interface clearer and easier to localize, but it’s not a reason to change labels blindly. Check your installed version and look for that option only if it’s available. For an English-language page, possible labels include "All work," "All case studies," or "Show all." Choose one that accurately describes what the showcase contains.

Before saving, ask yourself whether the button promises more than the block displays. If the page shows only selected case studies from the past year, "All projects" could be misleading. In that case, change the section’s introductory text or adjust the source query instead of masking the limitation with a polished label.

Multiword terms and checks after updates

The author has documented a fix for an issue with multiword category names in the masonry layout. That doesn’t mean your site will necessarily run into the same problem. But if you use terms like "Online Stores" or "Urban Interiors," include them in your test set. Check each term, its URL, and the visible list on a real page. After a Projectify update, repeat the check: filtering and term labels are especially sensitive to changes involving WordPress, Elementor, and your theme.

Don’t create terms that differ only in capitalization, spacing, or a nearly identical spelling. Visitors will see two similar options and assume the site contains duplicates. Keeping the taxonomy clean can do more for usability than adding another visual effect.

Choose a Layout for How People Will Browse

The Projectify listing includes demo styles such as full alpha, full interactive, circle alpha, circle numbered, and slider. They show different ways to present a collection, but they aren’t a recommendation to choose the most complex option. Each layout affects how visitors browse: some make a collection easy to scan, some focus attention on one item, some invite visitors to use arrow controls, and others show a filterable grid.

When to use a grid or masonry layout

A grid works well when visitors need to compare several projects at a glance. It can showcase a range of services, case studies, or a series of resources. Masonry can accommodate images of different heights, but it won’t fix an inconsistent set of images. If one item uses a portrait poster, another a wide screenshot, and a third a square logo, the collection will still feel uneven. First establish a visual standard for the images, then test masonry with ten different posts.

Context is especially important for a filterable grid. Add a short explanation above the block to tell visitors what they can filter. For example: "Choose a service to see relevant case studies." Without that prompt, visitors may not realize that the labels are active filters.

When a slider or fullscreen layout makes sense

A slider makes sense when each project deserves attention and the collection is small. For example, you might feature four large case studies on the home page. Check the arrows, forward and back navigation, keyboard focus, touch controls, and whether visitors can still reach the case study itself. Projectify’s changelog includes fixes for arrows and slide navigation, so test these carefully after an update.

A fullscreen or large-format layout can make an emotional impression, but it shouldn’t replace useful information. Visitors need to know how to move to the next project and open the detailed page. If your layout shows a title only on hover, check how it works on devices that don’t have reliable hover behavior. Not everyone uses a mouse.

Circular and numbered layouts

Circular and numbered layouts work when sequence is part of the story, such as projects organized by phase, a series of objects, or a carefully ordered portfolio. They’re less convenient for a large catalog because visitors can’t compare every item as quickly. Don’t try to squeeze dozens of posts into a circular layout just because it looks unusual.

Once you’ve chosen a layout, run a simple test: give the page to someone who wasn’t involved in setting it up and ask them to find a case study of a certain type. If they can’t tell where the filter, arrow, or link to the detail page is, the issue is with the showcase’s design, not with the user being "unfamiliar" with it.

Example: Build an Agency Case Study Showcase from Existing Posts

Let’s walk through a repeatable example. An agency has a custom post type for projects. Each post has a title, featured image, introduction, published case study page, and a term from one taxonomy: "Websites," "Branding," or "Marketing." The agency wants to add a clear collection to its services page so visitors can browse featured work, filter by service, and open a detailed case study.

Set the goal and prepare your content

The goal isn’t to display every post. It’s to create a curated showcase that answers a potential client’s question: "Can you show me something you’ve done for a similar project?" Start by selecting eight strong case studies. Each needs an accessible featured image, a clear and accurate title, and a service term. Don’t use drafts, outdated service pages, or demo posts that you might forget to unpublish.

On a separate test page, create a container wide enough for the layout. Add a section title and a short introduction, such as: "Choose a service and open a case study to see the challenge, the work, and the outcome." This tells visitors how the block works before they interact with it.

Step 1: Add the widget and choose the source

Find Projectify in Elementor’s widget panel and drag it into the container you prepared. On the Content tab, first choose the post type that contains the portfolio. If your version lets you select posts or define the query source, use that option, but don’t adjust the design until the right items appear on the canvas.

Save the page and open the preview right away. First check whether every visible card belongs to the portfolio. If the block includes news or pages, go back to the source settings. Don’t try to compensate by manually excluding individual posts until you’ve checked whether you selected a source type that was too broad.

Step 2: Filter by service and check the terms

If your widget version has a taxonomy setting, select the taxonomy for services. Choose only terms that make sense to visitors. If the widget offers include and exclude options, start with the simplest rule: include the three main groups. Complex rules are useful only if you can explain them to the person who will maintain the page.

Publish the test page and click each visible group. Beforehand, note which posts you expect to see: three under "Websites," two under "Branding," and three under "Marketing." If the output differs, don’t change the filter label. Find the unexpected post in WordPress and check its assigned terms. This fixes the source rather than the symptom.

Step 3: Choose an order that fits the collection

For an agency home page, a curated sequence is often useful if the source and widget settings allow it. Put the most representative work first rather than automatically showing the most recent posts. For an alphabetical catalog, sort by title. Random order usually isn’t a good fit for this example: visitors may return to the page and not find the case study they wanted to open.

The official listing describes several sorting options, but your installed version’s interface is the source of truth. If it doesn’t offer the option you want, don’t try to create it by editing files. Use the ordering supported by the source, or edit the posts themselves to keep navigation clear.

Step 4: Choose a layout and style the cards

For this example, start with a grid or masonry layout so visitors can compare several projects. Check that titles are readable, important parts of the featured images aren’t cropped, and each card opens the right detail page. Then adjust the available style settings, such as text contrast, spacing, and hover color. Before making the text smaller, check the container width and the length of the titles.

A strong card doesn’t need a lot of copy. Usually, an image, a title, and a clear action are enough. If you add a subtitle, make sure it provides useful information, such as the industry, service type, or outcome. Don’t repeat the word "project" on every card just because the section is called a portfolio.

Step 5: Check the links and the live page

Open the showcase using its regular public URL, not just from Elementor. Select a term, then click two cards. Open one link in a new tab and make sure the case study is published, its title matches the card, and the image displays correctly with your theme. Go back and check that visitors can still see which service they selected, or can quickly figure out how to narrow the list again.

Then check the page in a narrow browser window. This isn’t a substitute for testing on a phone, but it can quickly reveal whether the cards are too cramped. Use Elementor’s available preview modes, but also check the finished page in a regular browser after clearing the cache. The showcase is ready only when the filter, navigation, and links work outside the editor.

Check the Showcase Before and After Publishing

There’s no single sign that a showcase is ready. Cards may appear but link to the wrong pages. A filter may update the list but leave out posts with multiword terms. A slider may work with a mouse but not respond to the keyboard. Check the whole flow: content, interaction, links, the published page, responsive behavior, and caching.

Check the content

Compare the actual cards with the list you prepared in advance. For each group, note the expected number of items and one specific post that must appear. Check the newest post, the oldest one, the one with the longest title, and a post with an unusual image aspect ratio. These examples can quickly reveal issues with ordering, content, or layout constraints.

Check the interactions

If the layout includes filters, click each one and then return to the full collection. If it has slider arrows, move through a few full cycles in both directions. If the selected layout offers a lightbox, check both opening and closing it, moving between items, accessing the project link, and making sure visitors aren’t left without a clear way back. Projectify’s history mentions fixes for lightbox behavior and project or category links, so these checks matter.

Check the published page

Elementor shows a preview on the canvas, but the public page also runs through your theme, cache, optimization tools, and real asset-loading rules. Open the page in a private window or in a browser where you aren’t logged in as an administrator. Compare titles, images, card counts, and links. After an important change, update the page in Elementor, refresh the browser tab normally, and clear the cache if your site requires it.

Check accessibility and narrow layouts

Check the contrast of text over images, readability when zoomed in, keyboard focus order, and whether controls have enough visible space. Not every layout can meet these needs perfectly without help from the theme, but testing will show you its actual limits. On a narrow display, make sure cards don’t collapse into a strip with unreadable titles and controls don’t run off the edge.

Key check: On the public page, someone without administrator access can see the expected posts, understand the purpose of the filter or controls, open any case study, and return to the collection without errors.

Responsive Layouts, Images, and Performance

Projectify displays existing posts, so image quality affects more than appearance. If ten cards load full-size, uncompressed images, no polished layout can make up for the wait. If an image contains important information that the title doesn’t explain, visitors lose that context when the image doesn’t load.

Use consistent image guidelines

Prepare images before publishing: use reasonable dimensions, compress them, give the files clear names, and add appropriate alt text to the posts. You don’t need to force every image into the same aspect ratio if your chosen layout handles different heights well. But aim for consistency: similar brightness, no incidental text, sufficient contrast, and no sensitive information in case study screenshots.

The showcase shouldn’t be the only place where visitors can learn what a project is about. The title, short caption, and case study page should make the content understandable even when images are disabled or the connection is slow. This also makes the content more resilient if you change the layout later.

Don’t treat mobile as a smaller desktop

On a narrow display, the way people browse may change. Cards become a vertical list, filters wrap onto another line, and a slider needs clear touch controls. Check Elementor’s available responsive preview modes, but don’t judge the page only by how it looks in the editor. Open the published page on an actual device or at least in a narrow browser window without developer tools.

If titles start getting cut off, first simplify the titles and check the container width. Don’t hide titles just to preserve large images. In a portfolio, the title is often the only text that explains why a project matters.

Cache and content changes

After replacing a featured image or editing a term, don’t assume Projectify failed to update the page. First make sure the post is saved and published. Then update the Elementor page, open it again, and clear the cache if your site uses one. If the issue persists in a private window after those steps, check the query rules or look for a conflict.

Update Without Breaking a Working Setup

The official Projectify listing publishes a changelog and recommends downloading the latest archive from the Downloads section, extracting the installation ZIP, and replacing the current version through the plugins area. Envato’s documentation also explains how to download updates. This is a standard process, but don’t treat an update as a "download and forget" task. Projectify depends on how its widget works with Elementor, your theme, taxonomies, and caching.

Record your setup before updating

Make a backup. Then note the URL of the showcase page, the selected post type, the visible terms, the display order, and one to three interactions to test. Take regular screenshots of the current page for your own reference. This doesn’t create new documentation, but it gives you clear checkpoints if settings or the layout change after an update.

If you have a staging site, update there first. If you don’t, choose a low-traffic period and don’t update WordPress, your theme, Elementor, Projectify, and your optimizer all at once. When five components change together, it’s hard to tell which one caused a problem.

What to do after installing an update

1. Check that Projectify is still active in Plugins > Installed Plugins.
2. Open the saved Elementor page and make sure the widget is still there and its main settings haven’t disappeared.
3. Open the public page and repeat the checks you recorded: the full collection, each term, links, arrows, and lightbox if you use them.
4. Clear the cache only after saving and running the basic checks, then repeat the test in a private window.
5. If the update causes a serious regression, restore the backup or previous working state according to your recovery process instead of editing the add-on’s files by hand.

The changelog mentions fixes for Elementor, taxonomies, arrows, translatable strings, and links in the lightbox. These updates show what to include in a regression test. They don’t mean a new version will necessarily cause an error. The right approach is to update with a backup in place and test the actions your page depends on.

Purchases, archives, and support

Don’t store or share account credentials, purchase codes, or archives in public page notes. Envato describes a purchase code as information from a license certificate used to verify a purchase and by certain author tools. The practical takeaway for this guide is to use the original archive from your own account and check the support terms on the product listing, since they may vary between marketplace items.

Practical Improvements Without Editing Core or Plugin Files

Projectify benefits most from good editorial habits, not complex customizations. Since we couldn’t find public documentation for the product’s specific extension points, don’t invent PHP hooks or copy random JavaScript. There are several safe, reversible steps you can take to improve the showcase.

Give editors a content checklist

Create a short internal guideline for every post that might appear in Projectify: a title within the chosen length, a featured image, a published link, one main term, and a checked excerpt. This isn’t a plugin setting, but it prevents the main cause of visual inconsistency. You can change the guideline without touching code or risking an update.

Give the block a clear place on the page

In Elementor, place the showcase after the introductory context instead of at the top of a page without explanation. Use a short heading and paragraph to introduce the topic, then show Projectify. You can also add a standard button or text link to the full archive if one exists. That way, the showcase is a curated selection rather than the only way to navigate the content.

Use Elementor’s built-in spacing controls

If cards sit too close to the surrounding text, first adjust the container’s margin and padding using Advanced in Elementor. There’s no need to edit Projectify or WordPress files just to change spacing. Check both desktop and narrow layouts after making the change, and restore the previous value if necessary. Rolling it back takes seconds and doesn’t depend on the add-on’s internal implementation.

An improvement is successful if it doesn’t make the page fragile. A clear layout with well-prepared posts is more likely to survive updates than a stack of undocumented changes layered over the plugin.

Troubleshooting Common Issues: From Symptoms to Safe Checks

A problem with the showcase doesn’t always mean Projectify is at fault. WordPress, Elementor, the theme, caching, optimization tools, editor permissions, and the browser all sit between the post and what visitors see. Troubleshoot the symptom you can observe. First record exactly what visitors are seeing, then check the nearest part of the setup that could explain it. Don’t change the sort order, styles, cache plugin, and theme all at once; that makes it harder to identify the cause.

The widget doesn’t appear in Elementor

Symptom: After installing Projectify, it doesn’t appear in the Widgets search, or Elementor reports an error. Likely cause: The add-on isn’t activated, Elementor is disabled, or the editor already has a conflict that appeared before the new widget was added.

What to check: Go to Plugins > Installed Plugins, find Projectify and Elementor, and make sure both are active. Then open a simple test page in Elementor without adding the new block. If the editor doesn’t work on a blank page, start with Elementor’s official basic troubleshooting steps: updates, a backup, and temporary checks for plugin and cache conflicts.

How to fix it: Restore Elementor, refresh the editor page, and search for the widget again. If WordPress showed an installation message, check that you selected projectify.zip rather than the full archive. When to roll back: If activating the add-on prevents you from accessing the editor, restore the backup or previous working state using your usual process. Don’t edit the plugin files by hand.

The page shows the wrong posts

Symptom: News, test pages, or old content appears instead of case studies. Likely cause: The selected source is too broad, or the posts aren’t organized with a consistent taxonomy.

What to check: In WordPress, open the list of posts that should appear and compare their post type and assigned terms with the items on the page. Then return to Projectify and check the available source, post type, and taxonomy filter. Don’t look for the cause in the card color or hover effect.

How to fix it: Choose the correct post type and assign the right terms to the posts themselves. Remove demo and outdated content from the source. When to roll back: If a complex selection rule has become hard to follow, switch temporarily to one simple source and one group, confirm that it works, and then add conditions one at a time.

A filter omits posts or fails with a multiword term

Symptom: Selecting a group makes cards disappear, shows the wrong number of items, or produces different behavior for a term with several words. Likely cause: Posts have different terms assigned, duplicate terms exist, the page is cached, or you’re using a version that needs an update for this case. Projectify’s changelog includes a specific fix for multiword category names in the masonry layout, so it’s worth checking deliberately.

What to check: Compare the term names in the WordPress post list, including spaces and similar variations. Then save the page, clear the active site cache, open it in a private window, and click the filter. Check not only the number of cards but also the name of a specific post that should appear.

How to fix it: Merge duplicate terms, assign the right term to each relevant post, and repeat the test. If the issue started after an update, check the changelog and archive version, then reproduce it on a staging site. When to roll back: If the problem breaks the live showcase after an update, restore a backup and gather details for the author instead of changing plugin files on the production server.

Changes appear in the editor but not for visitors

Symptom: The Elementor canvas looks right, but the public page shows an old selection, title, or image. Likely cause: The page wasn’t saved, visitors are seeing a cached copy, or the theme or optimizer is changing how resources load.

What to check: Save the page, open its regular URL in a private window, and clear the site cache using its built-in controls if available. Then compare the URL and content: sometimes the editor is changing a draft or a different page than the one linked from the menu. Check the source post too, to make sure it isn’t still a draft.

How to fix it: Make sure the page and posts are published, clear the cache, and check again. When to roll back: You don’t need to roll back if saving and clearing the cache fixes the issue. If it persists, disable optimization tools one at a time on a test copy and record what happens.

Arrows, slides, or the lightbox behave unpredictably

Symptom: Navigation works in only one direction, an image opens but the link to the case study isn’t clear, or the behavior differs between the editor and the live site. Likely cause: The interactive layout hasn’t been tested on the live page, conflicts with an optimization script, or needs an update to the components it depends on.

What to check: Move forward and back several times, close the lightbox, open a card, return, and repeat in a private window. Check keyboard focus and a narrow layout. Projectify’s changelog includes fixes for arrows, transitions, and the lightbox, so include these actions in your checks.

How to fix it: Temporarily switch to a simpler layout on a test page to separate source issues from interaction issues. Then check whether Projectify and Elementor are up to date, and look for cache or optimization conflicts. When to roll back: If the effect gets in the way of reaching the content, use a tested grid or another working layout until you can reproduce the issue and find a safe fix.

Cards feel cramped or titles are cut off on narrow displays

Symptom: The block looks fine on a large monitor, but captions overlap on a phone, images lose their context, or controls run off the edge. Likely cause: The container is too narrow, titles vary too much in length, cards contain too much text, or the layout isn’t suited to the number of items.

What to check: Open the published page at a narrow width, look at several cards in a row, and test the links. Check Elementor’s available responsive settings for the container and widget. Don’t judge the layout only on the static canvas.

How to fix it: Simplify editorial titles, increase the available width, show fewer items, or choose a more suitable layout. When to roll back: If a spacing change makes the desktop version worse, restore the previous value and look for a solution in the container setup or post content.

When Projectify Is a Good Fit

Projectify makes sense when your site already has useful WordPress posts and you need a polished, manageable way to display them in Elementor, not a new content type. The strongest results come from teams that prepare the source first: organize images, titles, links, and taxonomies, choose a clear display style, and test it on the published page.

If you can answer "Which posts will visitors see?", "How can they narrow down the collection?", and "Where will each click take them?", you have a solid foundation. From there, get the installation archive, create a test page, and build your first working block. Once you’ve prepared the content, you can download CodeCanyon Projectify and test the setup on a copy of your site without putting the live showcase at risk.

Don’t make the block more complex than the task requires. A clean collection of case studies with a predictable filter, readable cards, and reliable links is more useful than an impressive setup that’s hard to test and maintain. A visitor journey you can verify matters more than decorative complexity.