[Resolved] Radio buttons not working in the backend (WP-Admin)…

Home Forums Support [Resolved] Radio buttons not working in the backend (WP-Admin)…

Home Forums Support Radio buttons not working in the backend (WP-Admin)…

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #2222378
    Gerhard

    Dear Support,

    Since the update to WP 5.9.3, the radio buttons can no longer be selected in the backend, no matter under which menu item (e.g. /wp-admin/edit.php / e.g. Post / All Post). It is not visible which posts are selected, e.g. to delete or quick edit.

    WordPress 5.9.3
    GeneratePress 3.1.3
    GP Premium: 2.1.2

    Thank you for the information…

    Best regards
    Gerhard

    #2222390
    David
    Staff
    Customer Support

    Hi there,

    have you checked for Plugin Conflicts by temporarily disabling all plugins ?

    #2222409
    Gerhard

    Hi,

    Yes, all plugins were deactivated and the default twentytwentytwo theme switching didn’t help either.

    #2222804
    David
    Staff
    Customer Support

    Are there any errors reported in Dashboard > Tools > Site Health ?

    #2223357
    Gerhard

    Hi,

    Thank you very much, i found the problem.

    If WordPress is secured with .htaccess file and “headers” are set, then WP has the problem that wordpress.org cannot be contacted.

    Sample .htaccess in wordpress root directory:
    […SNIP…]
    <IfModule mod_headers.c>
    Header unset server
    Header unset ETag
    Header set X-Content-Type-Options nosniff
    Header always set X-XSS-Protection “1; mode=block”
    Header always set X-FRAME-OPTIONS “SAMEORIGIN”
    Header always set Strict-Transport-Security “max-age=31536000; includeSubDomains; preload”
    Header always set Permissions-Policy “geolocation=(), microphone=(), payment=()”
    Header set Referrer Policy: strict-origin-when-cross-origin
    >>>>>>> Header set Content-Security-Policy “default-src ‘self’ ‘unsafe-inline’ ‘unsafe-eval'” <<<<<<<<<<
    Header set Connection keep-alive
    Header set Expect-CT “enforce, max-age=21600”
    FileETag None
    </IfModule>
    […SNIP…]

    The following entry must be set in the wp-admin directory, in the .htaccess file:

    <IfModule mod_headers.c>
    Header unset Content-Security-Policy
    </IfModule>

    Then the WP backend works again without any problems, no further changes are required.

    You can close the ticket again, thank you.

    #2223484
    David
    Staff
    Customer Support

    Glad to hear you found the issue!

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.