Skip to main content
 

Testing the ability to POSSE posts to pnut.io via @WithKnown courtesy of @dgold.
https://github.com/dg01d/KnownPnut

 

@raretrack Be sure to file the bug at https://github.com/idno/Known/issues. If you're hosting it yourself, it may be easier just to back up the entire database rather than manually exporting.

Glad to hear you're getting plugins to work. Which version are you using at present 0.9.2?

 

@kartik_prabhu Webmentions to things other than posts-pages, archives, etc. In this particular case, to my homepage https://github.com/pfefferle/wordpress-webmention#how-can-i-handle-webmentions-to-my-homepage-or-archive-pages

 

Replied to a post on github.com :

Yes, that tweak (https://github.com/kshaffer/hypothesis_aggregator/pull/7) does appear to work. It fixes both the fatal error and the fact that the curator name and appropriate URL wasn't working.

Great "marketing" work @xolotl! ;)

 

Replied to a post on github.com :

Feature cover image quality too poor · Issue #260 · raamdev/independent-publisher https://github.com/raamdev/independent-publisher/issues/260

I think that this had been answered before. Perhaps the solution at https://github.com/raamdev/independent-publisher/issues/162 will fix your problem?

 

UX/UI Suggestion: Meta box in the admin UI with PressForward metadata and comments · Issue #902 · PressForward/pressforward https://github.com/PressForward/pressforward/issues/902

I'd suggest that it would be worthwhile and convenient to have a meta box in the admin UI for editing the final draft that contained all of the pre-existing PressForward metadata.

Bits and pieces of it appear in other portions of the PressForward UI throughout the vetting (reading, nominating) process (typically hidden under the "info" button which pops up the details), but having portions of it while actually editing the draft of the post would be very handy/useful. In particular, it would be nice to have access to the comments which are added to the particular piece in the earlier parts of the process.

