DEV Community: Ozan Yıldırım

RSS to X (Twitter) PHP Bot

Ozan Yıldırım — Sat, 18 Oct 2025 23:27:31 +0000

RSS to X (Twitter) PHP Bot. Most sites already broadcast updates via RSS, but posting to X (Twitter) is still a manual chore. In this mini build, we ship a self-hosted PHP bot that reads your RSS feed and publishes new items to X using the official API—no plugins, no monthly fees. It’s the sibling of our Instagram bot: simple cURL requests, a little formatting, and a cron job.

What it does

Reads RSS and picks the latest items (with a per-run limit).

Builds the post text (title + link, truncated to fit X limits).

Calls X API with a bearer token to publish.

De-dupes items (so you don’t double-post) and avoids overlapping runs.

Why this approach

Total control (self-hosted), zero subscriptions.

Works with any stack (plain PHP + cURL).

Easy to extend: hashtags, UTM links, schedules, language filters…

What you’ll need (no secrets shown)
An X developer account and a Bearer token for posting (app in write mode).

A public RSS feed URL.

PHP with cURL.

(Optional) a tiny file/DB store to remember posted GUIDs.

Posting flow (high-level):

GET RSS → parse items

For each unseen item: build status = "{title} {short_link}"

POST to X’s API with Authorization: Bearer …

Store GUID hash to avoid duplicatesRSS to X (Twitter) PHP Bot. Most sites already broadcast updates via RSS, but posting to X (Twitter) is still a manual chore. In this mini build, we ship a self-hosted PHP bot that reads your RSS feed and publishes new items to X using the official API—no plugins, no monthly fees. It’s the sibling of our Instagram bot: simple cURL requests, a little formatting, and a cron job.

What it does

Reads RSS and picks the latest items (with a per-run limit).

Builds the post text (title + link, truncated to fit X limits).

Calls X API with a bearer token to publish.

De-dupes items (so you don’t double-post) and avoids overlapping runs.

Why this approach

Total control (self-hosted), zero subscriptions.

Works with any stack (plain PHP + cURL).

Easy to extend: hashtags, UTM links, schedules, language filters…

What you’ll need (no secrets shown)
An X developer account and a Bearer token for posting (app in write mode).

A public RSS feed URL.

PHP with cURL.

(Optional) a tiny file/DB store to remember posted GUIDs.

Posting flow (high-level):

GET RSS → parse items

For each unseen item: build status = "{title} {short_link}"

POST to X’s API with Authorization: Bearer …

Store GUID hash to avoid duplicates

Code & Source : https://minicoursey.com/rss-to-x-twitter-php-bot

RSS to Instagram PHP Bot

Ozan Yıldırım — Sat, 18 Oct 2025 21:57:02 +0000

Ship RSS to Instagram with a Tiny PHP Bot (No Plugins, No CMS)
Most blogs already syndicate updates through RSS—but Instagram is still a manual grind. In this mini-build, we turn any site (ours wasn’t WordPress) into an auto-publisher: new RSS items → square, readable title cards → posted to an Instagram Professional account via the Instagram Graph API.

The goal is practical and reproducible:

Input: your site’s RSS feed.
Transform: generate a clean 1080×1080 image with the post title (high contrast, safe margins, custom font).
Output: publish to your own Instagram Business/Creator account using the two-step Graph flow (/media → /media_publish).
Why this approach?
No third-party schedulers: Great tools exist, but monthly fees add up. We wanted a zero-subscription path we control.
Works with any stack: It’s plain PHP with cURL and GD. Drop-in files; no Composer required.
Readable thumbnails: Instead of reusing wide (1200×630) OG images that shrink poorly in the grid, we render a square title card that stays legible on mobile.
What we built (at a glance)
rss_to_instagram.php — polls your RSS, de-dupes posts, creates a media container, then publishes.
iggen.php — a tiny image endpoint that renders title-only square cards (configurable padding, font, colors). Returns JPEG (IG requirement).
Optional helpers used during setup (not required in production): OAuth login to get a user token, exchange for a page token, quick “test publish” scripts, and small diagnostics.
Requirements (the non-negotiables)
Instagram Professional account (Business or Creator) linked to a Facebook Page.
A Facebook App in Development mode, with you as Admin/Tester.
Permissions requested at login: instagram_basic, pages_show_list, pages_read_engagement, and instagram_content_publish.
Use a Page Access Token when publishing (user tokens won’t publish).
Security & housekeeping
Never commit secrets. In the sample code we’ll publish, all tokens/IDs are redacted and loaded from environment variables or a local config file ignored by Git.
Add a simple file lock so your cron job can’t double-run.
Consider a tiny de-dup store (file or DB) keyed by RSS guid to avoid accidental reposts.
What you’ll learn
How to grab a long-lived user token, derive a Page Access Token, and publish safely.
How to generate consistently readable IG images with GD (font selection, padding, fallback).
How to harden a quick script for real-world use (timeouts, error logging, limits).
In the next section, I’ll share the redacted code snippets and a step-by-step setup. If you can run PHP and edit a couple of files, you can ship this in under an hour—and finally let Instagram take care of itself.

