bvbaked

That endpoint is a specific WooCommerce endpoint, so if it were to have changed it would be in the documentation for the plugin and not core WordPress. You may be best to check their documentation to see if anything changed with an update as that is where the response would be formatted

The two files you mentioned are part of the WordPress core API for users and terms, and the updates are focused around the editing process so should not have an impact on the products API endpoints.

Yes, this is very much possible and the agency I work at has hundreds of WordPress sites in Gitlab.

I would strongly recommend using composer to manage it. This provides some hefty benefits, such as not needing to commit all the core WordPress files (which you don’t need in your repo) as well as easily updating the version.

What you’ll do is commit the wp-content directory as these files are unique for you, but manage the rest via composer. This can also allow you to manage plugins, which also offers the same benefits of keeping your repo clean and easy to manage

There are many guides on how to do this, and I don’t have any specific ones I know of and highly recommend, but the knowledge is out there with a fairly easy search.

Just one tip, in case it doesn’t get mentioned – watch your wp-config file! It has particular information you do not want people seeing like database information that might land you in some hot water

Is there a reason you’d like it in the footer instead of the header?

These sorts of items get loaded in the header for very specific reasons, the biggest is so that they load as soon as possible. If you were to load it in the footer, you may be missing specific tracking metrics that fire before the code is loaded making your data incorrect, which kind of defeats the purpose of tracking it in the first place.

Out of respect to their privacy, you may want to remove that video since it does include personal information.

As for the main issue with the login state, it is handled via cookies so there is the slim possibility that something is interfering there such as an ad-blocker. Caching can also come into play where the page is cached in the logged out state and therefore after logging in it still shows them being logged out.

That might explain the intermittent issues

I think the block editor is great, but there are some shortcomings.

One of them is changing configurations across breakpoints. You generally don’t get a lot of flexibility, but stacking is built in via the columns block. Set up your logos as columns in a columns block and check the stack on mobile option. That should take care of the row->columns problem

The right to left is not something I have generally seen supported unless I am missing a feature. I have been able to solve this by using a style variation – in this case you’d create one for the columns block to have the stacking enabled as well.

This does require a bit of knowledge of coding and some way of including a code snip in the theme (PHP and possibly some CSS). This is an article on creating block style variations you can reference, and honestly ChatGPT can probably provide the code snippet for you since this is not an overly difficult ask. Ask it to create a style variation for the columns block that changes the alignment from the end (right) to start (left) on mobile and it’ll probably give you exactly what you need.

To add it to your theme you can use a code snippet plugin that allows for PHP (likely easiest) or edit the theme file yourself if you are comfortable (likely more difficult).

Just be warned that editing theme files opens the possibility of losing your code on an update, so a child theme might be a more future-proof option but adds a little more complexity to this

It might depend on the version you have. I see typography style and colors are available in Pro, but not free.

The best course would be to contact their support, as they’d be able to direct you to your fix and highlight what options are available.

How big is your database and what kind of theme are you running (classic or block)?

The bigger the database, the longer queries will take to run, and the more complex queries will start taking even longer as they have to sort over more and more records. I work at an agency that uses classic themes and ACF page layouts and we’ve had issues with this causing the database to get far too large.

One suggestion would be to check your revisions. These are all saved as a separate post record with all of the post meta as well causing a lot of unnecessary records. Setting a low limit to the number of revisions kept might help to get rid of some of the size which may help speed things up, but it is hard to say.

A much harder route to improve performance would be to review the actual queries themselves and working to optimize them. That would be more relevant if the site was working well and only a few pages or queries are flagged as slow, which I’m not sure is the issue in your case.

You can learn about changing revisions here.

I think it depends on what you’re expecting to do with these sections in the future and what the display is.

I don’t disagree that this could be a separate template, but these sound somewhat reusable as well. For example, you may want to feature those upcoming walks elsewhere on your site as well. In that case, the query block could be created as a pattern for reuse elsewhere. Same with the others.

If your front page is expected to be very different from other pages (not just patterns and blocks, but the entire format) then I say you should use a template. However if it follows most of your other pages but with different content creating a template is not needed and you may be better off creating patterns for the things you reuse and use the standard page template.

In my opinion, templates are best for large scale differences that you either need to stand out or want to reuse.