r/SoftwareTips

My client had a phpBB forum that died 5 years ago. 60,000 topics, ~180k comments, spanning 2008-2020. He wanted to preserve the content. WordPress was the practical choice (my opinion) for long-term manageability.

Every migration plugin I tried was either abandoned, broke above 5k posts, or couldn't handle phpBB's schema at all. So I wrote a custom PHP script that connected directly to MySQL and streamed data in batches.

The setup:

• Ran everything in Docker: phpBB container (old DB), WordPress container (new DB), PHP script as a third container
• My workflow: if something broke, I'd just docker compose down -v && docker compose up -d and start fresh from clean images
• This let me test aggressively without worrying about corrupting state

The approach:

1. Connect to both databases: PDO to phpBB (read-only) and WordPress (write)
2. Batch process topics: SELECT with LIMIT/OFFSET, 500 rows at a time. Loop until no more rows
3. Map phpBB tables to WordPress:
   • phpbb_topics + phpbb_posts (first post) --> wp_posts
   • phpbb_posts (replies) --> wp_comments with comment_parent
   • phpbb_forums --> wp_terms (categories)
   • phpbb_users --> just usernames (no emails/passwords for privacy)
4. Convert timestamps: phpBB uses Unix integers, WordPress wants YYYY-MM-DD HH:MM:SS
5. Handle comment threading: iterate replies in order, chain comment_parent to previous ID
6. Add indexes on temp tables before big JOINs: otherwise 60k rows is slow

What I removed:

• User emails and passwords (privacy)
• Profile pictures (not worth it for dead forum)

Results:

• 60,247 topics --> 60k WordPress posts
• ~180k comments with threading
• All timestamps preserved (2008-2020)
• Some data was lost
• Total time: 1 day including testing, debugging, redoing from scratch 7 times

