RokSprocket - WordPress Plugin

RokSprocket for WordPress: setting up post showcases, layouts, and filters

RokSprocket is useful when a standard WordPress post list is no longer enough: you need to pull content by rules, pin key items manually, and display them as a slider, mosaic, tabs, a compact list, or a news block. This guide focuses not on a promotional overview of the plugin, but on practical use: preparing the site, installing the ZIP package, choosing a content source, setting up filters, selecting a display mode, and checking the result on the live front end.

There is an important caveat with RokSprocket: it is an older RocketTheme product, and it should be treated as a tool for careful testing, not as a modern block builder. Official pages confirm support for the WordPress provider, the Simple Provider, multiple display modes, filters, sorting, and shortcodes, but current compatibility with newer environments should not be taken for granted. That is why this guide pays close attention to testing on a site copy, diagnosing empty blocks, dealing with images, cache, and theme conflicts.

This article is a good fit for a site owner, webmaster, or editor who inherited a RocketTheme/Gantry site, wants to restore an older homepage, display a curated set of content in a visual block, or decide whether RokSprocket is still worth keeping instead of switching to a modern block, post grid, or slider.

When RokSprocket is useful for displaying content

The main idea behind RokSprocket is not just to show the latest posts. The plugin creates a separate showcase instance: you choose a source, set filters, configure the order, override individual titles, images, and links, and then decide how the result should be displayed. This is especially useful for sites where the editor wants control over the "above the fold" area or a recommendations block without editing templates.

RokSprocket is especially well suited to magazine, news, portfolio, and promo pages, where the same content needs to be presented in different ways: a large slider at the top, a category mosaic below, tabs with themed selections in a sidebar, or short headlines from recent posts in the footer.

What it does better than the standard Recent Posts widget

The default recent posts block works well when a simple list is enough. RokSprocket becomes more useful when the block needs editorial logic. For example, you can manually add specific items, combine them with a category filter, use manual ordering for the first cards, and still allow new posts to fill in automatically. For visual content blocks, not only titles matter, but also images, summaries, links, limits, animation, and behavior on smaller screens.

• For a main promo block, Features is a strong choice when image, title, text, link, arrows, pagination, and autoplay matter.
• For categories, portfolios, and tag-based showcases, Mosaic works well because it builds a tiled layout and lets visitors sort or filter by tags.
• For compact navigation, you can use Tabs, Lists, or Headlines if the block needs to take up less space.
• For manual cards without a separate WordPress post, the Simple source is a good fit because the content is created directly inside RokSprocket.

Who this plugin may not be right for

RokSprocket is not something to choose just because you want "a nice-looking block." If the site is already built with the block editor, Elementor, a modern theme with Query Loop support, or an active post grid solution, a new project is better off starting with a supported option. RokSprocket makes sense when you are maintaining an existing RocketTheme site, migrating an older structure, trying to preserve familiar Features or Mosaic layouts, or testing an archived product on a separate copy.

The key reality check before deciding: if you cannot quickly roll back the installation, clear the cache, disable a conflicting plugin, and restore the page from a backup, do not install RokSprocket directly on the live site.

What to check before installing an older RocketTheme plugin

Preparation matters more than the installation itself. Official materials describe RokSprocket as a plugin for WordPress 5.x and reference the wp_roksprocket.zip package. RocketTheme's compatibility matrix shows an older plugin branch. That does not automatically mean it will break on your site, but it does mean you should test it like a legacy product: separately, with logs, with a backup, and without assuming full compatibility.

Before installation, make a quick map of the site: which theme is active, whether Gantry is being used, whether caching or optimization is enabled, and which plugins affect images, shortcodes, AJAX, widgets, and the block editor. The more layers you have, the more carefully you need to test.

RokSprocket pre-installation checklist

