Make WordPress Core

Opened 6 months ago

Closed 6 months ago

Last modified 6 months ago

#60297 closed defect (bug) (invalid)

Editor throws error when wordpress is installed in a subdirectory and permalinks are activated

Reported by: iamklaus's profile iamklaus Owned by:
Milestone: Priority: normal
Severity: major Version: 6.4.2
Component: General Keywords: close
Focuses: ui, administration Cc:

Description

I have wordpress installed in a subdirectory. As soon as I activate permalinks in the wordpress settings, I cannot edit pages anymore. I see a blank page and errors in the console. Everything else works. I can even edit blog posts without any problems. It only occurs editing pages. Here is my url:

https://dachfensterinfo.de/cms/

I use nginx. Here is my config:

upstream wordpress-prod-php-handler {
    server unix:/var/run/php/php8.2-fpm.sock;
}

server {

    server_name dachfensterinfo.de;
    root /var/www/dachfensterinfo.de.django/;

    location /cms {
    
        alias /var/www/dachfensterinfo.de.wordpress/;
    	index index.php;
    	try_files $uri $uri/ /cms/index.php;


gzip on;
gzip_disable "msie6";

gzip_vary on;
gzip_proxied any;
gzip_comp_level 6;
gzip_buffers 16 8k;
gzip_http_version 1.1;
gzip_min_length 256;
gzip_types
  application/atom+xml
  application/geo+json
  application/javascript
  application/x-javascript
  application/json
  application/ld+json
  application/manifest+json
  application/rdf+xml
  application/rss+xml
  application/xhtml+xml
  application/xml
  font/eot
  font/otf
  font/ttf
  image/svg+xml
  text/css
  text/javascript
  text/plain
  text/xml;

    
        location ~* \.php$ {
	    include snippets/fastcgi-php.conf;
       	    fastcgi_param SCRIPT_FILENAME $request_filename;
            fastcgi_pass wordpress-prod-php-handler;
       }

       location ~* .(woff2|ogg|ogv|svg|svgz|eot|otf|woff|mp4|ttf|css|rss|atom|js|jpg|jpeg|gif|png|ico|zip|tgz|gz|rar|bz2|doc|xls|exe|ppt|tar|mid|midi|wav|bmp|rtf)$ {
           expires max;
           log_not_found off;
           access_log off;
       }
    }


    location = / {
	    return 301 $scheme://dachfensterinfo.de/cms;
    }

    location / {
     
    	    proxy_pass http://127.0.0.1:7000/;
    	    proxy_read_timeout 60;
    	    proxy_connect_timeout 60;
    	    proxy_buffering off;
    	    client_max_body_size 100M;
    
    	    proxy_set_header Host $host;
    	    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    	    proxy_set_header X-Real-IP $remote_addr;
    }


    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/dachfensterinfo.de/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/dachfensterinfo.de/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = dachfensterinfo.de) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    listen 80;
    server_name dachfensterinfo.de;
    return 404; # managed by Certbot


}

The errors that I see in the browsers console (Chrome):

react-dom.min.js?ver=18.2.0:10 TypeError: e.substr is not a function
    at p (block-serialization-default-parser.min.js?ver=30ffd7e7e199f10b2a6d:2:1911)
    at f (block-serialization-default-parser.min.js?ver=30ffd7e7e199f10b2a6d:2:1214)
    at i (block-serialization-default-parser.min.js?ver=30ffd7e7e199f10b2a6d:2:759)
    at Xn (blocks.min.js?ver=7204d43123223474471a:10:36346)
    at core-data.min.js?ver=99b262137df116eb6013:2:50646
    at Object.Kt [as useMemo] (react-dom.min.js?ver=18.2.0:10:52029)
    at e.useMemo (react.min.js?ver=18.2.0:10:9875)
    at Un (core-data.min.js?ver=99b262137df116eb6013:2:50600)
    at editor.min.js?ver=3f5791ae786456067a27:12:142712
    at wt (react-dom.min.js?ver=18.2.0:10:47637)
ar @ react-dom.min.js?ver=18.2.0:10
react-dom.min.js?ver=18.2.0:10 Uncaught TypeError: e.substr is not a function
    at p (block-serialization-default-parser.min.js?ver=30ffd7e7e199f10b2a6d:2:1911)
    at f (block-serialization-default-parser.min.js?ver=30ffd7e7e199f10b2a6d:2:1214)
    at i (block-serialization-default-parser.min.js?ver=30ffd7e7e199f10b2a6d:2:759)
    at Xn (blocks.min.js?ver=7204d43123223474471a:10:36346)
    at core-data.min.js?ver=99b262137df116eb6013:2:50646
    at Object.Kt [as useMemo] (react-dom.min.js?ver=18.2.0:10:52029)
    at e.useMemo (react.min.js?ver=18.2.0:10:9875)
    at Un (core-data.min.js?ver=99b262137df116eb6013:2:50600)
    at editor.min.js?ver=3f5791ae786456067a27:12:142712
    at wt (react-dom.min.js?ver=18.2.0:10:47637)

Change History (3)

This ticket was mentioned in Slack in #core-test by hardikgohil. View the logs.


6 months ago

#2 @hardikgohil
6 months ago

  • Keywords close added
  • Resolution set to invalid
  • Status changed from new to closed

Hi @iamklaus, welcome to WordPress Trac. Sorry if you have issues with your site. This tracker is used for the development of the WordPress software and not for assistance with individual sites.

For individual site help, please use the support forums: https://wordpress.org/support/welcome/

#3 @swissspidy
6 months ago

  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.