home.social

#textpattern — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #textpattern, aggregated by home.social.

  1. @Hubzilla Support Forum Using HZ as a blog work on shared hosts, but does not make much sense, as it's database size will be about 100 times bigger, than just using a proper CMS. I recommend #textpattern for this.
  2. @Hubzilla Support Forum Using HZ as a blog work on shared hosts, but does not make much sense, as it's database size will be about 100 times bigger, than just using a proper CMS. I recommend #textpattern for this.
  3. Note for #Textpattern CMS users: Textpattern version 4.9.0 has been released 3 years 10 months and 28 days after the last update (4.8.8).
    Download: #^https://textpattern.com
    Thank you very much to all the devs!

    The new version brings the well-known stability, yet it is now compatible with PHP 8.5 & MySQL 8.4, and makes your life much easier running email from your domain by adding long-missed "support for SMTP for sending emails via third-party systems to improve deliverability. Industry-standard PHPMailer also available internally."

    All details here: #^https://textpattern.com/weblog/textpattern-490-released-php-85-mysql-84-features-fixes-fine-tuning-and-much-more

    I am running close to 60 custom-made websites on Textpattern, and am not expecting any major troubles updating.

    #Textpattern #v490 #update @Textpattern CMS

  4. Note for #Textpattern CMS users: Textpattern version 4.9.0 has been released 3 years 10 months and 28 days after the last update (4.8.8).
    Download: #^https://textpattern.com
    Thank you very much to all the devs!

    The new version brings the well-known stability, yet it is now compatible with PHP 8.5 & MySQL 8.4, and makes your life much easier running email from your domain by adding long-missed "support for SMTP for sending emails via third-party systems to improve deliverability. Industry-standard PHPMailer also available internally."

    All details here: #^https://textpattern.com/weblog/textpattern-490-released-php-85-mysql-84-features-fixes-fine-tuning-and-much-more

    I am running close to 60 custom-made websites on Textpattern, and am not expecting any major troubles updating.

    #Textpattern #v490 #update @Textpattern CMS

  5. Note for #Textpattern CMS users: Textpattern version 4.9.0 has been released 3 years 10 months and 28 days after the last update (4.8.8).
    Download: #^https://textpattern.com
    Thank you very much to all the devs!

    The new version brings the well-known stability, yet it is now compatible with PHP 8.5 & MySQL 8.4, and makes your life much easier running email from your domain by adding long-missed "support for SMTP for sending emails via third-party systems to improve deliverability. Industry-standard PHPMailer also available internally."

    All details here: #^https://textpattern.com/weblog/textpattern-490-released-php-85-mysql-84-features-fixes-fine-tuning-and-much-more

    I am running close to 60 custom-made websites on Textpattern, and am not expecting any major troubles updating.

    #Textpattern #v490 #update @Textpattern CMS

  6. Note for #Textpattern CMS users: Textpattern version 4.9.0 has been released 3 years 10 months and 28 days after the last update (4.8.8).
    Download: #^https://textpattern.com
    Thank you very much to all the devs!

    The new version brings the well-known stability, yet it is now compatible with PHP 8.5 & MySQL 8.4, and makes your life much easier running email from your domain by adding long-missed "support for SMTP for sending emails via third-party systems to improve deliverability. Industry-standard PHPMailer also available internally."

    All details here: #^https://textpattern.com/weblog/textpattern-490-released-php-85-mysql-84-features-fixes-fine-tuning-and-much-more

    I am running close to 60 custom-made websites on Textpattern, and am not expecting any major troubles updating.

    #Textpattern #v490 #update @Textpattern CMS

  7. Note for #Textpattern CMS users: Textpattern version 4.9.0 has been released 3 years 10 months and 28 days after the last update (4.8.8).
    Download: #^https://textpattern.com
    Thank you very much to all the devs!

    The new version brings the well-known stability, yet it is now compatible with PHP 8.5 & MySQL 8.4, and makes your life much easier running email from your domain by adding long-missed "support for SMTP for sending emails via third-party systems to improve deliverability. Industry-standard PHPMailer also available internally."

    All details here: #^https://textpattern.com/weblog/textpattern-490-released-php-85-mysql-84-features-fixes-fine-tuning-and-much-more

    I am running close to 60 custom-made websites on Textpattern, and am not expecting any major troubles updating.

    #Textpattern #v490 #update

  8. My research on this has sent me in a complete circle back to @textpattern again. Turns out I starred the wet_textfilter_markdown plugin on GitHub years ago, which can be used to replace Textile in #Textpattern's Write screen. It can even be made the default.

    I just need a nice and reasonable way of dealing with images now, something that doesn't drive me crazy while trying to write something. Oh, and maybe some decent CSS to improve the typography I've mushed over the years.

  9. My research on this has sent me in a complete circle back to @textpattern again. Turns out I starred the wet_textfilter_markdown plugin on GitHub years ago, which can be used to replace Textile in #Textpattern's Write screen. It can even be made the default.

    I just need a nice and reasonable way of dealing with images now, something that doesn't drive me crazy while trying to write something. Oh, and maybe some decent CSS to improve the typography I've mushed over the years.

  10. My research on this has sent me in a complete circle back to @textpattern again. Turns out I starred the wet_textfilter_markdown plugin on GitHub years ago, which can be used to replace Textile in #Textpattern's Write screen. It can even be made the default.

    I just need a nice and reasonable way of dealing with images now, something that doesn't drive me crazy while trying to write something. Oh, and maybe some decent CSS to improve the typography I've mushed over the years.

  11. Also worth a read: #wordPress anecdotes like #capitalPdangit which broke Perfectly oPerable Plugins and web Pages without develoPers knowing what the Phuck is going on in Mattmullenland 👉 https://core.trac.wordpress.org/ticket/13971

    (via
    @[email protected] of #textPattern fame, see https://forum.textpattern.com/viewtopic.php?pid=337934#p337934 )

  12. Also worth a read: #wordPress anecdotes like #capitalPdangit which broke Perfectly oPerable Plugins and web Pages without develoPers knowing what the Phuck is going on in Mattmullenland 👉 https://core.trac.wordpress.org/ticket/13971

    (via
    @[email protected] of #textPattern fame, see https://forum.textpattern.com/viewtopic.php?pid=337934#p337934 )

  13. Also worth a read: #wordPress anecdotes like #capitalPdangit which broke Perfectly oPerable Plugins and web Pages without develoPers knowing what the Phuck is going on in Mattmullenland 👉 https://core.trac.wordpress.org/ticket/13971

    (via
    @[email protected] of #textPattern fame, see https://forum.textpattern.com/viewtopic.php?pid=337934#p337934 )

  14. Also worth a read: #wordPress anecdotes like #capitalPdangit which broke Perfectly oPerable Plugins and web Pages without develoPers knowing what the Phuck is going on in Mattmullenland 👉 https://core.trac.wordpress.org/ticket/13971

    (via
    @[email protected] of #textPattern fame, see https://forum.textpattern.com/viewtopic.php?pid=337934#p337934 )

  15. I'm kinda bemused about the ongoing #WordPress / #Automattic drama. I have never used WP (all the blogs I have ever created either used the #Textpattern CMS, was hosted on Google's Blogger, used my own #Perl-coded CMS, or were hand-coded HTML), so I just follow the news without having had my toes in the WP ecosystem. I therefore have little to no skin in the game.

  16. I'm kinda bemused about the ongoing #WordPress / #Automattic drama. I have never used WP (all the blogs I have ever created either used the #Textpattern CMS, was hosted on Google's Blogger, used my own #Perl-coded CMS, or were hand-coded HTML), so I just follow the news without having had my toes in the WP ecosystem. I therefore have little to no skin in the game.

  17. I'm kinda bemused about the ongoing #WordPress / #Automattic drama. I have never used WP (all the blogs I have ever created either used the #Textpattern CMS, was hosted on Google's Blogger, used my own #Perl-coded CMS, or were hand-coded HTML), so I just follow the news without having had my toes in the WP ecosystem. I therefore have little to no skin in the game.

  18. I'm kinda bemused about the ongoing #WordPress / #Automattic drama. I have never used WP (all the blogs I have ever created either used the #Textpattern CMS, was hosted on Google's Blogger, used my own #Perl-coded CMS, or were hand-coded HTML), so I just follow the news without having had my toes in the WP ecosystem. I therefore have little to no skin in the game.

  19. I'm kinda bemused about the ongoing #WordPress / #Automattic drama. I have never used WP (all the blogs I have ever created either used the #Textpattern CMS, was hosted on Google's Blogger, used my own #Perl-coded CMS, or were hand-coded HTML), so I just follow the news without having had my toes in the WP ecosystem. I therefore have little to no skin in the game.

  20. Y’all know what this #WordPress kerfuffle means, right? We need to wake good ol’ #Textpattern from its long slumber. It’s been lying in waiting, carefully maintained, ready for a resurrection.

    It was the reason I never got on the WP train back in the early aughts. Textpattern just jived much more with my web sensibilities. And Dean Allen was a mf’ing king.

    textpattern.com/

  21. Y’all know what this #WordPress kerfuffle means, right? We need to wake good ol’ #Textpattern from its long slumber. It’s been lying in waiting, carefully maintained, ready for a resurrection.

    It was the reason I never got on the WP train back in the early aughts. Textpattern just jived much more with my web sensibilities. And Dean Allen was a mf’ing king.

    textpattern.com/

  22. Y’all know what this #WordPress kerfuffle means, right? We need to wake good ol’ #Textpattern from its long slumber. It’s been lying in waiting, carefully maintained, ready for a resurrection.

    It was the reason I never got on the WP train back in the early aughts. Textpattern just jived much more with my web sensibilities. And Dean Allen was a mf’ing king.

    textpattern.com/

  23. Y’all know what this #WordPress kerfuffle means, right? We need to wake good ol’ #Textpattern from its long slumber. It’s been lying in waiting, carefully maintained, ready for a resurrection.

    It was the reason I never got on the WP train back in the early aughts. Textpattern just jived much more with my web sensibilities. And Dean Allen was a mf’ing king.

    textpattern.com/

  24. Y’all know what this #WordPress kerfuffle means, right? We need to wake good ol’ #Textpattern from its long slumber. It’s been lying in waiting, carefully maintained, ready for a resurrection.

    It was the reason I never got on the WP train back in the early aughts. Textpattern just jived much more with my web sensibilities. And Dean Allen was a mf’ing king.

    textpattern.com/

  25. I want to use anything other than #WordPress for a project. (I don’t consider their humble brag about powering 40 % of the web to be a positive.) I’ve wanted to give #Textpattern another go, but the project needs a lot of work to be brought back up to date. I think I‘ve landed on Chyrp Lite. It‘s quite neat! ✍️ #CMS #ChyrpLite
    chyrplite.net/

  26. I want to use anything other than #WordPress for a project. (I don’t consider their humble brag about powering 40 % of the web to be a positive.) I’ve wanted to give #Textpattern another go, but the project needs a lot of work to be brought back up to date. I think I‘ve landed on Chyrp Lite. It‘s quite neat! ✍️ #CMS #ChyrpLite
    chyrplite.net/

  27. I want to use anything other than #WordPress for a project. (I don’t consider their humble brag about powering 40 % of the web to be a positive.) I’ve wanted to give #Textpattern another go, but the project needs a lot of work to be brought back up to date. I think I‘ve landed on Chyrp Lite. It‘s quite neat! ✍️ #CMS #ChyrpLite
    chyrplite.net/

  28. I want to use anything other than #WordPress for a project. (I don’t consider their humble brag about powering 40 % of the web to be a positive.) I’ve wanted to give #Textpattern another go, but the project needs a lot of work to be brought back up to date. I think I‘ve landed on Chyrp Lite. It‘s quite neat! ✍️ #CMS #ChyrpLite
    chyrplite.net/

  29. I want to use anything other than #WordPress for a project. (I don’t consider their humble brag about powering 40 % of the web to be a positive.) I’ve wanted to give #Textpattern another go, but the project needs a lot of work to be brought back up to date. I think I‘ve landed on Chyrp Lite. It‘s quite neat! ✍️ #CMS #ChyrpLite
    chyrplite.net/

  30. While updating my personal #netbsd server to patch #regresshion, I updated all my installed packages, which broke #php, which broke apache.

    So I shaved all those #yaks and discovered that my CMS (#textpattern) was years out of date, and not compatible with modern PHP. And my self-written tagging plugin would require changes, if I upgraded.

    So <big sigh of relief> I am finally rid of PHP, Apache, and MySQL on that server! That feels really good. (Even if I'm sad my old content is gone.)

  31. While updating my personal #netbsd server to patch #regresshion, I updated all my installed packages, which broke #php, which broke apache.

    So I shaved all those #yaks and discovered that my CMS (#textpattern) was years out of date, and not compatible with modern PHP. And my self-written tagging plugin would require changes, if I upgraded.

    So <big sigh of relief> I am finally rid of PHP, Apache, and MySQL on that server! That feels really good. (Even if I'm sad my old content is gone.)

  32. While updating my personal #netbsd server to patch #regresshion, I updated all my installed packages, which broke #php, which broke apache.

    So I shaved all those #yaks and discovered that my CMS (#textpattern) was years out of date, and not compatible with modern PHP. And my self-written tagging plugin would require changes, if I upgraded.

    So <big sigh of relief> I am finally rid of PHP, Apache, and MySQL on that server! That feels really good. (Even if I'm sad my old content is gone.)

  33. While updating my personal #netbsd server to patch #regresshion, I updated all my installed packages, which broke #php, which broke apache.

    So I shaved all those #yaks and discovered that my CMS (#textpattern) was years out of date, and not compatible with modern PHP. And my self-written tagging plugin would require changes, if I upgraded.

    So <big sigh of relief> I am finally rid of PHP, Apache, and MySQL on that server! That feels really good. (Even if I'm sad my old content is gone.)

  34. While updating my personal #netbsd server to patch #regresshion, I updated all my installed packages, which broke #php, which broke apache.

    So I shaved all those #yaks and discovered that my CMS (#textpattern) was years out of date, and not compatible with modern PHP. And my self-written tagging plugin would require changes, if I upgraded.

    So <big sigh of relief> I am finally rid of PHP, Apache, and MySQL on that server! That feels really good. (Even if I'm sad my old content is gone.)