Nick the Geek

That is still correct but I just did an update that in addition to fixing an issue in 4.9.x it is setting the stage for fully supporting the HTML5 “Pro” themes.

Long story short, there are some minor HTML differences but the output is pretty close. I’m using it with an HTML5 Genesis theme (fully custom) on my personal blog and the output is working. I also was testing it recently using a couple other HTML5 themes for this recent update and the output worked for where I had it.

The caveat is that in some themes there may be special markup, especially on the front page widget areas, that will not be styled correctly.

That is what the update I’m working on seeks to resolve. I”m shooting to have it out shortly after the new year pending time available to work on it during my Christmas break.

Yes it is being maintained. There was an update for 4.8 compatibility and one in the wings for 4.9. I’m also working on a couple other planned feature updates.

Hey everyone, been working on a fix for this and I’ve got a release candidate in Git that should get it working.

https://github.com/NicktheGeek/genesis-featured-widget-amplified/releases/tag/0.9rc

It will require manually updating from the zip file but if anyone is able to test to make sure it works on different sites that would be very helpful.

I’m planning on releasing the update early next week. I’ve tested all the options and it is working well for me but I don’t want to push it out on the weekend in case there may be a conflict with a version of WP I’ve not tested or some other plugin.

noting that the fixes for translation have just been released for version 1.0 so you should be able to build your translation using .po/mo files correctly.

noting that the fixes for translation have just been released for version 1.0 so you should be able to build your translation using .po/mo files correctly.

since we never heard anything back and since we have tested with wp 4.6.1 and also 4.7 I’m going to assume this was a theme or other plugin issue that is resolved.

noting that the fixes for translation have just been released for version 1.0 so you should be able to build your translation using .po/mo files correctly.

Just wanted to update here. I was able to verify the 1.0.8 version did package correctly and is showing update available in WP sites. I’ve also got reports that this did resolve the issue for at least one person.

Alex,

We had to do some custom things to make it work with a third party count service. It requires customizing the plugin to use a different count service and then using that third party service. It works … most of the time. There are several times the counts have gone down, incorrectly reported, and several other things so we aren’t ready to pull the trigger on this for everyone (blanket functional button without counts is better than a quasi working solution we may have to change which requires additional setup).

Once the service we are using is more bullet proof or we get a solution that is we will work on setting up an advanced option which will allow the counts to work again … hopefully with minimal setup and zero problems ??

Alex, sorry for the confusion. I had some things out of sync with github version and the wp.org version. Long story short it caused the 1.0.7 update to be wrong. The fix should have been applied via a new version, which it is. 1.0.8 is the corrected version and should be showing on your site once everything syncs up and your site checks to see if there is an update.

This will get the LinkedIn button working (assuming certain server issues don’t apply which can affect the method we switched to).

Let me know if this doesn’t get the button working for you.

ok, found the issue. The git repo and WP.org svn were out of sync. We were already at 1.0.7 so when I tried to tag the new release for 1.0.7 it did some weird stuff with the directory instead of updating. The correct fix is in 1.0.8 which I just tagged for release. I will verify it correctly packaged that release here in a few minutes when it updates in the repo, but the directory structure looks correct. I’ve also fixed the change log so it correctly shows the update we did for 1.0.7. I believe everything is in order now. Sorry for the confusion.

Heading off to update the git repo so it is all in sync so this doesn’t happen again.

oh weird, the release didn’t tag correctly. I need to review what happened and make sure it updates correctly. I’ll do a 1.0.8 update in a few minutes to address what happened. Short version is the files are there but in a subdirectory instead of replacing the files that were changed.

Linked in should be fixed with the 1.0.7 update. Twitter disabled the count API so we are currently unable to display the counts. We are looking into options using various services to restore this functionality but right now this requires some added work that removes the “simple” from simple share.

If you are at 1.0.7 can you please share a link to your site so I can see what is happening with the LinkedIn button?

@hanwall, can you share a link to your site. We did a good bit of testing. It is possible there is a file permission issue that prevents the button from working due to the changes we had to make to allow the button to continue to work.

I’m thinking you may need to contact LinkedIn support on this. The button just invokes a script that loads the LinkedIn share page with prepopulated data. It doesn’t actually handle the “share” functionality for that.