Deviant Media LLC

@dscp8g Try this:

add_action('admin_menu', 'custom_menu');

function custom_menu() {
    add_menu_page(
        'Page Title',              // The text to be displayed in the title tags of the page when the menu is selected
        'Custom Menu',             // The text to be used for the menu
        'manage_options',          // The capability required for this menu to be displayed to the user
        'custom-menu-slug',        // The slug name to refer to this menu by (should be unique for this menu)
        'custom_menu_page',        // The function to be called to output the content for this page
        'dashicons-welcome-write-blog', // Icon URL
        6                           // Position in the menu order
    );
}

function custom_menu_page() {
    // JavaScript to open the link in a new tab
    echo '<script type="text/javascript">
            window.open("https://www.deviant.media", "_blank");
          </script>';
    // Display a message on the page
    echo '<div class="wrap"><h1>External Link Opened</h1><p>The webpage has been opened in a new window/tab.</p></div>';
}

Here are a few areas to investigate:

1. PHP Configuration Limits: Check your server’s PHP configuration, specifically the post_max_size and memory_limit settings. A post with a large amount of content could exceed these limits, causing the request to fail. You might need to increase these values in your php.ini file.
2. Database Configuration: Large posts could also be hitting limits within your database configuration or the database server’s capacity to handle large inserts. Check your MySQL (or database server) settings, particularly the max_allowed_packet parameter, which might need to be increased.
3. WordPress Configuration: Although unlikely, it’s worth checking if there are any theme or plugin conflicts that might interfere with inserting large posts. Sometimes, plugins or themes can introduce unexpected behavior or limitations.
4. Web Server Configuration: Your web server (e.g., Apache, Nginx) might have configuration limits on the size of the request body. For Apache, this is controlled by the LimitRequestBody directive, and for Nginx, the client_max_body_size directive.
5. Error Logging: Examine WordPress and server error logs for more specific messages regarding the failure. These logs can offer clues that pinpoint the exact issue.
6. Timeout Issues: If the request takes too long to process, it could hit a timeout limit, resulting in an error. This can be addressed by increasing the timeout settings on your web server or PHP configuration.

Since the error message indicates a database insertion issue ("code":"db_insert_error","message":"Could not insert post into the database."), I’d particularly focus on database-related settings and logs to start. If you’ve recently updated WordPress or plugins, ensure compatibility and check for known issues related to post insertions.

You would use gravity for the dropdown and to build out the questions.

Here’s how you can adjust the function to specifically redirect to the “News” category URL when an article belongs to multiple categories but is accessed through a non-“News” category URL:

function redirect_to_news_category() {
    if (is_single() && !is_admin()) {
        global $post;
        // Define the main category slug
        $main_category_slug = 'news';
        // Get current category slug from URL
        $current_cat = get_query_var('category_name');
        
        // Check if the current category is not the main category and the post belongs to the main category
        if ($current_cat && $current_cat !== $main_category_slug) {
            // Check if the post belongs to the main category
            if (has_category($main_category_slug, $post->ID)) {
                // Build the redirect URL
                $redirect_url = site_url() . '/' . $main_category_slug . '/' . $post->post_name;
                wp_redirect($redirect_url, 301); // Permanent redirect to the main category URL
                exit;
            }
        }
    }
}
add_action('template_redirect', 'redirect_to_news_category');

What This Code Does:

• It checks if the current request is for a single post and not within the admin dashboard.
• It defines “news” as the main category slug and checks the current URL for a different category slug.
• If the accessed category is not “news” but the post belongs to the “news” category, it redirects to the URL that uses “news” as the category slug.
• This redirection is done using a 301 HTTP status code, indicating a permanent redirect, which is beneficial for SEO as it passes link equity to the redirected URL.

Deployment:

• Add this code to your theme’s functions.php file or a site-specific plugin.
• Replace 'news' with the actual slug of your main category if it’s different.
• Test this on a staging site first to ensure it works as expected without impacting other functionalities or SEO negatively.

Important Considerations:

• Caching & Performance: If you’re using caching plugins or server-side caching, ensure they’re configured to handle redirects properly to avoid redirect loops or caching the wrong responses.
• SEO Monitoring: After implementing redirects, keep an eye on Google Search Console for any increase in 404 errors or other crawl issues.
• Backup: Always back up your website before making changes to the code.

This custom solution should address your specific requirement to redirect articles accessed through non-main category URLs to the main category URL, consolidating your SEO efforts and reducing duplicate content issues.

