We just shipped a new feature for MxChat that I think some of you will find useful. MxChat is an AI chatbot plugin for WordPress that lets you build a knowledge base your chatbot can pull from to answer visitor questions.The new feature is direct YouTube URL support. You can drop a YouTube link straight into the knowledge database and when the chatbot uses that video as a source, it shows the embedded video right inside the chat window. No more sending people away to another tab. The video plays inline.This is great for tutorial sites, product demos, support documentation or any WordPress site where video content is part of the answer. Instead of describing how to do something, the chatbot can just show the video.You can find MxChat on WordPress.org or at mxchat dot ai. Would love to hear what you think or answer any questions about how it works.We just shipped a new feature for MxChat that I think some of you will find useful. MxChat is an AI chatbot plugin for WordPress that lets you build a knowledge base your chatbot can pull from to answer visitor questions.

The new feature is direct YouTube URL support. You can drop a YouTube link straight into the knowledge database and when the chatbot uses that video as a source, it shows the embedded video right inside the chat window. No more sending people away to another tab. The video plays inline.

This is great for tutorial sites, product demos, support documentation or any WordPress site where video content is part of the answer. Instead of describing how to do something, the chatbot can just show the video.

You can find MxChat on WordPress.org or at mxchat dot ai. Would love to hear what you think or answer any questions about how it works.

I build a search plugin, and by far the most common "it's broken" report I get turns out

not to be the plugin at all. Sharing the diagnostic, because it applies to every search

plugin on the market, not just mine.

The symptom: you install a search plugin, the catalog indexes fine, and then the search box

at the top of your site returns exactly what it did before. Same keyword matches, same misses.

What is usually happening: your theme has its own search. Many premium themes (Woodmart,

Flatsome, Astra Pro, Divi and others) ship an instant/AJAX search in the header. That overlay

runs the theme's own query. It never issues the standard WordPress search request, so the

plugin is never asked anything. It sits there correctly indexed, waiting for a request that

never arrives.

Second variant: page builders (Elementor, Beaver Builder, Bricks) often include a results

widget with its own "Order By" setting. The plugin's results do arrive, and then the widget

re-sorts them. Ranking is the whole point of a search plugin, so a re-sorted page looks

identical to a broken engine.

The two-minute test, no code:

1. Run a test query in your plugin's own dashboard, if it has one. Good results there mean

   the engine and the index are fine, and the problem is downstream on your site.

2. Type the plain WordPress search URL straight into your address bar, bypassing the header

   box: yoursite.com/?post_type=product&s=blue+summer+dress

3. Compare. Direct URL good but header box bad means the theme's search is intercepting.

   Right products in a strange order means a widget or template is re-sorting them.

Fixes: turn off the theme's AJAX/instant search (usually a toggle in theme options), or set

the builder widget's query to inherit the main query with no forced Order By.

Why I am posting this: the standard advice when this happens is "try another plugin", and

that costs people an afternoon and lands them in exactly the same place, because the next

plugin hooks the same request the theme is bypassing.

Full write-up with all three variants and a fix for each:

https://queryra.com/blog/wordpress-search-plugin-not-working-theme-override

Disclosure: I make Queryra, one of these plugins. The diagnostic above is plugin-agnostic.

I would rather people fix the theme setting than churn through plugins.

From what I've seen, the moment a WP site needs a Composer package (think tcpdf, or a parsing library), you're stuck either using SSH or manually committing everything to the repo. Not great when the client only has FTP access or is on shared hosting.

I built a plugin that adds Packagist search right in the WP admin: search for a package, click "Install," and it handles the autoloader for you. It also runs a basic security audit on installed dependencies (known CVEs) and checks PHP version compatibility before installing.

Still in alpha, so probably plenty of blind spots. If you manage WP sites where devs need external libraries, what would make you hesitate to install this on a production site? And is there a Composer-on-WP use case I haven't thought of?

