#wordpress 2025-02-16

2025-02-16 UTC
[snarfed], gRegor and [tw2113] joined the channel
#
GWG That IndieAuth bug fix people were complaining about was just pushed to stable
DJ_[dj_je][d], IWDiscord and noderanger[d] joined the channel
#
GWG [snarfed]: Keep me posted if you need help
adar joined the channel
#
GWG [snarfed]: Stepped away... but I wonder if I updated something and lost Twitter because of X. Will be looking when I return to my desk shortly
derwen joined the channel
#
derwen Hi, Is there anyone here that has successfully setup an Indieweb blog using ClassicPress. I see that a number of the Wordpress Indieweb plugins support Wordpress 4.9 and ClassicPress used to support plugins that support Wordpress 4.9. I'm not sure if ClassicPress still supports these plugins or if they will continue to be backwards compatible into the future. Any help would be appreciated.
derwen joined the channel
#
GWG I started testing them all against ClassicPress. You should be fine
#
derwen Hi GWG, which Indieweb plugins have you tested? Did you test any themes that support microformats?
#
GWG derwen: Well, I have a theme I wrote for that
#
GWG But I'd imagine other ones would
#
GWG I'm happy to help any way I can
derwen joined the channel
#
derwen Thanks for the offer of help GWG. Do you know if ClassicPress will continue to support Wordpress 4.9 plugins (and if Indiweb plugins will continue to compatible with Wordpress 4.9)? I'm concerned about building a blog with ClassicPress and then having to a different CMS because the Indieweb plugins no longer work.
derwen1 and adar joined the channel
#
adar *having to switch to a different CMS
#
GWG ClassicPress is tracking WordPress 6.2 now, not 4.9
#
GWG Version 1 tracked 4.9. They rebased it
#
GWG Also, being someone who switched many of my sites to ClassicPress and who maintains many Indieweb plugins, I feel safer than ClassicPress will be supported than WordPress in that regard, though trying to keep both
#
[snarfed] hi GWG! switching here from GitHub
#
[snarfed] sorry, my site is tough to debug against, I"m using custom CSS instead of synd links's
#
GWG That Twitter problem was easy
#
GWG But the other one...Fed.Brid.Gy...won't it return the URL of whatever it was federated from?
#
GWG If it is Brid.gy, then I can map fed.brid.gy to a specific icon, which would solve the problem
#
[snarfed] ...but it would still use the text "website" for any other unknown domain, right?
#
[snarfed] that still seems wrong if the setting is set to "no text"
#
GWG It should map it to the website icon. Let me look again
#
GWG Let me read the logic.
#
GWG I think I found it.
#
GWG It loads the icon before it checks to see about a fallback to the website icon, so returns null
#
GWG Just inverted the entries.
#
GWG That should fix it
#
GWG You want to try the Github version?
#
[snarfed] Sure! That will take me a bit of time, but I'll figure it out and let you know
#
[snarfed] GitHub head should fix both issues?
#
GWG Yes.
#
GWG I can push it to stable, if you want
#
GWG The fix is definitely there
#
GWG I'll play with it a bit.
[morganm] joined the channel
#
adar GWG: thanks, that gives me some confidence in ClassicPress
#
GWG [snarfed]: Should be going up in Version 4.5.2
#
GWG Any time.
#
GWG Re ClassicPress
#
GWG [snarfed]: Ready for an update via the wordpress repository
#
[snarfed] thanks GWG! installed, Twitter synd links look right again, but http://fed.brid.gy links still have the "website" text: https://snarfed.org/2023-04-03_so-long-twitter-api-and-thanks-for-all-the-fish
derwen, sebbu2 and gRegor joined the channel
#
GWG Weird,.my test page does not show the text