4 ms·

Well, there's a blast from the past. I thought WordPress had squashed tp long ago. Happy to be wrong about that. Bit surprised it's still alive, supports moder

by e12e 6y ago

Well, there's a blast from the past. I thought WordPress had squashed tp long ago. Happy to be wrong about that. Bit surprised it's still alive, supports modern php - but apparently still require mysql/MariaDB - no sqlite, no postgresql support? Still, if it ever saves me from managing WordPress with its awful plug-ins... I could see admining a dedicated mysql instance being worth the effort...

petecooper 6y ago
Textpattern person here. >I thought WordPress had squashed tp long ago. Wordpress is much more widely-used. Textpattern is still around! Edit: I almost forgot about this: https://wordpress.org/news/2006/04/wordpattern/ https://wordpress.org/news/2006/04/wordpattern/ >supports modern php - but apparently still require mysql/MariaDB - no sqlite, no postgresql support? Correct. MySQL and store brand remixes mostly work just fine, no plans for SQLite or PostgreSQL as far as I know. Pull requests are welcome! https://github.com/textpattern/textpattern https://github.com/textpattern/textpattern
- e12e 6y ago
  I'm sure mysql works perfectly fine for text pattern - but if I already need to maintain a postgresql db with backups and point-in-time recovery (or rent a managed instance) - not needing to setup mysql would be nice. And as for sqlite - it would allow for even simpler setups (and quite[1] easy backups). [1] via the backup dot command for example https://stackoverflow.com/a/34577922 https://stackoverflow.com/a/34577922
stefdawson 6y ago
> no sqlite, no postgresql support? Sadly not. We haven't made the jump to PDO (yet) and still use some MySQL-specific database features, such as ordering by FIELD. Once we wean the core code off that and schedule in the migration to PDO with all the prepare/execute goodness that brings, we'll support whatever database engines that PHP offer under PDO.
- e12e 6y ago
  Funny, I think I first heard about textpattern and PDO at approximately the same time...
  - stefdawson 6y ago
    Haha. Yeah. Moving to PDO has been on the todo list for well over a decade and keeps getting pushed back. It's hard graft to refactor all the underlying calls and decide whether we want an ORM layer or not, and which to choose or roll-our-own, and then change all the places in the code that use the DB layer to do prepare-execute. And the plugin upheaval that rides its coattails. It's one of those things that's always overlooked in the "ain't broke so don't fix it" camp. But I know it needs doing. One day...
    - e12e 6y ago
      > change all the places in the code that use the DB layer to do prepare-execute. Take this with a big grain of salt, but I vaguely remember tp not being great at using prepared statements / safe quoting provided by the db driver - has that been improved (if it ever was a problem)? Is it easy for plug-ins to accidentally open up to sql injection?
      - stefdawson 6y ago
        Prepared whatnow? :) Nope, we don't use them yet. Bane of my life. We rely on all core calls and plugin authors escaping content before calling our DB layer. That has to change and will be part of the move to PDO. It's just a lot of faff work and there are always shinier things to work on. I've been secretly hoping that some kind soul will do it and issue a Pull Request. But maybe I should stop being lazy, bite the bullet and do it myself!
        e12e 6y ago
        Thank you for your candid reply. I had a nagging memory of some troubles from bugtraq or an equivalent list (mind, many, many cms and blogs had trouble with sqli..). I am a bit surprised that hasn't been (universally, permanently) fixed in the last decade, though.
tootie 6y ago
WordPress is probably stronger than ever right now. I've never selected it for a project, never seen any client select it on purpose, never seen anyone give it more than a lukewarm endorsement, yet it still shows up everywhere. Even in giant enterprises. It's inescapable and undying. I suppose that's as good as testament as anything that it's not nearly as bad as people say.
deleted 6y ago
[deleted]

by e12e 6y ago

petecooper 6y ago

Textpattern person here. >I thought WordPress had squashed tp long ago. Wordpress is much more widely-used. Textpattern is still around! Edit: I almost forgot about this: https://wordpress.org/news/2006/04/wordpattern/ https://wordpress.org/news/2006/04/wordpattern/ >supports modern php - but apparently still require mysql/MariaDB - no sqlite, no postgresql support? Correct. MySQL and store brand remixes mostly work just fine, no plans for SQLite or PostgreSQL as far as I know. Pull requests are welcome! https://github.com/textpattern/textpattern https://github.com/textpattern/textpattern

e12e 6y ago
I'm sure mysql works perfectly fine for text pattern - but if I already need to maintain a postgresql db with backups and point-in-time recovery (or rent a managed instance) - not needing to setup mysql would be nice. And as for sqlite - it would allow for even simpler setups (and quite[1] easy backups). [1] via the backup dot command for example https://stackoverflow.com/a/34577922 https://stackoverflow.com/a/34577922

stefdawson 6y ago

> no sqlite, no postgresql support? Sadly not. We haven't made the jump to PDO (yet) and still use some MySQL-specific database features, such as ordering by FIELD. Once we wean the core code off that and schedule in the migration to PDO with all the prepare/execute goodness that brings, we'll support whatever database engines that PHP offer under PDO.

e12e 6y ago
Funny, I think I first heard about textpattern and PDO at approximately the same time...
- stefdawson 6y ago
  Haha. Yeah. Moving to PDO has been on the todo list for well over a decade and keeps getting pushed back. It's hard graft to refactor all the underlying calls and decide whether we want an ORM layer or not, and which to choose or roll-our-own, and then change all the places in the code that use the DB layer to do prepare-execute. And the plugin upheaval that rides its coattails. It's one of those things that's always overlooked in the "ain't broke so don't fix it" camp. But I know it needs doing. One day...
  - e12e 6y ago
    > change all the places in the code that use the DB layer to do prepare-execute. Take this with a big grain of salt, but I vaguely remember tp not being great at using prepared statements / safe quoting provided by the db driver - has that been improved (if it ever was a problem)? Is it easy for plug-ins to accidentally open up to sql injection?
    - stefdawson 6y ago
      Prepared whatnow? :) Nope, we don't use them yet. Bane of my life. We rely on all core calls and plugin authors escaping content before calling our DB layer. That has to change and will be part of the move to PDO. It's just a lot of faff work and there are always shinier things to work on. I've been secretly hoping that some kind soul will do it and issue a Pull Request. But maybe I should stop being lazy, bite the bullet and do it myself!
      - e12e 6y ago
        Thank you for your candid reply. I had a nagging memory of some troubles from bugtraq or an equivalent list (mind, many, many cms and blogs had trouble with sqli..). I am a bit surprised that hasn't been (universally, permanently) fixed in the last decade, though.

tootie 6y ago

WordPress is probably stronger than ever right now. I've never selected it for a project, never seen any client select it on purpose, never seen anyone give it more than a lukewarm endorsement, yet it still shows up everywhere. Even in giant enterprises. It's inescapable and undying. I suppose that's as good as testament as anything that it's not nearly as bad as people say.

deleted 6y ago

[deleted]