Enhanced Select not working with SSL

Home Forums Quform WordPress Enhanced Select not working with SSL

This topic is: resolved
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #35261
    amplastic
    Participant

    When I view the page with my quform using http:// then it displays the fields with enhanced select correctly. When I view the page with my quform using https:// then it displays the fields with enhanced select as non-enhanced. Is there any way to get enhanced select to work with https ?

    Attachments:
    You must be logged in to view attached files.
    #35263
    amplastic
    Participant

    chatgpt says

    The reason why the Quform plugin’s “enhanced select” feature only works correctly when viewed with HTTP instead of HTTPS could be due to a security feature in modern web browsers called “Mixed Content Blocking”.

    Mixed Content occurs when a webpage served over HTTPS contains resources (such as scripts, images, or stylesheets) that are loaded over an unencrypted HTTP connection. Modern web browsers block these resources by default to protect users from security vulnerabilities, which can lead to the feature not working correctly.

    It’s possible that the Quform plugin’s “enhanced select” feature uses some resources (such as images, stylesheets, or scripts) that are loaded over an unencrypted HTTP connection. When the webpage is served over HTTPS, the browser may be blocking these resources, which is causing the issue.

    To resolve this issue, you should make sure that all resources used by the Quform plugin’s “enhanced select” feature are loaded over an encrypted HTTPS connection. You can check the browser console for errors and warnings related to mixed content to help identify the resources causing the issue. Once you’ve identified the resources causing the issue, update their URLs to use HTTPS instead of HTTP. This should ensure that the feature works correctly even when viewed with HTTPS.

    #35264
    amplastic
    Participant

    I was able to fix this, it had to do with cache

    #35270
    Ally
    Support Staff

    You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.
Be inspired. © 2024 ThemeCatcher Ltd. 20-22 Wenlock Road, London, England, N1 7GU | Company No. 08120384 | Built with React | Privacy Policy