Hi Nathan
Thanks for the feedback. Would you mind letting me know the exact shortcode you used, with parameters (if any?).
I will look into it.
Thanks!
Hi! Thanks for your response. I wasn’t using any parameters. Just the shortcode [pocket_links].
Here is the page where the shortcode is in use:
http://wpnathan.com/page-three/
That’s just a test website where I do training webinars for iThemes Training. I can keep that page with the errors up until Monday when the next webinar happens.
The error has changed a bit since I posted the ticket. Previously, there were more than a dozen instances of the error I posted above. Now there are only two errors:
Warning: Invalid argument supplied for foreach() in /xxxxxxxxxx/wp-content/plugins/pocket-wp/pocket-wp.php on line 339
Warning: implode() [function.implode]: Invalid arguments passed in /xxxxxxxxxx/wp-content/plugins/pocket-wp/pocket-wp.php on line 424
Great thanks Nathan!
I will look into this right now.
Cheers
Hey Nathan,
Can I just double check you went through the setup process? Ie, you got a consumer key from Pocket, authorized it via the settings page and got an access key successful message?
It seems that I was able to reproduce the error when I tried to use the shortcode without completing the setup process.
Cheers
Ok, I have pushed an update… It basically just checks that the feed was retrieved properly, and if not, posts a message advising to ensure the plugin is setup properly. That should prevent those errors.
However, I’m not sure that was your actual issue, as you said in the first post that the links appeared properly…
Anyway, maybe try the update and try adding your Pocket consumer key and authorizing again. Let me know how you go.
Cheers
Thanks for looking into this!
I updated the plugin and went through the setup process again, creating a new application and connecting it to the site.
Now, I’m back to a bunch of errors followed by my pocket list.
You can see it here: http://wpnathan.com/page-three/
Cheers. Thanks for reinstalling! I’m pretty sure there is an issue with processing the tags (or lack thereof)… Will have a fix in a few mins.
Ok, just pushed another update and should be fixed now in 0.4.2… Seems the issue was that I was not handling untagged links properly. The update will add the tag “untagged” in the tag list which sits underneath the link/excerpt. If you want to remove this tag list, use parameter tag_list=”no”
Hopefully that fixes it for you… If not, let me know!
Cheers
Working perfectly now! Thanks.
Excellent! Thanks for helping me debug, Nathan.
I’ll mark this as resolved.
Cheers
