#wordpress 2019-05-28
2019-05-28 UTC
[fluffy], [jgarber], [Rose], [frank], [jgmac1106] and [tonz] joined the channel
jeremych_ joined the channel
# 
[tonz] yes, will try with SecRuleRemoveById 950120 (that being the rul in question, per https://raw.githubusercontent.com/SpiderLabs/owasp-modsecurity-crs/master/base_rules/modsecurity_crs_40_generic_attacks.conf
[calumryan] and [kevinmarks] joined the channel
[Rose], [tonz], [coreagile], [jgmac1106], [kevinmarks786], [davidmead], [cleverdevil] and [eddie] joined the channel
[jgmac1106], [tbc], [tantek], [Rose], [davidmead] and gRegorLove_ joined the channel
# 
GWG And then it is /feed/json instead of just /feed
[kevinmarks] and [kevinmarks786] joined the channel
gRegorLove__ joined the channel
[tonz] joined the channel
# [tonz] Ok, so the RFI errors by modsecurity have been taken care of by the hoster, in my attempt at logging into https://meso.tzyl.nl with a micropub client. It still results in a 403 forbidden ‘unauthorized’ message though. My error log now says [Tue May 28 19:13:09.364956 2019] [lsapi:notice] [pid 1978128] [client 173.230.155.197:42778] [host meso.tzyl.nl] Backend log: PHP Warning: Invalid argument supplied for foreach() in
[chrisaldrich], [tantek] and [tonz] joined the channel
[jgmac1106], [kevinmarks786] and [eddie] joined the channel
[tonz] joined the channel
[schmarty], [jgmac1106], [eddie], [tantek], arush and [arush] joined the channel
# 
[arush] Hi all. It seems I am not the only one tearing my hair out over WordPress Indieauth. This is oddly comforting somehow.
# [arush] I do not have a solution yet, but if I find one before the others in this channel do, I will be more than happy to post it. The problem that I’m reading through sounds like the one that I am having.
# [arush] It will authorize exactly once, on a completely fresh word press install, and after that point everything returns a 403 error because there is not a matching token in the database when a micro public post is attempted.
# [arush] Micropub
# [arush] The end points are there, Services can find and discover them, they just cannot authorize, except for that one time after I reinstalled the plug-in and then attempted to use on your Swarm. Erin Pereki is probably going to murder me after the amount of times I have tried to submit check-in‘s.
# [arush] I am trying to add a new person to the indieweb and this plug-in is making a liar out of me.
# [arush] With. It’s the authorization plug-in that I think is causing the problem.
# [arush] Yes, and I ran the script check. It says everything checks out.
# [arush] Everything else seems to be working fine. There is a PHP issue with the simple location plug-in, but I need to finish writing the code change that will fix that and submit it as a pull request. I just haven’t had time because I’ve been digging into this authorization weirdness.
[jgmac1106] joined the channel
# [arush] It’s an on caught error, and I would have to go look up the specifics again. It drops a friendly error of the site is having technical difficulties, and puts the full PHP error in my server log. It triggers when you try to look up the location when you were writing a post or in your profile.
# [arush] I will do that. I need to figure out how to log into this chat through Slack on my laptop here. Because I do not want to have to try and type that entire long error on my phone.
# [arush] I went there, but when I launch slack, and type in my email address invite me to join again instead of logging in.
[tantek] joined the channel
