@cswordpress @redcrew Thanks for the recommendation Amanda!
I'm guessing you installed PressForward directly on your production server without using a test environment? I can tell because all of your posts are trying to redirect, but are redirecting to themselves! It's a known bug I mentioned here: http:/
Until then you may want to go to the settings and set the redirect time to "0" which will prevent all of your pages from continually re-loading OR you could uninstall it from your production site and run on a test server.
I've been loving it since I installed and can't wait for the forthcoming patch. I'm curious what others think of it for the off-label use I've proposed.
a post by Chris AldrichChris Aldrich(Chris Aldrich)@cswordpress @redcrew Thanks for the recommendation Amanda!
I'm guessing you installed PressForward directly on your production server without using a test environment? I can tell As I was scrolling through Twitter this morning, I came across a recommendation in favor of Press Forward, a free software alternative to closed-source tools for journalists that can also act as a self-contained RSS reader and Instapaper/Pocket replacement for use on WordPress-powered sites. The above is to provide context for those who haven’t been following this conversation. Plus, I’m still figuring out this crafting replies on my own site thing.
Anyway, I received some very helpful feedback from the author of the original post regarding my current installation, which included a link to the project’s Github. This is great, both because I’m really looking forward to using this since I really don’t like messing around with Pocket/Instapaper due to their accessibility issues, plus owning your bookmarks. So far the only problem I’ve found, other than the issue mentioned in the feedback, is one where the bookmarklet cannot be accessed with a keyboard. You have to use a mouse. So I’ll be filing an issue, and hopefully a pull request, because along with the Indieweb implications and uses for this, it also presents a great alternative for controlling the display of the lists of links we collect, allowing for the creatin of accessible user interfaces.
Also, Twitter’s 140-character limit is extra frustrating when you realize that you can reply to tweets from your own website, not be stuck trying to fit things in 140-char chunks, and keep ownership of the content, which is why I replied here. I need to finish getting customerservant.com switched over to a theme with complete microformat/microformat 2 support, and am looking at how to do this with the Genesis framework if possible.
Share this: Facebook Twitter
Fuller reply with context for those not following here. unvarnished.me/?p=43507
, Jan 06 2017 on twitter.com
@cswordpress I hadn't run across the keyboard issue with the bookmarklet yet, but I'm glad you're taking a look at fixing it. If you get some time, feel free to add your fix and links to the code at http:/
Several of us in the WordPress IndieWeb "camp" have been pushing to have more microformats2 compatible themes available to increase the selection. If you can push the Genesis framework project to include them, that would be phenomenal! Some of the notes on this work can be found and added to at https:/
Also on: @ChrisAldrich
Fixed, and thank you for the recommendation and address to Press Forward's Github!
Amanda J. Rush, Jan 06 2017 on twitter.com