Steve Borsch

I rely on Spots so much that, IMHO, I think that widget WYSIWYG should be part of WP core.

Experiencing the same thing as you are, believerinsight and ilanfl, but wondering if either of you are running a caching plugin? I ask since I’m running W3TC and, though it is set to NOT cache admin pages, I just noticed that a critical homepage Spot I added above my slider (900px by 200px) had a HUGE “Edit Spot” that appeared for non-loggedin users!

This is very bad.

Suggestion for Immediate Fix: Spots need to have a DONOTCACHE applied to them.

That worked! Really appreciate the update.

Hmm…did you forget to put black tape over your webcam? ??

Seriously though, scp script would be cool. The issue with rsync are the shifts Dreamhost has made with my VPS OS (one time they “forgot” to upgrade), move to the new datacenter, changes in pathnames and other adventures that have broken my rsync process and it’s just too much work to keep it going.

But the “Holy Grail” of backup is one master good one and incremental backups. I hate to use this metaphor but the “Time Machine” for WordPress (using Apple’s great Time Machine backup which has saved my butt twice already) is what would be awesome.

Thanks for working on this Mika!

Having the same issue (as are many others on the Woocommerce forum) since my site uses Woocommerce pro and the shopping cart gets cached between sessions.

Fragment caching *should* work (so as to not cache the cart dynamic plugin between sessions) but it doesn’t work, regardless .

It would be great if W3 Total Cache had an “This Installation” tab in wp-admin which listed all currently installed plugins, pages and so forth and we could check a box to not cache certain pages and dynamic widgets.

Anyone have a thought?

Alex,

Having *exactly* the same issue after upgrading to WP 3.4 last night on one of my mission-critical sites!

Thumbnails mysteriously vanished on many of my posts and pages (and all galleries are pretty much broken) and regenerating them causes errors to begin at image 204 out of 2000+.

Didn’t change hosting. Didn’t add plugins. Stumped.

Bought the Pro version for a mission-critical site and before launch, turned off all plugins to set it up. Why? In the Admin settings, choosing a new deck ‘should’ popup a selector but instead, it sends me to a second page.

Clearly there is a lightbox conflict. But instead of helping they suggest I copy my production site in to a sandbox environment and selectively disable plugins. Any developer that understands jquery and javascript knows that eyecandy in the admin is superfluous and just adds problems.

Sorry I shelled out $79 since I can’t make new decks without shutting down my site.

Yikes! Now I’m additionally hosed: I unchecked the box and you nuked FLV support in total!

Looks like I’ll have to SPEND MY SATURDAY re-transcoding all the videos from FLV to MOV and uploading them to Vimeo. Dammit.

Hi Alex,

As described in your attention-grabbing upgrade message, I downloaded/unzipped/installed the JW Player in wp-content.

However, I’m still getting the error, “[ERROR: FLV shortcode is disabled until you install JW FLV Player! See the admin area for details.]” and this is on a production site! Shame on me.

What do I do?

~Steve

Should mention that — if you want to keep the Frisco for Buddypress code in this footer.php file — I’m guessing you will have to copy-n-paste that code and place it within here…but I didn’t do that so you will have to experiment to see what works.

Yes. You make a copy of “footer.php” from the Buddypress default theme folder and then place that copy (renamed from “footer copy.php” to “footer.php”, of course) in your Frisco theme folder.

Here is the code I changed so you can look at the differences between the Buddypress default theme code and what I used:

</div> <!-- #container -->

		<?php do_action( 'bp_after_container' ) ?>
		<?php do_action( 'bp_before_footer' ) ?>

		<div id="footer">
			<?php if ( is_active_sidebar( 'first-footer-widget-area' ) || is_active_sidebar( 'second-footer-widget-area' ) || is_active_sidebar( 'third-footer-widget-area' ) || is_active_sidebar( 'fourth-footer-widget-area' ) ) : ?>
				<div id="footer-widgets">
					<?php get_sidebar( 'footer' ) ?>
				</div>
			<?php endif; ?>

			<div id="site-generator" role="contentinfo">
				<?php do_action( 'bp_dtheme_credits' ) ?>
				<p>This website is brought to you by <strong><a href="https://www.yourdomainhere.com">Your Domain Name</a></strong><br />Send Email to <strong><a href="mailto:[email protected]">Your Name</a></strong></p>
			</div>

			<?php do_action( 'bp_footer' ) ?>
		</div><!-- #footer -->

		<?php do_action( 'bp_after_footer' ) ?>

		<?php wp_footer(); ?>

	</body>

