Welcome to the NZRT Wiki Podcast. Today we’re looking at Featured Image Plus.

If you’ve spent any time managing a WordPress site, you’ve probably run into the limitations of the default featured image system. It works, but only just. You get one image, one size, and very little control over how it gets cropped or displayed across different parts of your site. Featured Image Plus is a WordPress plugin that steps in to fix exactly that problem, and at NZRT we use it to keep our media management consistent and efficient across the board.

So let’s start with what the plugin actually does, and then we’ll walk through how we use it specifically at NZRT.

The first thing Featured Image Plus adds is support for multiple crops. By default, WordPress generates a handful of image sizes when you upload a photo, but you don’t have much say over how those crops are defined or how they apply to featured images specifically. With Featured Image Plus, you can define multiple featured image sizes tailored to wherever those images are going to appear. That means a hero banner, a thumbnail in a post grid, and a social share preview can all pull from the same source image but get their own perfectly cropped version. You define the sizes once, and the plugin handles the rest.

Next up is Quick Edit support. If you’ve ever needed to swap out a featured image on a post, you know that the default workflow sends you into the full post editor just to make that one change. With Featured Image Plus, you can edit the featured image directly from the posts list view. You hover over the post, hit Quick Edit, and you’re done. No need to open the full editor, save, and navigate back. For day-to-day content management, this saves a surprising amount of time.

Related to that is Bulk Edit. If you’ve ever had to update featured images across a large number of posts at once, you’ll appreciate this one. Whether you’re rebranding, cleaning up old content, or switching image sets after a campaign, you can select multiple posts and change their featured images in one go. No clicking through post after post.

The plugin also includes an Image Resizer, which automatically crops your uploaded images to the optimal dimensions for each defined size. So instead of you manually resizing images before uploading them, the plugin takes care of that step. You upload once, and it generates the right crop for every context you’ve set up.

Finally, there’s Gallery Support. This one’s a bit different. If a post doesn’t have a dedicated featured image set, Featured Image Plus can pull an image from an embedded gallery within that post and use it as the featured image automatically. This is handy for image-heavy posts where the gallery content is the main visual.

Now let’s talk about how we actually use this at NZRT, because the plugin’s value is in how you configure it, not just that you install it.

One of our primary use cases is defining a standard featured image size for SmartSlider. If you’ve heard our episode on SmartSlider 3 Pro, you’ll know it’s the slider tool we use across the site. SmartSlider pulls featured images as slide backgrounds, and it needs images at a specific aspect ratio to look right. Featured Image Plus lets us lock that size in so every featured image is automatically cropped to work perfectly in the slider without any manual intervention each time someone publishes a post.

We also use it for product images. When product photos are uploaded, Featured Image Plus auto-crops them to our standard product dimensions. That keeps the product grid visually consistent without requiring whoever is doing the upload to think about sizing.

Another thing we’ve set up is a default image fallback for posts that don’t have a featured image assigned. Instead of a blank space or a broken layout, the site automatically shows a defined default. This is particularly useful for older content or imported posts that might not have had featured images attached in the original source.

Speaking of imports, the Bulk Edit feature comes into its own during content migration. When we bring in posts from another system, they often come in without featured images or with images that need to be swapped out. Being able to select a batch of imported posts and apply the right featured image across all of them in one action is a genuine time-saver during those migration workflows.

So to summarise, Featured Image Plus gives you multi-size crop control, faster editing from the posts list, bulk image management, automatic resizing on upload, and gallery fallback support. At NZRT, we’ve wired it into our SmartSlider setup, our product catalogue, our default image configuration, and our import processes. It’s one of those plugins that quietly does a lot of heavy lifting once it’s configured properly.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at JC Importer.

JC Importer is a utility plugin for WordPress, and at NZRT we use it whenever we need to bring in large amounts of data without doing it all by hand. Specifically, it gives you the ability to import posts from CSV files, create users in bulk, map your data columns to the right WordPress fields, preview what you’re about to import before you commit to it, and catch duplicate entries before they cause problems. Those five capabilities cover most of the heavy lifting you’d ever need to do when populating or updating a WordPress site with external data.

