karlo

[karlo]

I bet a free theme it is not 🙂 Try look at that linksalpha embed stuff. Like http://www.linksalpha.com/social/loader_iconbox?link=http%3A%2F%2Fcollege.broomfieldwebette.com%2Finstitutions%2Ffairfield-university%2F&id=663515406 Or in Firefox try click “info” link for the 2 JS errors,

ReferenceError: LOTCC is not defined
ReferenceError: bk_addPageCtx is not defined

leads to a file hosted by linksalpha – which does a LOT of things. In an iframe 🙂 Including loading old jQuery 1.8.3 from Google.

When I checked site 3-4 hours ago “superfish” was not defined and menus were without superfish. Right now they work so I think Linksalphas setup or implementation on your site is a bit shaky. Is a tracking service so what to expect…

What ever it is I think you should use dev. tools in browsers to check because source code does not tell whole story. Is very alive with JS coming in from all angles, may be also in random order/position 😉 If something takes out CF7 and Superfish it cant be good.

[karlo]

Until then and depending on how much you fiddle it might be best to improve bbPress conditional, what I did is not enough. If you disable bbPress, site go poof.

if ( function_exists( 'is_bbpress' ) && is_bbpress() ) {
...stuff...
}

format is better.

And for Jump Start widget areas where you cant use function_exists this seems to nail bbPress

get_post_type() == 'topic' || get_post_type() == 'forum'

If you use double quotes conditional works but when you edit you only see get_post_type() ==, I guess it breaks – may be local issue, I see sample code use double quotes, but single quotes works 100%.

[karlo]

Will be fixed and is an easy one too but wait for Jason to get out of bed. I just got nasty flash backs seeing this issue, then I post.

Tell him to update docs when he is done 😉

[karlo]

Ohhh http://support.themeblvd.com/forums/topic/switching-template-parts-in-search-results/#post-13408 – right under the nose. Well then this is relevant. I vote update docs! Is nifty and important part of Jump Start.

[karlo]

Aha, http://support.themeblvd.com/forums/topic/post-format/ more changes, $part, $type If relevant, remove these posts and spell it out in plain English. Post formats should be pimped more 🙂

[karlo]

From Jump Start 1.1.0 changelog

* New internal functions for working with post formats. — See */framework/includes/post-formats.php* and */framework/includes/media.php*

Is probably it – if this is the problem 🙂

Not mentioned here http://support.themeblvd.com/updating-to-jump-start-1-1/

[karlo]

I am too lazy to find the post but once my post format went crazy as well, was because info on http://dev.themeblvd.com/tutorial/incorporating-post-formats/ had become outdated, and I had to change. Then it worked.

Chunk for post formats is something like this, here locally!

else if ( ! is_404() )  {
		$post_format = '';	// Determine post format where relevant
		if ( is_object( $post ) ) { 
			$post_format = get_post_format();
			if ( $post_format )
				$part = $post_format;
		}
	}

Whole section starts with

global $post;
	if ( is_category ( 'xxxx' ) )
		$part = 'cat-xxxx';

	else if ( in_category ( 'xxxx' ) && is_single() )
		$part = 'single-xxxx';

and so it ends with post format. So not 100% the same as in docs.

Pretty sure you said you had to update docs.

Not sure where ! 404 comes from, debug notice fighting or another plugin causing issues, ignore…

[karlo]

Think I forgot something.

Is this not what Theme Blvd Widget Areas plugin does?

Create, then under “Widget Area Assignments”, set “Custom” to is_search() and it will only show up on search pages.

[karlo]

Can’t you just wrap custom widget code, like from here http://dev.themeblvd.com/tutorial/addremove-widget-area-location/ in is_search() conditional http://codex.wordpress.org/Conditional_Tags#A_Search_Result_Page ? And why not if you can’t? because I think you can.

Only 2 lines added to the function:

if ( is_search() ) {
	echo '<div class="header-right-widget">';
	themeblvd_display_sidebar( 'header_widget' );
	echo '</div>';
}

Or you can wrap entire themeblvd_add_sidebar_location inside another hook, “wp” perhaps. So nothing happens at all unless on a search results page. If you add is_search() like I did it there is sidebar building action going on, except no output unless on a search results page. Not sure what is best, pretty sure it matters very little.

Or what about Widget Logic? Does sidebar not become invisible with no widgets? Widget Logic can take conditionals like is_search() Other plugins have GUI for this, like Dynamic Widgets http://wordpress.org/plugins/dynamic-widgets/

[karlo]

http://support.themeblvd.com/forums/topic/renew-jumpstart-license/ 🙂

I think updating through WordPress admin should be removed. Also for plugins from .org site. All of them. Will teach people to check changelogs, encourage testing or more manual work. Learn from mistakes too. With that comes more knowledge and so everyone wins.

Actually I think even installation through WordPress admin should be removed 🙂 For themes and plugins. Convenience must bend over to info. WordPress does the opposite and that is stupid.

Recurring payments can make sense if hot on payments, or just having a lot of them!, but making it easy to auto-update is different. Tell that to Google, Mozilla and now also WordPress! – but in context of custom sites build on Jump Start, I think mostly a bad idea.

Also if I was dev. I would not say good bye to a way out of this:
Thanks for the update I was highly encouraged to apply, it broke 10 sites of mine. What should I do now???

With auto-update you get idea all WILL be fine, responsibility is not really yours. But it is 😉

[karlo]

Yes no problems. I wonder if they could not increase quality of communication by having a “Dev Journal”? Those make pages are a bit like that but also for discussion. Some will skip! In this case he is laying down the law but if thread become 2 mile long with lots of obvious better suggestions then what would it end up with? Still 100% sure they do not change anything? Journal should not have comments but simply state relevant facts and decisions, no fluff. With no controversy. This about mp6 class should be mentioned/listed. Apparently those involved have zero doubts – those outside can have or at least speculate! May be done on a weekly basis. Should be IRC/TRAC/Twitter chitchat/Make pages for the lazy or for the person who do not like he says, oh I think she is in the UI team and she says.

[karlo]

You better keep eye on this thread by Nacin http://make.wordpress.org/ui/2013/11/19/targeting-the-new-dashboard-design-in-a-post-mp6-world/ I see first comment is a question, heh.

[karlo]

Internet provide generators for many things, also rems https://offroadcode.com/prototypes/rem-calculator/ 🙂

[karlo]

Almost official burial of that class https://twitter.com/Rarst/status/402181651439972353 – as of today.

That class was for targeting a plugin, fin.

She and others in that chitchat are in UI team. Or is it only her? Think 2 of them are in teams at least – so ok to be confused here as well, heh. But fin is fin!

[karlo]

Seems wise. Just because there are auto update feature does not mean everyone will update. Cannot assume much.

Not sure how big an issue it is with Jump Start, I only stumbled over those form elements. Might be bigger deal for other plugins. Especially those who have been creative 🙂 Depends on eyes but I think non-core style will stand out more with MP6 than before. And double that when most come to expect responsive perfection. Random or old CSS code wont magically work well at low res.

[Author]

Replies