You can set up your server to protect a directory of your choice and allow access only to the user running apache/nginx/etc. You would have to write something to verify the user’s credentials and then deliver the file or redirect to the proper url. It’s not difficult, but I don’t know of a solution that … Read more
How to Install WP to Subdomain but Serve on Subdirectory?
Can’t do a src to node modules folder
I need advice for creating native WordPress directory site based on native WordPress functionality only
Bedrock WordPress retro-porting to standard WP installation: is this allowed?
“Cannot modify header information – headers already sent by” while using get_stylesheet_directory_uri()
I found the answer server { server_name www.example.com; return 301 $scheme://example.com$request_uri; } server { listen 80; server_name example.com www.example.com; return 301 https://example.com$request_uri; } server { listen 443 ssl; server_name example.com www.example.com; root /www/sites/Yoga-Frontend/dist/Yoga-Frontend; ssl_certificate /etc/ssl/bundle_example.com.crt; ssl_certificate_key /etc/ssl/example.com_private_key.key; location /yoga { index index.php index.html index.htm; try_files $uri $uri/ /yoga/index.php?q=$uri&$args; } location ~ \.php$ { fastcgi_split_path_info ^(/yoga)(/.*)$; … Read more
New user – Create a folder
Anyone who’s editing data would indeed need a WP login, with username and password. Otherwise you’re risking just anyone coming along and editing the information. One approach would be to create a custom role that can edit only their own listing – by this I mean, they can only edit the particular “listing” CPT that … Read more
How to separate an overgrown blog into sub-blogs – without breaking existing inbound links?