Dynamically generating a structure

You’d probably be best off using a custom template for the entire page. Use the usual tab technique of hiding or showing content based on which day was clicked.

You can query for posts which fall within any arbitrary date/time range with the “date_query” arg. To get the posts for any particular day of the week, you’d need to convert the date/time range for that particular day in the user’s timezone into an equivalent GMT date/time range with which you can query posts with.

Hi @bcworkz ,

Thank you very much for the reply.

1. When you suggested custom template for the entire page, what does that mean? I will be having different number of classes on each day. So without having to create custom template for each day, will I be able to generate online classes with just one custom template?
2. And how can I generate that structure for each class recursively (per day)?
3. Also I want to let you know that few classes repeat on multiple days. Few classes on all days. Few classes only once per week.

• This reply was modified 1 year, 11 months ago by sanumolu5.

“Template” has become rather ambiguous. To be clear, I’m referring to a classic theme .php template named according to template hierarchy. If you have a newer block theme, I think this would be more akin to a custom pattern. All days can be generated from this one file. JavaScript and CSS manage which day is visible.

Once you have the user’s timezone offset, your code would determine what GMT date/times span that particular day. strtotime() will convert most textual date strings into a Unix timestamp. Adjust as necessary to get the equivalent GMT date/times. Then you can query for any classes whose times fall within that range. I mentioned “date_query”, but that would be for a post’s published date. If the date/times you need to query for are saved in post meta, you’d be using “meta_query” instead.

Whether such a query will find classes occurring on multiple days depends on how their times are saved. “Every Tuesday and Thursday” doesn’t work well. “2023-05-16 15:00, 2023-05-18 15:00” works better. Each class time as a separate meta field, preferably as a Unix timestamp, would be ideal from a query standpoint, but really any consistently logical scheme can be accommodated since you’re custom coding everything.

This isn’t literally a re-entrant recursive process where a function calls itself, it’s really just a couple of nested loops. Over simplified, but like this:

$days = ['Monday','Wednesday','Friday'];
foreach ( $days as $day ) {
   //query for $classes on $day
   foreach ( $classes as $class ) {
      // output $class
   }
}

The complexity comes from coming up with the correct date/time span for each day, and how that can be used to query for classes within each span.