Perhaps I’m missing a setting somewhere, but since I’ve gotten OwnYourSwarm working (using JSON as opposed to the “Simple” setting, the post data arrives as expected, however, Post Kinds is defaulting the post to be a
note instead of a
checkin as I would expect. (In general, I would think that all posts arriving from OYS would always default to be checkins despite the fact that they may have note-like content as well as photos.)
In the settings on my site, I’ve even got the “Default Kind for New Posts” set to
checkin, as I use it often, yet the posts still show up as a note.
Ideas about what may be missing or going wrong?
As a small caveat, I’ll note that this install is running Post Kinds Version 3.0.6, but I suspect that nothing has changed since about June that might fix or affect this issue.
In version 3.8.1 it currently appears that comments from WordPress and Micro.blog (both of which have Gravatar as a commonality) appear to be automatically using the default mystery person avatar even though there is a separate avatar defined within the Avatar fields for Semantic Linkbacks Data.
If I add my my email address within the comment editing interface, then the appropriate Gravatar is pulled and displayed as expected. This leads me to believe that somehow SL either isn’t finding/pulling the Gravatar URL that it’s storing, or the code is potentially skipping looking for it within its logic structure.
I’ve noticed this also seems to be the case for other WP sites which I have reason to suspect are running this same version as well.
Webmentions from other non-Gravatar related sites don’t seem to be affected by this and they’re displaying the proper avatar images as defined within their h-cards.
They’d previously been working, but for some reason, with the setting set to facepile all the RSVP types in settings, none of the RSVPs are facepiling like they’re supposed to now.
Steps to reproduce
- Annotate any particular individual article on https://www.quantamagazine.org/
- Links to the annotations are redirected back to the root domain and not the individual page
The links should direct to the canonical URL of the article
All the annotations to individual pages seem to automatically become orphans and are associated with the root domain instead of the individual permalinks.
Example: The annotations at https://hyp.is/lUpgtn15EeivjHMsJK03Tg/www.quantamagazine.org/ and https://hyp.is/6C98en11EeieFgMy1hP9tQ/www.quantamagazine.org/ on the page https://www.quantamagazine.org/mathematics-shows-how-to-ensure-evolution-20180626/ don’t resolve properly because of the orphaning issue on this website.
This is happening to me on a variety of browsers on Windows 8.1 and Windows 10 including: Chrome 67 and Firefox Quantum 60.0.2 (64-bit).
It also appears to be an issue on both the current versions of Chrome/Firefox on Android v8.0.0
I’d guess that the issue is site specific to quantummagazine.org somehow.
After updating to the most recent version 3.8.0 of Semantic Linkbacks I’m getting the following error in the Comments sections of both posts and pages:
Warning: in_array() expects parameter 2 to be array, string given in htdocs/blog/wp-content/plugins/semantic-linkbacks/includes/class-linkbacks-walker-comment.php on line 25
It seems to be throwing the error the same number of times that there are comments on the post. Additionally the comments section is showing both the raw mentions and facepiled versions. I’ll have to test some additional posts, but it also seems to have changed some mentions that were previously moderated out to now be showing.
Perhaps better than allowing simply the download of an OPML file, it would be nice to have the ability to provide a link to an OPML file as well? This way feed readers like Inoreader that support OPML subscription would be able to auto update themselves when new feeds/friends are added to the list?
Depending on your infrastructure, you could potentially leverage the old Link Manager within WordPress which provided OPML outputs as well as outputs arranged by category. This would prevent you from needing to rebuild the side-files unless you’re doing that already.
Apparently the v3.7.7 update seems to break the display of avatar images in facepiles for likes, bookmarks, etc. Instead of showing the expected avatar image, it’s showing the author’s name wrapped with an href for the originating site.
It’s not just my site either as I notice that the facepiles at https://ramblinggit.com/2018/05/241/ (using Sempress) are also displaying the same way.
I’d simultaneously updated the Webmention plugin and tried uninstalling and reinstalling both plugins as well as checking a variety of settings (including the discussion setting for showing Avatars) and uninstalling a variety of potential conflicting plugins, but to no avail.
I know there were recent changes for privacy related pieces, perhaps this is the cause?
It looks like the new “read” functionality for mentions automatically facepiles them anyway, but I’ve noticed that the settings at
/wp-admin/options-discussion.php#semantic_linkbacks doesn’t include a checkbox for reads.
This really isn’t an issue (at least for me), but you may want to be aware of it or tweak it for parity’s sake.
I could have sworn I filed this as an issue before myself, but I’m not seeing it in the queue. Perhaps I mentioned in chat somewhere?
Simple location’s privacy setting seems to override the post’s public/private settings on my site as well. Perhaps it’s a naming conflict (function/filter/etc.) with WP’s core content visibility code?
In any case, I can’t make a post private while Simple Location is installed/activated either. This seems to happen regardless of other plugins. I do seem to be able to use @vishae’s method of using the quick edit option to change a post to private. I’m not sure if this may indicate a potential solution to the issue based on what is firing on a post save/update versus what fires on a quick edit save.
Additionally, I don’t seem to be able to mark a particular location as “private” in a post either as upon saving it it defaults back to public in the UI. I only seem to be able to use “public” or “protected” options for locations.
It would be nice if there were a way to distinguish between various watch types to differentiate between films, television, and internet based streaming media — perhaps with a data field and a toggle along with three appropriate icons for each of these rather than the single watch icon now (a generic “play” button).
Further, most of the current meta data fields are fairly solid for the most often used fields, but I often find that it would be nice to have fields for Season # and Episode # for television shows.
The last “big” piece that would be nice to have is a quickly usable ratings field of sorts so one could provide a rating 1-5, 1-10, or 1-100 rating field? Maybe it could be a simple numerical data field that calculates/displays a rough 5 star-based scale? h-review markup could also come into play here as well, though it would be nice to capture the raw data even if there is no UI display built for it.
A few random tips/pointers:
@GWG has put out a very customized version of his Twenty Sixteen Theme on Github. For those who have some development skills or are willing to look at examples to try changes themselves, the commit history of this particular theme is very enlightening and does a reasonable step-by-step job of providing snapshots of what he changed in Twenty Sixteen to make it more IndieWeb-friendly. For most themes, one may not want to go as far as he did to remove Post Formats in favor of Post Kinds for greater flexibility, but most of the rest is pretty useful and solid as an example if one is converting/forking other popular themes to make them more IndieWeb friendly.
There are a number of very IndieWeb-friendly themes and even child themes listed on the Themes page of the wiki. Most of these should “just work” though a few may have small bugs which could be filed to their respective repositories to improve them.
It’s generally recommended not to use the mf2 plugin with themes which are already very IndieWeb-friendly as it can cause issues or have unintended consequences. That plugin is generally better used when themes only have the minimal microformats v1 code which is added by WordPress core.
There are also lots of details and brainstorming for improving themes in general on the wiki page for WordPress/Development/#Themes.
For ease-of-use as well as to help designers, theme builders, and maybe even Gen2 it might be useful to have a “master template” for views which includes all of the output of the data fields within Post Kinds in a single view.
If done in a relatively modular fashion with good commenting, perhaps even Gen2 folks could more easily delete or move pieces within such a master template to mash up various pieces to get what they’d like to display. Including alternate versions for displaying things could be useful as well (eg: raw display of things like start time and end time as well as a separate calculated duration time based on these two.)
I noticed that Kartik has an an original-of page at https://kartikprabhu.com/original-of which may have inspired the original-of URL functionality for use in Syndication Links.
For improved UI, is there a code snippet that could be created (or which already exists?) that could be added to a custom page to allow the creation for a simple search for such things the way Kartik has done? I’m thinking of something along the lines of
<?php get_search_form(); ?> which can be added to 404 page templates to allow the addition of a search box on such a page to get the user moving in the right direction.
This type of
original-of search functionality could also be added to a simple widget as well so that one doesn’t need an entire page for it. Suggested verbiage: “Have a social media permalink for a piece of content? Use it here to search for the original version on this site.”
As mentioned in IW chat:
When placing the URL https://abraham.uno/909/listening-an-indieweb-podcast-episode-0/ into the Webmention Form at http://boffosocko.com/2018/03/19/an-indieweb-podcast-episode-0-considering-the-user/#Respond+on+your+own the following Fatal Error appears at http://boffosocko.com/wp-json/webmention/1.0/endpoint:
Fatal error: Uncaught Error: Cannot use object of type WP_Error as array in /htdocs/wp-content/plugins/webmention/templates/webmention-api-message.php:119 Stack trace: #0 /htdocs/wp-content/plugins/webmention/includes/class-webmention-receiver.php(161): require_once() #1 /htdocs/wp-includes/class-wp-hook.php(298): Webmention_Receiver::serve_request(false, Object(WP_REST_Response), Object(WP_REST_Request), Object(WP_REST_Server)) #2 htdocs/wp-includes/plugin.php(203): WP_Hook->apply_filters(false, Array) #3 /htdocs/wp-includes/rest-api/class-wp-rest-server.php(380): apply_filters('rest_pre_serve_...', false, Object(WP_REST_Response), Object(WP_REST_Request), Object(WP_REST_Server)) #4 /htdocs/wp-includes/rest-api.php(271): WP_REST_Server->serve_request('/webmention/1.0...') #5 /htdocs/wp- in /htdocs/wp-content/plugins/webmention/templates/webmention-api-message.php on line 119