I've discovered @hypothes_is can be a useful tool for annotating a conference schedule to determine what I'm going to attend. #edtech
Reading through the schedule for WordCamp Orange County on 6/10-11 @ocwordcamp #WCOC
https:/
@rhiaro Is anyone adding notes on this to the etherpad?! I'd love to see/hear examples
https:/
@colinwalker I haven't added some of the direct UI pieces I want to just yet, but PressForward does go a huge distance towards integration. I've written a bit about it in the past: http:/
Mostly something to keep in mind, potentially for a year or so out if it ever gains traction. It's a possibility given these particular developers...
@AramZS Here are links to two (I've fixed the bulk of the rest), though that I can tell, these were native posts (prior to installing PressForward and which continually autoredirect to themselves, and thus never render, though one can view source for them) and not ones which were imported:
http:/
http:/
Other than having native WP GUID's these two are otherwise completely similar in database/metadata to the other posts which had been imported from other systems.
Don't kill yourself trying to troubleshoot these as I've already fixed the hundreds of others, but do drop me a note if you don't find anything so I can manually tweak them so that they no longer auto-forward and actually resolve to something.
@AramZS I've double-checked and had cleared caches previously (which if not done wouldn't have forwarded as I'd had the forward value set to 0 before.)
I've cleared everything out and reinstalled the new .org version from the repository and am finding the same issue seems to persist. (Even testing in a new browser install.)
One thing I am noticing is that a lot of my older posts were actually imported into my self-hosted install from either other non-WordPress sources or an older WordPress.com account. When editing these which don't have any values set for `pf_forward_to_origin`, I notice that the UI default for PF is for them to `Forward` rather than the typical default of `Don't Forward` which I get for new posts.
I'm also noticing that these older posts have the original site's GUID set in wp_posts which means that they're being forwarded to those URLs (some of which don't exist anymore). I'll try to circle around and make a caveat note in the documentation of this for others who may experience it (and not know why).
Perhaps there's some other glitch in my database causing this? Since @regan008 has tested it and confirmed on your side (and the code looks correct to me), I'll throw in the towel. Since I've got to make some of these additional GUID changes (along with some others) in my database anyway, I'll just go in and add values for all these older posts so they're "forced" to work anyway.
Thanks, as always, for such continued work on a fantastic tool!
Did this get rolled up into the 4.3.0 pre release?
https:/
If it did, it doesn't seem to have fixed the root issue after I just installed and tested it. I'm still finding that older posts (pre-PressForward) which have no value set for `pf_forward_to_origin` are attempting to forward (back to themselves) when setting a time >0 in the forward settings. Those which have a value of `forward` do forward properly and those with a value of `no-forward` don't. The problem is for posts which existed prior to installing PressForward which have no value set at all.