Gone Fishin

I may have found a simple solution to this issue.

Just add the following into the style.css file:

1. to ‘#sidebar’, add “overflow: hidden;”, and
2. to ‘#footer-wrap’, add “clear: both;”.

The “overflow:hidden;” causes the sidebar to encapsulate (contain within itself) any clears (ie. “clear:both”) so that they do not clear the ‘float’ of the #content column.

Then, adding “clear: both;” to the footer container is needed to keep it from being positioned immediately under the sidebar instead of underneath the content also as it should be.

Note: modifying any theme’s files directly risks losing your modifications when the theme is updated. It is preferable to create a child theme with your own style.css file that contains at least:

#sidebar {
	overflow: hidden;
}

#footer-wrap {
	clear: both;
}

I have tested this fix with Firefox and Opera but not with different screen sizes. It would be nice to know if it works for others as well.

Now if ThemeZee could make those changes to this great theme, we could mark three topics as “resolved” ??

I hope that helps.

That worked great! Thank you.

For a clue to the problem, see:
https://www.ads-software.com/support/topic/huge-vertical-gap-in-sidebar-content

In my experience, there are some widgets that will not cause this. But, a few can easily do so.

For an explanation of what I have found to be the problem, see:
https://www.ads-software.com/support/topic/huge-vertical-gap-in-sidebar-content

I beg your pardon, Silkalns, but just to clarify … the topic you linked to is not the same question as ‘ceomkg’ raised. His issue is not about the Tagline (description) not showing, but about neither the Site Title nor the Tagline showing, ie. none of the Header Text.

If a logo (header image) is uploaded then the site title and tagline do not display at all, even if “Show header text with your image” is enabled in the Header submenu and even if “Display Header Text” is enabled in Customize > Site Title & Tagline.

The use of a header image excludes the use of header text due to the logic in header.php.

Oh, and about the missing tagline issue at https://colorlib.com/wp/forums/topic/missing-tagline/#post-6337, it really isn’t too difficult to fit a tagline in underneath the site title. It just takes a 14px font instead of a 16px. I’d post about it on your site over there, but I don’t have an account.

Cheers,
Terry

P.S. Very nice theme by the way!

Thanks Scott. Updated ??

PHP version: 5.3.27

Actually, Jeremiah, what I am trying to achieve is functionality to take over where Permalink Finder leaves off. Something that will present suggestions of potentially related posts and/or popular posts without too much fuss (or coding). Something like Smart 404, but that plugin hasn’t been updated in over two years.

I have currently settled for just a simple default redirect page via “404 to Start” as I don’t really wish to spend the time right now to hack something up.

And just a rhetorical thought, for a WYSIWYG editor, couldn’t you just tap in to the (TinyMCE?) editor bundled with the core?

I hope that helps ??

Hi Coral,

That looks to be an issue with your webserver’s configuration.

The third warning is normal when there is an error condition that outputs warnings to the browser. The second looks to be caused by the first.

If you have access to your webserver’s ‘php.ini’ file, you can add a line with this content: “allow_url_fopen = On” (without the quotes), and see if that cures it.

If you do not have access to the php.ini file, you can ask your webhost to turn that PHP option on for you.

If none of those two solutions are options for you, you will just have to wait until the plugin author can code up a work-around for these types of situations.

I hope that helps.

Thank you for the response, Jeremiah.

I installed the plugin. Configuration is certainly not a problem as it is pleasingly simple.

However, I was hoping that I would be able to configure a page, post, or category as a redirect. Or, at least execute some custom PHP code.

Looks like I’ll just have to hack on my themes 404.php page.

Thanks anyway ??

P.S. Just FYI, for those using your plugin, a WYSIWYG editor option for the text-to-display field might be real handy.

Yes. That is exactly what I did: enclosed the offending functions within if-not-function_exists blocks. But I didn’t bother with the ‘v6’ versions of the functions.

Thanks for the code example. Hopefully it will help others until this is resolved at the source.

Terry

Well I still have not learned how to disable country-based blocking by manually manipulating the database.

However, I was able to get Wordfence working again by enclosing the two functions (that collide with the PHP GeoIP extension function names) inside “if (!function_exists())” blocks.

Since I had to manually edit the Wordfence code, I do not consider this issue resolved.

It’s a temporary issue with the WordPress repository — comes and goes. Try again. On failure, try again later.

I am not a WordPress expert by far, but it appears to me that WP3.5 adds functionality that this plugin does not need or use. But it throws an error because the plugin just isn’t programmed to be aware of the new capabilities.

lecyril is on the right track. But I do not recommend changing any functions such as ‘get_var’ to ‘query’. Doing so could make the plugin unsafe.

The better solution is to use lecyril’s dummy argument idea. Anywhere you find “$wpdb->prepare( $sql )” (with $sql being a variable as shown or any string contained in quotes), just add in an empty string (contained in either single- or double-quotes) as a dummy argument, ie:
$wpdb->prepare( $sql, ” ) , or
$wpdb->prepare( $sql, “” )

In this case, both are functionally equivalent.

Since posting the above, I read https://www.ads-software.com/support/topic/troubleshooting-wordpress-35-master-list

The info on ‘PerishablePress “5G” blacklist’ combined with the fact that I was using a modified version of the BulletProof Security .htaccess file in the /wp-admin directory, led me to remove all regular expressions for opening and closing brackets in that file.

That FIXED the problem with Wordfence.