Nick the Geek

What version of the plugin are you using? I just did an update earlier today that should resolve this.

@mclennan, sorry for the delay, there was a bigger mystery that was causing several people issues after they updated GFWA 0.9 I’ve been trying to solve. It was weird.

Anyway, I just published a release candidate for 0.9.1 that will solve and issue with activating the plugin in Genesis with certain versions and allows safe HTML in the byline and meta field.

You can download it here
https://github.com/NicktheGeek/genesis-featured-widget-amplified/releases/tag/0.9.1

I’m planning on doing the release tomorrow, likely during my lunch.

@quingdom and @tamingtwinsblog ok, I was able to narrow this down.

The Genesis Featured Widget Amplified plugin did not change it’s markup or output. However, it did change the timing and manner in which the Widget was registered.

With GFWA 0.8.2 and older the widget registered late enough that the Foodie Pro – Featured Post widget was loaded in place of the GFWA widget.

Since the GFWA widget does not support HTML5 themes like Foodie and since it was not actually loading output, my recommendation is to deactivate the Genesis Featured Widget Amplified plugin in favor of the Foodie Pro – Featured Posts widget built into the theme.

@vaishy67 ok, I was able to narrow this down.

The Genesis Featured Widget Amplified plugin did not change it’s markup or output. However, it did change the timing and manner in which the Widget was registered.

With GFWA 0.8.2 and older the widget registered late enough that the Foodie Pro – Featured Post widget was loaded in place of the GFWA widget.

Since the GFWA widget does not support HTML5 themes like Foodie and since it was not actually loading output, my recommendation is to deactivate the Genesis Featured Widget Amplified plugin in favor of the Foodie Pro – Featured Posts widget built into the theme.

@vaishy67 I’m sorry you are having trouble with this. The thread is a duplicate of https://www.ads-software.com/support/topic/problems-with-the-latest-version-of-genesis-featured-widget-amplified/

I checked your site and I noticed it is using the Foodie theme. I’ve seen this reported with the Foodie theme a few times. The odd part is this plugin doesn’t officially support the HTML5 themes. I’ve attempted to identify any HTML changes in the widget output but have failed to do so.

The image is outputting as the “full size image” so I suspect the image setting has been changed/lost. That can be fixed by editing the widget setting, but I do not believe it will fix the alignment issue.

I’ve asked this before because it seems as though the plugin was using a custom version that supported HTML5. Do you remember where it was installed from or if it may have been customized?

@quingdom sorry I saw your latest update after I submitted.

The alignment issue is likely because foodie is an HTML5 theme. The HTML markup in the plugin is different from what the theme expects.

Is there a chance there was a modified version of the plugin on the site prior to the update?

I am working on a version that will support HTML5 but it is not likely to be ready for a while yet.

@quingdom Thanks, I see that the images are too large and it is using a srcset for the images instead of the standard src.

I did some experimenting and it seems the issue is the setting is set to “full size” … rather the setting is coming up empty. Can you check the widget to make sure the correct image size is selected and save please. It may require making a change then changing it back so it will let you save correctly.

For what it’s worth, I’ve updated the method of getting image sizes so it will pull in all the image sizes including displaying full width as an option in the updated version I linked to above. I just pushed that up a few minutes ago so if you have already downloaded it, that will not have the change so you’ll want to download it again and replace the version you’ve added to the site.

I”m going to have to hold on a fix for this until I can replicate it. Ideally a screen shot of the widget settings and even better a link to view it as “broken” would really help. I’ve just spend an hour trying to jump from an older version to the current version and otherwise replicate this but it seems to work for me each time. It may be a specific setting or the theme or a few other things that I’m not accounting for but it is aligning images and using the correct image size for me.

Sorry this isn’t a super quick fix, but I will get it solved once I have the info I need to replicate it. I’m just hesitant to make a change that could break sites that are working without being able to test the parameters.

@tamingtwinsblog I’m very sorry to hear it is causing you trouble too. I’m hoping to have a working fix this evening after work. ??

@quingdom I’ll work on replicating it this evening but if you’d like to use the start of the 0.9.1 release you should be able to activate without any problems.

Then you can help me with more information about the widget settings etc so I can get this resolved more quickly.

The file should be available in the GitHub repo here https://github.com/NicktheGeek/genesis-featured-widget-amplified/archive/hotfix/0.9.1.zip

You may need to unzip it to rename the folder then zip it to install it or upload via FTP.

So far the only change is that I removed the activation hook to check the version of Genesis and instead have it using the genesis_init hook, which is much better over all and ensures the theme is Genesis or a child theme and has the added benefit of genesis_init ensuring the minimum Genesis version.

TLDR; it will activate now but doesn’t have any changes to fix the layout issue.

I need to check the logic for the activation check. Can I get more info on what wa wrong with the layout.

@mclennan ok I see the issue. I completely misunderstood what you were trying to do.

So here is what is happening. The output is being escaped, which is why you see the markup on the screen.

This is important because it prevents XSS attacks. I’ve actually updated with even more escaping in the latest update but not where it would affect this.

I can look at using a different method to allow the content to be output safely with limited html support so scripts and other potentially unsafe content can’t be skipped into a field.

I may do this in a way that it can be set via an option or a function. The reason is the other methods that would allow HtML require additional processing that could slow a site down if there are a lot of instances on a page.

@mclennan

Sorry for the really long wait. I’m working on some updates for features and fixes. I can’t replicate this issue though. I’m worried maybe I’m doing things wrong. Can you let me know how you are using this, like screen shots of the settings etc. I’m wondering if maybe a specific combination is throwing it off.

WP 4.9 issue should be resolved with version 0.9 that was just released.

I *think* this issue would have been resolved with 0.8.2.

I’m going to mark this as resolved since I cannot replicate at this point so either 0.8.2 or 0.9 resolved it (maybe both).

If the original issue is not working after updating to 0.9 please let me know.

@chris_c, thanks for testing that!

Everyone else, GFWA 0.9 just went out and I’ve tested the update in a couple of production sites just to make sure it is working with the SVN update (sometimes I miss adding new files or whatever and it doesn’t work so I wanted to make sure aside from the manual git tests I had already done).

This update resolves the reported issue. I’m going to mark this thread as resolved but please let me know if it doesn’t work for you.