</html>

Hello Nikoy — Sorry about the delay in responding.

Of course you should NOT modify the core Frisco-for-Buddypress files, but instead use David Carson’s smart usage of creating our own “functions-custom.php” and “custom.css” files, so any future Frisco updates don’t erase your customizations.

Though I usually modify the actual code with a filter for functions-custom.php for stuff like removing specific functions (e.g., the Buddypress login form), as it turns out the simplest way to do this for a non-coder is to:

a) Create a custom.css file with your text editor

b) Place this CSS in it:

/* remove login form */
#login-text {display: none;}
#sidebar-login-form {display: none;}

c) Save it as custom.css and place that in the frisco-for-buddypress theme folder on your server.

Hope this helps — Steve

P.S. If anyone has a functions-custom.php filter for removing the login that might be a better method for Nikoy, please add that here. Thanks.

Hi cdgregory,

Yes, enable custom.css so you don’t lose this in an update (and be careful you don’t just copy over an entire “frisco for buddypress” updated directory when it comes out!

1) First off the CSS for a logo. I wanted to use most of the 960px width so used this code in my custom.css and also wanted to leave the text logo the same so copied over that too:

#header {
  background: url(images/logo.png) left top no-repeat !important;
	}

#logo {
	float: left;
	margin-bottom: 0;
	margin-top: 0;
	float: left;
        max-width: 950px;
}

#header h1 {
	float: left;
	margin-bottom: 0;
	margin-top: 20px;
	text-align: left;
    max-width: 820px;
}

#header h1 a {
	color: #FFF;
	text-decoration: none;
    font-size: 1em;
    font-weight: 500;
    text-shadow: 0 -1px 0 #052343;
    line-height: 1.2em;
    letter-spacing: .5;
    text-align: left;
    max-width: 820px;
}

2) Play around with these values. As you can see from mine, we’re essentially white to gray to be subtle. But for the gradient, you have three color values (top, middle and bottom or 0%/15%/100% respectively). The code is here for you to ensure that you’ll have a gradient for all “modern” browsers (e.g., Firefox, Chrome/Safari, IE versions, etc.):

#header #search-bar {
    background: #ffffff;
    background: -moz-linear-gradient(top, #ffffff 0%, #ffffff 15%, #e1e1e1 100%); /* FF3.6+ */
    background: -webkit-gradient(linear, left top, left bottom, color-stop(0%,#ffffff), color-stop(15%,#ffffff), color-stop(100%,#e1e1e1)); /* Chrome,Safari4+ */
    background: -webkit-linear-gradient(top, #ffffff 0%,#ffffff 15%,#e1e1e1 100%); /* Chrome10+,Safari5.1+ */
    background: -o-linear-gradient(top, #ffffff 0%,#ffffff 15%,#e1e1e1 100%); /* Opera11.10+ */
    background: -ms-linear-gradient(top, #ffffff 0%, #ffffff 15%,#e1e1e1 100%); /* IE10+ */
    filter: none; /* IE6-9 */
    background: linear-gradient(top, #ffffff 0%,#ffffff 15%,#e1e1e1 100%); /* W3C */
}

Hope this helps — Steve

One word sums up my reaction to the one thing I hadn’t tried and that’s, “Duh!”

Thanks David.

Thanks for the reply David.

“Is there anything in the functions-custom.php file? It will probably need at least the opening php tag or the sky might fall.”

Actually, I copied your functions.php and called it “functions-custom.php” without making any changes (but also I did remove the functions.php file). Was THAT naming the issue? I wonder if your documentation meant to remove yours and replace it with a “custom” one, but that the name should actually remain being called “functions.php”.

“In this instance, sidebar.php is the file you need. Copy it from bp-default into Frisco folder. Then go to line 43-55 and replace with your custom login.”

Actually, I love S2Member’s login widget and the parameters one can toggle on-and-off so I *did* copy-n-move sidebar.php and just removed the hard-coded login form from it so now it just uses the S2Member widget.

Ditto on the problem here (and also had the Visual Editor stop working after the 2.8 upgrade). I isolated it by deactivating all plugins and then turning the on one-by-one (I use about 20) and you’re right hermedia…Social Media Page is the culprit.

Bummer as there are no other 2.8 solutions available yet (other than hand-coding!).