Nick C

Hi, @todorchristov!

By default the Genericons stylesheet that Genesis Simple Share uses base64 encodes the woff font, which is the source of the warning you’re seeing from Pingdom. This is to work around an issue with cross-origin requests, where a stylesheet loads a font from a different domain or CDN.

If you’re serving the font from the same domain (or using a CDN but can enable cross-origin resource sharing), you could change the second @font-face declaration in wp-content/plugins/genesis-simple-share/lib/css/genericons.css to look like this instead:

@font-face {
    font-family: 'Genericons';
    src: url('../font/genericons-regular-webfont.woff') format('woff'),
         url('../font/genericons-regular-webfont.ttf') format('truetype'),
         url('../font/genericons-regular-webfont.svg#genericonsregular') format('svg');
    font-weight: normal;
    font-style: normal;
}

(Replacing the base64 encoded version of the woff url with a path to the file.)

That will remove the warning from Pingdom. The actual performance gain from doing this is likely to be very small indeed, though, so personally I leave the file unedited on my sites. There are almost always bigger performance gains to be made elsewhere.

Hi, @zwoo. I’m able to run Author Pro 0.9.0 on WordPress 4.6.1 without seeing a 500 error.

Do your server logs show any errors?

To restore admin access, you could remove or rename the genesis-author-pro folder via FTP.

Hi, biberkopf!

The child theme root is the correct place to add these files. To confirm which file is being used, you can use a plugin such as What Template File Am I Viewing, which adds the template path to the admin toolbar: https://wordpress.org/plugins/what-template-file-am-i-viewing/.

Note the Author Pro plugin unhooks the following Genesis entry actions in genesis-author-pro/functions/template.php, though:

• genesis_before_entry
• genesis_entry_header
• genesis_before_entry_content
• genesis_entry_content
• genesis_after_entry_content
• genesis_entry_footer
• genesis_after_entry

If your custom file is hooking functions to any of those actions, it won’t have an effect by default. Instead of this:

add_action( 'genesis_entry_content', 'my_custom_function' );

function my_custom_function() {
	echo '<div>Test custom template</div>';
}

You can do this:

add_action( 'genesis_before_while', 'my_book_hooks' );

function my_book_hooks() {
	add_action( 'genesis_entry_content', 'my_custom_function' );
}

function my_custom_function() {
	echo '<div>Test custom template</div>';
}

This hooks your custom functions after existing ones have been removed, which makes sure your functions run.

Hi, floridahikes. I see 938 Facebook likes on http://floridahikes.com/florida-trail-app: http://d.pr/i/W0hM

If you still see a zero count there, it’s worth whitelisting the site in any browser privacy add-ons you use, or checking in another browser.

Sorry that you had to reapply the fix, srower. We do plan to resolve this issue, and have an open ticket here if you would like to track the progress: https://github.com/copyblogger/genesis-simple-share/issues/65