Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #165621 > unrolled thread
| Started by | Jiri 'Ghormoon' Novak <ghormoon@gmail.com> |
|---|---|
| First post | 2016-03-19 14:40 +0100 |
| Last post | 2016-03-23 16:40 +0100 |
| Articles | 6 — 4 participants |
Back to article view | Back to linux.debian.user
wordpress from packages - wp-content location not applied? Jiri 'Ghormoon' Novak <ghormoon@gmail.com> - 2016-03-19 14:40 +0100
Re: wordpress from packages - wp-content location not applied? arian <debian@semioptimal.net> - 2016-03-19 19:30 +0100
Re: wordpress from packages - wp-content location not applied? Jiri 'Ghormoon' Novak <ghormoon@gmail.com> - 2016-03-19 20:30 +0100
Re: wordpress from packages - wp-content location not applied? Adam Wilson <moxalt@riseup.net> - 2016-03-20 09:40 +0100
Re: wordpress from packages - wp-content location not applied? Jiri 'Ghormoon' Novak <ghormoon@gmail.com> - 2016-03-23 16:40 +0100
Re: wordpress from packages - wp-content location not applied? Jean-Louis Mas <Jean-Louis.Mas@imag.fr> - 2016-03-23 16:40 +0100
| From | Jiri 'Ghormoon' Novak <ghormoon@gmail.com> |
|---|---|
| Date | 2016-03-19 14:40 +0100 |
| Subject | wordpress from packages - wp-content location not applied? |
| Message-ID | <repgK-sb-5@gated-at.bofh.it> |
Hi,
what may I be missing, if the configuration that came with wordpress
package doesn't apply correctly?
there is: /usr/share/wordpress/wp-config.php:
define('WP_CONTENT_DIR', '/var/lib/wordpress/wp-content');
but that doesn't have any effect unless I define it in
/etc/wordpress/config-www.domain.tld.conf too.
am I missing something essential or may it be a bug?
Thanks,
Gh.
[toc] | [next] | [standalone]
| From | arian <debian@semioptimal.net> |
|---|---|
| Date | 2016-03-19 19:30 +0100 |
| Message-ID | <retNo-3yP-3@gated-at.bofh.it> |
| In reply to | #165621 |
[Multipart message — attachments visible in raw view] — view raw
No idea of wordpress, but
> there is: /usr/share/wordpress/wp-config.php:
> define('WP_CONTENT_DIR', '/var/lib/wordpress/wp-content');
>
> but that doesn't have any effect unless I define it in
> /etc/wordpress/config-www.domain.tld.conf too.
what happens when you define it _only_ in /etc/wordpress?
you should not need to touch stuff in /usr/ for configuration purposes per file hierarchy standard. If that's how it's usually done for wordpress, that's weird. I don't know wether there exists policy for packaging concerning modifying paths, but I'd find it reasonable to change this. However, if debian packages differ from upstream here, that would definitely necessitate documentation.
regards, arian
[toc] | [prev] | [next] | [standalone]
| From | Jiri 'Ghormoon' Novak <ghormoon@gmail.com> |
|---|---|
| Date | 2016-03-19 20:30 +0100 |
| Message-ID | <reuJs-4ca-3@gated-at.bofh.it> |
| In reply to | #165634 |
Hi,
the line in /usr is there by default (in package) and is not applied,
until I copy it to /etc. that's the strange part.
Gh.
arian wrote:
> No idea of wordpress, but
>
>> there is: /usr/share/wordpress/wp-config.php:
>> define('WP_CONTENT_DIR', '/var/lib/wordpress/wp-content');
>>
>> but that doesn't have any effect unless I define it in
>> /etc/wordpress/config-www.domain.tld.conf too.
> what happens when you define it _only_ in /etc/wordpress?
>
> you should not need to touch stuff in /usr/ for configuration purposes per file hierarchy standard. If that's how it's usually done for wordpress, that's weird. I don't know wether there exists policy for packaging concerning modifying paths, but I'd find it reasonable to change this. However, if debian packages differ from upstream here, that would definitely necessitate documentation.
>
> regards, arian
>
[toc] | [prev] | [next] | [standalone]
| From | Adam Wilson <moxalt@riseup.net> |
|---|---|
| Date | 2016-03-20 09:40 +0100 |
| Message-ID | <reH3Y-4h8-9@gated-at.bofh.it> |
| In reply to | #165641 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, 19 Mar 2016 20:27:03 +0100
Jiri 'Ghormoon' Novak <ghormoon@gmail.com> wrote:
> Hi,
>
> the line in /usr is there by default (in package) and is not applied,
> until I copy it to /etc. that's the strange part.
>
> Gh.
>
> arian wrote:
> > No idea of wordpress, but
> >
> >> there is: /usr/share/wordpress/wp-config.php:
> >> define('WP_CONTENT_DIR', '/var/lib/wordpress/wp-content');
> >>
> >> but that doesn't have any effect unless I define it in
> >> /etc/wordpress/config-www.domain.tld.conf too.
> > what happens when you define it _only_ in /etc/wordpress?
> >
> > you should not need to touch stuff in /usr/ for configuration
> > purposes per file hierarchy standard. If that's how it's usually
> > done for wordpress, that's weird. I don't know wether there exists
> > policy for packaging concerning modifying paths, but I'd find it
> > reasonable to change this. However, if debian packages differ from
> > upstream here, that would definitely necessitate documentation.
> >
> > regards, arian
> >
>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
[toc] | [prev] | [next] | [standalone]
| From | Jiri 'Ghormoon' Novak <ghormoon@gmail.com> |
|---|---|
| Date | 2016-03-23 16:40 +0100 |
| Message-ID | <rfT34-5r3-15@gated-at.bofh.it> |
| In reply to | #165621 |
Jean-Louis Mas wrote:
> Le 19/03/2016 14:31, Jiri 'Ghormoon' Novak a écrit :
>
>> what may I be missing, if the configuration that came with wordpress
>> package doesn't apply correctly?
>> there is: /usr/share/wordpress/wp-config.php:
>> define('WP_CONTENT_DIR', '/var/lib/wordpress/wp-content');
>>
>> but that doesn't have any effect unless I define it in
>> /etc/wordpress/config-www.domain.tld.conf too.
>> am I missing something essential or may it be a bug?
> When using Wordpress package from repos in Debian (and Centos also), you
> never edit /usr/share/wordpress/wp-config.php
>
>
> /***
> * WordPress's Debianised default master config file
> * Please do NOT edit and learn how the configuration works in
> * /usr/share/doc/wordpress/README.Debian
> ***/
>
> That's the way linux packaging do. Configs files are in /etc, logs in
> /var/log and so on. So it's perfectly normal
>
> You should instead edit /etc/wordpress/config-www.domain.tld.conf
>
> /etc/wordpress/config-www.domain.tld.conf is the same as the usual
> wp-config.php
>
> If you have multiples Wordpress virtualhosts on your server, you can use
> different Wordpress config files
>
> Regards
>
Hi,
a do NOT edit it. the line is there since beginning, but does not apply.
I have to copy it over to /etc to make the setting take effect. I
thought it should work anyway when it's set in /usr (and not overriden
anyhow in /etc)
Gh.
[toc] | [prev] | [next] | [standalone]
| From | Jean-Louis Mas <Jean-Louis.Mas@imag.fr> |
|---|---|
| Date | 2016-03-23 16:40 +0100 |
| Message-ID | <rfT34-5r3-13@gated-at.bofh.it> |
| In reply to | #165621 |
Le 19/03/2016 14:31, Jiri 'Ghormoon' Novak a écrit :
> what may I be missing, if the configuration that came with wordpress
> package doesn't apply correctly?
> there is: /usr/share/wordpress/wp-config.php:
> define('WP_CONTENT_DIR', '/var/lib/wordpress/wp-content');
>
> but that doesn't have any effect unless I define it in
> /etc/wordpress/config-www.domain.tld.conf too.
> am I missing something essential or may it be a bug?
When using Wordpress package from repos in Debian (and Centos also), you
never edit /usr/share/wordpress/wp-config.php
/***
* WordPress's Debianised default master config file
* Please do NOT edit and learn how the configuration works in
* /usr/share/doc/wordpress/README.Debian
***/
That's the way linux packaging do. Configs files are in /etc, logs in
/var/log and so on. So it's perfectly normal
You should instead edit /etc/wordpress/config-www.domain.tld.conf
/etc/wordpress/config-www.domain.tld.conf is the same as the usual
wp-config.php
If you have multiples Wordpress virtualhosts on your server, you can use
different Wordpress config files
Regards
--
Jean Louis Mas
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web