.htaccess Wordpress example For future reference it would be nice to include an example for the .htaccess files for wordpress multisites. As wordpress is a super easy, yet powerfull tool just like caddy. I mean, I freaking love caddy, how it magically just works is simply amazing! And I hate it, th…

At the end: This directive is the solution in combination with updating Caddy to the current verision: uri path_regexp (\/{1})(\w|\d|\s)+\/wp- /wp- Thank you guys! :bowing_man: :bowing_man: :bowing_man: The thread can now be closed

One of the links is unfortunatelly pointing to the wrong domain. Here is the correct URL from section #3 Log In ‹ — WordPress I am unfortunately stuck :frowning:

Do you have an existing WordPress multisite installation? Is it already behind an Apache RP? If not and you’re building a new WP installation, do you have a good use case for multisite? Unless you do, multisite is putting all you eggs in one basket. This arises because a common database is used for …

The idea was to automatically generate user sub-websites, like i.e. demo-pages for wp-plugins. For that functionality to work multisite is necessary. I am pretty new to the whole web-development topic, so of course I am thankful for any tips about how to accomplish just a solution without using mu…

[image] Geohound: The idea was to automatically generate user sub-websites, like i.e. demo-pages for wp-plugins. For that functionality to work multisite is necessary. You’re right. Multisite is required for auto-generated sub-websites, however, multisite isn’t required to demo pages for wp-…

Hey Basil, thanks for your input. The key functionality is to auto-generate custom user-websites in subdirectories and wordpress multisite seemed great for the purpose of auto generating websites and the vast ocean of plugins to enable the users to use the features they need. The wordpress single …

[image] Geohound: Honestly, I’d love to take on @Whitestrake on his offer to help and translate the rewrite rules to the caddyfile :smiley: The nginx method here appears to use the nginx map directive and a config file generated by a plugin to determine blog ID from the URI. As far as I can s…

Thanks again for all the kind folk helping me out here! @basil @Whitestrake @francislavoie Looking at the user facing website ( Test Site ) I could see that all ressources (styles, images, etc) were not being found, because wordpress multisite uses for all subsites actually the same ressources. So …

Why won’t uri strip_prefix won’t do what you need? It looks like you just need to strip /demo from the beginning, yeah?

@matt The issue is that this should work for a variety of subdirectories, not just /demo/ but /site/ etc Any ideas? Like so: /demo/wp-.... => /wp-... /site1/wp-... => /wp-... /site2/wp-.. => /wp-... But only for those requests that request ressources from one of the wp- directories, as mentione…

Maybe you can do something like this (would strip any first path segment from the front of the URL): uri path_regexp ^/[a-zA-Z0-9]+/wp- /wp- Basically this would match the beginning of the path (starting with a /) followed by any number of alphanumeric characters (you can adjust this if you have a…

Caddy Community

Caddyfile Wordpress Multisite

Help

show post in topic

Home
Categories
Guidelines
Terms of Service

Powered by Discourse, best viewed with JavaScript enabled