So how does it actually work in practice? The process runs in five steps, and they’re pretty straightforward. First, you upload your CSV file into the plugin. Second, you tell the plugin how your columns match up to WordPress fields — so for example, which column in your spreadsheet is the post title, which one is the content body, which one is the author, and which one holds the category. Third, and this is the part that saves a lot of headaches, you run a preview. It shows you a sample of five rows so you can confirm everything is mapped correctly before anything actually gets written to the database. Fourth, once you’re happy with how it looks, you execute the full import. And fifth, you go through the results and check the error log to see if anything didn’t make it through cleanly.

Now, why does NZRT actually reach for this tool? There are four main situations where it comes in handy for us. The first is when we’re pulling product listings out of Dolibarr — our ERP system — and we need to get those into WordPress in one go rather than entering them one by one. The second is when we need to create a whole set of pages for module categories in bulk. The third is when HR data needs to come across into WordPress, like employee information that originates in Dolibarr’s HR module. And the fourth is when we need to update pricing and product descriptions across a large number of entries at once — again, doing that manually would take far too long.

The common thread across all of those use cases is that you’ve got structured data living somewhere outside WordPress — usually in a spreadsheet or a Dolibarr export — and you need a reliable, repeatable way to get it into the site without risking errors from manual entry or wasting time on repetitive copy-paste work.

If you want to dig deeper into the broader context around this plugin, there are a few related wiki notes worth checking out: the Plugins Overview, the WordPress Overview, and the NZRT Site Overview. Those will give you a fuller picture of how JC Importer fits into the wider stack.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at Menu Icons.

If you’ve ever visited the NZRT website and noticed those clean, recognisable symbols sitting beside each navigation link, you’ve already seen Menu Icons in action. Today we’re going to walk through what the plugin does, how it’s set up, and why NZRT uses it the way it does.

So first, what is Menu Icons? It’s a WordPress plugin that adds icon support to your menu items. Out of the box, WordPress menus are just text links. Menu Icons layers on top of that and gives you the ability to attach a visual icon to any item in your navigation. NZRT uses it specifically for the primary menu and for module page links, giving the site a more visual, icon-based navigation feel rather than relying on text alone.

Let’s talk about what the plugin actually brings to the table. It ships with over one thousand icons drawn from two popular icon libraries — Font Awesome and Icomoon. That’s a substantial library, so you’re unlikely to run out of options for whatever navigation concept you’re trying to represent. Alongside the icon library, there’s a built-in icon picker that lives right inside the WordPress menu editor. So when you’re setting up or editing your menu, you don’t need to leave the screen or fiddle with code — you just click, browse, and pick the icon you want.

Beyond simply attaching an icon, you also have control over how that icon looks. You can set a custom colour for each icon, which is important for NZRT’s approach. You can also configure the size of the icon, so it fits proportionally with your menu text and overall layout. And there’s tooltip support as well — meaning if a visitor hovers over an icon, you can display a short explanatory label, which is handy for accessibility and clarity, especially if the icon is being used without visible text beside it.

Now let’s look at how NZRT actually sets this up. The process happens inside the WordPress admin area, in the menu management section. The first step is adding your menu items — these are the different modules or sections of the site, things like Customer, Sales, Finance, and so on. Once your items are in the menu, you go through each one and select the appropriate icon using that built-in icon picker we just mentioned. The key instruction here is to use the module colours when making your icon choices. So when you’re picking an icon for Finance, for example, you’d set the icon colour to match the Finance module’s brand colour. The same goes for every other module. Finally, you configure the tooltip text for each item — that’s the little label that appears on hover.

