meandron

2) Turned out being a bug that had already been fixed with version 2.1.59 (I had 2.1.58).

Thank you very much Franky for your outstanding support!

Just sent you additional information to your e-dynamics email address.
Of course I will share the solution once we get there :-)!

EDIT:
This is what i get in the “Console” log of my browser after clicking “submit”:

Uncaught ReferenceError: form is not defined
    at Object.<anonymous> (eme.js?ver=2.1.58:293)
    at i (jquery.js?ver=1.12.4-wp:2)
    at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:2)
    at x (jquery.js?ver=1.12.4-wp:4)
    at XMLHttpRequest.c (jquery.js?ver=1.12.4-wp:4)

• This reply was modified 4 years, 10 months ago by meandron.
• This reply was modified 4 years, 10 months ago by meandron.
• This reply was modified 4 years, 10 months ago by meandron.

Thank you for your answer!

Regarding 2):
-> Am I right that after the click on “submit” the page shall scroll up automatically?

What happens after the click is that the submit button gets replaced by a spinning wheel and all the form content is gone. When I manually scroll up, I can see the corresponding message.

Won’t dig any deeper…

Thank you for your answer!

Just as I’m curious: What WP-function / code causes (or caused) the redirect? Then I could investigate further:
I have already checked the DB: There is no “http” anywhere.

Site-Url is:
https://www.cameratavocale.de/wordpress

I thought there must be no trailing “/” – but in this case, it is somehow necessary: Or is the problem caused by the fact, that the side’s base is in the “wordpress” folder, i.e. that it is not typical, as like:
https://www.cameratavocale.de
?

• This reply was modified 4 years, 10 months ago by meandron.
• This reply was modified 4 years, 10 months ago by meandron.
• This reply was modified 4 years, 10 months ago by meandron.
• This reply was modified 4 years, 10 months ago by meandron.
• This reply was modified 4 years, 10 months ago by meandron.

I figured it out by myself:

The original URL was as follows (generated by Kirki):
https://www.cameratavocale.de/wordpress?action=kirki-styles&ver=3.0.45
Note the missing ‘/’ after wordpress!

I “hacked” it in:
class-kirki-modules-css.php/enqueue_styles()
From:
add_query_arg( $args, site_url()),
To:
add_query_arg( $args, site_url() .’/’),

My site URL is as:
https://www.cameratavocale.de/wordpress
should it be:
https://www.cameratavocale.de/wordpress/
?

Or is there an issue with Kirki?

• This reply was modified 4 years, 10 months ago by meandron.
• This reply was modified 4 years, 10 months ago by meandron.
• This reply was modified 4 years, 10 months ago by meandron.

Too blind to see:
A missing slash caused the problem – as answered above.

Correct:
https://www.cameratavocale.de/wordpress/?action=kirki-styles&ver=3.0.45

Mine:
https://www.cameratavocale.de/wordpress?action=kirki-styles&ver=3.0.45

The issue is not the HTTPS redirect I guess but the 301 status code the HTTPS call is resolving to, say to http.

How can I track down what is going on, i.e. why this 301 response code is even created?

Thank you very much for your answer, but I think the problem is more complicated:

The call is done via https, say:
https://www.cameratavocale.de/wordpress?action=kirki-styles&ver=3.0.45
and then gets redirected to http – for whatever reason.

Sorry it’s in German, but I hope the trace will help:

--2020-01-16 01:59:29--  https://www.cameratavocale.de/wordpress?action=kirki-styles&ver=3.0.45
Wiederverwendung der bestehenden Verbindung zu www.cameratavocale.de:443.
HTTP Anforderung gesendet, warte auf Antwort... 301 Moved Permanently
Platz: https://www.cameratavocale.de/wordpress/?action=kirki-styles&ver=3.0.45[folge]
--2020-01-16 01:59:29--  https://www.cameratavocale.de/wordpress/?action=kirki-styles&ver=3.0.45
Verbindungsaufbau zu www.cameratavocale.de|94.130.216.214|:80... verbunden.
HTTP Anforderung gesendet, warte auf Antwort... 200 OK
L?nge: nicht spezifiziert [text/css]
In ?www.cameratavocale.de/wordpress/index.html@action=kirki-styles&ver=3.0.45? speichern.

All other https (resource) calls are resolved fine via https, i.e. return 200 without any redirection.

My htaccess is as (I’m behind a proxy):

# BEGIN WordPress
# Die Anweisungen (Zeilen) zwischen <code>BEGIN WordPress</code> und <code>END WordPress</code> sind
# dynamisch generiert und sollten nur über WordPress-Filter ge?ndert werden.
# Alle ?nderungen an den Anweisungen zwischen diesen Markierungen werden überschrieben.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
RewriteBase /wordpress/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
</IfModule>
# END WordPress

• This reply was modified 4 years, 10 months ago by meandron.
• This reply was modified 4 years, 10 months ago by meandron.
• This reply was modified 4 years, 10 months ago by Jan Dembowski.