Testimonials Shortcode order not working

Hi there,

Just to confirm, on https://theclearevidence.org/testimonial/ the testimonials are showing in the correct order, with the most recent one at the top, correct?

And it appears on https://theclearevidence.org/feedback/, where you used the shortcode, the order is reversed, with the oldest appearing at the top?

If so, that is intentional. The shortcode by default shows testimonials in ascending order from oldest to newest. So the shortcode’s default behaviour differs from the archive page’s behaviour.

To show your testimonials with most recent first, write the shortcode as [testimonials order=DESC]

More info at https://en.support.wordpress.com/testimonials-shortcode/#attributes

Hi @kokkieh

That was my understanding as well before @macmanx suggested the following,

By default, Testimonials are displayed in order by date added, with the most recent first.

Thus I removed order=DESC from the shortcode. Now I have changed the shortcode back to [testimonials columns=2 order=DESC] and it is giving the results I was looking for.

As [testimonials columns=2 order=DESC] was the shortcode I was using when I opened this support topic, thus I checked the history and guess what, I was using [testimonials columns=2 order:DESC] with : instead of =, chk out my first query.

I made this mistake because it is mentioned like “order: “ at https://en.support.wordpress.com/testimonials-shortcode/#attributes and I just copy pasted it without realizing that it should have been changed to order=DESC in the shortcode.

Thanks @lizkarkoski, @macmanx and @kokkieh for your support, it came out to be a silly mistake on my part.

• This reply was modified 6 years ago by urshadow.

I made this mistake because it is mentioned like “order: “ at https://en.support.wordpress.com/testimonials-shortcode/#attributes and I just copy pasted it without realizing that it should have been changed to order=DESC in the shortcode.

I can see how someone could make that error. We’ll see if there’s a way to clarify that in the documentation to avoid future confusion.

Glad we could get it sorted out ??