Your website loads for me on Firefox if I go to http://ladderlead.unaux.com/ but if you try loading it as a secured connection HTTPS, then it will not load. Do you have an SSL installed?

Your issue with the WordPress block theme not correctly displaying the custom category archive page instead of defaulting to the general archive template could stem from a few reasons. Here are some potential causes and solutions:1. Theme Hierarchy and Naming Convention

WordPress uses a specific template hierarchy to determine which template file to use for different types of content. For category archives, WordPress looks for template files in the following order:

• category-slug.php
• category-id.php
• category.php
• archive.php
• index.php

Ensure your template naming follows WordPress conventions. Since you are working with a block theme and using the Site Editor to create templates, the issue might be less about naming and more about how WordPress is recognizing your template for specific categories.2. Flush Rewrite Rules

Sometimes, WordPress doesn’t recognize new templates or changes to the permalink structure until you flush the rewrite rules. This can be done simply by going to Settings > Permalinks and clicking Save Changes without making any changes. This process rewrites the .htaccess file and refreshes WordPress’s understanding of your site structure.3. Check for Conflicts

Plugin or theme conflicts can cause issues with template loading. Try deactivating all plugins except for those required for your custom post types and taxonomy, and see if the correct template is loaded. If it works, reactivate your plugins one by one to identify the culprit.4. Custom Query in Template

If your category archive template is being selected but not displaying the correct posts, ensure you’re not overwriting the main query with a custom query without properly resetting it afterward. Use the pre_get_posts action hook to modify the main query if needed, rather than creating new queries in the template.5. Inspect the Template Hierarchy

Debugging tools like Query Monitor can help you understand which template files WordPress is trying to load and why it might be falling back to the archive.php or another template. This can give you insight into where the process is breaking down.6. Custom Code for Template Selection

If none of the above solutions work, you might need to use a more manual approach by hooking into the template_include filter to force WordPress to use your custom category archive template under specific conditions. Here’s a basic example:

add_filter( 'template_include', function( $template ) {
    if ( is_category( 'your-category-slug' ) && !is_singular() ) {
        $new_template = locate_template( array( 'your-custom-template.php' ) );
        if ( '' != $new_template ) {
            return $new_template ;
        }
    }

    return $template;
});

Replace 'your-category-slug' with the slug of your category and 'your-custom-template.php' with the path to your custom template file within your theme.Summary

Ensure your custom template is correctly named and recognized by WordPress, flush rewrite rules, check for conflicts, and consider using debugging tools to inspect the template hierarchy. If all else fails, manually force template selection with custom code.

First, make sure your HTML form has the necessary fields and a submit button. For example:

<form id="myForm">
  <label for="name">Name:</label>
  <input type="text" id="name" name="name" required>

  <label for="email">Email:</label>
  <input type="email" id="email" name="email" required>

  <input type="submit" value="Submit">
</form>

Next, you’ll need to create a JavaScript function that will handle the form submission and perform validation. Place this script just before the closing </body> tag in your HTML document:

<script>
  document.getElementById("myForm").addEventListener("submit", function(event) {
    // Prevent the form from submitting automatically
    event.preventDefault();

    // Get the values from the form
    var name = document.getElementById("name").value;
    var email = document.getElementById("email").value;

    // Perform validation
    if (name === "") {
      alert("Please enter your name.");
      return false; // Prevent form submission
    }

    if (!isValidEmail(email)) {
      alert("Please enter a valid email address.");
      return false; // Prevent form submission
    }

    // If all validation passes, you can submit the form
    // You can add additional processing code here

    // For demonstration purposes, let's alert a success message
    alert("Form submitted successfully!");
  });

  // Function to validate email format
  function isValidEmail(email) {
    var emailPattern = /^[a-zA-Z0-9._-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,4}$/;
    return emailPattern.test(email);
  }
</script>

In the above code:

• We use addEventListener to attach a JavaScript function to the form’s submit event.
• Inside the event handler function, we prevent the form from submitting automatically using event.preventDefault().
• We retrieve the values of the name and email fields.
• We perform validation checks:

• Check if the name field is empty.
• Check if the email field matches a valid email pattern using a regular expression (isValidEmail function).

• If any validation check fails, we display an alert message and return false to prevent form submission.
• If all validation checks pass, you can add your custom processing code (e.g., sending data to a server) or simply submit the form.

This code provides basic client-side validation for your form. You can customize it further according to your specific requirements.