jennifer2010

Actually I see that the custom SEO title changed the OG title tag. The problem is it changes both the <title> tag of the page at the same time as the og:title tag — which doesn’t make a whole lot of sense to me.

It’d be nice to change those individually so we have a separate title for facebook and a separate title for search engines.

Ah okay, awesome! Thank you ??

Apparently it’s been reported as a bug and they closed my topic as a duplicate — it’s already been reported. They don’t really seem to be too concerned, because it works for some people.

Are you on NGINX?

I viewed the page source in Chrome and see that it is being generated, but it’s not being displayed on the page (just a blank white page). I went to the post sitemap as well to check and it’s also a blank white page, while the source code does reveal the sitemap data…

That worked like a charm. Thank you for the response!

Resolved:
<?php
echo do_shortcode(‘[ultimatesocial_facebook]’);
?>

C8H10N4O2, thank you for the solution. I don’t know why W3TC wouldn’t include these instructions in the plugin, nor would NewRelic on their site.

@andrew – that doesn’t work. The size of the font stays the same regardless of what unit or measurement is used. I specifically would like the font size to be responsive based on the size of the browser being used.

@esmi, yes.

Thank you for the response, Kyle!

I implemented the above directions but unfortunately the outcome was not that good ??

It looks like this now:
https://img716.imageshack.us/img716/2823/newlb.jpg

Here’s my css code:

.video_callout {
height:150px;
border-top:3px solid;
border-bottom:3px solid;
border-color: #b2b2b2;
}
.callout_text {
width:50%;
text-align:left;
}
.callout_image {
width:100%;
text-align:right;
}
.callout_text span.label {
font-style:italic;
font-size:40px;
color:black;
}
.callout_text span.duration {
color:red;
font-size:40px
}

Any ideas!?

Thanks so much!

UPDATE: I fixed it (for the most part) using float:left on text and float:right on image – thank you!

There’s a “purge” button at MaxCDN I used, I didn’t have to do much really. I found my pull zone, went to cache and hit purge I think. That did the trick.

Right, that probably purged everything from the cache, lol. Anyways, glad it worked for you. There’s also a Purge button in W3TC in the CDN section but you have to enter the path to the file you want purged. Hasn’t been working for me, though MaxCDN’s purge button hasn’t either.

Ah, glad you got it figured out!

James: Thanks for the details. It sounds like MaxCDN serving your old CSS file. When you update your CSS file, you have to “purge” the old version from MaxCDN’s cache. Otherwise, they’ll continue serving the old CSS and you won’t see your changes.

To do this, you’ll need to login to MaxCDN, your site’s pull zone > cache > then enter the location of the file you want to purge and purge it.

However, I seem to have a problem with purging my own CSS. For whatever reason even though I purge it, it’s still caching my old CSS file without any changes. I’ve sent them a support request and am waiting to hear back. It may be unique to me so I’d give it a try on your end anyways.

I know how to look at the source code – but how do you “load” CSS? I’m not sure I follow you here.

If you know the location of your CSS file by heart then just type it in the address bar and “load” the page. Otherwise, I just view my source code then click on the link to my CSS file.

So what I’m saying is you can compare the CSS file on your server to the one being cached by MaxCDN. More than likely the one on MaxCDN doesn’t contain the changes you want. I use a CName with MaxCDN so that cdn.mywebsite.com points to the zone on MaxCDN. If I wanted to compare the css I’d look at mywebsite.com/wp-content/themes/theme/style.css then look at cdn.mywebsite.com/wp-content/themes/theme/style.css

That makes sense now! I was reading a bunch of outdated comments from Frederick citing “The error log lives in: wp-content/w3tc/log/minify.log” so was wondering why it wasn’t there… Thanks for letting me know

Ah you mean those logs. I thought you meant w3tc logs.