That colour-matching rule is worth pausing on, because it reflects a deliberate design decision. Rather than having a navigation bar full of icons in a single default colour, NZRT maps each icon’s colour to the visual identity of its corresponding module. This means that when you’re looking at the menu, you’re not just reading text labels — you’re also getting a colour signal that matches what you’ll find when you land on that module’s pages. It’s a small touch, but it creates a more cohesive visual experience across the site.

Speaking of those modules, let’s run through what’s actually in the NZRT primary navigation. There are six main items using icons. You’ve got Products, Customer Management, Finance, HR, Suppliers, and EDM. Each of those has its own icon and its own colour pulled from the corresponding module’s brand palette. Together they make up the icon-based navigation that visitors use to move around the NZRT site.

The reason NZRT leans into this icon-first approach comes down to user experience and visual module association. Icons give users an immediate visual cue that helps them orient themselves quickly. Rather than scanning through a list of text labels, visitors can pick up on the icon and colour combination and navigate more intuitively. For a site that covers multiple business modules — each with its own identity — that visual differentiation is genuinely useful.

If you want to dig deeper into how this fits into the broader site structure, there are a few related areas worth reading. The Page Structure and Navigation doc covers how pages are organised and linked together. The NZRT Site Overview gives you the big picture of how all the pieces of the site connect. And the Plugins Overview is a good place to see where Menu Icons sits alongside the other tools in the WordPress setup.

So to recap — Menu Icons is a straightforward but effective plugin that brings icon selection, colour control, sizing, and tooltips into your WordPress menu editor. NZRT uses it to give the primary navigation a visual, module-aware feel, with icons and colours matched to each section of the site.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at Pages with Category & Tag.

If you’ve spent any time working with WordPress, you’ll know that out of the box, the platform treats posts and pages very differently. Posts get all the organisational tools — categories, tags, archives — while pages are left on their own, floating without any taxonomy support at all. That’s where the Pages with Category & Tag plugin comes in, and today we’re going to walk you through exactly what it does and how NZRT puts it to work.

So let’s start with the problem it solves. When you create a standard WordPress page — think your About page, your Contact page, a Services overview — WordPress gives you no built-in way to group or label those pages with categories or tags. They just exist independently, with no organisational structure connecting them. For a small site with five or ten pages, that’s probably fine. But once you’re managing dozens or even hundreds of pages covering different departments, content types, or business units, that gets messy very quickly.

The Pages with Category & Tag plugin fixes that by bringing the same taxonomy tools you already know from posts and applying them directly to pages. Once it’s active, you can do things you simply couldn’t do before.

Let’s go through the five main features. First, you get page categories. Just like you’d assign a blog post to a category, you can now assign any page to one too. This lets you group related pages together in a logical way. Second, there are page tags. Tags work differently from categories — they’re more freeform and keyword-based — and now your pages can carry them as well, making it easier to surface related content across the site.

Third, the plugin adds archive pages. If you navigate to a category or tag that contains pages, WordPress will now generate an archive view listing all of those pages. This is really useful if someone wants to browse everything within a particular grouping without having to search or click through menus. Fourth, there are taxonomy filters, which let you filter your pages by category or tag — handy when you’re managing content behind the scenes and want to quickly find everything in a particular group. And fifth, you get sidebar widgets for page categories and tag clouds. If you want to show visitors a visual list of page categories or a tag cloud in your sidebar, those widgets are now available to you.

Now let’s talk about how NZRT actually uses this plugin, because that’s where it gets practical for your day-to-day work here.

NZRT uses page categories primarily for module organisation. The modules in play include Customer, Sales, Finance, HR, Supplier, and EDM. So if you’re building out or maintaining pages that belong to one of those business areas, you should be assigning the appropriate page category when you publish. This makes it much easier to manage those sections as the site grows — you can quickly pull up all Finance pages, for example, or filter to see everything under HR without digging through the entire page list manually.

Beyond modules, NZRT also uses page categories for department pages, so pages that belong to a specific internal team or division get categorised accordingly. There’s also provision for regional pages, which would apply if content needs to be segmented by geographic area. And finally, content type pages fall into this system too — things like case studies and testimonials get grouped under their own category so they’re easy to find and manage as a distinct content type.

