Client
Wookedin2gaming
Project Type
Custom RSS/XML Feed Development for WordPress
Destination Platform
NovelUpdates
Overview
Wookedin2gaming approached us with a challenging RSS feed requirement for a manga and novel publishing website.
The website used a purchased custom WordPress theme, and its content was not created through WordPress’s traditional “Add Post” or “Add Page” interface. Instead, the site used a specialized content structure for publishing manga and novel chapters.
The key requirement was to create an RSS feed that would expose only publicly available/unlocked chapters, allowing NovelUpdates to automatically discover and publish eligible updates.
The project therefore required more than a standard WordPress RSS feed. The feed needed to understand the site’s custom publishing structure and distinguish between content that was available to readers and chapters that were still locked.
The Challenge
The website had two primary types of chapters:
- Unlocked chapters — available to readers without payment.
- Locked/advanced chapters — initially restricted and available only after payment or until they became free through the site’s release mechanism.
The client wanted the RSS feed to include chapters appearing in the site’s “NEWLY BREWED” section, while excluding chapters that remained locked.
This was particularly important because NovelUpdates needed a feed containing only eligible chapters rather than relying on the website’s page source.
The project also had to account for the site’s custom content structure rather than relying on standard WordPress post queries.
The Solution
We developed a custom RSS feed specifically around the website’s existing publishing workflow.
The feed was configured to work with the site’s custom manga/novel content and expose the appropriate unlocked chapters for external consumption.
A major part of the implementation involved handling publication dates correctly so that newly released chapters appeared in the expected order.
The feed was subsequently adjusted to use the site’s GMT+8 timezone, matching the client’s server and staff publishing environment.
Handling Same-Time Chapter Releases
During testing, an important edge case was identified.
Multiple chapters could be released at exactly the same date and time. When several items had identical timestamps, the feed could not reliably establish which chapter should appear first.
For example, two consecutive chapters could initially have:
- Chapter 111 — 10:00:00
- Chapter 112 — 10:00:00
The feed required a distinct chronological order.
The solution was to use a one-second difference when multiple chapters were released at the same time:
- Chapter 111 — 10:00:00
- Chapter 112 — 10:00:01
This helped maintain the intended descending order within the RSS feed.
The client subsequently implemented different release timings for chapters, and reported that the feed worked better.
Timezone and Publication Date Handling
The project also uncovered a timezone-related issue involving chapters without a scheduled release date.
The feed script was using GMT in certain situations, which could cause the publication time in the RSS feed to differ from the site’s actual publishing environment.
The implementation was updated to properly account for the client’s GMT+8 timezone.
Later investigation identified that chapters without a scheduled date were being processed using GMT time. The plugin/script was updated and a revised version was supplied to the client.
Feed Reliability Improvements
After the initial implementation, the project continued through several rounds of testing and troubleshooting.
The client reported situations where:
- Some newly released chapters did not appear at the expected position.
- Multiple chapters released simultaneously were not consistently picked up by the destination platform.
- The feed occasionally became unavailable.
- The feed was loading significantly more historical releases than necessary.
The feed was subsequently optimized to limit the number of loaded items.
The client reported that the feed had been loading more than 2,000 releases, even though the destination service only needed the latest updates.
We changed the feed configuration to return a maximum of 100 items, reducing unnecessary processing and keeping the feed focused on recent releases.
Results
The project evolved from a simple RSS requirement into a custom feed solution designed around a specialized publishing workflow.
Key improvements included:
- Custom RSS feed for a non-standard WordPress content structure
- Filtering of eligible/unlocked chapters
- Integration for automatic discovery by NovelUpdates
- Correct handling of the client’s GMT+8 publishing timezone
- Improved chronological ordering of chapters
- Handling of chapters released at the same time
- Troubleshooting of feed availability issues
- Reduction of feed items from 2,000+ to 100
- Ongoing maintenance and troubleshooting as new edge cases appeared
The client continued using the feed and returned for additional adjustments as the publishing workflow evolved.
Technical Takeaway
This project demonstrates why a standard WordPress RSS feed is not always sufficient for websites using custom themes, custom post structures, or specialized publishing workflows.
A reliable XML/RSS integration may require understanding:
- How content is stored
- How publication status is determined
- How scheduled and unscheduled content is handled
- How timezone conversion affects
pubDate - How identical timestamps affect item ordering
- How many records should be loaded
- How the destination platform consumes and processes the feed
For websites that need to send selected WordPress content to an external platform, a custom XML/RSS feed can provide much more precise control than a default WordPress feed.
Destination
The completed feed was designed for automatic content discovery by NovelUpdates, allowing eligible chapter updates to be supplied through a dedicated RSS feed.
WP2XML Services
This case is an example of the type of custom XML/RSS work we handle at WP2XML.
If your WordPress website uses a custom theme, custom content structure, membership system, scheduled publishing, or specific filtering rules, a standard RSS feed may not meet your requirements.
We can develop a custom XML, RSS, or JSON feed based on your exact feed specification and integration requirements.
Leave a Reply