What to check	Why it matters	How to handle it safely
A site copy	The plugin affects content output, styles, scripts, and widgets.	Install it on a staging copy or temporary domain first, not on the live page.
WordPress and PHP versions	Official compatibility refers to an older WordPress branch, and newer PHP versions may trigger warnings.	Check the error log after activation and again after opening a page with the widget.
ZIP package source	For older commercial and club products, it is risky to use archives from untrusted sources.	Use only your own verified archive or an official source, if one is available.
RokCommon and RocketTheme dependencies	In the RocketTheme ecosystem, some functionality may have depended on a shared library and theme.	Compare the plugin set from the older site and do not blindly update them one by one.
Cache, minification, lazy loading	RokSprocket relies on a dynamic interface and front-end scripts.	While testing, disable script bundling, lazy loading, and aggressive caching for the test page.

Why a staging copy is mandatory

The installation may complete without errors, but the real problem can show up later: the showcase instance may fail to save, a filter may not find any posts, images may come up empty, the grid may break in a narrow column, or an AJAX request in the admin panel may get an unexpected response from cache or server-side security. Those symptoms are hard to troubleshoot calmly on a live site. On a copy, you can enable debug mode, temporarily disable cache, and test for theme conflicts without risking the visitor experience.

What you should not assume

Do not treat RokSprocket as a modern block-based solution if your version does not include a dedicated editor block. Do not promise editors that every mode will work the same way in every theme. Do not assume WordPress.org auto-updates exist if the plugin was installed from a RocketTheme ZIP package. It is better to describe the plugin upfront as a tool for a tested integration, not as a universal replacement for your current post grids.

Installing the ZIP package and enabling it for the first time in the admin panel

The official WordPress documentation describes installation by uploading the wp_roksprocket.zip archive. The overall flow is the same as with any manually installed WordPress plugin from ZIP: open the add plugins screen, upload the archive, install it, then activate it. The key difference is that after installation, you should not immediately place the block on the homepage. First, create and save a separate RokSprocket instance.

Basic installation sequence

1. Open the staging copy of the site and sign in to the admin panel with administrator access.
2. Go to Plugins - Add New - Upload Plugin.
3. Select the wp_roksprocket.zip archive and click Install Now.
4. After the successful installation message appears, click Activate Plugin.
5. Check whether the RokSprocket menu or its management screen appears.
6. Open the installed plugins list and make sure there are no obvious PHP warnings or dependency messages.

If the plugin was already installed on the site and you are replacing files, be more careful. RocketTheme documentation warns that deleting it through the plugin manager and reinstalling it can lead to lost settings. In practical terms, that means: back up files and the database first, deactivate the plugin, replace the files in a way that does not wipe saved settings, and only then verify the instances.

Initial check after activation

After activation, do not start with the homepage. Create a temporary instance using the simplest possible source and a limit of just a few posts. If the interface saves settings, the content list loads, and the test page displays the block without errors, you can move on to the real setup. If buttons like Save, Apply, or content selection do not work even at this stage, the problem is almost certainly not the layout. It is far more likely to be admin-side JavaScript, AJAX, a plugin conflict, server cache, or an outdated dependency.

Mini-test after installation: create a RokSprocket instance with one simple filter, Status = Publish, save it, refresh the admin page, and confirm that the selected settings are still there.

How RokSprocket gathers content: providers, Simple items, and WordPress posts

The most common RokSprocket setup mistake is choosing a nice-looking display mode before understanding the source. In this plugin, the first question is where the block items come from. For WordPress, the official documentation lists several providers: WordPress, CFS, CPT, Types, Simple, and PostTypes. Not all of them are equally relevant on every site, so it is best to start with two straightforward scenarios: regular WordPress posts or manual items through Simple.

The WordPress provider for dynamic selections

The WordPress source is the right choice when the block should pull real posts, pages, attachments, or other supported content types. Filters are the main tool here: category, tag, status, author, date, post type, keywords in the title or content. This source works well for news, blogs, knowledge bases, content libraries, and sections where new content should appear in the block automatically.

The advantage of a dynamic source is less manual work after setup. The downside is that you need tight control over the rules. A filter that is too broad will fill the showcase with random content, while one that is too narrow will give you an empty block. For the first pass, add filters gradually: start with published posts, then the target category, then a tag or date, and finally sorting.