The core idea behind all of this is that WordPress pages, as powerful as they are for building a structured site, benefit enormously from some extra organisational scaffolding once the volume of content grows. The plugin provides that scaffolding without changing how pages fundamentally work. You’re not rethinking your page structure — you’re just adding a layer of taxonomy on top of what you already have.

If you’re ever adding new pages to the NZRT WordPress site, keep this in mind: check whether the page belongs to one of the established categories before you publish. Leaving pages uncategorised works against the whole point of having this plugin active. And if you think a new category might be needed — say for a new business unit or content type — that’s worth flagging with the team rather than creating unofficial categories without alignment.

This plugin sits alongside other tools documented in the NZRT wiki, including notes on post types and taxonomies more broadly, page structure and navigation, and the general plugins overview. Those are all worth a read if you want the fuller picture of how the WordPress setup here is organised.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at Post Type Switcher.

If you’ve spent any time managing a WordPress site, you’ve probably run into this situation. You’ve got a blog post that really should be a page, or a page that belongs in a custom post type, and you’re staring at it wondering how to move it without breaking everything. That’s exactly the problem Post Type Switcher solves.

At its core, Post Type Switcher is a WordPress plugin that lets you convert content from one post type to another. So if you’ve written something as a standard blog post and you later realise it actually belongs in your custom post type for case studies, or testimonials, or module pages, you can make that change without losing a single thing. Your content stays intact, your metadata stays intact, your comments stay intact. It just lives under a different post type.

Let’s talk about what the plugin actually gives you. There are five main capabilities worth knowing about.

The first is what the plugin calls Quick Convert. This is a one-click conversion experience. You’re inside a post or page, you make your selection, and the switch happens. No complicated workflow, no export and reimport dance.

The second is Bulk Convert. Rather than opening posts one at a time, you can select multiple pieces of content and convert them all at once. If you’re doing a bigger site reorganisation, this saves a lot of time.

Third is what’s described as Safe Conversion. This is probably the most important one to understand. When you switch a post from one type to another, everything that belongs to that post comes with it. The content itself, the custom fields and metadata, the comment threads. Nothing gets left behind.

Fourth, there’s Hierarchy Support. If you’re working with post types that have parent and child relationships, those relationships are preserved through the conversion. So if you had nested pages or structured content with a parent, that structure stays coherent after the switch.

And fifth, Status Preservation. When you convert a post, it keeps whatever publishing status it had. If it was published, it stays published. If it was a draft, it stays a draft. You’re not accidentally taking live content offline just by changing its type.

Now let’s look at how NZRT actually uses this. There are four main use cases documented for us.

The one you’ll probably encounter most is converting blog posts into module pages. If the team has written something as a news post or a blog entry and it turns out it really belongs as a structured page inside a specific site module, Post Type Switcher handles that transition cleanly.

Similarly, if a page needs to become a product, that’s a straightforward conversion. Same goes in the other direction. The plugin doesn’t care which way you’re going.

The other two use cases are about converting standard posts into testimonials or case studies. These are typically custom post types, and getting content into the right type means it shows up in the right templates and feeds. Rather than recreating a post from scratch inside the correct type, you just switch it.

The underlying reason all of this matters for us is content structure. When you’re running a site with multiple custom post types, it’s easy for content to end up in the wrong bucket, especially early in a project when the structure is still being defined. Post Type Switcher gives you a way to correct that without a data migration headache.

It’s also worth noting what the plugin does not do. It’s not changing your content, it’s not reformatting anything, and it’s not touching your taxonomies or terms in ways that would break associations. It’s genuinely just moving the post from one type to another while keeping everything else as is.

If you want to dig deeper into how post types work in WordPress generally, the wiki cross-references a note on Post Types and Taxonomies, as well as the broader Plugins Overview and WordPress Overview pages. Those are good places to go if you need context on how the ecosystem fits together.

