Bill Robbins

[Bill Robbins]

Fantastic 🙂

[Bill Robbins]

Good Morning Deborah,

I believe I see the trouble here. Edit your home page and look in the right hand column for a box labeled attributes. In that box is a drop down menu for templates. Choose the home page template there and update your page.

See if that doesn’t do the trick. If you still have trouble, please leave a couple of widgets in the home bottom sidebar so I can see what’s the hang up.

Take care,
Bill

[Bill Robbins]

Good Morning Ana,

Sorry for the trouble there. I just took a look at your site and it appears you were able to get the home page template set up for your front page last night and started adding images and content to it. If you are still having trouble, let me know and I’ll be happy to help out.

Have a great day,
Bill

[Bill Robbins]

Joe,

Delete that copy of the theme and download a fresh one from our downloads section. That looks like the updater from before the theme was part of Organized Themes.

See if that doesn’t do the trick for you,
Bill

[Bill Robbins]

Hey Joe, I’m so sorry, but I’m not following you here. Are the URL slugs for the customer orders on your site not working?

[Bill Robbins]

Hi Joe,

Hope you’re doing well. What API are you running into trouble using? Let me know and we’ll go from there.

Bill

[Bill Robbins]

Fantastic news. Let me know if you have any other questions.

[Bill Robbins]

Thanks Rhonda. Have a great day too ?

[Bill Robbins]

Hey Robert,

You could also edit the body-tag.php file to allow you to choose the layout directly on the blog page. Replace all of the content of that file with this:

(See support site for code).

Be careful making that edit if you do it inside the WordPress admin since it is a function file. You can always temporarily disable the theme and make the edit with another theme active. Then preview Church Builder before activating it to make sure all is well. That’s a good way to guard against PHP errors locking you out of the admin.

And I believe that will allow the layout option directly on the blog page to work like the other pages. The Page Builder option won’t do anything, but the sidebar/no-sidebar options should work after that.

Bill

[Bill Robbins]

Fantastic. Try adding this to your Custom CSS and see if that doesn’t help out:

#header nav#top-menu ul ul ul { display: none; top: -2px; }

#header nav#top-menu ul ul li:hover ul { display: block; }

Let me know if you run into trouble,
Bill

[Bill Robbins]

Hi Robert,

Good question. The blog page inherits the default layout that’s set in the content section of the customizer (Appearance > Customize in your dashboard). I believe if you switch that to one of the sidebar options there it should cause it to appear.

Let me know if that doesn’t do the trick for you,
Bill

[Bill Robbins]

Hi Rhonda,

If you don’t mind making a way for me to be able to see the site, I’d be happy to take a look for you.

Thanks,
Bill

[Bill Robbins]

Glad that did the trick for you 🙂

[Bill Robbins]

Hey Lara,

I moved your reply to a separate topic. Looking at the site, did you happen to create a header.php file inside your child theme? Some of the changes in version 1.1.7 affected the parent theme’s header.php file. This section in version 1.1.6:

<div class="menu-button"><?php echo get_theme_mod( 'mobile-nav-label', 'Menu' ) ?></div>
				
				<nav id="primary-site-navigation">
					
					<ul data-breakpoint="767" class="flexnav">
						<?php wp_nav_menu( array( 
							'theme_location'	=> 'primary',
							'container'			=> 'false',
							'items_wrap'		=> '%3$s',
							'depth'				=> 3,
							'fallback_cb'		=> false
							) ); ?>
					</ul>
					
				</nav>

was changed to this in version 1.1.7:

(See support site for the rest of the code there).

Try updating your child theme’s header.php file and see if that won’t allow the new scripts to correctly work with the menu. It should also take out the unnecessary “menu” button just above the navigation.

Let me know what you turn up,
Bill

[Bill Robbins]

That’s one way to look at it, but that could ultimately get your site hacked which not be good.

Go with a good web host. That’s the best solution.

[Bill Robbins]

Generally software takes up more resources as time goes on. That’s why Microsoft Word could run with 2mb or RAM back in 1994, but you couldn’t even begin to run Windows much less any apps with that small amount now.

New WordPress versions do often take up more memory than the ones they replace. It might not be much, but since most shared hosts are very stingy on resources to begin with it doesn’t take much to push things over an edge.

Sometimes swapping out plugins can fix it since not all plugins use the same amount of resources, but at best that is a stop gap measure. Future updates will almost certainly take more resources so even a “fix” now will likely require revising in the future.

[Bill Robbins]

Hi Karen,

