Skip to main content

Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, IndieWeb, mnemonics, and the entertainment industry including: finance, distribution, representation

boffosocko.com

chrisaldrich

chrisaldrich

+13107510548

chris@boffosocko.com

stream.boffosocko.com

www.boffosockobooks.com

chrisaldrich

mastodon.social/@chrisaldrich

micro.blog/chrisaldrich

 

That's a great Christmas present. Congratulations! https://twitter.com/evrenk/status/959148056766754816?s=09

 

Old posts with no value set for `pf_forward_to_origin` are automatically forwarded · Issue #899 · PressForward/pressforward https://github.com/PressForward/pressforward/issues/899

This has probably been present for a while, but I just noticed after turning on forwarding posts to the canonical URL by setting a time >0 in the forward settings: all the old posts in my database (prior to having PressForward) auto forward as a default back to their own URLs. This means that every X seconds (as set in the setting) pages on my site automatically reload (or are redirected to themselves) and this makes the site relatively useless to attempt to read. (This seems to be a follow on error not noticed in https://github.com/PressForward/pressforward/issues/878, but which persists after the upgrade to 4.2.2 which resolved the problem for posts set to `no-forward`.)

Users adding PressForward on preexisting sites are going to have a tremendous shock if this is the default.

A better option is that all old posts (prior to installation) should default to no-forward (or at least not forward if there is no value set for `pf_forward_to_origin` in the database. PressForward should, in my mind, ideally default to no-forward in all new future posts with the possible exception of posts generated specifically by PressForward's nomination/draft workflow to default to `forward`/`no-forward` based on a possible new setting option in addition to the time setting.

It would be nice if the portion for null/non-existent values of `pf_forward_to_origin` was fixed before 4.2.2 rolled out into the WordPress repository if it hasn't been pushed already.

Running 4.2.2 on WP 4.7.2

Congratulations again to everyone, as always, on what I think is surely one of the most valuable plug-ins in the entire WordPress repository.

 

Congratulations to @LtlFreeLibrary, @ToddBol & Stewards everywhere on 50,000 LFLs!! http://lfl8424.boffosocko.com/2016/11/04/congratulations-on-little-free-library-number-50000

 

That was just a terribly depressing @JohnsHopkins Lacrosse game... Congratulations Brown.

 

Congratulations and good luck. Hopefully you won't be as addicted to the as some of us have become!

 

Congratulations to fellow @JHU_Alumni Matthew Robbins on the release of Crimson Peak today http://www.imdb.com/title/tt2554274/ @JohnsHopkins

 

Congratulations to @MarlonJames5 for winning @ManBookerPrize for A Brief History of Seven Killings http://amzn.to/1NbCN63

 

David, Congrats on officially putting your plugins up on Wordpress!

My WP skills are certainly below that of yours, but I applaud you for making the effort on behalf of the IndieWeb. I'm happy to help test/bang on your plugins and give feedback, (and If I can to delve through the code to help there too occasionally).

One thing I notice about post kinds in the 1.3.0 version is that the number of post kinds is much smaller compared to the circa 1.2.X releases. Did you deprecate them? temporarily? while you work out issues on each?

On syndication links I notice that the resultant icons (on your site as well as mine) shift over a few pixels when hovering over them - is this by design or a quirk in my (our) CSS perhaps?

Congratulations again and keep up the good work!