The short version is this. Post Type Switcher is a simple, safe utility that gives you flexibility when your content structure evolves. And in a managed WordPress environment like ours, that kind of flexibility is genuinely useful.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at Plugins Overview.

If you’re working with the NZRT WordPress setup, this episode gives you a clear picture of the plugin ecosystem that keeps everything running. There are nine active plugins in total, and they cover four main areas: media management, data import, navigation, and content flexibility. One thing worth noting right up front is that Dolibarr integration is handled separately through agent REST API calls using the nzrt-tools MCP server, so there is no plugin bridge needed between WordPress and Dolibarr. That’s all taken care of at the agent layer.

Now let’s walk through the nine plugins one by one so you know what each one does.

First up is SmartSlider3 Pro, made by Nextend. This one handles your hero sliders and image galleries. If you see a visually polished sliding banner on an NZRT page, that’s SmartSlider3 doing its job.

Next is JC Importer. This is a CSV and data import utility, originally from the Joomla ecosystem but used here on the WordPress side. When you need to bring in bulk data from a spreadsheet or CSV file, this is your tool.

Third is Menu Icons, made by Icomoon. This gives you an icon-based menu system, so you can add visual icons alongside your navigation menu items instead of plain text links.

Fourth is YouTube Mass Videos Importer. The name tells you exactly what it does — it lets you embed large numbers of YouTube videos in bulk rather than adding them one at a time.

Fifth is Featured Image Plus, made by Pix. This extends WordPress’s default featured image handling with additional options, giving you more control over how thumbnail and hero images behave across different post types.

Sixth is Pages with Category and Tag. By default, WordPress doesn’t let you apply categories and tags to pages, only to posts. This plugin adds that taxonomy support so your pages can be organised the same way your posts are.

Seventh is Post Type Switcher, made by johnbillion. This is a conversion utility that lets you change a piece of content from one post type to another, for example turning a post into a page or vice versa, without having to recreate it from scratch.

Eighth is WPCat2Tag Importer. This one handles category-to-tag migration, which is useful when you want to reorganise your taxonomy and move items that were filed under categories into tags instead.

And ninth is the Kadence theme, made by Kadence WP. While technically a theme rather than a plugin, it’s listed here because it functions as the flexible block-based foundation the site is built on and is managed alongside the plugin stack.

All nine of these are currently active.

Now, if you ever need to install or reinstall any of these, the plugin zip archives are stored in the NZRT vault. The folder structure there mirrors the plugin names, so you have subfolders for the video embedder, featured image plus, JC Importer, menu icons, the SmartSlider3 Pro package, pages with category and tag, post type switcher, WPCat2Tag importer, and the YouTube mass videos importer. To activate any of them, you go to WordPress Admin, then Plugins, then Add New, and use the Upload Plugin option to push the zip file directly.

To put the full picture together, it helps to think of the plugins in four groups. For media, you have SmartSlider3 Pro, the YouTube importer, and Featured Image Plus. For content organisation, you have Pages with Category and Tag, WPCat2Tag Importer, and Post Type Switcher working together to give you a flexible taxonomy system. For admin and data tasks, JC Importer handles bulk data ingestion and Menu Icons tidies up the navigation. And as mentioned at the start, Dolibarr sits outside this plugin layer entirely, connected through the agent REST API rather than any WordPress-side bridge.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at SmartSlider3 Pro.

SmartSlider3 Pro is a premium slider plugin for WordPress, and at NZRT it’s one of the tools we rely on for building polished, professional-looking pages. If you’ve ever visited the NZRT site and seen a smooth scrolling hero banner or a showcase of services rotating on screen, chances are SmartSlider3 Pro is doing that work behind the scenes.

So what exactly does it do? At its core, SmartSlider3 Pro lets you build responsive sliders, carousels, and grid galleries. Responsive means it automatically adjusts to whatever screen size your visitor is using — desktop, tablet, phone — the slider scales and reflows to fit. That’s a big deal for a modern site where you can’t predict what device someone’s coming from.

