Hi, thanks.
I did mean to report the bug as normal. I thought the "reportbug"
program had modified the field for me.
I am a newbie to Apache admin & wordpress, but a longtime user of
Debian. Considering the comments below about nginx, etc., I'll note
that the wordpress package in the stretch distro I am using is set to
depend on apache2 at the moment, but could be set to have alt.
dependencies in the future. One Debian Package way to handle something
like this would be for distros where Apache2 comes by default with
mod_rewrite not enabled to also include an extra "mod_rewrite_config"
package that, when installed requires/sets the symlink
/etc/apache2/mods-enabled/rewrite.load, then wordpress could be set to
require mod_rewrite_config when it is requiring apache2, and of course,
not, if it was using nginx or some other web server alternative.
Then wordpress, for instance, or other packages could depend on either
apache2.mod-php
On 09/25/2016 12:29 PM, Santiago Vila wrote:
severity 838819 normal
thanks
On Sun, 25 Sep 2016, Josh Stern wrote:
I'm a newbie to apache & wordpress, working with testing out wordpress
in a virtual hosts configuration on my own box. After getting
wordpress up and running, I found that a lot of basic functionality
was not working correctly & it took me a while to track down the
problem. It turns out that many wordpress packages require a
permalinks setup other than the default to function. However,
wordpress's ability to find it's own pages with permalinks other than
the default seems to depend on apache2 having mod_rewrite enabled,
which was not true of the default installation, & seemingly not well
documented by wordpress, either online or on the debian system.
Ideally this info should appear as part of a prominent README and
perhaps be configured by the wordpress package installation. I
understand that mod_rewrite may be considered a minor security risk,
but seemingly one accepts that with the decision to use the wordpress
package.
Hi.
I'm not the maintainer, but WordPress works fine with nginx, which has
nothing to do with Apache, so there is not really a "dependency" on
Apache's mod_rewrite.
I'm downgrading this to normal because it's a documentation bug at most.
(Documentation bugs are usually minor or normal, unless the bug is that
we tell the user to "rm -rf /" as root or things like that).
Maybe the documentation you ask is in
/usr/share/doc/wordpress/examples/apache.conf.
(examples are also considered to be "documentation")
Thanks.
