Jon Schroeder

I’m not sure if progress has been made on any of these fronts, but here are the things I’d most like to see:

• A sensible way of adding meta boxes to posts/pages/CPTs. This is something that should be as simple as adding a custom post type to implement, and it’s far too complex at the moment to simply add a meta box.
• Many-to-many post relationships
• A core method for reordering posts/pages/CTPS. There are several plugins out there that do this well, but this is something that should be part of core. To reorder your CPT, there should be a simple way to enable drag/drop reordering.
• A better, more fine-grained approach to the content width issue. You should be able to set different content widths for different parts of the site, and beyond that, the implementation of this kind of sucks overall

Thanks for everything you do, contributors!

Jers83, there’s been a major update, and a shortcode implementation is complete – so you can put this onto pages now if you’d like. Just wanted to let you know!

Not a particular size, but they do need to be vertical (taller than they are wide) and at least 450 pixels wide by 600 pixels tall. WordPress is great at cropping downward, but it won’t make small photos bigger.

Customizing the size is a feature planned for a future release.

If your images are already large enough, is there anything else I can help with?

This is actually a feature that should be in the next version. Right now, it just works on the /staff page (make sure your permalinks are set to something other than default), but there will be a shortcode implementation to let you put it wherever you’d like in the next version (and options for making the grid something other than a 4 by whatever grid).

Hopefully, that will hit the repo on Monday.

My apologies for the inconvenience (and for the delay in replying).

This issue should be closed, this was fixed. Just wanted to put it out there just in case.

Ah. I screwed it up through the settings. I typoed by php date representation and was getting the wrong value as a result. Apologies! This was on my end.

Oh, the site is right here, BTW, if it’s helpful: https://newworldorchids.com/

Yes, I deactivated all plugins and switched to twentyfourteen and I’m still seeing the wrong dates.

Figured it out. I added one; here’s the code that’s needed (if you drop this into the plugin, then users could have access to it as well:

https://pastebin.com/4XT3uuZH

Much appreciated! I’d like to leave you a review, but if you have a tip jar, I’d be happy to buy you a beer – yours is the best plugin with this sort of functionality I’ve seen.

Thanks, Artprima! Appreciate the dialogue, and I’ll look forward to the update.

Your plugin is being used at vicesdallas.com, though the site isn’t live just yet.

If you’re looking for more suggestions (sorry if you aren’t!), there were a few sections on this site with too much content (a drink menu listing types of Whiskey, for example), where using the editor was simply too cumbersome and/or it didn’t easily support a layout with three or more columns.

It would be wonderful if there were a way to more quickly input large amounts of items. Something like the Bulk content creator plugin, for example – but this particular feature set probably wouldn’t be as necessary or as useful as the post meta boxes from above.

Regardless, I’ll look forward to seeing an update when you get time for it.

Thanks!

Sure, Artprima. I’m basically thinking of a post meta box on the “Add New Menu Item” to select the menu section (or a multiselect box to pick multiple menu sections) where that menu item would automatically be assigned.

It would be even more convenient if, once I added a new menu item and selected the menu section, that menu section would be used as a default for the next menu item added.

Make sense? I almost accomplished this through the Advanced Custom Fields plugin by adding a page link field directly to the add menu item screen (this correctly pulled in the menu sections and allowed me to select one, but did not correctly save the selection).

Might I suggest another possible fix (for the second issue brought up in this thread)?

Matt, the .fade CSS class is set to opacity:0 in twitter bootstrap; perhaps in a future release, you might use a different name (as this is likely to cause problems in quite a number of themes.

The fix is quite easy, but it might save you some grief.

We’re not using any caching, so perhaps we’re experiencing different issues.

I actually got this working by disabling come components of Jetpack. Here’s what I have enabled:

Comments
Subscriptions
Carousel
Tiled Galleries
Sidebar Widgets
Enhanced Distribution

Perhaps that helps narrow it down?