In terms of layout options, you’ve got three main modes to work with. You can build a traditional full-width slider, where one slide fills the screen at a time. You can do a carousel, which shows multiple items side by side and scrolls horizontally. Or you can go with a grid gallery, which lays your content out in a more structured, photo-gallery style. Each mode suits different purposes — heroes, module showcases, product images.

The animations are worth mentioning too. SmartSlider supports slide transitions, fade transitions, and even 3D transitions. So if you want your hero banner to feel a bit more dynamic, you have options beyond just a basic wipe from left to right.

One of the more powerful features is the layer system. This is what lets you stack content on top of your slides — things like text headings, images, and call-to-action buttons. You’re not just stuck with a background image. You can build a full visual composition on each slide with multiple layered elements. And all of this is done through the Smart Slider Editor, which is a drag-and-drop interface, so you don’t need to write code to build something that looks great.

SmartSlider3 Pro also supports video. You can embed YouTube videos directly, or use your own video files in common web video formats. That opens up a lot of creative options for video-first content.

Now let’s talk about how NZRT specifically uses SmartSlider3 Pro. We maintain a set of ready-to-use templates stored in a folder called SmartSlider. Inside that folder there are three template files. The first is for ICS, that’s the Internet Consulting Services business unit. The second is for Iteasel, the portable wooden display easel product line. The third covers Customer Sales Management. Each of those files is a self-contained SmartSlider export. When you import one, you get the full template including the module’s branding colors, the standard layouts and animations we’ve settled on, pre-configured call-to-action buttons that link through to the relevant module pages, and the correct logo and footer placement.

This means if you’re setting up a new page for one of those modules, you don’t start from scratch. You import the right template file and build from there.

To actually place a slider on a page, you use a shortcode. In practice, this is a short tag you drop into a WordPress page or post. It references the slider by its ID number — so if your slider has been assigned a particular ID inside the SmartSlider system, you’d paste the corresponding shortcode into your page content and WordPress handles the rest. You find that shortcode inside the SmartSlider dashboard, copy it, and drop it wherever you want the slider to appear. No code knowledge needed.

As for where sliders actually appear on the NZRT site, there are four main locations. The home page uses a slider to showcase featured products and services. Each module page has its own module showcase slider. The blog section uses a content carousel. And product pages use SmartSlider for product image galleries. So it’s quite spread across the site — almost any page that needs a visual highlight or rotating content is likely using SmartSlider3 Pro in some form.

If you want to dig deeper, the related wiki notes to look at are SmartSlider Templates, the RetroTube Theme, the Plugins Overview, and the Page Structure and Navigation guide. Those will give you more context on how SmartSlider fits into the broader WordPress setup at NZRT.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at YouTube Mass Videos Importer.

So, what does this plugin actually do? In short, it lets you pull multiple YouTube videos into WordPress in one go, rather than adding them one by one. At NZRT, we use it specifically for loading product demonstrations, tutorials, and promotional videos onto our WordPress site, and it saves a significant amount of manual effort when you have a lot of video content to manage.

Let’s talk about what it can do. There are five main features worth knowing about. First, bulk import. You can bring in multiple videos at once by providing either a CSV file with a list of YouTube URLs or by pointing the plugin at an entire YouTube playlist. Second, custom fields. The plugin lets you map YouTube video data, things like the video title, description, and tags, directly to custom post fields in WordPress. So you have control over how that data lands in your content structure. Third, thumbnail download. When a video is imported, the plugin can automatically download the thumbnail image from YouTube and attach it to the post. You don’t have to manually grab screenshots or upload images yourself. Fourth, post creation. The plugin can automatically create WordPress posts with the video embeds already in place. So once the import runs, you end up with ready-to-publish content. Fifth, scheduled import. You can set imports to run on a schedule, which means if you regularly add videos to a YouTube playlist, the plugin can keep your WordPress site in sync automatically without you having to trigger it each time.