The Simple Provider for manual cards

The Simple source is useful when you do not want to create separate WordPress posts just for a homepage block. For example, you may need four service cards, three banners, a set of links to external pages, or a group of promo items with custom images. In that scenario, the content lives inside the RokSprocket instance rather than in the site's main post list.

This works well for small showcases, but not for large archives. If you try to maintain dozens of items manually through the Simple Provider, the editor will quickly lose control: the content will not participate in the normal site structure, and it becomes harder to search, move, and reuse. For a regularly updated blog or news section, it is better to use WordPress posts plus filters.

Providers for custom post types and older CCK tools

The CPT, Types, CFS, and PostTypes providers relate to setups where the site uses custom post types or custom fields. In older RocketTheme projects, this could be useful for portfolios, catalogs, testimonials, or services. But on a modern site, you cannot simply turn on one of these sources and expect it to work. You need to confirm that your post type is actually visible to the plugin, that image and link fields are being picked up correctly, and that filters are not excluding the items you need.

How to choose a content source

Source	When to use it	What to check
WordPress	For posts, pages, and dynamic selections that should update along with the site.	Publication status, category, tag, post type, and sort order.
Simple	For manual cards, banners, promo blocks, and small curated groups without a separate post.	Title, description, image, link, and manual order.
CPT and PostTypes	For custom post types, if they exist on the site and are supported by your build.	Post type visibility in filters, plus image, link, and text fields.
CFS and Types	For older sites where those tools were already used for extra fields.	Installed version compatibility, field value accuracy, and the absence of empty images.

Filters and sorting: how to build a controlled selection

Filters in RokSprocket work like an editorial sieve: they decide which items make it into the list before display. According to the official documentation for the WordPress provider, you can filter by title, slug, content text, tag, status, category, post type, parent page, dates, author, comment count, and password-protected status. That is powerful, but it is also where empty blocks are most often created.

Start with a broad rule and narrow the selection step by step. If you immediately set category, tag, author, and date, you will not know which condition excluded the posts. A safer approach is to start with Status = Publish, then add the category, review the list, and only then add a tag or post type.

Selecting specific items

The specific post selection tool is useful for blocks where the editor needs to pin important content. For example, the homepage may need to show three chosen articles regardless of publication date. One nuance matters here: manually selected items do not fully replace filters. If you add a filter, RokSprocket may still pull in additional posts that match the conditions. That is why you should review the final item list after every change, not just the settings panel.

Layered filters

Filters can refine each other. For example, first show only published posts, then only posts from the "Reviews" category, then only content with the required tag. The result becomes more precise, but the risk of an empty selection goes up. If the list becomes empty, remove rules in reverse order and see at which step the items reappear.

Automatic, Manual, and Random

Sorting comes after filtering. Automatic works well for news blocks, where the order is driven by date, title, author, or another field. Manual is better for a homepage, where the editor needs to arrange key items personally. Random can work for small recommendation blocks, but use it carefully: random order makes result validation harder and can conflict with cache when the page is expected to look predictable.

How to choose a sorting method

Mode	Where it fits	What to check
Automatic	Fresh news, updated categories, category-based feeds.	The sort field and direction, so older posts do not accidentally appear above newer ones.
Manual	Homepage blocks, editor's picks, promo sections.	That new posts do not disrupt the manual order of the first items.
Random	Small recommendation blocks where order is not critical.	Cache behavior, duplicate prevention, and whether the result is still understandable to the editor.

If RokSprocket is showing extra content, it is almost always useful to temporarily simplify the filters to a single condition and rebuild the rules one by one.

How to choose a display mode: Features, Mosaic, Tabs, Lists, and more

The display mode in RokSprocket controls not only the visual style, but also the set of available settings. The documentation emphasizes that each mode has its own global parameters and per-item parameters, and the admin panel only shows options relevant to the selected mode. That means you cannot configure Features and then expect Mosaic to behave the same way.

Features for a hero slider and featured showcase

