bvbaked

If this occurred by activating plugins it looks there there is either an error in the plugin or a conflict.

Your best bet of resolving this would be to contact your hosting provider to see if there is a method of restoring a backup from before you made edits. It is possible to deactivate plugins through WP CLI, so if it is available your host may be able to support that way to deactivate the plugin causing the issue.

This error should be logged, if logging is enabled. That should give you a clue as to the plugin that caused it which you should avoid or raise with the plugin developer

Can you elaborate on what you mean by it doesn’t work? I copied that style and saw the padding added on screens below 769px in width, so it seems to be working for me.

I’m just adding this in browser, so my guess is if you aren’t seeing it your styles are getting added before the theme/plugin that is setting them therefore it is overwriting. A few options to fix this could be:

• Increase your specificity to have them apply
• Use !important in your style (I tend to stay away from this, but it is an option)
• Change the ordering. Doing this would depend on how the styles get added. If it uses the wp_enqueue_style() function, you can add a dependency to ensure it loads after another stylesheet or change the priority of the action to make it run later

Sounds like you just need a spam filter for your site. I’d look into a recaptcha option for your theme or form plugin to get some extra protection on the form submissions.

My guess is that none of these submissions are actual people going to your site to fill out the form, so likely to be coming from bots and that would hopefully get rid of most of them

Since the links looks like they are generating correctly, it is worth trying to reset permalinks by visiting the Permalinks page in the Settings menu.

If permalinks are ever added or modified, the rewrite rules also need to be updated. Visiting that page will do so – no save or other interaction required.

Just doing some in-browser testing, the padding-top is the culprit here. That forces all of the content down since you added the spacing at the top. Changing it to padding-bottom gives you the same effect, but the content is at the top instead.

However, with the images you are using they stack as the image of the script is very wide forcing it across three lines (logo/script/nav)

I think this is a reasonable approach to the problem, and a workable solution as without adjusting the actual block functionality for styles/variations there aren’t specific breakpoint options available for blocks

1. They are important if you plan on making any edits. If you’re using a theme as-is though, no they are not important
2. You do not need them for any site, regardless of size, unless you intend on making an edit to the theme

The benefit that a child theme provides is that you can extend or customize an existing theme while still keeping all of the other functionality of it. If these edits were to be made in the parent theme, then you update it, they would be lost. By using a child theme, you can update the parent and get all the updates, along with keeping your edits to it intact.

If you’re looking at themes that haven’t been updated in a long time, there is a chance they may not be getting one and there is no active maintenance on it. I would recommend staying away from themes like that since there could be vulnerabilities introduced at some point that never get fixed.

As you mentioned, there is a possibility that an update to the parent theme causes a problem with the additions you make in a child theme. The likeliness of that depends on the extent of the changes – adding a CSS file should be fairly unlikely to cause any major problems, but if a class gets changed you may need to rework it slightly to have it apply. If you were to try and write a bunch of custom templates or change existing ones though, you could run into a lot of problems after an update… it all depends

If your additions of the CSS file are not working, I suspect there may just be a problem with how it was done and not because it is added through a child theme.

To get information from a user, there are two possible methods. The first would be to use the WordPress get_user_meta() function since the ACF fields get written into the usermeta table. This is fine for simple meta fields like a text field or select. If it is something more involved, you may want to use the ACF specific functions instead as they offer an extra layer of formatting. In this case you would want to prefix the user id with ‘user_’ which then targets usermeta.

$text = get_user_meta( 1, 'text', true );
$text = get_field( 'text', 'user_1' );

Those would be an example of the two methods for getting the value of a field called ‘text’ from the user with the ID = 1

Sounds like you’d be getting a post ID (or IDs) of a company post type, which you can then modify your query to get the assigned companies only. As @bcworkz mentioned prior, this would need to be added to a pre_get_posts hook on that specific query. You can find/edit the queryId by viewing the code editor view of your page. The block will start something like

<!-- wp:query {"queryId":18, "query": {...} -->

Hope this helps some

Sure, there are a couple of different ways to make them the same.

You could make the videos wider to match the images by removing these lines (that should result in them having width: 100%;)

.port-image > iframe {
    width: auto;
}
body .post_content .port-image > iframe,{
    width: auto;
}

The other option would be to make the images smaller to match the videos by adding the following lines

.port-image {
  height: 150px;
  aspect-ratio: 2 / 1;
  margin-inline: auto;
}