Now let’s walk through how an import actually works. You start by providing your YouTube URLs or a playlist link. Then you configure your import settings, and here you’re choosing things like what post type to create, which author to assign the posts to, and what category they should fall under. After that, you do the field mapping step. This is where you tell the plugin to take the YouTube video name and use it as your post title, or take the video description and put it in the post body, and so on. Once everything is configured, you execute the import. Finally, you verify that the posts have been created correctly by checking them in WordPress.

In terms of how NZRT actually uses this tool, there are four main use cases. Product demo videos, so if we have demonstrations of something we’re showcasing, those get pulled in here. Tutorial content, educational videos that support our services or tools. Promotional videos, marketing material that lives on YouTube and needs to be surfaced on our WordPress site as well. And customer testimonial videos, provided those testimonials have been uploaded to YouTube in the first place.

If you’re exploring related areas in the wiki, this page connects to the Adult Mass Videos Embedder documentation, the general Plugins Overview, and SmartSlider3 Pro, all of which are worth looking at if you’re working with media and video content on the NZRT WordPress setup.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at WPCat2Tag Importer.

If you’ve ever worked with a WordPress site that’s been around for a while, you’ve probably run into a situation where the taxonomy — that’s the way content is organised using categories and tags — has gotten a bit messy over time. Maybe categories were set up in a hurry early on, or the site’s content strategy changed, and now what used to be organised as categories would make more sense as tags, or the other way around. That’s exactly the problem WPCat2Tag Importer is designed to solve.

At its core, WPCat2Tag Importer is a WordPress plugin that migrates content between two of WordPress’s built-in taxonomy types: categories and tags. You can go either direction — converting categories into tags, or converting tags back into categories. This gives you real flexibility when you’re restructuring how your site’s content is labelled and discovered.

Let’s walk through what the plugin actually does, and why each feature matters.

The first thing to know is that it supports bulk migration. Rather than going post by post and manually reassigning taxonomy terms, you can run the conversion across your entire content library in one operation. If you’ve got hundreds or thousands of posts, that’s a massive time saver.

Next up is hierarchy handling. WordPress categories support parent-child relationships — so you might have a category called Technology with subcategories like Hardware and Software underneath it. Tags, on the other hand, are flat — they don’t have a hierarchy. WPCat2Tag Importer gives you the option to flatten that hierarchy when you convert. So if you’re moving categories to tags, it can take those nested structures and bring everything up to the same level. That’s worth thinking through carefully before you run the migration, because once you flatten, those parent-child relationships are gone.

One of the most important features — and this is good practice for any bulk operation — is the preview step. Before the plugin actually makes any changes, you can run a preview to see exactly what’s going to happen. Which categories are going to become tags, how many posts will be affected, what the end result will look like. You review that first, and only then do you execute. This is what the documentation calls safe operation, and it’s genuinely useful for catching anything unexpected before it becomes a real problem.

After migration, you’ve also got the option to set up URL redirects. This matters because when categories become tags, the URLs change. A URL that used to point to a category archive page will no longer work unless you redirect it. The plugin can handle that automatically, which helps you avoid broken links and keeps your search engine rankings intact.

Finally, you get a detailed log report after the migration runs. This gives you a record of everything that changed — useful both for troubleshooting and for documenting what was done, especially if you’re working as part of a team.

Now, where does NZRT actually use this? There are a few specific scenarios called out in the wiki. One is converting category-based module organisation into tags. If content was originally bucketed into categories to represent modules or sections, and the site’s architecture has evolved to where tags are a better fit, this plugin handles that shift cleanly.

Another use case is migrating a legacy category structure. Older WordPress sites often accumulate categories over time without a clear plan, and WPCat2Tag Importer gives you a way to clean that up as part of a broader content reorganisation.