Features works well when you need to highlight a few items in a large format: image, title, short text, link, arrows, pagination, animation, and autoplay. It is a strong mode for the above-the-fold area, promo content, top stories, or a "recommended" selection. The key settings here are limit, excerpt length, title display, HTML stripping, default image, and autoplay delay.

Mosaic for tiles, portfolios, and category blocks

Mosaic displays content as blocks and can use tags, columns, number of blocks on load, animation, and ordering. It is one of the most distinctive RokSprocket modes. It works well for portfolios, article collections, content galleries, service catalogs, or sections where visitors should be able to scan several cards quickly.

Tabs, Lists, and Headlines for compact navigation

These modes work best when space is limited. Tabs help display several themed groups without creating a long page. Lists work well in a sidebar or lower content block. Headlines makes sense for short news titles, especially when visitors need a quick path to fresh content.

Grids, Tables, Sliders, and Quotes

These modes should only be enabled when they genuinely solve the problem. A grid is useful for evenly sized cards. A table layout can help with structured data, but it should not replace a proper HTML table where accessibility matters. Sliders and quote layouts can work for standalone visual sections, but they need testing for speed, keyboard navigation, and mobile behavior.

Choosing a mode by use case

Use case	Best-fit mode	Main check
Above-the-fold area with featured content	Features	Image, text, link, arrow controls, and autoplay.
Portfolio tiles or a themed showcase	Mosaic	Columns, tags, number of blocks, and loading additional items.
Compact navigation across several items	Tabs or Lists	Title readability, tab behavior, and the absence of overflow.
Short news feed	Headlines	Item order, headline length, and links to posts.

Configuring Features and Mosaic without unnecessary mistakes

The most practical RokSprocket use cases in WordPress usually revolve around Features and Mosaic. The first creates a prominent showcase block, the second builds a tiled layout with cards and tags. Their settings are different, but the logic is the same: first source and filters, then item parameters, then display mode, then publishing through a widget or shortcode.

Features: image, text, link, and autoplay

For Features, start with a small limit. If you display too many slides, visitors will not see most of them anyway, and the block becomes heavier. Check Article Titles, Article Text, Preview Length, Strip HTML Tags, Arrow Navigation, Pagination, Animation, Autoplay, and Autoplay Delay. For a typical promo block, it is better to keep navigation clear and avoid overly fast slide transitions.

Check image and link fields separately. If a post has an unsuitable featured image, you can override it at the RokSprocket item level. This is especially useful on the homepage: the editor does not change the post itself, but sets a different image specifically for the showcase.

What to check after saving Features

• Slides can be changed manually, not only automatically.
• The button or title leads to the correct item.
• The image is not stretched and does not crop out the important part of the frame.
• The summary text does not overlap the arrows, pagination dots, or the title.
• With Autoplay turned off, the block does not throw an error in the browser console.

Mosaic: tags, columns, and Load More

Mosaic is useful because it turns content into a controlled tile layout. Key settings include Theme, Display Limit, Columns, Preview Length, Only Show Tags, Strip HTML Tags, Blocks Per View, Article Details, Block Animation, Ordering, and Image Resize. Do not turn on every effect at once. First make sure you have the right set of cards, then add tag filters and animation.

If Load More is enabled, make sure it does not reload items that were already shown. If the block appears on a cached page, random sorting can make validation harder. In that case, temporarily switch to a predictable order, clear the cache, and only return to the desired mode after the result is stable.

How to choose the number of columns

The number of columns should match the width of the area where you place the widget. For a wide homepage section, you can test multiple columns. For a sidebar, it is usually better to use a compact mode or a different layout. If the theme already defines its own grid, RokSprocket may end up inside a container that is too narrow, which can make the cards wrap awkwardly.

Do not try to fix a broken Mosaic grid with random CSS tweaks before checking column settings, widget area width, and cache. CSS should only come into play after the block's core logic is working correctly.

Placement on the site: widget, shortcode, and theme position

