Mike

Experiencing the same issue as @flushaa. Login took 30-40 seconds on average but reverting to the previous version took it back down to 4-5 seconds.

Perfect! Thank you so much again for the quick updates and speedy replies! =)

Wow, that was super fast! Very much appreciated!! Tested out the update and only encountered a minor snag. There is some jquery injected into the page through thumbs-rating.php around line 253, which checks for the already voted state. Removing that function still enables the ratings to record, but also leaves out the “You already voted!” message to the user. Otherwise, all worked as expected =)

Sure thing. Around line 170 in bowe-codes/includes/functions.php, I added the line below to pull specific information about a user using the xprofile shortcode plugin (https://www.ads-software.com/plugins/bp-xprofile-shortcode/).

$member_html .= do_shortcode( "[xprofile field=15 user='$user_id']" );

Hope that helps!

Figured it out by hacking the plugin a bit =)

Yes, thanks for the workaround! Gotta love how we can all come together and troubleshoot stuff =)

This plugin prevented me from uploading images, too. I enabled debugging through wp-config and through the plugin settings like you mentioned above, but there’s no error reporting. This issue occurs specifically when you’re running the (Yoast) WordPress SEO plugin in tandem with this plugin. Disabling either WordPress SEO or Post Thumbnail Editor resolves the issue, but they currently are conflicting with each other somehow. We’re running the latest version of WP on WPE, which just got updated the other day, and that may have offset something, because we didn’t experience this problem before.

Just a heads up… the erroneous error pops up on my end, too, despite everything working properly =)

Thanks so much for the update! Everything works =)

Totally. Matt actually referenced this post — https://www.ads-software.com/support/topic/consider-checking-doing_ajax-for-is_admin-checks?replies=3 — in an email to me, which I thought was pretty interesting. In any case, the updated code will display DFIs on the ajaxed search page =)

Matt, the FacetWP plugin author, was able to figure it out =) He’s returning the search results on my page via ajax, which gets ignored by the DFI filter, so he changed line 62 in set-default-featured-image.php from

if ( is_admin() || '_thumbnail_id' != $meta_key )

to

if ( ( is_admin() && ( ! defined( 'DOING_AJAX' ) || ! DOING_AJAX ) ) || '_thumbnail_id' != $meta_key )

All is well now. Perhaps, you can update your plugin, if other people run into the same issue =) Thanks again for all your help, Matt and Janw!

Thanks again for the quick reply =) So the regular post thumbnail template tag (code below) does work but only for posts where I’ve manually uploaded and set the featured image. It doesn’t work for any of the posts that uses the WooCommerce/tag-based DFI images. I’ll see if the FacetWP dev knows any more about this and maybe I can get this squared away.

post thumbnail code I’m using:
<?php the_post_thumbnail(); ?>

Thanks for the quick reply! I changed $product to $post_id on all of my functions/filters, but the DFI still doesn’t want to display. It works everywhere else on my site except on the FacetWP search results page. I can give you access to my site, if that’ll help explain things more, but I don’t want to spend too much of your time either.

I tested it out with using the default icomoon name, but it was still a no-go. I actually winded up incorporating the font into my theme and just used a few css rules instead, which made everything easier and lighter load-wise =) Anywho, thanks again for the swift responses and making the plugin freely available!

Hey there again – Apologies for the delay on here to your reply. I’ve checked with WPE and they’ve got allow_url_fopen enabled. I also checked the fonts directory and my font did manage to upload in there. Not sure if this bit of information helps, but I have a notice that reads “You already have a font pack installed. If you want to install a new font pack, you must first uninstall the current one.” So it seems to be also recognizing that it’s installed; however, I still see a loading/spinning icon below this notice off the left without the font preview (https://steppic.com/show/220335af652b369a01cf7113209aadd4.html).