The third scenario is consolidating taxonomy after content reorganisation. If you’ve just gone through a significant restructure — merging content, removing sections, rebranding — the taxonomy often needs to catch up, and this plugin is the tool for that job.

If you want to dig deeper, the wiki points you to three related notes. There’s one on Post Types and Taxonomies, which gives you the broader WordPress content model context. There’s a Plugins Overview, which is the master list of plugins in use across the site. And there’s a note on JC Importer, which handles a different kind of import workflow if you need to bring content in from external sources rather than reorganise what’s already there.

So to sum up: WPCat2Tag Importer is a focused, flexible, and safe tool for reorganising WordPress taxonomy. Preview first, think through your hierarchy options, make sure redirects are enabled if your URLs matter, and always review the log once it’s done.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at WP-Script Core.

So let’s start with the big picture. WP-Script Core is a custom WordPress plugin built by NZRT. Its job is to extend the RetroTube theme — that’s the theme running on nzrtnetwork.com — with frontend user interface scripting capabilities. In plain terms, it’s a tool that sits on top of the theme and gives it extra powers on the browser side of things, the part that visitors actually see and interact with.

Now, before we go any further, there’s one thing worth calling out clearly, because it’s a common point of confusion. WP-Script Core is not a Dolibarr integration bridge. You might be wondering what that means. Dolibarr is the ERP system NZRT uses — it handles things like projects, tickets, invoices, and agent workflows. You might assume that because WP-Script Core is a WordPress plugin and NZRT connects WordPress to Dolibarr, this plugin must be the thing doing that connection work. It isn’t. When WordPress agents need to talk to Dolibarr, they call the Dolibarr REST API directly, using their own per-agent API keys. That happens completely separately from this plugin. WP-Script Core has nothing to do with that pipeline.

So what does WP-Script Core actually do? Its purpose breaks down into three main areas.

The first is theme UI extension. This is the core reason the plugin exists. It adds frontend scripting and layout features to the RetroTube theme that the theme doesn’t provide out of the box. Think of it as a companion layer that sits alongside the theme and enhances what it can do visually and behaviourally.

The second area is custom scripts. The plugin handles the injection of page-specific scripts and styles. What this means in practice is that certain pages on nzrtnetwork.com can have their own scripts loaded precisely when and where they’re needed, rather than having everything loaded globally all the time. This keeps things clean, targeted, and performant.

The third area is NZRT branding. Beyond generic layout features, the plugin implements custom theme behaviours that are specific to nzrtnetwork.com. These are the little things that make the site feel distinctly NZRT — behaviours, interactions, and styling choices that reflect the brand and wouldn’t belong in a general-purpose theme.

Putting it all together, WP-Script Core is really about making the RetroTube theme work exactly the way NZRT needs it to for their specific site. The theme provides the foundation, and WP-Script Core builds on top of that foundation on the frontend.

If you’re working in this area and you need to understand how Dolibarr connects to WordPress more broadly, the wiki has related notes you can follow up on. There’s a Dolibarr REST API Setup note, a WP-Dolibarr Integration Overview note, a WordPress REST API note, and a Plugins Overview note. Those will give you the full picture of how the different moving parts connect at the system level. But just remember — WP-Script Core isn’t part of that integration chain. Keep it in its lane: frontend, theme, UI scripting, branding.

One last thing worth reinforcing as you work with this plugin. Because it operates at the theme UI layer, changes you make here will have direct visible effects on the site for anyone visiting nzrtnetwork.com. It’s not a backend utility running quietly in the background. It touches what users see. So treat modifications carefully, test in context, and be mindful that the RetroTube theme and WP-Script Core are working as a team — changes to one can interact with the other.

That’s the essence of WP-Script Core. A custom plugin, tightly scoped to frontend UI work on the RetroTube theme, with no role in Dolibarr integration, and three clear jobs to do: extend the theme’s layout capabilities, inject page-specific scripts and styles where needed, and deliver the custom behaviours that make nzrtnetwork.com feel like NZRT.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.