tflight

Excellent, thanks! And it looks like the target user is in $args[2].

Yes, thank you! That’s exactly what I couldn’t find. ??

I’ve seen that, but that function doesn’t seem to receive the user being switched to, just the user being switched from ($user). Or am I missing it?

2023-09-07 15:06:41 : SELECT DISTINCT SQL_CALC_FOUND_ROWS wp_posts.* FROM wp_posts INNER JOIN wp_postmeta AS a ON ( a.post_id = wp_posts.ID ) LEFT JOIN wp_postmeta AS b ON ( (( b.post_id = a.post_id )) AND (( b.meta_key LIKE CONCAT( '_', a.meta_key ) )) ) WHERE 1=1 AND ( ( ( b.meta_id IS NOT NULL ) AND ( a.meta_value LIKE '%dark%' ) ) OR ( ( wp_posts.post_title LIKE '%dark%' ) OR ( wp_posts.post_content LIKE '%dark%' ) OR ( wp_posts.post_excerpt LIKE '%dark%' ) ) ) AND ((wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'acf-disabled')) OR (wp_posts.post_type = 'page' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'acf-disabled')) OR (wp_posts.post_type = 'attachment' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'acf-disabled')) OR (wp_posts.post_type = 'product' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'acf-disabled')) OR (wp_posts.post_type = 'alerts' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'acf-disabled')) OR (wp_posts.post_type = 'staff' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'acf-disabled'))) ORDER BY wp_posts.post_title LIKE '{e2ae4afcb0d00f85a894569b16c2fa9550df0cdfdbb31d98cca597c9fb840f32}dark{e2ae4afcb0d00f85a894569b16c2fa9550df0cdfdbb31d98cca597c9fb840f32}' DESC, wp_posts.post_date DESC LIMIT 0, 24

10.5.16-MariaDB – MariaDB Server

#1 – 6963 total, Query took 0.0007 seconds.
#2 – 182499 total, Query took 0.0007 seconds.
#3 – 8010410 total, Query took 0.0007 seconds.
#4 – 182500 total, Query took 0.0563 seconds.
#5 – 6963 total, Query took 0.0012 seconds.
#6 – 6963 total, Query took 0.0962 seconds.
#7 – 8010503 total, Query took 1.8671 seconds.
#8 – 6852 total, Query took 0.0013 seconds.
#9 – 6852 total, Query took 0.1182 seconds.

Hi @abzlevelup,

Version 5.14.1 is installed on that site.

Hi @abzlevelup,

Here is a demo site. Fresh install just now with zero other plugins, default WordPress theme. Steps to reproduce:

1. Visit https://09d146e151.nxcli.net/calendar/ and note the event you can see on April 30.
2. Click on ‘List’ to go to the list view. You will see 8 events listed here, the same number I’ve set in Settings –> General –> ‘Number of events to show per page’. You will now be at https://09d146e151.nxcli.net/calendar/list/ So far so good.
3. Click on ‘Next Events’ to see more events as there are more than 8 upcoming events. You will now be at https://09d146e151.nxcli.net/calendar/list/page/2/ and again, so far so good.
4. Now click on ‘Month’ to go back to the Month view. Here is where things go wrong. You seen a message “There were no results found for this view” but that is incorrect. Recall there is an event on April 30, as seen in step 1. Note you are on a “paged” URL, but shouldn’t be.

Hi @bph ,

Thanks again for your comments. I’m familiar with those filters and use them in themes I develop that are not using Gutenberg. I’m also familiar with how the Classic plugins are basically just a front to those filters.

In my brain I associate those plugins and the corresponding filters as one in the same. So my assumption, perhaps unwarranted, was that if the plugin would no longer be supported that the filters were likely going to be deprecated soon.

A firm statement somewhere that the filter will remain supported for at least x period of time would give me more comfort for myself and my clients that need a more tightly controlled CMS vs a site editing or page builder experience. This week I happen to be working on both.

Hi @jaimemarchwinski ,

I use Redis object caching, but flushing it or disabling it makes no difference. No other plugins are installed.

Hi @jaimemarchwinski ,

Yes, per my initial post I tested this with no other plugins and a default WordPress theme and a dev site.

As for CMS, nothing that you are accustomed to is going away

But WordPress is saying it is going away by dropping support for the Classic Editor and Classic Widgets.

I appreciate your thoughtful response to my post.

WordPress could certainly be both a CMS and a page builder, you are correct. I hope that is the case. But official support for the Classic Editor (and Classic Blocks) was originally supposed to be gone by now. Even with the extension of support until “at least 2022”– we are now in 2022 so support could end tomorrow and the extension fulfilled.

I do have clients looking for a more site/page builder experience, and for them I will (and do) build on the block editor.

However I also have enterprise clients for whom tight controls (separation of presentation and content) is critical. And if support for the Classic Editor disappears tomorrow that would be a major headache.

Without official support of the Classic Editor and Classic Widgets, WordPress appears to be dropping support of the CMS experience.

Hello @matumu !

I have tried both of those steps and neither are making a difference for me. I use ‘Day and name’ for my permalink settings. I changed that and it didn’t make a difference. I also disabled, deleted, and reinstalled the plugin, while the ‘Post name’ permalink settings were in place, and that didn’t make a difference either.

Themes generally don’t auto-update. So either some sort of process is setup specifically to auto update your theme, or someone clicked the update button.

The theme developer being NimbusThemes, not WordPress.

This wasn’t the fault of WordPress, this was the fault of the theme developer who pushed a breaking update.