We use the Intuitive Custom Post Type Order plugin, via a recommended plugin in the TGM Activation. It’s really easy to use with a drag and drop interface. https://wordpress.org/plugins/intuitive-custom-post-order/
Just tried this out, super simple! Integrates so well, thanks!
Thanks all – yeah I actually have a plugin which I created with the theme and wanted to add this functionality to the plugin, but I may take you up on your suggestions.
Sorry for the delay – there’s a lot going on at the moment. I know the situation must be frustrating.
I’ve just gotten back to Gary (Gamajo) with a possible plan for a 2.4.2 release. Hopefully that will make sense. I’ll keep you updated.
Sorry for the brief responses, everyone… I’ll get back to you when I have more news. Thanks.Cheers, Stephen
Totally lost, so what version do we download? Or are we waiting for a release (i.e. v2.4.2)?
Do you know of the best approach to setup custom taxonomy ordering for the end user? I don’t wish to have a plugin dependency, just a little bit of logic that can achieve this.
Would appreciate your advice, thanks.
Perhaps someone that is smarter than me can help me out. For some reason the Customizer works intermittently. More than not all the required settings load up.
But…upon first load, or every say 10 to 15 loads (not always the case), I get the below error:
Uncaught TypeError: Cannot read property ‘load’ of undefined
When this happens the Customizer stall and not settings display. Do you have any idea what the issue could be?
I actually just wrapped this widget with it’s own container, which allowed me to trigger the click event, so all good.
...would like to add, that this is a standard Google embed map that can be added through a text widget, this is not a map from the Google Map API.
You have probably experienced this when you’re scrolling down a web page and then there is an embedded Google map.
Instead of it continuing with the scroll, you hit the map and essentially you start zooming into the map.
As you can imagine, this would be quite annoying from a users standpoint, so I am wondering how I would approach this and put a fix in place where the zooming should only happen if the user actually wants to interact with the map.