@eay: Let us know if we can be of any help as you build: http://indiewebcamp.com/wordpress

Shoreditch Theme fatal error with Jetpack « WordPress.com Forums

When attempting to either activate or preview the new Shoreditch theme (technically shoreditch-wpcom) on a relatively new self-hosted install I get the following error:

Fatal error: Can't use function return value in write context in /home/wp-content/themes/shoreditch-wpcom/inc/jetpack.php on line 129

This happens regardless of whether Jetpack is activated or not.

Activating the theme required digging into mySQL settings and rolling back the theme manually to recover the site.

There's at least one other reported error from someone last week who was using a multisite install: https://wordpress.org/support/topic/shoreditch-theme-throws-jetpackphp-error-on-multisite

Testing on a wordpress.com install didn't throw similar error.

IndieWeb and Android Mobile

@dshanske I remember you mentioning it briefly the other day and then saw something more specific this morning: http://indiewebcamp.com/irc/2016-05-03/line/1462285944410

Have you hacked around with either Bookmarklet Free or URL Forwarder apps from the Google Play store? They’re mentioned in the following two places:
https://snarfed.org/easy-indieweb-interactions-on-android
http://stream.boffosocko.com/2016/sharing-from-the-indieweb-on-mobile-android-with-apps-and

I’d gotten URL Forwarder set up and configured to make mobile sharing for my WithKnown install to make bookmarking, sharing, reposting, and a few other functionalities work incredibly quickly and well. I’ve put off doing so on WP since I have some other back-end dependencies that need tweaking so that I don’t create redundant loops with some of my other configuration. With any luck one or the other will get you pretty far without having a full micropub application.

With these you can use Android’s ubiquitous sharing icon and share to one or the other of the apps which will do the URL scraping to be able to do some of the posting types you want. Depending on the output, you may need one or two additional tweaks, but it’ll give you a reasonable template for a workflow. I’m sure some further url parameters and integration could be put in to auto checking the correct post kind and thereby making your posts fully indieweb compatible on WP. Adding Indieweb Press This https://github.com/pfefferle/wordpress-indieweb-press-this/ functionality for bookmark, share, watching, listening, et al. would complete a larger cycle of functionality.

Then, I’m sure there’s the additional functionality of API calls to Twitter/Facebook/etc. to implement the actual retweet/like on the native platform, but that could be handled later/separately (though Bridgy Publish might be able to handle this? I seem to remember a mention of it in the bookmarklet set up.)

Finally, if “Post Properties” could import the same URL and scrape the metadata, the entire process would be almost too simple and not need a “traditional” mobile app at all.

For URL Forwarder the base settings should be:
Reply: http://YOURSITENAME.com/wp-admin/press-this.php?v=8&type=reply&u=@url
Like: http://YOURSITENAME.com/wp-admin/press-this.php?v=8&type=like&u=@url
Repost: http://YOURSITENAME.com/wp-admin/press-this.php?v=8&type=repost&u=@url

Hopefully this gets you a few steps further on android mobile without a huge amount of work…

It looks like no one is maintaining this actively and the last patch was in 2014. Just keeping up with Twitter and Facebook API changes can be painful.

You might find similar functionality using a group of IndieWeb related plugins https://wordpress.org/plugins/indieweb/ much of which is in active development on GitHub as well. Documentation and additional information can be found at http://indiewebcamp.com/wordpress.

Some of the rest of the autoposting portions can be had through JetPack's Sharing functionality or alternately through NextScript's SNAP plugin: https://wordpress.org/plugins/social-networks-auto-poster-facebook-twitter-g/

@zoonini, @WordPress should definitely add this kind of child theme support as a default! I would use it all the time.

@zoonini Is there a canonical location where WordPress/Auttomatic keeps such child themes as the one you created for Pique? I've run into some sporadically on Github, but wondered if side work (with bonuses) like https://wordpress.org/support/topic/woocommerce-support-for-pique-theme?replies=26#post-8196671 lives somewhere besides a forum where it's possibly not as discoverable? Maybe it's just that I've never thought to actively look for them before, but it seems like they could have some greater long term value if the code isn't all rolled up into the primary theme.

I actually think, just for ease of use and simplicity that all themes should really come pre-packaged with child themes, but until then...

Thanks again for sharing your talents and genius! #Happiness

Posted on 3/24/16:
@Kathryn and Ola, thanks for the tweaks and the child theme! I hope that Ola is dumping the code back to Sarah [https://github.com/sarahmonster/pique] or wherever you keep it internally, so that Woo support is at least partially baked in when it's released to the .org side. I'm sure it may be on the theme's internal roadmap, but don't forget to declare WooCommerce support in functions.php when the final version is rolled out.

I particularly liked the careful thought to keep the theme's buttons consistent as well as the change from 3 columns of products instead of 4. The only tweak I might further suggest is the color of the "add to cart", "proceed to checkout", and "pay" buttons (see http://boffosockobooks.com/product/amerikan-krazy/ which I've not restyled presently to highlight the existence) which all appear as purple [#a46497]. (Though the purple helps to highlight them, I wanted to make sure it was a conscious design choice rather than an oversight.) Either way, throwing the CSS code for the changes on these directly into the bundle makes it much easier for less sophisticated users to tweak the code later.

Other than that, I've looked through most portions fairly carefully and everything seems to be working as I'd expect it to without any glaring issues/errors. My thanks to you, Sarah, and Ola for the beautiful work that went into this as well as the after-the-fact adjustments.

@stephenwrks, A few things in the theme that you might consider taking advantage of and using on your current page are increasing the featured image opacity (25, 50, 75, or 100%) of the photos using the theme customizer/theme options/panels 1-8. This will let you "brighten" up your page without making the foreground text difficult to read and highlight the beauty of your photos.

You might also consider creating a secondary menu called "social" in the menu interface with custom items being links to your social media sites and then in the customizer/menu section setting the footer menu to use this menu. Then your social media bugs will appear in the footer of the page rather than into the second widget where it's at now. This will help streamline and balance out your page a bit (See the Custom Menus section at https://theme.wordpress.com/themes/pique/ and https://en.support.wordpress.com/menus/social-links-menu/ for more details.)

Good catch @dshanske! It was exactly https://github.com/jihaisse/wordpress-syndication that was the cause. I could have sworn that I'd cleaned out all of the older/legacy indieweb plugins after the "master" IndieWeb plugin was rolled out a while back, but apparently that one was quietly hiding in my plugins folder waiting to catch me.