meanthemes

As soon as I hit that “Post” button I realised that I was an idiot… 2 arrays!

This is the code that works (as per the docs)…

'show_on' => array( 'key' => 'page-template', 'value' => array( 'template-menu.php' , 'template-about.php' ) ),

Thanks again for your amazing work!

Yep, I saw that but I didn’t know what qualified as full access and support as opposed to grab a code snippet for a free plugin on www.ads-software.com repo. It’s no problem, I’ve sent it back to the customer to see their thoughts.

I may well sign up myself though at some stage ??

Thanks for all of your help

Aha, I see you’ve fixed the missing “You need to register” notification – it wasn’t there earlier so that makes much more sense now.

I’ll let my customer know she’ll need to pay to access. If it’s only 1 snippet of code is there a discount of some kind as there is no way she’ll sign up for everything just to get 1 snippet ??

Oh right, you mean register and pay right?

Hi all, ok reading between the lines of what I think hijiri is getting at with the FAQ and some testing this evening, I’ve come to a conclusion.

If in your theme code you are using the following in a query

'orderby' => '' or 'order' = > ''

or both of those, then the new version of Intuitive CPO will take those instead of its own overrides.

Remove both of those from your query and Intuitive CPO should start working again.

If other people can test this and the hijiri can confirm that this is the case then I think we have a solution.

However, it would make sense if there was an option in the iCPO settings that you could switch it back to 2.1.0 behaviour ie. “Override orderby and order queries” checkbox.

There is no heat lol!

The problem I have is that all my customers keep updating the plugin only to find it breaks and then they log a support ticket, then I refer them to the FAQ I made which explains rolling back to 2.1.0, but then they update the plugin again and then I tell them to downgrade again, it goes round and round and round and round and round.

Amplify this by the fact I’ve been recommending this amazing plugin for ages and lots of people are updating the Intuitive CPO plugin only to discover it reorders their website – its getting rather silly on my end.

Sadly since the last update, it is no longer amazing, it has a major flaw but I’m sure it could be amazing again if the code from 2.1.0 was reintegrated.

Hey Olly, no I’m not being aggressive, I’m just trying to use plain English without any surrounding fluff so as not to confuse the situation further.

No offence intended at all, just eager to hear a solution ??

Hi hijiri,

I don’t think you understand. Your functionality has broken since the latest updates. I don’t need an FAQ on overriding, what I need is an answer to why all of the ordering broke since your latest updates, which you confirmed you saw was broken.

Whatever you changed since 2.1.0 has broken something, I’ve got a lot of customers complaining about this at the moment as I’ve recommended your plugin and I’ve sold thousands of themes.

If you cannot resolve the issue, I will have to create my own version of the plugin from your 2.1.0 version and the taxanomy ordering from 3.x

Please provide a sensible update on whether you will be dealing with this issue.

Hi there, it still doesn’t seem to work for me,

Here is the query I am using and I must stress, Intuitive CPO overwrote this just fine in 2.1.0…

$main_query = new WP_Query( array ( 'post_type' => 'meanthemes-homepage', 'posts_per_page' => '9999', 'orderby' => 'date', 'order' => 'asc' ) );

Please can you take another look at your code and compare it to 2.1.0 method?

I can confirm, admin is perfect, front end seems to ignore the query. 2.1.0 worked without issue for me so hopefully its a simple roll back of that part of the code.

Thanks, any ideas on when a fix will be available, already getting people asking me why ordering is broken (I recommend this plugin on a number of my themes).

Thanks, but your plugin does not work out of the box with the standard the_post_thumbnail(‘imagename’) approach, I’d suggest getting it working so the image outputted is the correct crop, not use a background image technique as it’s just doesn’t work well on the responsive designs.

Why is ratio a problem when this CSS can fix stretched images… img { max-width: 100%; height: auto; }

Your method seems pretty restrictive but equally it’s almost there, if it just output what it needed within the img src=”” and did away with the background image stuff.

EDIT: I’ve re-read this now and I see what you are saying, you are saying the image area is a kind of window / placeholder and you are using CSS to mask off the image to the crop… in which case I’m not sure how consistent this plugin will be with all of the crops out there and responsive design. I’ll have a think of a more workable solution as currently we can’t use your plugin as it doesn’t work for us.