Creating a RokSprocket instance is not enough. You still need to display it on the page. The official product page mentions support for module shortcodes, and RocketTheme theme documentation commonly shows the widget-based workflow: create a RokSprocket instance, then add the widget to the right position and select the block you created. On a WordPress site, that location depends on the theme: a classic sidebar, homepage area, footer, custom widget area, or the block-based widgets editor.

The widget as the primary path

If the site is built on a RocketTheme/Gantry theme, start with the widget. Those themes often have their own positions, overrides, and demo areas. The problem "RokSprocket is configured but not visible" often simply means the instance was assigned to the wrong position, the current override hides that position, or the widget was added to an area that is not rendered on that page.

1. Create a RokSprocket instance and save it under a clear internal name.
2. Open Appearance - Widgets or your theme's widget management screen.
3. Add the RokSprocket widget to the target area.
4. In the selection field, choose the instance you created instead of blindly creating a new one.
5. Save the widget and open a page where that area is actually rendered.

The shortcode for a page or block

A shortcode is convenient when you need to insert the showcase inside a page, a post, or a template where a widget area does not fit. But shortcode syntax depends on the installed version and the instance, so you should not type it from memory. Use the shortcode shown by RokSprocket itself, and place it inside a Shortcode block, not in a normal paragraph. If the shortcode appears as plain text, check whether the plugin is active and whether the code was inserted into a field that does not process shortcodes.

Checking the theme and output area

A theme may have several templates: homepage, archive, single post, page, shop page, landing page. A widget area visible on one page may be missing on another. That is why after adding RokSprocket, you should check not only the homepage, but also the page where the block is expected to work consistently. If the theme uses cached templates or its own builder, clear both the theme cache and the browser cache.

Where to display a RokSprocket instance

Output location	When it is convenient	Typical mistake
The theme's widget area	For a homepage, sidebar, footer, or RocketTheme positions.	The widget was added to an area that is not rendered by the current template.
Shortcode on a page	For manual insertion inside content or a landing page.	The shortcode was inserted into a paragraph, HTML block, or field where it does not run.
Builder template	For sites where pages are assembled in a separate visual editor.	The builder processes the shortcode earlier or later than the plugin expects.

Practical scenario: a magazine-style homepage

Imagine a content-driven site where the homepage needs to show three zones: a large featured articles block, a category mosaic, and a short feed of recent posts. This is a strong RokSprocket scenario because it uses different display modes for different tasks instead of trying to solve everything with one slider.

Goal

Create a homepage where the editor can manually pin important content at the top, automatically display posts from several categories in a tiled layout, and show a short list of new posts below or in the sidebar. At the same time, every block should be easy to verify: it should be clear why a post appeared in the showcase, in what order it is displayed, and where its link goes.

Preparation

Before configuration, prepare the posts: add featured images, fill in titles, and check categories and tags. For the main slider, choose items with strong visuals. For the mosaic, make sure tags are not just duplicating categories without adding value. For the headline feed, decide whether you need manual ordering or if date-based sorting is enough.

Setup steps

1. Create a Home Features instance with the WordPress source and manually add 3 to 5 key items.
2. Select the Features mode and enable the title, summary text, link, and clear arrow navigation.
3. Create a Home Mosaic instance, add a filter for the target categories, and enable tags if visitors need sorting.
4. Configure Columns, Blocks Per View, and Ordering, then make sure cards are not repeated.
5. Create a third instance in Headlines or Lists for recent posts with a simple filter, Status = Publish.
6. Add each instance to its own widget area or insert them as shortcodes on a test page.

Validation

Open the page in incognito mode so you see it like a regular visitor. Check that the top block shows the selected items, the mosaic filters by the expected tags, and the headline feed does not display drafts. Then change one test post: replace the featured image, category, or tag. If the block is supposed to update automatically, the change should appear after clearing the cache. If the block is manual, the post should not appear unless you choose it.

A nuance that often gets in the way

If the homepage uses a separate theme setting, the widget may be added to the correct area but not to the correct override. On RocketTheme/Gantry sites, this is especially important: the homepage may use a dedicated layout different from regular pages. Check the exact template that serves the homepage, not just the general widget list.

