Support for Emoji · Issue #2 · eholin/WP-Advanced-Recent-Posts https:/
In some of the displays (Thumbnail and Dropcap primarily), if/when there is no image, the first letter of the title appears in the display block. (This is nice/simple UI display by the way.)
It would be interesting if when an emoji were the first "word" in a title if the emoji displayed instead of just an "&" which is the first character in most (all?) emoji strings. Bonus points if it could display the emoji in the block, and then remove it from the displayed title.
Example of current display when an emoji is the first "word" in a title:
I know this was fixed in a prior version, but it looks like it's slipped back in again in v3.0.2?
Perhaps it was fixed in one of the dev versions I downloaded from Github, but it's not in the production version on WordPress.org at the moment.
Only secure locations allowed (Chrome) · Issue #17 · dshanske/simple-location https:/
Using Simple Location Version 3.0.2 (most recent stable from WordPress.org) 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 https:/
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.
I know there was a brid.gy issue which recently answered the Twitter problem: https:/
Perhaps there's something similar for Facebook?
I've been following the conversation on https:/
I'll spend some time in the next two days to see if i can stumble across the "fix" snarfed did and close this out. Thanks for the reminder @pfefferle.
@aaronpk @indiescripter Another option to encourage others to post their replies on their own sites rather than directly on yours, you could provide a URL box and details for people to webmention you indirectly (especially if they don't support Webmention yet). See the comment section at the bottom of http:/
For additional ideas, see: http:/
Redirecting despite settings · Issue #878 · PressForward/pressforward https:/
Seconds to redirect user to source: 0 means no redirect. PressForward makes use of canonical URLs. If you would like to redirect your readers automatically to the items aggregated by the feed reader and published to your site, this setting will determine how long to wait before redirecting. The default setting is 0 seconds. The redirect setting can be manually overridden in the Edit Post page by editing the forwarding status in the publish box.
I've got the "seconds to redirect" set to 1 and regardless of whether I have the per post override set to either "Forward" or "Don't forward" all posts want to forward to the canonical URL. This is disconcerting particularly for the posts that I don't want to forward, and when this happens I'm seeing the page not only forward to itself (and therefore refresh), but it does it every few seconds continually which makes the page terrifically hard to try to read. Is it possible that it's not checking for the "forward/don't forward" toggle somehow?
@Chronotope Okay, so I've spent the majority of my time since your tweet playing with (read: drooling over) @pressfwd.
It is awesome and almost exactly what I've been looking for for ages without knowing it. I think that I'm not only an immediate convert, but an evangelist.
In fact, not just hours earlier in the day, I'd made this comment on the WordPress Reader Refresh (at https:/
"Some nice visual changes in this iteration. Makes it one of the most visually pretty feed readers out there now while still maintaining a relatively light weight.
I still wish there were more functionality pieces built into it like the indie-reader Woodwind.xyz or even Feedly. While WordPress in some sense is more creator oriented than consumption oriented, I still think that not having a more closely integrated reader built into it is still a drawback to the overall WordPress platform."
From the sound of your tweets and how I see it laid out, in some sense I suspect you're personally almost also using it as a built in bookmark or to-read app like Pocket or InstaPaper? This is almost exactly the type of "off label" use case I'd like to bend it to--though it doesn't really require that much bending given its current architecture. Are you displaying all the items you've read/commented on publicly (and where is it?) or are you just using the comment functionality and the nominated portions as a private "I've read this list" on your back end?
I've been thinking about the topic for a while since just before InstaPaper's acquisition by Pinterest and recently written a few things including about Owning My Online Reading Status Updates: http:/
I've even thought about using the Wallabag self-hosted version of something similar to this, but I'd prefer something more closely integrated with WordPress and PressForward has almost everything one could dream for.
If you have a few minutes next week to chat via phone about some of these uses, I have a feeling you could expand your user base a bit as a result. I also know of a few folks working on similar WP-based readers who might be encouraged to merge their work into your much more polished project.
My thanks to the whole team for not only a beautiful plugin, but for some well written and spectacularly documented code on Github!
Settings UI/UX feature requests: Ability to globally auto-set post publicly/post to self · Issue #4229 · hypothesis/h https:/
Perhaps it exists already and I'm not seeing it, but most of what I highlight and annotate, I typically prefer if it were automatically published freely and in the open. Currently it appears that highlights default to "only me" after they're highlighted. Annotations appear to default to public initially as they're being written, but when re-entering the text without manually hitting publish, they then are posted automatically to "only me".
This may be a reasonable default, but it means spending more time with the interface while I'm reading/working and thereby taking me out of the flow of my work.
Unfortunately, there is no default setting for forcing my highlights and annotations to be public, which means when I'm done reading that I have to go into the UI and manually do three button presses to make this happen for EVERY post. Click to edit, click the setting arrow, and finally click to publish. UGH!
In addition to allowing a master setting toggle for public/private at the main account level which would alleviate a large portion of my issue, I'd also recommend that rather than a drop down menu with two options that there just be a simple toggle to switch between public/private on each post so the user can accomplish in one click (or fingerpress on touchscreens) what currently takes two. Admittedly it's also controlling a "publish" function simultaneously, but I think that each post could have a public/private toggle and a separate "publish" button without cluttering up the UI too much.
The IndieWeb plugin does have quite a few related plugins which all interact well, but you don't necessarily need them all. You can obviously pick and choose based on the specific functionality you'd like to have. Their modularity helps to make understanding what sets of functionality each piece provides a lot easier.
In particular the two that will recreate most of the requested functionality of wp-social above are [Webmention ](https:/
The other sub-plugins within the larger IndieWeb suite add supplementary functionality if you want/need it. This also helps to cut down on code bloat which can slow your site down. In fact, if you only want a few in the suite, you can install them separately from the larger plugin. The others also help to not only extend functionality, but to better automate portions of it.
They are all also are being actively developed/supported on GitHub.
Feature request: Archive internal page/post links to Internet Archive on publish/update · Issue #23 · ManageWP/broken-link-checker https:/
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 Archive.org'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.
**Implementation**
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](https:/
I'm sure that Archive.org/The 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: https:/
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.
Importer "chokes" on Turkey emoji · Issue #27 · jtsternberg/DsgnWrks-Instagram-Importer https:/
I had recently posted the following to instagram: https:/
When the importer came to suck in the data and import it into my WordPress install it resulted in the following error:
![error](https:/
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: http:/
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.
UI: Duration doesn't make sense in Read post kind · Issue #65 · dshanske/indieweb-post-kinds https:/
When making a "Read" post in which data exists in the "time" tab for published dt and updated dt, the output displays more like one would anticipate with a music post type (or jam, listen, play, watch, travel) using start/end vocabulary instead and outputting a "Duration".
Duration may make sense if one were doing a start/end time for their reading, but then the scraper shouldn't be automatically pulling in the publish/update dates/times. Personally I'd prefer to let the publication time of my post indicate when the thing was read and have Post Kinds indicate the publication of the original piece I was reading.
Possibly better would be an if/then statement to differentiate types and for Read types outputting a date/time for the original publication and/or potentially an updated date/time if it exists.
At present, the issue is most common on New York Times posts for which the scraper pulls in the correct metadata.
Example: http:/
I'm circling back on this issue (https:/
In any case, here's what I'm seeing presently (with the latest Version 4.7.2, WP 4.6.1):
Books with the same title, but different authors and different other meta data can be input, but when actually inserting the citation, the superscript number for the first book input with that matching book title is appearing.
The desired book reference does (now) appear in the list of references (it wasn't before), but appears under the subsection "Uncited items". This seems like the best/most intuitive way to display it from a UI perspective.
Example:
http:/
Several of these books have the same title, namely "Complex Analysis".
Most show up improperly when cited as 3 (the first one I input), while incomprehensibly to me, 6 and 8 show up properly instead of as 3 as the others do that have the same title. 8 and 9 on the last book at the bottom both appear properly though 9 has a longer title which differentiates it from the other.