Skip to main content

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







(Consider Adding Web Annotations to WordPress) – WordPress Trac

Mostly to provide some additional resources to the conversation I'll add the following:

Web Annotation Working Group's [ three recommendations and two additional notes]

Prior to the WPTavern post which motivated the conversation, there was a [ post written by Dan Whaley of] who worked extensively within the group. This post has some interesting overview, but those interested in a fully implemented annotation platform (presumably using many of the pieces of the proposed standard) should take a quick look at [], what it is and what it allows. Their front page has a pretty useful video introduction.

Keep in mind that some of the standard is geared specifically toward browsers and browser vendors, though WordPress could certainly implement some of the pieces from the CMS side.


Old posts with no value set for `pf_forward_to_origin` are automatically forwarded · Issue #899 · PressForward/pressforward

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, 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

## 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

## 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

## 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


Duplication of links upon update · Issue #45 · dshanske/syndication-links

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.

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.


Retrieve Running Time for listen and watch post kinds? · Issue #71 · dshanske/indieweb-post-kinds

For sites like Soundcloud, ITunes, Netflix, youtube (if it's available) it would be nice to retrieve the "running time" of the music, show, film, etc. to display as a running time in the UI for listen, watch, and jam types (rather than the published/updated) for other post types.

Sample URLs
WordPress blueberry podcasts:

When not scrape-able, allowing one to simply enter a 0:00:00 time and a finish time and letting it display the appropriate running time (without entering a date) would be useful for these types as well. (I'm presuming it requires dates to calculate currently as I haven't yet checked....)


Suggestion: Store GPS coordinates in the recommended WordPress format/standard · Issue #29 · jtsternberg/DsgnWrks-Instagram-Importer

It would be nice if the plugin stored the GPS coordinates with the standard/suggested WordPress standard:

This would allow the usage of secondary plugins (like [Simple Location]( to access the stored data and do something with it.


New update causes tab issues with All in One SEO Pack · Issue #70 · TweetPressFr/jm-twitter-cards

With the recent update to stable on 5 hours ago (v7.7) a change somewhere in the code is causing problems in the admin interface with the All in One SEO Pack.

In particular one can't switch between the two tabs in AIOSP interface "Main Settings" and "Social Settings". Only the details on the "Main Settings" tab can be seen and attempting to switch to "Social Settings" only changes the url (which then ends with <code>&action=edit#aioseop_opengraph_settings</code>. Attempting to switch back does nothing but change the URL to <code>&action=edit#aiosp</code>.

Disabling JM Twitter Cards and refreshing the post admin interface allows AIOSP to work properly and reenabling JMTC causes it to break again.


Crossposted to


Update of JM Twitter Cards causes tab issues with All in One SEO Pack · Issue #736 · semperfiwebdesign/all-in-one-seo-pack

With the recent update to JM Twitter Cards to stable on 5 hours ago (v7.7) a change somewhere in the code is causing problems in the admin interface with the All in One SEO Pack.

In particular one can't switch between the two tabs in AIOSP interface "Main Settings" and "Social Settings". Only the details on the "Main Settings" tab can be seen and attempting to switch to "Social Settings" only changes the url (which then ends with <code>&action=edit#aioseop_opengraph_settings</code>. Attempting to switch back does nothing but change the URL to <code>&action=edit#aiosp</code>.

Disabling JM Twitter Cards and refreshing the post admin interface allows AIOSP to work properly and reenabling JMTC causes it to break again.


Also cross-posting to JMTC which may be the source of the problem.


Improved support for SNAP · Issue #39 · dshanske/syndication-links

Many of the channels in SNAP are already supported, but most are currently missing. Support would include not only adding the SVG icons for them, but adding auto-import for displaying them in the list based on the storage location within SNAP.

SNAP currently supports the following:
500px - perhaps leave this off as [ is currently shutting down](
+Google+ (did the icon get fixed for It doesn't currently display in the stable version)

Those marked with a * currently have support for icon display
Those marked with a + currently have support for import of the link


Topic: Turn off sharing buttons on mobile devices « Forums

Since mobile devices have better built in sharing support, it would be nice if they didn’t display there, particularly as they tend to cover up the actual content on small screens and make it unreadable/unviewable.

See here for some motivation and sample code for how JetPack does this with their sharing icons:


Only secure locations allowed (Chrome) · Issue #17 · dshanske/simple-location

Using Simple Location Version 3.0.2 (most recent stable from in Chrome (both desktop and in Chrome mobile browser on Android):

When I click on "Get Location" button, I get a modal window that says:

Only secure locations allowed (see
This is on a "live" site and not a dev environment. I'm guessing it may be because I'm using http and not https while requesting my location?? I'm anything but a js expert, so this is just a guess...

In Firefox, it correctly asks "Would you like to share your location with this site?" and proceeds properly.


Feature request: Archive internal page/post links to Internet Archive on publish/update · Issue #23 · ManageWP/broken-link-checker

I might suggest the following functionality could fit in well with the plugin's general purpose, particularly since the Internet Archive recommends the plugin. It could also help to "close the loop" in the plugin's overall functionality for helping to maintain data integrity and working links for WordPress sites on the web.

**Suggested Functionality**
When one initially publishes (or possibly updates) a post/page, it would be awesome if all of the URLs referenced on the page as well as that of the page itself were pinged for archiving to the Internet Archive's Wayback Machine at the day and time of their being referenced in the post. (Or perhaps within a day or two of the post so as not to overwhelm's servers with multiple subsequent updates for typos/tweaks which invariably happen post-publication.)

With this functionality, then in the future, if (when) resources change, move, etc. one could use the primary functionality in Broken Link Checker not only to restore a link to a close or reasonable copy of the original, but restore it to the _same_ day it was originally referenced.

As I'm sure you're all too aware, this can be very handy as the average web page has a lifespan of 100 days or less. I can see this being very useful to not only the general public, but particularly for bloggers, linkbloggers, journalists, and academics.

To my knowledge, there are no plugins within the WordPress repository that manage this type of functionality as a standalone plugin, though there is the heavily underused [Post Archival in the Internet Archive]( plugin which essentially adds one's individual post/page permalink URL to the Internet Archive as it's published, though it doesn't include the archival of any links (references) within that same post.

I'm sure that Wayback Machine may provide some additional documentation for implementation, though I suspect the code in the above-referenced pluign is a very good examplar. I also recently came across this snippet: after a recent conference on Saving/Archiving News Sites which may be beneficial as well. It certainly exhibits at least an interest/demand for such a functionality.

I haven't dug into WordPress core, but I'm guessing some of the functionality for parsing URLs within pages/posts for sending Trackbacks/Pingbacks would have a filter or hook for providing all of the URLs in a post/page necessary for such processing and archiving while the_permalink() or get_permalink() gives the last.

Given the popularity of this spectacular plugin, it could also potentially become one of the largest forces for archiving vast swaths of the internet to the Internet Archive, short of WordPress adding such functionality directly into core.


The minute I finish building a @WordPress site for a friend, the first thing I hear is a SquareSpace ad


Topic: WordPress “chokes” on Turkey emoji for Thanksgiving « Forums

When I do this:
Try to post a standard post with any title (or other standard post fields) that includes a Turkey Emoji 🦃
(see also:

This happens:
The post occurs as expected, but WordPress "sanitizes" the turkey emoji out of the post! I suspect that this particular emoji is either so new it's isn't recognized by the system like others, or its UTF-8 equivalent code may be improperly recognized as rogue code somehow when the inputs are sanitized.

For thoroughness, I thought I'd post this issue here as well as the original in relation to the Instagram plugin and related post which caused me to recognize the problem:

Has anyone else seen this with relation to the recent Thanksgiving holiday in the U.S.?


Importer "chokes" on Turkey emoji · Issue #27 · jtsternberg/DsgnWrks-Instagram-Importer

I had recently posted the following to instagram:

When the importer came to suck in the data and import it into my WordPress install it resulted in the following error:


I tried uninstalling, reinstalling, and re-authenticating to see if that was the problem with no luck. I was about to give up the whole affair in utter despair (because DsgnWrks Instagram Importer is my absolutely favorite plugin in of all time and because I didn't want to use Instagram anymore if I couldn't "own" my own photos.)

In desperation, I manually "imported" the post/photo and between that and surprisingly seeing a newer post being imported properly this morning, I'm able to take a reasonable guess as to what the problem is! I also tested on another instagram account and found the same results which "confirms" the issue.

Apparently Instagram posts with the Turkey Emoji 🦃 (I'm using an Android phone ) don't work well with either the Importer or even WordPress itself. I suspect that WordPress is viewing the translated code for the Turkey emoji (see also: as malicious code and not allowing it to be imported into the database. When trying to use the turkey emoji in a Title field (and several others) to post the photo manually, WordPress will post properly, but it scrubs the emoji code out of the post completely.

Does anyone have any experience in properly sanitizing emoji code to prevent this type of error in the future? Has anyone noticed other emoji that cause problems? I somewhat often use them and haven't seen any issues with other emoji like this.

The quickest fix is potentially to scrub out any Turkey emoji codes in future posts prior to attempting import--particularly as WordPress doesn't seem to be able to handle it properly either.