Hey Marie,

I’m not support, but I was browsing around and what you’re asking is fairly simple, but you will need some rudimentary CSS3 knowledge. The source for the All Blogger Tricks example gives you everything you need.

First thing you need to do is add a custom ID to your color section, for example, calling it “colorchange”. Don’t set a custom background color in order to keep any specificity conflicts out of play.

Next, you need some custom CSS:

#colorchange {
    -webkit-animation: colorBackground 20s infinite;
    animation: colorBackground 20s infinite;
}

@-webkit-keyframes colorBackground {
    0% { background-color: #fbcf61; }
    20% { background-color: #6bd57e; }
    40% { background-color: #ff6f6f; }
    60% { background-color: #57cff4; }
    80% { background-color: #0ed4c8; }
    100% { background-color: #fbcf61; }
}

@keyframes colorBackground {
    0% { background-color: #fbcf61; }
    20% { background-color: #6bd57e; }
    40% { background-color: #ff6f6f; }
    60% { background-color: #57cff4; }
    80% { background-color: #0ed4c8; }
    100% { background-color: #fbcf61; }
}

And that’s it. I think that should be all you need in terms of browser prefixes, too. I’m not sure what your level of knowledge is, but anything with “-webkit” in front of it should be the same as the unprefixed version. You can add keyframes by adding more in-between percentages (e.g. 0%, 10%, 20%, 30%, and so on), but this gives you five colors (first and last keyframes should be the same). You can change them by changing the background-color hex values. Keep in mind this won’t work in IE8 or IE9.

Gradients are currently not animatable with CSS, so you would need a JavaScript solution like the one you linked. In that one, it looks like you have to set the desired colors as RGB values in an array and target a specific div in jQuery, so you need to know how to do that and enqueue the JavaScript for it in WordPress. I don’t have time for that tutorial, but a freelancer could probably set you up in like 10-20 minutes to be honest.

Hi guys,

Nav Menu Roles does not yet work with the public version Enfold. I know because I am pretty sure I’m the guy who helped get support for it (and a few other menu plugins) in the upcoming version. I am guessing staff dev versions are a little ahead of the public version here.

It is easy enough to add this code to line 510 or so of class-megamenu.php until the release:

do_action( 'wp_nav_menu_item_custom_fields', $item_id, $item, $depth, $args );

But, actually, I’m surprised everyone forgot about add_theme_support( 'avia_conditionals_for_mega_menu' ); ;) That should solve it without a plugin.

• This reply was modified 10 years, 4 months ago by mayorninja.

I think the problem is killyman is not using The Events Calendar from Modern Tribe, he’s using Events Manager, as he said in his first post and in the title. I’m not sure about what kind of conditionals are possible with Events Manager, but it looks to me like it uses a custom post type called “event” and it also looks like killyman just embedded a shortcode in a page called “Screenings,” without caring about an event archive or any of that, and wants that as the parent. So, I would propose that the filter should look like this:

add_filter('avf_title_args', 'fix_events_page_title', 10, 2);
function fix_events_page_title($args, $id)
{
	if (is_singular('event'))
	{
		$args['title'] = 'Screenings';
		$args['link'] = get_permalink(get_page_by_title('Screenings'));
	}

	return $args;
}

I’m not even sure if this is a good idea because of potential downsides, but I may have a suggestion to improve the mega menu editing interface. It’s probably one of the least important things possible to worry about, but hey, might as well post it.

I actually think what you have now is really great and very functional, but it’s a little odd from a UX standpoint. You can tell it’s engineered to get around WordPress’ limitations (which is not your fault of course). Check a box to make a mega menu, and suddenly pages or custom links turn into columns. Drag them in a level deeper, and they’re pages and custom links again. Check another box, and now the description is a thing you can use to put custom content in. Not bad, just kind of weird.

Some months ago, a little-known plugin was released called Big Voodoo Mega Menu & Related Links Menu. While it falls flat in its front-end implementation, the back-end is pretty good. Here’s a look at it. Columns and what Enfold calls text blocks are their own separate elements, with their own properties, and I think it works well.

Downsides vs. the current Enfold way are:

• It’s not as easy to link to a page from a column heading (since you can’t just make a page also a column with this method)
• Pages and text blocks can be on the same level as columns, which would be layout chaos
• There’s nothing stopping you from making a column or text block a top level item, which would also be layout chaos.

But maybe there’s a clever way to solve those issues, like still doing the “page becomes a column” thing if a user is absolutely insisting, and a JavaScript check to keep columns inside the second level and text blocks inside the third level (although what do you do about adding them to the menu initially?). And, on the other hand, maybe it’s not a big deal, and users will use the tools as intended.

Anyway, I think it’s more intuitive, but a lot easier to break, so I’m not sure if it’s a useful suggestion. I’ll let you decide.

I’m really liking how well-thought-out the masonry elements were (I’m not surprised Kriesi nailed it yet again though), but they have prompted me to suggest going back and improving some of the older elements at some point soon.

For example, the masonry options include things for activating an overlay or not, displaying the title on hover, gap space between items, etc., and the portfolio element has none of that. Similarly, the content and logo sliders have transition options, options for the type of controls, and a place for a heading, and the post slider does not. Both of those neglected older elements are probably more major and are probably used more than the new ones, but they have hardly been improved since the start. I’d bet anything that you guys are already aware of this, but I personally think it would be best to make everything more coherent sooner rather than later.

It also seems like Kriesi’s aesthetic choices have become noticeably more refined in the past six months or so (the classy look of the masonry layout is on a level above the normal portfolio grid, and they don’t really look like they belong to the same theme), so it might be a good idea to go back and review the design of some older elements with fresh eyes.

Regarding the actual masonry elements, I wonder if it’s really necessary to force them to be full width. I modified things a little, shrunk it down to half width, and it seemed to work okay, except for the fact that the columns got too narrow. But, they could be responsive at the element level with this cool library. It’s not like masonry layouts work without JavaScript anyway.

Also, I think using tags to make a masonry element wider or taller is awkward. Meta box options would be better, because they help make the user aware of the purpose, rather than have them discover the option and how to do it in a modal window and then go back and use a standard WordPress feature for something other than its intended purpose. More importantly, though, because it affects the front end and what a viewer sees. The Enfold demo has “landscape” and “portrait” tags listed in blog posts when they would probably have nothing to do with the content if it was a real site, and it could affect things like tag clouds too.

All in all, I think it would have been better to make masonry layouts an option for the blog and portfolio elements instead of having to choose options from one or the other, but I can think of a few reasons why this would be tricky, so it’s fine. It does look like one unified blog/portfolio/masonry flexible element could work pretty well on the next theme.

Sorry I wrote so much! I’m really verbose and I couldn’t figure out how to cut it down.