Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter Robert Ehrenleitner

    (@robertehrenleitnerplus)

    Sorry, your answer is quite useless. Please read my question more thoroghly. This is a problem which occurs on my local machine only. Nevertheless, I am sysadmin on my local development system, the QA system and the productive system – there is no one else who can do that instead of me.

    Kind regards.

    Thread Starter Robert Ehrenleitner

    (@robertehrenleitnerplus)

    Sorry, I just noticed that this function is not even invoked. I also see that the filter function to robots_txt as implemented in ./app/Common/Traits/Helpers/Vue.php is not triggered – either because the filter is not triggered at all, or the callback is not hooked.

    Furtheron, I noticed that in the WordPress backend, when I go to the AIOSEO settings to the Robots.txt settings, there is a banner that says:

    It looks like you are missing the proper rewrite rules for the robots.txt file. It appears that your server is running on Apache, so the fix should be as simple as checking the correct .htaccess implementation on ww.wp.xz.cn.

    This message only appears on my development environment. Sure, I have the Apache webserver running and I have an .htaccess file, but I wonder what this file is missing if everything else is running fine. This is my .htaccess file:

    # BEGIN WordPress
    # Die Anweisungen (Zeilen) zwischen „BEGIN WordPress“ und „END WordPress“ 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
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /~myuser/wp/
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /~myuser/wp/index.php [L]
    </IfModule>
    
    # END WordPress
    

    Kind regards

    Robert Ehrenleitner

    (@robertehrenleitnerplus)

    In your case, it is also pretty sure that the web server has absolutely nothing to do with it. Most likely, it is due the different PHP environments you use. Note that they can be as different as they can even be different PHP versions, like PHP-CLI 7.4 and PHP-FPM 8.2 or whatever.

    Robert Ehrenleitner

    (@robertehrenleitnerplus)

    Be aware that with mod_php you are effectively using PHP-CLI, not PHP-FPM. These two also load different php.ini files. You may want Apache to use mod_proxy_fpm instead of mod_php. I expect that in this case, the website will stop working with Apache, too. But then, obviously an extension is missing. So, most likely, the two php.ini files differ in loading the LDAP extension.

    Also, beware that Apache loads additional configuration each time the website is loaded by parsing the file .htaccess. Nginx does not care about this file. The only alternative in Nginx is to put the relevant configuration into the virtual host configuration section.

    Robert Ehrenleitner

    (@robertehrenleitnerplus)

    Good morning,

    first of all make sure you are using the right connection string:

    ldap://cn=admin,dc=webd,dc=lan:password@localhost:389/dc=webd,dc=lan

    Note that if you are using TLS-secured LDAP, i.e. LDAPS, you need to change the scheme to ldaps://, and you may adapt the port.

    Also, make sure that the password is URI encoded, so e.g. my?password should be rendered as my%3Fpassword.

    The checkbox “Search LDAP for user’s groups and map to WordPress roles” can be checked to make the plugin map LDAP groups to WordPress roles if they exist. WordPress groups will not be created automatically.

    Kind regards,
    REH

    Thread Starter Robert Ehrenleitner

    (@robertehrenleitnerplus)

    Hi,

    ok, that’s a pity. However, I am looking forward to see this proposal be used to rethink how it could be possible to not load the entire redirects table upon every invocation.

    On the other hand, maybe I could revise the improvement if you tell me why the unit test failed.

    Kind regards.

    Thread Starter Robert Ehrenleitner

    (@robertehrenleitnerplus)

    Thank you.

    there are encrypted versions and unencrypted versions of file transfer

    Yes, this is true, but it is not what the paragraph says. Currently, the paragraph says that SFTP ist encrypted FTP, which is not correct.

    Let’s try to find other words, something like this:

    There are (at least) two common ways of encrypted file transfer, namely by using either FTPS or SFTP.

Viewing 7 replies - 1 through 7 (of 7 total)