Prerequisites
Instagram Professional (Business or Creator) account linked to a Facebook Page.

A Facebook App in Development mode. You (the publisher) are Admin/Tester.

When logging in to get tokens, request these scopes:
instagram_basic, pages_show_list, pages_read_engagement, instagram_content_publish.

You will publish with a Page Access Token (not a user token).

continuation of the article and codes: https://minicoursey.com/rss-to-instagram-php-bot

Disable Comments Without Plugin in WordPress

Ozan Yıldırım — Sat, 26 Jul 2025 22:55:59 +0000

Disable Comments Without Plugin to block spam and keep your WordPress site clean. Here’s how to turn off comments site-wide with a simple tweak.

Step 1: Add the Comments Disable Code
Add this to your child theme’s functions.php:

// Disable comments in WordPress
add_action(‘admin_init’, function() {
  // Close comments on all post types
  foreach (get_post_types() as $post_type) {
    if (post_type_supports($post_type, ‘comments’)) {
      remove_post_type_support($post_type, ‘comments’);
      remove_post_type_support($post_type, ‘trackbacks’);
    }
  }
});

// Hide existing comments
add_filter(‘comments_array’, ‘__return_empty_array’, 10, 2);

How It Works
This snippet removes comment and trackback support from all post types and hides any existing comments on your site.

Why Disable Comments Without Plugin?
Most sites don’t need WordPress comments anymore. Disabling them helps block spam and keeps your database lean.

Common Mistake
This won’t delete old comment data from your database. Use a cleanup plugin or a manual SQL query if you want to remove existing comments.

Pro Tip
Always place this tweak in your child theme’s functions.php so it stays active after updates.

Related Snippet
If you liked this, check out my guide on disabling the WP version number without a plugin in WordPress.

Source : https://quickdevtips.com/disable-comments-without-plugin

CSS Overflow — Hidden, Scroll & Auto Explained

Ozan Yıldırım — Sat, 26 Jul 2025 22:52:22 +0000

Ever had content spill out of its container and break your layout? The CSS Overflow property controls what happens when content is larger than its container. Whether you want to hide overflow, add scrollbars, or let the browser decide, mastering Overflow helps you build clean, controlled designs. In this MiniCoursey quick guide, you’ll learn how overflow works, the differences between hidden, scroll, and auto, and when to use each option to keep your layouts tidy.

What is the Overflow Property?
Overflow tells the browser what to do when an element’s content is too big to fit inside its box. By default, content that overflows just spills out. With Overflow, you can hide it, clip it, or make it scrollable.

Overflow: Hidden
overflow: hidden; cuts off any content that goes outside the container’s box. This is useful for sliders, cards, or images you want to crop.

.container {
  overflow: hidden;
}

Overflow: Scroll
overflow: scroll; always shows scrollbars — even if they’re not needed. This guarantees the user can scroll to see hidden content.

.container {
  overflow: scroll;
}

Overflow: Auto
overflow: auto; shows scrollbars only when the content overflows. This is the most common option for flexible, clean layouts.

.container {
  overflow: auto;
}

💡 Pro Tip: You can set overflow for X and Y directions separately with overflow-x and overflow-y.

⚠️ Common Mistake: Using overflow: hidden can hide important content — make sure it’s intentional!

FAQ
Q: What’s the default overflow?
A: visible — content just spills outside the box if it’s too big.

Q: Can I make a scrollable div?
A: Yes! Use overflow: auto or overflow: scroll plus a fixed height or width.

Related Link
👉 Check out previous: CSS Float Property — What It Is & When to Use It

Where to Learn More
Play with overflow on different containers. MDN’s Overflow docs have clear visuals and examples for tricky cases like scroll shadows and hidden content.

Conclusion
Congrats — you now know how to handle overflowing content with CSS! This small detail keeps your layouts clean, usable, and looking polished.

✨ Bookmark MiniCoursey for more quick & free mini courses!