Jacob Peattie

As you can see from the markup, the viewScript script is deferred, which means that its not loaded immediately, and may not be available yet when the browser parses the onclick attribute.

The solution is not to bind the click event using the onclick attribute. Instead you should bind the event using addEventListener in your script. This means that your script can still work while using the more performant loading method. Additionally, in most cases the onclick attribute will be stripped from your post content entirely for security reasons if a non-Administrator makes a change to the post, as they are usually not allowed to include JavaScript in posts.

The error is not in class-wp-hook.php. The error is caused by using add_action() with a callback that doesn’t exist. The message appears in class-wp-hook.php because that’s where it’s trying to run the callback.

The specific reason you’re seeing this error is that you have an extra space here:

add_action( 'wp_body_open', ' gtm_body_open', 1 );

In front of gtm_body_open. Remove that and the error should go away.

Paragraph spacing is controlled by the padding and margins on each paragraph. In your CSS I can see that your theme is setting a bottom margin of 20px for each paragraph:

.page_content p {
  margin-bottom: 20px;
  line-height: 25px;
}

But then in Additional CSS you’ve added:

.site-main p {
  color: white;
  padding: 19px;
}

Since this adds 19px to the top and bottom you now have a total of 59px between paragraphs.

• This reply was modified 3 years, 5 months ago by Jacob Peattie.

What are the parameters you’re using? Certain parameters are reserved by WordPress and if you add them WordPress is going to try and use them itself to find posts and it will return a 404 if it can’t find any. If you’re using a reserved term the reason adding $ would work is because it’s changing the name of the parameter, eliminating this conflict. A list of reserved terms is available here.

EDIT: In poking around your link I can see that you have registered a post type called “Artist”: https://diamaudix.com/artist/ Since artist has been registered as a post type using it as a parameter will cause WordPress to attempt to find an artist that matches the parameter value. Setting query_var to false or some other value when registering the post type will address the issue.

• This reply was modified 3 years, 9 months ago by Jacob Peattie.
• This reply was modified 3 years, 9 months ago by Jacob Peattie.

I don’t believe you can. This hook allows you to only load CSS for blocks that are in use, but WordPress can’t know what blocks are used on any given page until the page has been rendered, at which point the stylesheets can be only be added to the footer. This is the trade-off.

Without a plugin it’s not going to be possible. The RSS feed generated by WordPress is not a podcast feed and doesn’t include any of the data needed by podcast service to serve your podcast. You’re going to need a plugin or third party service to generate this feed.

You probably can’t encrypt the token. If you did then OKTA would probably receive an invalid token and reject the request. The proper way to encrypt tokens in transit is to ensure you’re using an HTTPS URL for the request.

If you want to avoid exposing the token to the end user in plain text in the browser via the form HTML, then the best solution to that would be to handle the form submission in WordPress on your own server and on the server adding the API tokens before forwarding the submission on to OKTA. The problem is that this solution would typically require coding the form response entirely yourself, rather than using a plugin.

However there are services like Zapier where you could send the form to that service and then using their tools configure the service to send data to the OKTA API. That way you could keep the credentials on Zapier, without exposing them to the user.