donmcleman

There was another HTML5 error: the class attribute had been called twice for the linkedin sharelink. To solve this I added a comma between the relevant classes in ssba.php.

// linkedin share link
    $htmlShareButtons = '<a class="ssba_linkedin_share, ssba_share_link"

Still unable to solve the mailto error.

I rolled back to the previous version and I still have both problems.

I had never previously validated the html on pages with the share buttons so perhaps the html problem has been there a long time? The error message is exactly the same.

As for not showing up, I wonder if there’s a conflict with some other recent change that I made… any suggestions what it might be?

This same question keeps coming up for this plugin. I can’t see any input from the developer. I sent him a tweet, got no response.

I’ve tried to change the code myself but it still fails validation. A post about a year back says other people tried the same thing.

It would probably be simpler to find another plugin…

Update: I’ve found a solution, but it’s probably not the best way?

I’ve added the shortcode to the start of comments.php so that the buttons appear after the navigation. In the css stylesheet for the child theme I’ve set display:none for the ssba div within <article>.

So the web page looks right but does it mean that two requests are made to display the buttons and then one request is cancelled, so creating more work than necessary to display the page?

Thanks for the quick reply.

However, I’ve re-enabled script debugging but this has created another problem in the backend: on the page called Edit Menus I can’t toggle open the accordion sections for item types (pages/links/categories).

I’ve found that removing the script debugging code lets me use this again. Obviously I’d prefer not to change code each time I want a different part of the backend to work – is there an alternative solution?

Could you explain what you mean?

Do you mean subscribers who add their address now receive spam???

Similar problem – when I add the widget to the sidebar the rest of the sidebar disappears, and the widget doesn’t appear either.

I’ve rolled back to a backed-up previous version until a fix is in place.

If I look back a few posts I see that someone else had the same problem.

All in One WP Security inserts code into the .htaccess file in order to blacklist query strings that include the word ‘encode’ so as to limit the risk of malicious attacks. The only way for me to install your plugin is to delete that rule.

How attached are you to the name ‘Email Encoder Bundle’? I’m sure you’d agree it lacks pzazz… how about Total Email Shield the Mother of all Protection and Saviour of the Universe?

I’ve just found this – why was it marked as resolved without comment? Will you be changing the name of the plugin?

Well, that is a turn-up. I managed to install on both sites, which means one.com are off the hook for once.

So it looks like a plugin conflict. The plugin that might seek to prevent installation is All in One WP Security. Are you aware of any settings that need to be changed?

And the answer is… I checked on another website and when setting up a project you leave the referrer box blank, ignoring the example underneath.

My own api key now works. Thank you.

It worked! So presumably this means there’s something wrong with my console settings. It happened on three sites I installed it on so I’m probably missing out some very basic stage, I’ll have another look.

Thank you!

Hey, thanks!

Well, that didn’t narrow it down much. Disabling other plugins made no difference; installed it on two other sites (one of which was also on one.com so for once they’re not responsible) and both came up with the same error.

I didn’t try uninstalling and re-installing as the installing on other websites will have dealt with that possibility.

The page on the Developers Console that lists projects shows the number of requests made for each site and the same number of errors. (For the main site I’m looking at there there are slightly more requests than errors as I’m also running the Web Fonts Developer API).

To cover all bases: I’ve been using Chrome on Windows 8, I’ll try Firefox on Windows 7.

Is this particular api dependent on another api to run perhaps?

I’ve added the line of code and re-run the check but no new info has appeared in the log file. The chart on the console does register that a check was made.

I’ll try simple things like disabling other plugins, re-installing, installing on another site.