Checking the result after setup

You cannot validate RokSprocket only from the admin panel. There you can see that the instance is saved and the content list was found, but you cannot see how the block behaves in the theme, how images load, whether text overlaps the arrows, whether cache breaks AJAX, or whether the shortcode prints plain text instead of the showcase.

Front-end validation

• Open the page as a guest and make sure the block is visible without signing in to the admin panel.
• Check every link: the title, image, and button should go where the editor expects.
• Compare the item order to the configured sort settings.
• Check images in the browser console: there should not be widespread 404 errors.
• Open the page at both wide and narrow window widths to see how columns and tabs wrap.
• Clear the page cache and repeat the check as an anonymous visitor.

Editor workflow validation

Ask the editor to perform one real task: add a new item to a category, replace an image in a RokSprocket item, swap the order of two cards, or hide the text for one slide. If the editor cannot understand where that is done, the setup is too complex for ongoing use. In that case, it is better to simplify the mode, reduce the number of instances, or choose a modern alternative with a more intuitive editorial interface.

Performance and accessibility check

Visual showcases almost always add styles, scripts, and images. With RokSprocket, this matters even more because older display modes can conflict with modern optimization tools. Check whether images are too large, whether autoplay makes the text harder to read, and whether links can be clicked without precise targeting of tiny controls. A visually appealing block should not make navigation or reading the site's main content worse.

Common RokSprocket issues: empty block, images, Mosaic tags, and older PHP versions

It is best to troubleshoot RokSprocket from simple to complex. First check whether the instance was created, whether a source is selected, whether matching content exists, whether the widget is published, and whether the theme is hiding it. Then move on to the browser console, AJAX requests, cache, plugin conflicts, and server logs. Do not start by editing plugin files: that almost always makes support harder and rollback more complicated.

Typical symptoms and safe checks

Symptom	Possible cause	What to check and how to fix it
The block is empty	No filter, a filter that is too narrow, or the wrong status or post type is selected.	Leave only one filter, Status = Publish, make sure the posts are published, then add the other conditions back one at a time.
The widget does not appear on the page	The instance exists, but the widget was added to the wrong area or the needed theme override is not active.	Check Appearance - Widgets, the selected instance, and the page template where the area should be displayed.
The shortcode is displayed as text	It was inserted into the wrong block or into a field that does not execute shortcodes.	Use a Shortcode block, check that the plugin is active, and verify the exact syntax shown in the RokSprocket interface.
The save button does not work	A JavaScript error, AJAX issue, conflict with another plugin, server cache, or an outdated dependency.	Open the console and the Network tab, inspect requests to admin-ajax.php, and temporarily disable cache and conflicting plugins on the site copy.
Images do not display	An incorrect image field, missing featured image, old path after migration, or a media processing conflict.	Reassign the image in the item, check the post thumbnail and 404 errors, and do not perform a mass URL replacement without a backup.
Mosaic repeats items or loads cards strangely	Cache, random sorting, older AJAX issues, or multiple mosaics on the same page.	Disable Random while testing, clear the cache, and check a single instance on a separate page.
PHP warnings appear	The plugin or dependency was not designed for the current environment version.	Test on a site copy, review the error log, do not try to hide fatal issues with CSS, and plan a replacement if the warnings interfere with normal use.

Safe CSS fix for narrow areas

CSS only makes sense after the block is correctly selecting content and rendering on the page. If the problem is visual, such as cards overflowing a narrow area, images stretching, or text breaking the layout, you can add a reversible tweak in Appearance - Customize - Additional CSS or in a child theme. Do not edit files inside the plugin folder.

/* RokSprocket: keep layouts inside narrow widget areas */
.widget_roksprocket,
.sprocket-features,
.sprocket-mosaic,
.sprocket-tabs,
.sprocket-strips,
.sprocket-grids,
.sprocket-lists {
  max-width: 100%;
  box-sizing: border-box;
  overflow-wrap: break-word;
}

