Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter yonatron

    (@yonatron)

    Thanks! I found the option for accepting GC payments right away. The thing I was writing about was how to sell eGift Cards online. I checked in the appropriate place: the details box when creating a new product, but I somehow just missed it!

    Right where there are options for Virtual or Downloadable, there’s also an checkbox for Square Gift Card. If you click that and save, your product gets a placeholder image, and on the front end there are fields for sender/recipient email addresses and gift message.

    So the functionality is there and reasonable, but it needs to be added to the official documentation! Especially because I have to do some testing to see what the email looks like for the recipient—either using a local install of my site or by switching a production or staging server to standby. Obviously this is a good idea anyway to make sure it works, but it’d be nice to see some email screenshots!

    @gubbigubbi, I don’t mean to derail the thread, but I couldn’t DM you on Twitter so I sent a public reply. Don’t know if you saw it, but if you still want to talk, my handle is @yonatron on Twitter and on the Making WordPress slack.

    Glad I was able to help! It took me a while to figure out how to make myself a new Access Token now that ig has changed the Basic Display stuff so much. So I imagine you have your hands full trying to fix that. Will be on the lookout for updates!

    Hi there,

    I’ve figured out why this is happening by looking at the code repo for this plugin and the Instagram API reference. The short version is that the developer’s old way of specifying the number of images was set up to only request your chosen number from Instagram. But IG changed the API and now you can only retrieve them in batches of 25. The dev has not yet updated the code in the plugin to discard the excess images after they’re retrieved.

    I figured out a way to do it, but it requires editing the code inside this actual plugin, which means if you make this change, it’ll get erased next time the plugin is updated. (though hopefully the plugin devs will fix the bug in the meantime!). I haven’t done lots of testing, but I got it to work on one site. If you want to risk it:

    1. Find the file server.php inside the plugin’s src directory
    2. go to line 161. It should currently read foreach($thumbs as $thumb) {
    3. Delete the line and replace it with the following: foreach (array_slice($thumbs, 0, $numberImages) as $thumb) {
    4. Save the file and reload a page on your site that uses the block

    Once again, only do this if you’re comfortable editing files on your site. I’m not responsible for outages or data loss etc. etc. And remember, this edit will disappear if you update the plugin!

    If you set Jetpack to Developer Mode, will it actually delete all the jpsq_sync_... entries from the wp_options table? Or does it just make it safe to manually remove them?

Viewing 5 replies - 1 through 5 (of 5 total)