acub

Here’s a clean and safe way of changing fonts throughout the site:

1. Upload your font files at Squirell Webfont Generator
2. Upload the result in your [child-theme-folder]/fonts
3. Add

@import url("fonts/stylesheet.css");

to your style.css, at the start, after the theme definition comment.

Depending on how many fonts you import, the path above might differ: “fonts/regular/stylesheet.css”, “fonts/condensed/stylesheet.css”
At this point, you have successfully installed your font and is ready to be applied to any elements. In my case, the font I embedded was Expressway. So all I needed to do was apply it to all the elements I wanted:

html, body, div, span, applet, object, iframe, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video {
	font-family: 'Expressway';
	}
h1, h2, h3, h4, h5, h6, div.ws-title div{
	font-family: 'Expressway Condensed';
	}

There are other ways of creating and embedding fonts in a website and I’m not endorsing this one. It’s just something I tried and worked.

Not that I know of. The first six characters of your reply did most of the job, though.

Please mark as resolved if that’s the case.

You need to disable all the files from the child theme except functions.php and style.css. By disabling I mean renaming (put “old_” before their names). Than re-enable them one by one and see which ones are causing erros. Compare them to their new versions and replicate your changes in parent version, saving the moded files in child theme folder.

In 3.0.12 a lot of structure changes were made, to both file templates and functions, because of the dev tools. Now almost all functions are filterable. You can alter their output without needing to know in what file they are.
Everything happens in your child theme’s functions.php and is 100% upgrade-safe.

Install and activate RTFR if you don’t have it by now.

Replace (left box)

.carousel({interval

with (right box)

.carousel({pause:false,interval

Remember to mark as resolved after you verify the solution.

You would need to unhide it for the all the possible queries that might return a list of posts and/or pages. And that includes all type of archives (yearly, monthly, daily, hourly), authors list of posts or pages, search result, categories, taxonomies, custom post type lists, tag archives and I’m sure I’m missing some.
You would need to add a selector for each of those body[class=””] selector s and, after you finish the list, add all of them {display: inline-block;}
Something like…

.archive .post .entry-title, .archive .page .entry-title,
.search .post .entry-title, .search .page .entry-title,
.category .post .entry-title, .category .page .entry-title,
.taxonomy .post .entry-title, .taxonomy .page .entry-title,
.author .post .entry-title, .author .page .entry-title
/* you might continue this selectors list for quite a bit and than... */
{display: inline-block;}

Well, I guess I don’t have to tell you that in an environment as flexible as WP that’s more than counter-productive. Much more.
Instead, the right approach is to find a more particular selector for the instances where you want to hide the titles. I understand you want to hide the titles only on single pages and on single posts. If that is correct, you need body.single-post and body.page selectors before your .entry-title. More than that, a good practice to add the id of a structural element of the page, usually a content container/wrapper in the selector. This gives the rule precedence over class-based selectors, no matter how precise they would be. #main-wrapper is perfect for that job. So the final solution would look like this:

body.single-post #main-wrapper h1.entry-title,
body.page #main-wrapper h1.entry-title {display: none;}

The solution above will even allow you to display custom lists of posts or pages (search results, categories, etc) inside single pages or single posts, through the use of plugins or functions) as long as their output doesn’t make the .entry-title a h1 (usually the lists are either a’s or li’s…)

Hope I haven’t been too technical.

Add this code in your child theme’s functions.php, one line above the ending ?>

add_filter('tc_fp_block_diplay', 'maverick_fp_block_display');
function maverick_fp_block_display($output) {
echo preg_replace(
	array( 	'/'.preg_quote('<h2>Home</h2>','/').'/',
		'/'.preg_quote('<h2>Services</h2>','/').'/',
		'/'.preg_quote('<h2>About Sandy</h2>','/').'/'),
	array(	'<h2>You have always been a Maverick</h2>',
		'<h2>Why Mavericks Have an Edge</h2>',
		'<h2>How I help you Go Maverick</h2>'),
	$output, -1);
}

It will replace your current names with the ones you asked. However, if you ever change any of the three page names, they won’t get matched anymore so they won’t get replaced. You’ll need to come to the function and replace the old name with the new one, without touching anything else.

You can put your description text to better use now.

Cheers!

Working solution for your problem here.