![meta box information](https://cloud.githubusercontent.com/assets/5882943/23576560/ac78ea2c-005d-11e7-86f0-5ff5fe8a3252.PNG)

Comments in particular, would presumably have ideas, thoughts, and editorial leanings that could help the writer/editors shape the final piece or notes on/around it, but as it stands, one needs to dig back into the PressForward interface, typically with search, to re-uncover the particular data and notes relevant to the original piece.

Ideally making it relatively small so that it could fit into the sidebar may be the most beneficial. If you want to go all-in on such a feature, I've seen a fantastic meta box in the [Academic Blogger's Toolkit plugin](https://github.com/dsifford/academic-bloggers-toolkit) labeled "Reference List" which is pinnable and maintains its position at the top of the UI while the rest of the page scrolls.

 

@keithjgrant You'll likely need knownreactions to test "like" posts: https://github.com/kylewm/KnownReactions

 

Example instance · Issue #1 · terminalpixel/postrchildbot https://github.com/terminalpixel/postrchildbot/issues/1

You should add a readme page with a link to the working instance http://postrchildbot.tpxl.io/

Congrats on this btw!

 

Bookmarklet chopping out NYTimes text · Issue #900 · PressForward/pressforward https://github.com/PressForward/pressforward/issues/900

When nominating/drafting from NYTimes stories, typically the first several graphs are excised or not copied over into the post.

Based on some quick experiments it appears that the portion of stories that appears before </div><!-- close story-body --> (typically followed by some advertising before the story resumes) are the ones being left out for some reason. From the bookmarklet's point of view NYT articles seem to begin with the portion <p id="story-continues-2" class="story-body-text story-content" rather than the true start of the article.

Given that the Mercury browser plugin doesn't exhibit this behavior, I suspect it's something to do with the bookmarklet's JS?

This is occurring in 4.2.2 and earlier versions of the bookmarklet. I'm seeing it in Chrome as well as Firefox, so it doesn't seem to be browser dependent.

If pre-highlighting text in the browser, one does get the typical blockquoted portion of a Press This bookmarklet output.

 

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.

 

OPML link not working · Issue #898 · PressForward/pressforward https://github.com/PressForward/pressforward/issues/898

## What I tried/expected:
From the page `/wp-admin/admin.php?page=pf-tools` under the `OPML Link` tab, the instructions indicate:
You can share your subscription list as an OPML file by linking people to http://example.com/?pf=opml.

## What happened:
Visiting the indicated link throws the following error:
`Warning: Creating default object from empty value in /htdocs/example/wp-content/plugins/pressforward-4.2.2/includes/opml/object.php on line 48
1`

## Additional information:
I've got a handful of feeds, so I should expect something to appear. Is there a setting I'm missing somewhere? I know that there's a setting for the /feedforward RSS functionality/plugin, is there a similar one for OPML that I'm missing?

Running GitHub version 4.2.2, WordPress 4.7.2

 

@MailChimp @MailChimpStatus @MailChimp_API @MailChimpUX Can you help WordPress community out here with a response? https://github.com/crowdfavorite/wp-social/issues/213#issuecomment-282094259

 

Text Before Links text should have stylable class · Issue #47 · dshanske/syndication-links https://github.com/dshanske/syndication-links/issues/47

In tweaking/changing the CSS for the multiple sizes (around v3.1.1), you removed the class from the "Text Before Links" portion, so it's not easily accessible for theming.

It might also be worth putting the entire output into a div with a class as well for better CSS control.

cross reference: https://github.com/dshanske/syndication-links/issues/29

 

Duplication of links upon update · Issue #45 · dshanske/syndication-links https://github.com/dshanske/syndication-links/issues/45

With v3.1.1 and relying on SNAP for POSSE, I'm noticing that after publishing and syndicating, if one comes back and edits a post and then updates it, Syndication Links regrabs the URL's and duplicates the links.

The first unedited version that is shown seems to be a plain http link and after editing/updating, the second duplicated link that is added automatically is an https version.

Manually deleting either of the included links from the Syndication Links box doesn't get rid of the links.

This duplication of the links only happens on posts which have been later edited/updated.

example: http://boffosocko.com/2017/02/16/podcast-directories-why-cant-we/
Here the Twitter and Facebook links, which are generated from SNAP, are duplicated, first as http and then again as https. As a test, the two other syndication links are non-SNAP generated links: huffduffer was manually inserted, and the WordPress one was generated from the WordPress Cross Post plugin, so I'm guessing it's an issue caused by the storage of SNAP links (which are https) versus Syndications Links' storage.

 

Colin and David, I've been a long time Feedly user myself and certainly feel your pain. (And in particular, I'm a bit irked that I can't seem to get Feedly to discover alternate RSS Feeds being broadcast from my site to provide consumers with more options about what content they'd like to consume from my site, see also: http://boffosocko.com/2016/12/18/rss-feeds-a-follow-up-on-my-indieweb-commitment-2017/ )

While slowly hacking away at IndieWeb philosophies, one of the big issues I've always hated was using an outside feed reader that wasn't directly integrated into my own site. I've played around a lot with woodwind.xyz which has some great IndieWeb features, but doesn't have the massive developer team behind it that Feedly does.

Recently while doing some alternate research I also came across the WordPress plugin PressForward that was originally designed for journalists and academics, but in short is actually a built-in RSS feed reader that you can self-host as part of your WordPress install. I've been loving its general functionality and also use it somewhat like a self-hosted version of Pocket/InstaPaper as well, so it serves multiple uses. While it may not have everything that Feedly does, it's incredibly functional, and better, it's open on Github with lots of documentation, so you could potentially add the features you want. I've written a bit more about it (including some useful links) here if you'd like to explore it a bit more: http://boffosocko.com/2016/12/31/pressforward-as-an-indieweb-wordpress-based-rss-feed-reader-pocketinstapaper-replacement/

Like both of you, I'm always eager to hear of other options should you come across them.