There is a plugin that advertises it can delete all your comments for you called Delete All Comments (https://wordpress.org/plugins/delete-all-comments/). I haven’t used it before so I can’t speak to how well it works personally, but that might be a good option for you.

Often times HTTP errors with the media uploader are from WordPress running out of memory. I did some consulting for one of our state universities over the summer and they were having that exact problem due to a lack of available memory. We had to get with the web host to increase the amount of resources available to the site and that took care of the issue.

Take care,
Bill

[Bill Robbins]

Hey Durenda,

You can do that. Go to the Appearance section in your WordPress dashboard and click on Edit. From the list of files on your right, choose fonts.php. Down right at the bottom you’ll see this line:

wp_enqueue_style( "options_typography_$font", "http://fonts.googleapis.com/css?family=$font", false, null, 'all' );

You can change the http: there to https: or you can take it out and make the URL there start with the // . The // is how I go about that in some of our other themes.

Hope that helps out,
Bill

[Bill Robbins]

Good question. With widgets that load their content from another website like a Twitter or Facebook widget, it’s usually a good idea to set a minimum height in the CSS. The embed code often has a height set, but also adding it to the CSS can be helpful. You just want to make sure that the widget is set to be tall enough that once the content loads, it won’t end up being any taller than that.

The script that arranges the widgets takes the height once the images are loaded and positions the images based on that height. If the height changes afterwards, the script will not reevaluate the placement. That’s typically the case of overlapping widgets there.

For this particular widget you might be able to use something like this:

#weblizar_twitter-2 { min-height: 500px; }

You can adjust the 500px there for the right fit. See if that doesn’t help out.

The images will readjust if the screen size changes past a breakpoint, but otherwise any changes to the size of any of the widgets after the page is loaded will not be taken into consideration by the script.

Hope that helps out,
Bill

[Bill Robbins]

Good Afternoon Bill,

Demo data can sometimes be a double edged sword since it doesn’t always make things clear where everything is located to change out.

The home page has the slider that you’ve discovered. Everything else on the home page is made with widgets. To edit those, go to Appearance > Widgets in your WordPress dashboard. The available widgets will be listed on your left. On the right are the areas in the theme that take widgets. Those are called widget areas or sometimes sidebars.

The home page in Epic has two widget areas. If you’re using the layout like the demo has, then you only need to use the home bottom widget area. Click on it on the right hand side of the widget screen and it will open up and show you the widgets that are located there. You can click on the title of a widget to open up that widget’s options which will allow you to edit away. You can also click the title of a widget and drag it around to reorder and rearrange them. If you drag a widget to the left and let it go it can be added to inactive widgets. That will keep the widget’s options, but remove it from the front of your site. You’ll also see a delete link at the bottom of each widget’s options that you can use to remove that instance of the widget.

See if that doesn’t help you change out the content on your home page. If you have any trouble, let me know.

Thanks,
Bill

[Bill Robbins]

Good Morning Ed,

That is a lot of space there. I believe it is coming from this style in your child theme’s style.css file:

nav#top-menu li a {
    padding-top: 5px;
    padding-right: 1px;
    font-weight: 600;
    margin-left: 15px;
    border: none;
    display: inline-block;
    font-size: 12px;
    margin-top: 27px;

}

That will add a 27px top margin to every link in the navigation menu, including the sub-menus. Most likely you’ll want to take out the top margin there. If you need to reposition the top level of the navigation menu, then add a margin directly to the nav#top-menu item. That way you can move the navigation around as a complete unit.

Hope that helps out,
Bill

[Bill Robbins]

Good Morning Samuel,

I did a test submission of your feed in iTunes by going to File > Subscribe to Podcast and entering the URL to your feed there. When I tried that yesterday, I received an invalid feed error, but this morning it pulls up your feed just fine. I ran it through Apple’s recommended validator and it passed there as well.

You might try altering the URL slug of your feed a bit and resubmit with the new URL. You can do that by editing your page and changing the slug just below the page title. Perhaps they have the feed cached and they are pulling in old information. A slightly different URL would be a way around that.

If Apple is still rejecting your feed today, then I believe you’ll need to contact them and get a reason why. Those are the two tests that Apple gives us to use prior to submission. Since it passes both we’ll need some indication from them as to why it is being rejected.

Let me know what you turn up,
Bill

[Bill Robbins]

It looks like it is the hover state that is missing there. That seems to be why the color is turning up gray instead of blue. Try this:

.boxcaption a,
.boxcaption a:visited,
.boxcaption a:hover {
  color: #273b96;
  text-shadow: none;
}

See how that works out.

[Bill Robbins]

If you made those code changes before submitting to Apple, I would tend to think that isn’t the cause since they would have rejected at that point.

Looking through the podcast episodes, I did notice a few of them don’t have an author specified. I made a copy of the code in the feed and added an author and then uploaded it to my server. I then submitted that URL to iTunes via the File > Subscribe to Podcast option and it pulled the podcast up.

It might be that making sure that every episode has a speaker will do the trick. Here are a few that don’t have one currently:

Sacrifice
The good news at the end of your rope
Is Christianity Just a Crutch?

See how that works.

[Bill Robbins]

Hi Samuel,

I ran a validator on your feed and it didn’t turn up anything (http://www.feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.harbourfellowship.com%2Fpodcast-feed). Is Apple sending you any error messages?

[Author]

Posts