@zack06007 It looks to me like this plugin isn't being actively maintained and I don't even see it in the main WordPress.org repository anymore. It's also possible that with the recent WP 4.7 update some of the functionalities have broken further. The last commit to the code was almost a year and a half ago with the bulk of the code being even older.
If you'd like to maintain a lot of this functionality in a better way with some smaller discrete plugins I would recommend the following:
- [**JetPack** ](https:/
- [**IndiwWeb Plugin for WordPress**](https:/
- [**Brid.gy**](http:/
If you need more help in setting these up or using them, feel free to visit http:/
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.
The minute I finish building a @WordPress site for a friend, the first thing I hear is a SquareSpace ad
https:/
Cross posted to WordPress for underlying support: https:/
Topic: WordPress “chokes” on Turkey emoji for Thanksgiving « WordPress.org Forums https:/
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: http:/
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: https:/
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 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.
@cvoxel You can totally do it with your WordPress blog already http:/
Because Independent Publisher works really well with [IndieWeb technologies](https:/
Using this, one could allow for [Fragmentions](https:/
For @WordPress users there's a simple @DuckDuckGo search plugin that works well. https:/
@Chronotope Those on @WordPress or VIP version may as a default and that'll give you a good start. https:/
@ergodicwalk Pssst. While the identicon on your blog is very fitting to your topic... http:/
Edge case post "duplication" · Issue #10 · meitar/wp-crosspost https:/
I once had a blog at wordpress.com that I exported and moved to a self-hosted wordpress.org install where I now use the WP-Crosspost plugin to cross-post back to the original .com version.
When going back to edit/modify old posts on the new self-hosted site, this plugin creates duplicate copies of the original posts, typically with a "-2" (or other incremental integer) appended to the original URL.
For those in a similar situation knowing about the issue (I can see some archivists seeing this as a major feature) is half the battle and some users may appreciate a caveat in the manual.
If it's a bug you feel that's really worth fixing or working around (it doesn't affect/bother me now that I'm aware of it), I'll note that in the self-hosted .org installation, the imported posts from the original .com site all appear to have a "guid" field in the wp-posts database which indicates the URL where the original version resided. Perhaps you could run a check against this value (and the base URL) before creating a new post with a new URL to catch the edge cases when they occur?
@Chronotope I knew when I saw your name earlier this week that I'd seen it before: http:/
@evrenk WordPress.org is DEFINITELY #IndieWeb compatible!! If you want to get started take a look at https:/
While the siren song of Medium seems strong, you don't necessarily own it all and can't control it to the extent you can on your own site. I'd recommend checking out IndieWeb-ifying your WordPress install and leverage the value of your existing social networks like Medium, Twitter, Facebook, et al by syndicating your content from WordPress to those other sites. Medium has a good WordPress plugin [https:/
I've supercharged my WordPress install with IndieWeb tools and now use it as my primary hub on the internet for writing and responding. I don't spend as much time on Facebook and Twitter as all the comments I want to see on my own material come back directly to me.
If it helps, follow the advice of Dave Winer: Anywhere but Medium [http:/
If you need help, don't hesitate to find any of the helpful folks at IndieWeb: https:/
@pfunder A "Read More" link on awesome #microliterature like http:/