mod keys

I believe that I have this solved.

The .htaccess file at the root has no pointers to the subdir (as suggested by the linked page above: Giving WordPress Its Own Directory

The index.php has the subdir as below:

/** Loads the WordPress Environment and Template */
require( dirname( __FILE__ ) . '/subdir/wp-blog-header.php' );

Thanks. I ended up using a plugin: Category Posts in Custom Menu

Ah! I believe that it is being caused by the navigation menu. (I used a trick to fake remove it and scroll shows entire image tops.)

I would remove the menu and see how that changes things. That would give a clue to adjusting the template to work around.

1. Login (as an admin) to your site and click Customize
2. Click Menus, then Menu Locations
3. Unselect your Top Menu (by choosing Select rather than an actual menu)
4. Hit the Save and Publish button and see what it looks like then

If that confirms the problem/solution for you… there are ways (CSS) to make that menu area transparent but you might then have problems with the menu text disappearing into dark areas of the photos (ah, design trade off).

If you need site admin help, please give me a call. I’m honest and affordable. I also have some experience with site security which is a WordPress essential!

Your site is working by design. The front page starts with a full size header and all other pages are meant to load with the page “scrolled up” to the content area.

What contact form are you using? (Like those extra features…)

Fixed! I had tried it but with a space between the two classes e,g,
.single-post .has-sidebar:not(error404) #primary

Thank you @alchymyth

Now that you are using a child theme, you can be assured that your customizations won’t be overwritten when you update the (parent) theme.

Here are the steps to use an inline style to fix this:

1. Make a copy of /template-parts/page/content-front-page.php
2. In the child theme folder, create folders /template-parts/page/
   and paste in your copy of content-front-page.php
3. Look for the line: <php the_title( '<h2 class="entry-title">', '</h2>' ); ?> and change the style to suit yourself
4. Example: <?php the_title( '<h2 class="entry-title" style="font-size:8px;">', '</h2>' ); ?>

I can’t really counsel you on the CSS… too complicated. But suffice to say that the example above is a hack, rather than an elegant solution. You might as well just skip the php and code it: <h2 style={whatever you need}>YOU ARE COOL</h2>

That should do guide you enough to open a new thread… Changing Style of Page Title for Responsive Site

Are you using a child theme? (Recommended!)

The front page content output is controlled by /template-parts/page/content-front-page.php on line 33.

You could either use an inline style or define a new class and stick it into your style.css (child theme!).

You could also just hard code the title but that’s not really recommended…

In this vein… I want to remove sidebar from single posts but am getting empty sidebar container (css not working right). I have twentyseventeen child theme, with sidebar enabled. (Works on blog page, all posts, categories, etc.).

My research told me to create a single-post.php (copied from single.php in the parent) and delete the get sidebar call. Then add CSS to my child theme style.css like so:

@media screen and (min-width: 56.875em) {
	.single-post .content-area
	{
	  float: left;
	  margin-right: -100%;
	  width: 100%;
	}
}

But it isn’t working. Here’s a post sample: https://techpoet.net/wordpress-4-7-released/

By the way, it looks like this line (parent css) is being invoked

.has-sidebar:not(.error404) #primary {
		float: left;
		width: 58%;
	}

• This reply was modified 7 years, 9 months ago by mod keys.
• This reply was modified 7 years, 9 months ago by mod keys.

Ah, so that’s the problem. I thought it was a feature (“force admins to hack into own system”)

WordFence does work on a Windows (IIS 6) server. It scans the WordPress files, anyway. Whether it is able to block and blacklist, I can’t tell yet.

In order to get into the dashboard, I just renamed the wordfence plugin folder.

Now to convince the client to get a real host.

Found a fix. I downloaded the Filosofo Home-Page Control and it ‘just worked’. I left its Home-Page Page option set at WordPress Default and its Blog directory option blank. This is rather strange behavior – a plugin which is telling WordPress to do what it is already configured to do that is, use a certain page as the index of my site and another “page” as the index of my blog.You can read the whole story of WordPress 2.1 in its Own Folder with a Static Front Page at the root here.

Found a fix. I downloaded the Filosofo Home-Page Control and it ‘just worked’. I left its Home-Page Page option set at WordPress Default and its Blog directory option blank. This is rather strange behavior – a plugin which is telling WordPress to do what it is already configured to do that is, use a certain page as the index of my site and another “page” as the index of my blog.You can read the whole story of WordPress 2.1 in its Own Folder with a Static Front Page at the root here.

Yeah farg! I did a fresh install on a different domain o’ mine. https://www.moksha.net Worked like it s’posed to. Only difference? I’m running WordPress from the root with none of that fancy stuff where WP is installed in the folder /blog and my index.php is out to the root of my website. I THINK THAT’S THE ISSUE!!! BUT I’M NO GENIUS OR NOTHIN’

Ah, you need to learn about The Loop!

Wonderful bedtime reading!

I am having the same issue. This is an upgraded 2.05 to 2.1
https://www.soulcode.net
1. I have my special index.php at the root
<?php
/* Short and sweet */
define(‘WP_USE_THEMES’, true);
require(‘./blog/wp-blog-header.php’);
?>
2. WP is installed in the folder /blog has
3. I am using the new 2.1 feature Options/Reading/Front Page
5. I have a page called Home with slug of home
6. I even tried using a different page through the Options/Front Page feature and it didn’t work
7. I played with using the static_front page plugin – didn’t work
8. The Blog page works correctly

You will need to read the documentation to understand the WordPress loop, using templates and perhaps a few other technical topics. Or hire a consultant… there are quite a few of us.