Comment on WordPress SEO Plugins by SEO Dave.

WordPress SEO Plugins It’s the WP-PageNavi CSS file “pagenavi-css.css” adding to the Stallion Responsive CSS code that’s built in.

I added built in support for the plugin to my themes years ago, but personally no longer use WP-PageNavi: trying to reduce code I don’t monitor to a minimum.

On the WP-PageNavi plugin options page there’s an option to disable the plugins CSS file, set it to not load the plugins default CSS file and it will fix the issue.

Each of the Stallion Responsive colour schemes includes CSS classes for the WP-PageNavi plugin so the WP-PageNavi CSS file isn’t needed. Saves loading an additional CSS file which is good for performance and since I created specific CSS code for each colour scheme the paginated links don’t look out of place.

On a side note: I had to increase the size of the paginated links to be quite large to not trip a Google PageSpeed Insights Usability check related to tap size targets on mobile devices. When you turn the “pagenavi-css.css” file off they will still be a little on the big size, but not as big as they are on your site right now! If you look at the paginated comments links on this page that’s the size they should be (they look H2 header size, yours look like a H1 on steroids :-)).

David

Update: The setting is

“Settings” >> “Pagenavi” : “Use pagenavi-css.css” – Tick “No”

Unfortunately doesn’t work as I expected with Stallion Responsive 8.1, looks like I’ll need to add a fix to the next release of Stallion Responsive. Issue is I’ve added a div with a class called “wp-pagenavi” and didn’t realise WP-Pagenavi adds that class again, so I’ll need to remove mine when WP-Pagenavi is active.

For now it’s either search for the Stalion PHP files (10 of them) that include this line:

<div class="post-content wp-pagenavi">

Change to

<div class="post-content">

The above will break the design if WP-Pagenavi is ever deactivated, when I create a fix it won’t be the above as use the WP-Pagenavi class for paginated links.

Or deactivate WP-Pagenavi until I create an upgrade, no time frame for the next update: might do a quick 8.0 zip file update, so add a few small fixes to 8.0, but not generate an update notice, users can manually upgrade using the zip file and FTP. Basically can easily update the zip file with new features, bug fixes etc…, but takes a lot of changes to update the version number from say 8.1 to 8.1.1 (poor design on my part for the auto update feature).