harryfp

Adding to this – we also use this extension and have opted to update the URLs ourselves as the dev doesn’t seem like they’re going to. Unfortunately we’re getting errors using the extension in “Test” mode after updating, and are in contact with the Opayo support team to figure out what’s wrong.

Hey @matheusfd — no problem at all, I’ve just created a ticket. I was really just hoping to chat with other devs that might have tried the same thing or similar things, as I didn’t necessarily want to clog the support line with questions about extending the plugin.

Looks fixed for me, thanks for the quick work! ??

Just to add here — I’ve just updated this plugin for a client and we’re now seeing the exact same issue:

[Fri Sep 15 16:09:49.482821 2023] [proxy_fcgi:error] [pid 1065:tid 140600024221440] [client 86.13.239.4:0] AH01071: Got error 'PHP message: WordPress database error Unknown column 'wpbdp_is_sticky' in 'order clause' for query \n\t\t\t\t\tSELECT   wp_posts.ID\n\t\t\t\t\tFROM wp_posts \n\t\t\t\t\tWHERE 1=1  AND wp_posts.post_name = 'myspace-property-agent-in-london' AND wp_posts.post_type = 'wpbdp_listing' AND wp_posts.post_status NOT IN ('hidden_property','archived_property') \n\t\t\t\t\t\n\t\t\t\t\tORDER BY wpbdp_is_sticky DESC, wp_posts.post_title ASC\n\t\t\t\t\t\n\t\t\t\t made by require('wp-blog-header.php'), wp, WP->main, WP->query_posts, WP_Query->query, WP_Query->get_posts', referer: [SITE URL]/wp-admin/post.php?post=21631354&action=edit&classic-editor

All of our listings 404 when trying to reach their URLs, and don’t show up in the directory at all. Any ideas how to fix this? It’s pretty urgent.

How can I roll this back?

• This reply was modified 1 year, 5 months ago by harryfp.

Hey guys, I just ran into this issue too. It seems like updating the plugin to 2.8 causes a block of tailwind CSS to be called in, which messes with anything with the “inline” class — including plugin notifications.

I can’t see anything in the changelog for 2.8 either, so I’m just not going to update until this is fixed.

Thanks!

Sorry, ignore this — I’d updated a different plugin that was causing a problem.

Thanks for your hard work on this plugin!