Bonus: Client found a way to monetize the archive (backlinks... somebody's still buying them). So dead forum became an asset.

If you want the code, describe the setup to any AI and it'll generate it, the approach above is the hard part.

Anyone else done migrations this big?

Since 2013, I've purchased four (4) Slider Revolution plugins with "lifetime" licensing, and I've honestly only used the Slider Revolution WordPress plugin for creating fancy photo sliders for my various page heading (I'm a property photographer) and to use a few of its themes.

But the update to SR7 now forces us lifetime customers to become subscription-based customers, and you gave little thought to honour the thousands of faithful customers who bought lifetime subscriptions.

And to add insult to injury (but not too surprising given the vulnerabilities we've faithfully endured over the years), SR6 produces a vulnerability that cannot be corrected unless one subscribes to SR7.

Warning: * Unknown WordPress core version: 7.0. Unauthenticated Sensitive Information Exposure via 'sliders/stream'.

Lovely. It was a nice ride but our time is done ThemePunch.

For you not to even think about offering and honouring a "lifetime" license for those who bought lifetime licenses speaks volumes about your company.

So now you're forcing me (and countless others) to move to another more affordable provider.

I'm choosing LayerSlider where I can pay just £155 ($207) for a "lifetime plugin" for three sites. I'm sure thousand will do the same.

In a world where nearly everything online is now subscription based, you folks still have not clued-in that you are not the only option. You're just following the others like lemmings off a cliff.

Cheers,

Frank

The app is called Puplytics.

Before this project I had basically zero real coding experience. I went from not understanding app structure at all to learning React Native / Expo workflows, App Store Connect, subscriptions, AI APIs, privacy compliance, camera permissions, TestFlight builds, backend deployment, and debugging random production issues at 2am.

Honestly the hardest part wasn’t even building the app — it was getting through Apple review.

I got rejected for:
• subscription flow issues
• missing legal links
• camera permission wording
• AI consent flow compliance
• metadata problems
• purchase restore handling
• sandbox purchase behavior
• UI edge cases on iPad
…and probably more I’m forgetting lol.

The app itself is a dog wellness tracking app focused on digestive health and daily wellness tracking.

Features include:
• AI stool scan analysis
• symptom tracking
• food logging
• sleep & mood tracking
• AI wellness chat
• trend analysis
• downloadable vet reports
• multi-pet support
• reminders and history timelines

The original idea came from dealing with recurring stomach issues with my own dog and constantly forgetting what food changes or symptoms happened during vet visits.

So I basically built the app I wished existed.

The craziest part is realizing how much you can actually build now if you’re willing to learn while moving fast.

Would genuinely love feedback from other builders / vibe coders:
• UI/UX thoughts
• onboarding feedback
• feature ideas
• App Store screenshots
• monetization thoughts
• anything that feels confusing or broken

Still improving it daily. (As of right now it’s been live for about 20 minutes lol)

The app is called Puplytics on the App Store if anyone wants to roast/test it 🙏

Hallo zusammen,

ein Freund und ich beschäftigen uns aktuell viel mit der Frage, wie kleine Service- und Handwerksbetriebe ihren Alltag organisieren.

Vor allem Dinge wie Termine, spontane Änderungen, Mitarbeiterkoordination, Rücktermine, Ersatzteile oder Kundenkommunikation.

Viele Betriebe arbeiten ja noch viel über Telefon, WhatsApp oder einfach alles im Kopf.

Mich würde ehrlich interessieren:

-Was sind bei euch aktuell die größten organisatorischen Probleme im Alltag?
-Wo geht am meisten Zeit oder Energie verloren?
-Welche Tools nutzt ihr und welche funktionieren gut und welche eher gar nicht?
-Und was würdet ihr euch einfacher wünschen?

Wir versuchen gerade besser zu verstehen, wie kleine operative Unternehmen tatsächlich arbeiten und wo digitale Organisation wirklich sinnvoll helfen kann, ohne dass man direkt riesige komplizierte Systeme braucht.

Würde mich über ehrliche Einblicke freuen :)

When I started at my current company, AI tools were still pretty limited. Our tech lead was an excellent engineer with strong problem-solving skills, and it was genuinely inspiring working with him on difficult tasks.

Over the last couple of years though, especially recently, I’ve noticed him relying on AI for almost everything — not just coding help, but also design decisions, architecture discussions, and even personal-life choices.

I’m not anti-AI and I use these tools myself, but sometimes it feels like critical thinking and skepticism are disappearing from the process. I’ve started trusting his technical judgment less because many decisions now seem to come directly from AI suggestions rather than deeper reasoning or experience.

Maybe this is just the direction the industry is heading, but I’m curious if anyone else has noticed a similar shift with senior engineers or mentors becoming heavily dependent on AI tools.

I’ve been noticing this for a while.

Phones and laptops are way more powerful now, but a lot of apps somehow feel slower than before.

Some apps take longer to open, use a lot of RAM, and sometimes lag even for simple things. And almost everything needs updates every few days.

I know modern apps have more features now, cloud stuff, AI, animations, cross-platform support, etc. But still, sometimes it feels like performance is no longer the main focus.

For people who actually build software, what do you think is the biggest reason?

• Too many features?
• modern frameworks?
• pressure to release fast?
• less optimization?
• something else?

Just curious what developers think about this.

Hello folks,

I am in the middle of building my personal/professional website, and wanted to know from you guys what could be the simplest and more efficient way to do so.

I got little knowledge of HTML, and I got a background as a graphic designer, so front-end is my go to.
I actually have a draft of my website made on Wordpress with a simple theme called Minimalio, but I want to develop it even further or just starting from scratch with another theme (or service outside WP if it happen to be easier/cheaper.

It will have a simple blog page, a portfolio page (with the possibility to filter by sections), and the usual about, biography and stuff.

Here's some more things so you got the bigger picture

• Freemium themes and plug-ins are a big no. I hate to spend time learning things just to know, later on, that I need to pay to unlock certain stuff
• I always had trouble understanding how themes works, and if I have to pay for a theme or not
• I'd like to have flexibility: there's no problem in investing some time to learn new stuffs if it helps to achieve what I'm aiming for
• I found Wordpress to be relatively cheap. I don't want to add another expensive subscription to my wallet (I got spammed with Webflow and similar).

Any advice is welcome! Even if you think WP is not the right platform.
If something is not clear, just ask and I'll try to elaborate on that :)

Have a nice one!!

TL;DR: I am using WordPress dot org and want to know simple solution to build my portfolio/blog page.

Our official system is so frustrating that you have to keep drafting responses in google docs and only upload everything. That creates version control issues and defeats the purpose of having dedicated software. Wondering if anyone has fixed this kind of adoption problem.

We built a data scraper that pulls publicly available information. One issue we keep running into is CAPTCHA/rate-limit protection.

We currently use CAPTCHA-solving software, but it only works for a limited number of requests (around 10 or so) before the site starts blocking or rejecting requests again.

We already use CAPTCHA-solving software, but it eventually gets blocked.

Would rotating proxies/VPNs help with this? Are there different types people use for scraping setups? Any advice on making the scraper more stable without constantly triggering anti-bot systems?

We’d also appreciate any advice on better practices for scraping public sites without constantly triggering anti-bot protections.