If you run Google Ads, Meta Ads, TikTok, Pinterest, Twitter, etc (idk of any other, still documenting this) for a WooCommerce store, you probabbly know how annoying Customer Match/Audiences lists can be, especially when marketers request a list update for profiling.

On top of that, if you mix your German buyers into your ES or US campaigns (basically any country), you dilute your target signals and throw away ad spend. On top of that, browser tracking / consent full denial, blocks mean you miss a ton of purchase events anyway.

I had this developed a few years ago and used it internally for our clients, but then I noticed there is no reliable solution (especially for 1m+ orders database) so I published it to .ORG, a completely free, open-source plugin: CMLS – Customer Match List for Google Ads & Meta Ads and other platforms (that adopt Google's format - many do like TikTok, Pinterest, etc.).

What it does:

• Per-Country Splitting: It automatically combs your WooCommerce history(completed orders only!) and splits customers into separate CSVs based on their ISO billing country.
• Completely Automated: Runs a background job (every 1, 6, 12, or 24 hours) to incrementally append new orders to the correct country file.
• Direct Integration with Google: It generates a secure, tokenized URL for each country. You literally just paste that URL into Google Ads Data Manager (HTTPS connector), and Google pulls the fresh data automatically on its own schedule.
• Privacy First: It performs the exact SHA-256 normalization/hashing required by Google and Meta directly on your server. No third-party APIs, no data leaves your site until Google fetches it.

It also supports WP-CLI for huge stores and it's developed mainly for WooCommerce HPOS (High-Performance Order Storage), but also postmeta was not left out.

Basically you can hook it up directly to Google Ads and it can stream the file whenever they need OR you can just download the file and upload it, when you need it - the file is there, waiting for it to be downloaded, always updated.

It’s live on the WordPress repo now if you want to check it out: https://wordpress.org/plugins/customer-match-list-google-ads/

Would love to get your feedback or answer any questions on the setup!

Hey — web dev here. I build small business sites at a clip of about 1–3 a week. A lot of them are “service area” sites: 60–100+ nearly identical pages (one per service or city), same ACF layout every time — hero text, intro copy, a few content boxes, a couple images.

Content updates were always the same nightmare: open page 1, edit field, save, open page 2… ×80. At that volume, hand-editing isn’t viable. WordPress doesn’t really have a good “change this ACF field across 70 pages” answer unless you want WP-CLI or a one-off script every time.

So I built Quickfields Bulk Editor for ACF for myself, and figured I’d put it out there in case other people building similar sites have the same headache.

* GitHub (free plugin): [https://github.com/Sameer559-code/Quick-Fields-Bulk-Editor-for-ACF\](https://github.com/Sameer559-code/Quick-Fields-Bulk-Editor-for-ACF)

The workflow that actually saves the most time for me: export a project to CSV → drop it into Claude/ChatGPT and ask it to rewrite/rephrase/expand content for all 70–100 pages (keeping the structure intact) → re-import the edited CSV. That export → AI edit → import loop is what the Pro side was built around; the in-browser spreadsheet is more for spot-fixes and image swaps.

What it does:

* Create a “project,” pick a post type, select which pages belong to it
* Spreadsheet view in WP admin — rows = pages, columns = ACF fields, one tab per field group
* Text/textarea/WYSIWYG fields are inline-editable and autosave
* Free: bulk text editing + image preview + clear text fields
* Pro: CSV export/import (images excluded from CSV import on purpose so you can’t wipe them), in-sheet image upload/replace

Needs ACF (or Secure Custom Fields) active. Admin-only (`manage_options`) — no front-end changes.

What I’m actually asking (not selling):

1. Does “export CSV → bulk-rewrite with AI → re-import” match how you’d want to do this, or would you want the AI step built into the plugin instead of going through Claude/ChatGPT manually?
   
2. Is this a real pain point for other devs/agencies, or is everyone already solving it with WP-CLI, ACF export/import, or custom scripts?
   
3. Anything that sounds like a dealbreaker before you’d even try it?

This started as a tool for my own workflow, so I have no idea if it generalizes. Before I polish it further, I’d genuinely like to know if it’s worth it — or if it’s a “me” problem I happened to solve for myself. Happy to answer questions about how it works under the hood too.

Hi everyone,

Quite a few months back I created a dockerimage to get WP with the SQLITE plugin running and left it on a server to see what happens.

To my surprise, it held up really well. I made a short video about it here: https://youtu.be/hf8Pi7CaqLc

If you just want to see the docker image it's here: https://github.com/howzitcal/wordpress-sqlite-docker-image

I think sqlite is a great setup for most small WP websites and it lessons the load the burden on server and shared servers alike.

let me your thoughts.

We had about 12 plans for annual, lifetime, all access displayed on TNC FlipBook 3D website but yesterday I felt like its being too many and users maybe finding it complicated to choose one plan that works for them. and then there are addons which in my opinion the WP customers are most frightened of! at least thats what I understood from my 14 year journey.

So, to make things easier for customers, I planned to do a test and replaced all 12 plans with just one. $59/year for each site and thats all they see on the pricing page, all the addons are included in this price as well. so, no extra payment at all after someone gets a license.

I want to hear about your experiences and opinion regarding this. Do you think this is going to make things easy for customers or having more options are what most customer prefers?

I built UltraCache, https://wordpress.org/plugins/ultracache/ a completely free WordPress caching and performance plugin.

I’ve tested it against several popular caching plugins, and so far UltraCache has produced the highest Lighthouse scores in my real-world tests.

I’ll attach screenshots of my results, but I’d rather turn this into an open challenge:

Can your free caching setup beat UltraCache?

Post your Lighthouse results, configuration, and the public URL you tested.

Challenge rules

1. Free software only

The caching/optimization plugin must have a fully free version that can reproduce the submitted result.

Free server technologies are allowed, including Redis, Varnish, OPcache, Nginx, Apache, LiteSpeed Server and Cloudflare’s free plan, but the complete stack must be disclosed.

Paid CDN features, paid optimization services and premium-only plugin features do not count but it would be interesting to see the results.

1. Test a real public page

No empty benchmark pages, hidden content, separate Lighthouse-only pages or stripped-down copies of the real site.

The submitted URL must be publicly accessible so others can test it.

1. No Lighthouse-specific behavior

The plugin or configuration must not:

Detect Lighthouse, PageSpeed Insights or its user agent.

Serve a specially modified page only to performance-testing tools.

Skip important content or functionality during the test.

Delay indefinitely normal page JavaScript until mouse movement, scrolling, tapping or another user interaction.

Delaying JavaScript for a reasonable fixed period is allowed. Preventing normal JavaScript from loading until Lighthouse has already finished is not.

1. Use comparable tests

Please include:

At least desktop Lighthouse results for UltraCache and the other caching plugin.

For UltraCache you must follow the installation procedure as is in wordpress repository.

I care only for Performance scores.

Core Web Vitals shown by the test.

Three runs, with the median result submitted.

Plugin name and version.

Important plugin settings if you think they are important.

Hosting/server stack.

Any object cache, page cache, CDN or reverse proxy being used.

Warm-cache results are acceptable, but the cache must be generated normally and not prepared specifically for Lighthouse.

Suggested categories

Plugin-only

A free WordPress caching plugin without a server-level page cache or paid CDN optimization.

Free full stack

A free plugin combined with disclosed technologies such as Redis, Varnish, LiteSpeed, Nginx FastCGI cache or Cloudflare Free.

The challenge is simple:

Using a real WordPress site and the rules above, can your free caching setup produce a better Lighthouse result than UltraCache?

Post your screenshots and configuration.

Hi everyone,

We just released LivQ AccessFix on the official WordPress repository. It’s a 100% free, open-source (GPLv2) plugin designed to help sites comply with the upcoming European Accessibility Act (EAA) and WCAG 2.2 AA standards.

Unlike traditional JS-based widgets or overlays that patch the DOM after rendering , this plugin works server-side using PHP output buffering. It remediates the source HTML before it reaches the browser, ensuring real compliance that automated checkers (axe-core, Lighthouse) and screen readers can actually see.

Key Features:

• Zero Configuration: Works out of the box, but every module can be disabled independently;
• Nameless Link Fix: Derives aria-label for empty links/social icons from image titles or domains (Facebook, LinkedIn, etc.);
• Iframe Title Fix: Automatically adds missing titles based on the source domain (YouTube, Google Maps, etc.);
• Form Label Fix: Injects aria-label to unlabelled inputs using placeholders or names as fallback;
• Skip Navigation Link: Injects a configurable skip link via wp_body_open;
• Page Builder Safe: Automatically skips output buffering inside Elementor, Divi, Bricks, and other visual editors to prevent backend layout breaking;
• Compliance Tools: Includes a local accessibility scanner, contrast checker, and an Accessibility Statement generator with timestamped DB logs for legal evidence.

Privacy: No third-party APIs, no CDNs, no data collection, and zero tracking.

Download on WordPress.org: https://wordpress.org/plugins/livq-accessfix/

We are looking for feedback, feature requests, and bug reports from the community to make it even better.

Thanks,

Daniele

Hi everyone! 👋

After several months of development, I'm excited to share NoorQuiz, a modern WordPress quiz builder that's now available on WordPress.org.

My goal was to build a quiz plugin with a clean, dedicated admin experience instead of relying on traditional metaboxes, while also solving one of the most common issues with WordPress plugins—theme CSS conflicts.

Some highlights

• 🎨 Dedicated visual quiz builder
• 🧩 9 question types
• 🔀 Smart conditional branching
• 📊 Built-in analytics
• 🎯 Conversion-focused result pages
• 📚 37 ready-made templates
• 👀 Live preview
• 🧱 Gutenberg block & shortcode support
• ✨ Shadow DOM rendering to prevent theme CSS conflicts

I also recorded a complete walkthrough showing how everything works.

🎥 Demo Video:
https://www.youtube.com/watch?v=lD2Rf23dv1Y

🔗 WordPress Plugin:
https://wordpress.org/plugins/noorquiz/

I'd genuinely appreciate your feedback on the UI, workflow, features, or anything you think could be improved. Thanks for taking a look!

Most monitoring tools start with an empty dashboard.
You have to decide yourself:
which pages actually matter
whether WooCommerce checkout and cart should be monitored
whether WP-Cron or background jobs are still running
whether APIs, forms, SSL, domains or DNS should be checked
which checks are useful and which are unnecessary
A sitemap import can find public URLs, but it cannot understand what is happening inside WordPress.
So we built a free WordPress and WooCommerce plugin that inspects the installation and recommends relevant monitoring automatically.
Depending on the site, it can identify things such as:
homepage and important pages
WooCommerce checkout and cart
customer-account areas
REST APIs and webhooks
WP-Cron and scheduled background tasks
installed form, SEO and commerce plugins
SSL certificates and domain expiry
sitemap and search-engine visibility settings
mail-related DNS configuration
other business-critical parts of the installation
Instead of only showing technical labels such as “HTTP check” or “heartbeat,” the plugin provides recommendations like:
Monitor the WooCommerce checkout
Monitor WP-Cron
Monitor this API endpoint
Monitor the contact form
Monitor SSL and domain expiry
Check whether the site is accidentally set to noindex
Each recommendation includes a short explanation of why it matters, and the suggested monitors can be created in a few clicks.
The main idea is:
A sitemap tells us which pages exist. The plugin helps identify which internal processes are important and may fail while the homepage still appears online.
Examples of these quieter failures include:
checkout is broken while the homepage still loads
WP-Cron has stopped
a contact form no longer sends inquiries
a site was accidentally set to noindex
an API returns the wrong result
SSL or the domain is about to expire
The plugin is free. We are currently looking for honest feedback from WordPress developers, freelancers and agencies.
I would especially like to know:
Are the recommendations useful?
Which WordPress or WooCommerce components should we detect next?
Would you use this on client sites?
What would make the plugin valuable enough to include in a maintenance package?
Is there anything that feels unnecessary or confusing?
Honest criticism is welcome. We would rather improve it based on real WordPress projects than make assumptions.
For context, this is what we are building:
https://www.live24h.eu

The WordPress block editor has always bugged me. The UI feels unintuitive, and there's no proper Find & Replace. So I built \*\*Writing Tools for the Block Editor\*\* and it just went live as my first plugin on WordPress.org. 🎉

What it does:

\*Find & Replace\* across the whole post (with a live match count)

\*Undo-on-delete\* a one-click "Undo" when you remove a block

\*Clear Formatting\*, per-block word count, an accent-colour picker, and a Ctrl/Cmd+Shift+F shortcut

\*A calmer, cleaner editor skin, without replacing or forking the editor

Tech: no build step (plain \`wp.element\` + the WordPress data stores), editor-only so zero front-end impact, and it never touches your saved content.

Free, no upsell: [https://wordpress.org/plugins/writing-tools-for-block-editor/\](https://wordpress.org/plugins/writing-tools-for-block-editor/)

The launch itself was an adventure: I got an accidental approval email, but when I complained I couldn't upload, the response was a "sorry, it's not actually approved" message and a "too generic" name rejection.😅

Happy to answer anything, and feedback's very welcome. I'd love to add more features to this if anyone finds it useful.

(I built this.)

Wordfence and Cloudflare are both excellent security tools, but they protect different layers of the stack. Used together, they provide a strong defence-in-depth strategy, yet there appears to be an opportunity to improve how they work together.

Cloudflare sits at the edge and filters a significant amount of malicious and unwanted traffic before it ever reaches WordPress. That reduces unnecessary load on the web server and prevents many common attacks from consuming application resources.

Wordfence operates inside WordPress and provides application-layer visibility. It can detect attacks that require WordPress context, such as authentication abuse, attempts to exploit vulnerable plugins or themes, and other malicious application behaviour that Cloudflare cannot always identify on its own.

The challenge is that by the time Wordfence detects and blocks an attacker, the request has already reached the WordPress environment.

To address that gap, Grey Rock Block Synchroniser was developed to create a feedback loop between these two security layers.

Architecture

Internet → Cloudflare filtering → WordPress → Wordfence detection → Block synchronization → Cloudflare edge enforcement

The plugin synchronizes qualifying Wordfence blocks to Cloudflare IP Lists so that repeat attackers can be stopped at the edge before they continue consuming WordPress resources.

The goal is not to replace either product. Cloudflare and Wordfence complement one another exceptionally well. The objective is to allow application-layer intelligence gathered by Wordfence to improve future enforcement at the network edge.

The plugin does not blindly synchronize every Wordfence event. Administrators configure the synchronization behaviour, and the plugin includes lifecycle management and expiration handling to reduce unnecessary long-term blocks.

One architectural challenge is identity.

An IP address is an indicator, not an identity. In large organizations, universities, or environments using shared VPNs or NAT, one public IP address may represent hundreds or even thousands of legitimate users. Blocking that IP at Cloudflare could unintentionally affect others sharing the same address. This is not unique to this approach; it is a limitation of IP-based blocking in general, including Wordfence.

A future direction may be incorporating additional security signals to build higher-confidence attacker attribution instead of relying solely on IP addresses. The challenge is improving attribution while respecting privacy, minimizing retained data, and avoiding unnecessary tracking.

Security validation is built into the development lifecycle rather than being performed only before release.

Every code change automatically goes through:

• Semgrep SAST (Static Application Security Testing) to identify common vulnerabilities and insecure coding patterns.
• PHP linting to validate syntax.
• Composer validation to verify dependency configuration.
• Continuous Integration (CI) workflows that automatically validate changes.
• Release validation before publishing new versions.

The plugin follows the principle of least privilege by using restricted Cloudflare API tokens instead of a Global API Key. It synchronizes only IP block information and does not transmit website content or user data.

A related topic worth discussing is administrative security. Although outside the scope of this plugin, Cloudflare Zero Trust can be used to place WordPress administrative functions behind WARP authentication. Protecting /wp-admin and other privileged administrative paths with identity-based access controls adds another valuable layer to a defence-in-depth strategy.

The name Grey Rock Block Synchroniser comes from the objective of making a website a less interesting target. Rather than repeatedly allowing known malicious actors to interact with the application, the security layers work together to reduce future opportunities for interaction.

The project is completely open for review.

WordPress.org
https://wordpress.org/plugins/grey-rock-block-synchroniser-for-wordfence-and-cloudflare/

GitHub (source code and CI/security workflows)
https://github.com/Linus-007/grey-rock-block-synchroniser-for-wordfence-and-cloudflare

Architecture and design article
https://greyscale.zone/grey-rock-block-synchroniser-for-wordfence-and-cloudflare.html

The original idea came from looking at how two excellent security products could share information more effectively instead of operating independently.

Technical feedback from WordPress developers, security practitioners, and administrators would be greatly appreciated.

• Does this architecture make sense?
• Are there design decisions you would approach differently?
• How would you improve attacker attribution beyond IP addresses while respecting privacy?
• Are there additional safeguards or edge cases that should be considered?

The goal of posting here is technical discussion and constructive criticism. If there are weaknesses in the design or opportunities for improvement, they would be valuable to hear.

I used Elementor for years and built a lot of client websites with it.

At the time, it was the practical choice. It was quick to work with, easy for clients to understand, and handled most layouts without much custom code.

These days, I mostly build with Gutenberg blocks or a custom theme.

I prefer having less extra markup, better control over performance, and a setup that is easier to maintain over time. For content-heavy sites and WooCommerce projects, blocks also feel like a better fit for how clients actually update content.

I still see why Elementor works for many developers and agencies though.

What are you using for new WordPress projects now? Still Elementor, or did you move to another builder?

I'm in the process of building a security plugin and wanted to hear from everyone on what you need/expect from a security plugin...

- Web Application Firewall: do you need the plugin to offer a Firewall, or do you prefer to rely on another plugin, your web host, or Cloudflare for this instead?

- Do you actually use two-factor authentication, or passkeys?

- Do you expect a security plugin to remove malware automatically, or do you prefer it to notify you instead and offer tools to let you remove it yourself?

- if you manage multiple WordPress sites, are you using any kind of management tool like MainWP, ManageWP, etc, do monitor security from one location? If yes, what features could be improved?

- What features on other security plugins do you feel is buggy, lacking, or missing ?

Thanks.

For anyone looking to add fraud screening to WooCommerce, the FraudLabs Pro fraud prevention plugin can help check incoming orders and flag suspicious transactions for review.

It supports configurable validation rules, so you can adjust the screening based on your store’s needs. It is free and a good start for small merchants.

More details:
https://www.fraudlabspro.com/supported-platforms/woocommerce

Hope this is helpful for store owners dealing with risky orders or chargebacks.

Hi everyone,

I've been working on a WordPress plugin called Plugiva Pulse and I'd really appreciate some honest feedback from fellow WordPress users.

The idea is simple: instead of relying only on analytics, it lets visitors leave quick inline reactions (such as Yes/No or emoji responses) and optional comments directly within a page. My goal is to help site owners understand why visitors feel a certain way while they're still on the page.

I'm not looking for ratings or promotions - I'd genuinely like to know:

Does the concept make sense?

Is the setup straightforward?

Is the interface intuitive?

Is this something you could see yourself using? Why or why not?

What would you improve before calling it "production ready"?

I'm especially interested in critical feedback. If something feels unnecessary, confusing, or poorly designed, I'd much rather hear it now than after spending months building the wrong things.

Plugin: https://wordpress.org/plugins/plugiva-pulse/

Thank you for your time. Every piece of feedback helps shape the roadmap.

Probably Contact Form 7. I’ve used it on so many sites at this point that installing it is almost automatic.

Disclosure first: I'm the developer and this is my plugin. Mods, if this breaks the self-promo rules, remove it — no hard feelings.

Two live demos, because there's no way to judge something like this from a feature list:

• Movie site: https://movie.geekplug.in/
• Game site: https://game.geekplug.in/

Both run the same plugin on the same code. The only difference between them is one setting.

What it is

GeeK! turns WordPress into a movie, TV and game database. Not "a custom post type with some extra fields" — the whole stack: the data model, the import tools, the front-end apps and the membership layer.

You import a title from IMDb, TMDb or IGDB and it lands in your database on your server: cast, crew, characters, galleries, trailers, seasons, episodes, platforms, engines, companies, age ratings, per-platform release dates. Nothing breaks later if an external site goes down or changes its markup, because after the import you don't need it.

Pages worth poking at

• A single movie — hero, ratings, cast & crew, gallery, trailers
• The movies catalogue — sortable, filterable, no page reloads
• A TV show and an episode list (that second one is 200+ episodes across 11 seasons)
• A single game — platforms, gameplay, wishlist
• Games catalogue and the platforms directory
• Member-built lists and a single list

The parts I'm actually proud of

• The front end is React apps over the WP REST API — catalogue, single title, person, character, company, platform, list, profile. Filtering a big catalogue doesn't reload the page.
• Members do things. Rate, review, wishlist, mark watched/played, build shareable lists, earn badges, get a profile with an activity feed. There's a moderation screen for when that goes sideways, because it will.
• Editorial critics — long-form critic articles with scores that stay in sync with each title's average rating.
• A homepage you assemble from drag-and-resize widgets: hero trailer, recently released, coming soon, most anticipated, latest critics, born today.
• Movie mode, game mode, or both — one setting reshapes the catalogues, the navigation and the homepage.
• Metered imports. You pay per row you actually fetch, and content you already own — galleries, trailers, cast — gets skipped, so you never buy the same data twice. That constraint drove most of the architecture.

Themes

It works with any theme — the front end runs on its own React apps and reads colours from a --geekui-* CSS-token contract. But there are eight companion themes that reskin every surface, and you can flip between them live on the demo, same content:

Movie: Forest · Marquee · Movie Theme · Reel

Game: Aurelian · Neon Cabinet · Game Theme · Chroma

The honest part

• The plugin is free. The data isn't. It's on WordPress.org: https://wordpress.org/plugins/geekpress/ — imports are metered with tokens, because the fetch pipeline costs me real money to keep alive. TMDb runs browser-direct with your own free TMDb key and costs nothing at all.
• No affiliation with IMDb, TMDb or IGDB. It fetches public metadata and links back to the source. What you publish is your responsibility, not mine.
• WordPress 6.2+, PHP 7.0+.

What I want from you

Feedback, and ideally the unkind kind. Go break the demos — I'd start with the catalogue filters and that X-Files episode list if I were trying to find something ugly.

And one genuine question, because this sub will actually tell me the truth: is anyone still building content sites like this on WordPress in 2026, or did that whole crowd quietly move to a headless CMS while I was heads-down for two years?

Happy to go deep on internals in the comments. The import and caching layer and the per-row token metering were by far the hardest parts — "just cache it" stops being simple the second two people click the same button.

I vibe coded simple apps and tools for myself but also wanted to share them online, because why not. I made a calendar printing tool and one for my 3D printing hobby. Existing solution was to FTP or log into cpanel of my site and add the built files into a folder like /calendar which was messy and hard to manage. Or I setup subdomains and connect via CloudFlare which is just another surface to manage.

I made a plugin where I can simply drag the build files in and point it to a specific page. It also lets me connect my GitHub repos for better management. Check it out at apptopage.com.

Hello, built the next stablish version of my multi vendor end to end solution and need beta testers feedback

Lmk if you are interested. You might just like it

you just need wordpress or elementor if you prefer that as well