chriscwm
Forum Replies Created
-
Thanks, @slickchris. I’ve done some additional debugging after you mentioned to check the keys. Sure enough the key was showing as invalid in plugin settings despite no changes to the YT account or the plugin settings. It just suddenly stopped working.
Apparently, the invalid key was responsible for the errors in the JS. Unfortunately, no console errors were generated which made identifying the issue not so apparent. Admittingly, I also did not make a huge effort in tracking it down. It hadn’t occurred to me it could be a key error since I just created the key two days prior and have never had these types of issues with Google’s keys and I saw no key related errors in the console. The first keys were generated using the provided button/wizard. The second was created in Google developers console.
After quite a bit of time trying use an existing key for the project with no success, I went through your setup guide and saw you required the “Where will you be calling the API from?” setting to be set to web server vs web browser, requiring a new key. Once I made that change, everything worked as expected.
Thanks for you help troubleshooting the issue. Again, I really do like the plugin and think you’ve all done a great job. Sorry for being a PIA.
Ok. Well, that’s unfortunate. I understand debugging a remote system is practically impossible and appreciate you taking a look. Sometimes things just don’t work out.
I did like the plugin and really did want to buy the paid version. Is there a money back guarantee so if that version doesn’t work (for me), I can get my money back? And if I upgrade through the free version will it retain my settings, namely the keys and tokens? It was not easy getting the client to help with 2FA of the social media accounts.
Regarding…
The YouTube API like others do have a limit of calls that can be made, and if exceeded may not appear,
Using transients will solve this problem.
Per your request:
[fts_youtube vid_count=6 large_vid=yes large_vid_title=no large_vid_description=no thumbs_play_in_iframe=yes vids_in_row=1 omit_first_thumbnail=no space_between_videos=0px force_columns=yes maxres_thumbnail_images=yes thumbs_wrap_color=#000 username=OhioDentalAssn]
I’ve tried in text editor, wysiwyg editor, gutenburg blocks, widgets, and numerous ACF fields. I’ve run the shortcode through the do_shortcode function. I’ve done all this on completely clean WP installations.
Believe me, I’ve exhausted all debugging options on my end. As a developer myself working with WP since version 1, I know most support requests are due to user error. Not this time, I know what I’m doing. I know how to debug software. And I know, the error is from your source.
I am 100% certain it’s not because of me, or the editor type or field type or theme or plugin I’m using. Regardless, a shortcode should work just about anywhere and not require a special widget.
I like the plugin and would like to buy the paid version for the combined feed, but I’m not convinced it will work considering the error I’m getting in the free version.
I just ran the shortcode through the do_shortcode() function directly in the theme and the same error occurs proving that no editor is responsible for adding the extraneous tags.
So what you’re saying is that even though this worked up until the last update it’s because I’ve pasted the shortcode into the same exact ACF WYSIWYG fields as the other two feeds. I’m not so sure that’s the correct answer. I’ve mentioned I have thoroughly debugged on the cleanest wp installation possible and the error still occurs.
I very much understand how and when WP adds markup to the editor content. I am certain that is not what’s happening.
I was considering buying the paid version but now I’m not so sure that’s a good idea. I’m not sure this plugin is reliable.
Forum: Reviews
In reply to: [Gutenberg] Just AwfulEverybody already knows that, including me, as evidenced by my comment. It was the worst thing to ever happen to WordPress.
My intention by leaving feedback is that maybe if WordPress realizes that almost everybody hates Gutenburg, that they might actually kill it off.