.widget_roksprocket img,
.sprocket-features img,
.sprocket-mosaic img,
.sprocket-tabs img,
.sprocket-strips img,
.sprocket-grids img,
.sprocket-lists img {
  max-width: 100%;
  height: auto;
}

After adding the CSS, check only the block you are trying to fix. If the whole page changes or the tabs stop working, remove the tweak and return to the display mode settings. For mobile layouts, you can test card stacking separately, but only after verifying the selectors in developer tools.

/* RokSprocket: stack dense item layouts on small screens */
@media (max-width: 767px) {
  .widget_roksprocket .sprocket-mosaic-item,
  .widget_roksprocket .sprocket-grids-item,
  .widget_roksprocket .sprocket-strips-item {
    width: 100%;
    max-width: 100%;
    float: none;
    clear: both;
  }
}

This tweak is safe because it is easy to remove. It does not alter data, does not call internal RokSprocket functions, and does not depend on the database structure. But selectors may vary in a specific theme, so before using it on a live site, test it on a staging copy.

RokSprocket setup and validation FAQ

Can RokSprocket be installed on a new WordPress site?

Yes, but only after testing on a site copy and understanding the risk. Official materials confirm an older compatibility branch, but they do not justify promising trouble-free operation in every modern environment. For a new project, it is often more reasonable to start with a supported block or a post grid plugin.

Do you need a RocketTheme or Gantry theme?

RokSprocket is described as a WordPress plugin, but many real-world workflows and RocketTheme demos rely on theme positions and widgets. The block may work without a RocketTheme theme, but styles, output areas, and visual alignment with the demo need to be checked separately.

How is the Simple Provider different from WordPress posts?

Simple stores manual items inside RokSprocket and works well for small promo cards. The WordPress source pulls real posts and is better for updated categories, news, and archives. If the content should live as regular site publications, choose the WordPress provider.

Why does the block not show posts even though they exist on the site?

Most often, the filter is too narrow, or the wrong status, category, post type, or author is selected. Start with one condition, Status = Publish, make sure the list appears, then add the remaining rules one by one.

What should you do if the shortcode does not work in the block editor?

Insert it into a Shortcode block, not a regular paragraph. Check that RokSprocket is active, that the shortcode was copied correctly from the plugin interface, and that the page is not being rendered by a template that does not process shortcodes.

Why are images in Features or Mosaic empty?

Check post thumbnails, item-level image overrides in RokSprocket, file paths after migration, and 404 errors in the browser. If the site was moved, inspect the media library and URLs first instead of changing settings across all instances at once.

Is it worth enabling Random sort?

For small recommendation blocks, it can be fine, but for a homepage and editorial showcases that need to be validated, manual or automatic order is better. Random sorting makes troubleshooting harder, especially when cache is enabled.

Can RokSprocket be fixed through PHP or JavaScript?

Not without precise documentation for its internal functions. It is safer to use the plugin settings, widget area, shortcode, or CSS in a child theme or Additional CSS. PHP or JavaScript edits inside the plugin can break when files are replaced and make rollback more difficult.

When RokSprocket is a good choice

RokSprocket is worth using if you already have a site built on the older RocketTheme ecosystem, need to restore or maintain existing content showcases, and the editor depends on modes like Features, Mosaic, Tabs, Lists, and filters without editing templates. The plugin can also be useful for careful testing on a site copy when you need to quickly assemble a controlled block from posts or manual cards.

Do not choose it blindly for a new project where current support, a block-based interface, modern compatibility, and long-term updates matter. In those cases, check Query Loop, Content Views, The Post Grid, Smart Slider 3, MetaSlider, or another solution that matches your needs more closely.

If this approach to displaying content fits after your compatibility checks, you can move on to get the WordPress version and test the plugin on a site copy. Make the final decision only after checking sources, filters, display mode, widget position, mobile rendering, and cache behavior.

A good setup result is not just a visible slider, but a clear editorial system: you know where the content comes from, why it appears in the block, how the order changes, what the visitor will see, and how quickly you can roll back changes if the selected mode does not work out.