Re: WordPress on Debian

[gricketson]

>> Is there perhaps a definitive document that explains how WordPress
>> things are set up in Debian. The /usr/share/wordpress/readme.html 
>> starts off by unpacking the zip file, which tells me that's not the
>> document that describes The Debian Way. There's no "man wordpress" or
>> "info wordpress". The online docs I have found haven't convinced me  
>> that one is more definitive than the conflicting another, and even if
>> it did, doesn't seem to have a good explanation of The Debian Way
>> concerning WordPress.
> 
> /usr/share/doc/wordpress/README.Debian
> 
> The standard location of Debian-specific instructions for a given package.
Maybe this has some information:
https://wiki.debian.org/WordPress

==
Powered with Debian Wheezy
http://www.elchanate.org/ 
.

Re: WordPress on Debian

[Eduardo M KALINOWSKI]

On 19-09-2016 15:29, Kent West wrote:
> Is there perhaps a definitive document that explains how WordPress
> things are set up in Debian. The /usr/share/wordpress/readme.html
> starts off by unpacking the zip file, which tells me that's not the
> document that describes The Debian Way. There's no "man wordpress" or
> "info wordpress". The online docs I have found haven't convinced me
> that one is more definitive than the conflicting another, and even if
> it did, doesn't seem to have a good explanation of The Debian Way
> concerning WordPress.

/usr/share/doc/wordpress/README.Debian

The standard location of Debian-specific instructions for a given package.


-- 
The best you get is an even break.
-- Franklin Adams

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: WordPress on Debian

[Miles Fidelman]

On 9/19/16 3:36 PM, David Wright wrote:


On Mon 19 Sep 2016 at 13:43:04 (-0500), Kent West wrote:

On Mon, Sep 19, 2016 at 1:29 PM, Kent West  wrote:


On Mon, Sep 19, 2016 at 11:53 AM, Tony Baldwin 
wrote:


On 09/19/2016 12:26 PM, Miles Fidelman wrote:


On 9/19/16 12:20 PM, Tony Baldwin wrote:

I make a new user on the server for each new WP site, and then install

their WP in /home/$user/www . much simpler than having bits of it all
over the machine.



So what I'm hearing is that I should forego using apt/aptitude to install
WordPress, and just install in manually?

Neither of those people appear to reveal their update policy or how
they deal with security fixes.



I just use the built in WordPress updater - which takes care of 
everything.  No need to worry about whether some packager has updated 
both the core and every theme and module that I use (guaranteed, they 
haven't).


Now, when it comes to perl based systems, such as the sympa mailing list 
manager (mailman, too for that matter), - better to use cpan to install 
and update all of one's perl system and modules.


As to security fixes - those are far more likely to come from upstream, 
in a timely manner.


Apt is a fantastic package management system, for widely used things, 
that don't change very often.  For anything else, relying on human 
packagers is a recipe for disaster - particularly when dealing with, 
potentially, 3 layers of packaging (the upstream package, an 
intermediate packaging system like cpan, and the Debian repository.)


Miles Fidelman



--
In theory, there is no difference between theory and practice.
In practice, there is.   Yogi Berra

Re: WordPress on Debian

[Ric Moore]

On 09/19/2016 12:11 PM, Kent West wrote:

There's a lot of conflicting documentation out there for installing
WordPress on Debian, so I thought I'd come to you folks, who generally
have a lot of wisdom and knowledge in all things Debian.

This will wind up being more a theoretical discussion than a specific
question of how-to, I'm afraid

Understand I'm pretty much a novice when it comes to Apache2 and
WordPress and MySQL, etc (and to web stuff in general).

It seems that some docs indicate that the WordPress (WP) should put part
of its installation in /srv, and part in /usr/lib, and part in /var/lib,
and part in /var/www, etc.

On a philosophical/theoretical level, I want all my web-facing stuff on
a single partition, preferably /home (as in /home/web), so that visitors
to the site have no ability to tinker on the other partitions. Why would
the HFS recommend that user-accessible files be on system partitions
instead of on "safer" partitions?

Am I thinking wrongly?

I don't really even know enough to ask the right questions, but I'm
hoping this might stir some conversations that lead me to asking the
right question few years vns.


A few years back, I just installed Proxmox to bare metal on a dedicated 
and used turnkeylinux containers. It's a one click install via html 
interface from your desktop browser..

http://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_4.2_.28ISO_Image.29
https://www.turnkeylinux.org/all
Today, Docker gets all the press for doing what Proxmox did years ago. 
Plus, the Proxmox server is built on Debian. Yay! Ric

--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: WordPress on Debian

[Anthony Baldwin]

On 09/19/2016 03:36 PM, David Wright wrote:

On Mon 19 Sep 2016 at 13:43:04 (-0500), Kent West wrote:

On Mon, Sep 19, 2016 at 1:29 PM, Kent West  wrote:


On Mon, Sep 19, 2016 at 11:53 AM, Tony Baldwin 
wrote:


On 09/19/2016 12:26 PM, Miles Fidelman wrote:


On 9/19/16 12:20 PM, Tony Baldwin wrote:

I make a new user on the server for each new WP site, and then install

their WP in /home/$user/www . much simpler than having bits of it all
over the machine.







So what I'm hearing is that I should forego using apt/aptitude to install
WordPress, and just install in manually?


Neither of those people appear to reveal their update policy or how
they deal with security fixes.


I use WP's built in updater once/month to keep those up to date, and 
generally keep the debian installation updated at about the same 
frequency with aptitude. the dokuwikis don't get updates as often but 
when there's an update available. I generally install it asap.

with some of those other things, I routinely pulled from github or wherever.

tony




Oh, I forgot to emphasize my broader question: am I correct in thinking
that pieces of a web server should not be strewn about on the file system,
simply because it conceptually exposes those parts of the file system to
*users*?


No. The Debian packaging system is designed to take care of tracking
where files are installed, and updating, or even removing, them correctly.

The files are "scattered" to their appropriate locations, but not in a
careless manner. Take a look at the (recently updated) FHS at
http://refspecs.linuxfoundation.org/fhs.shtml
to see why that is so. (Don't download the text version; you need the
formatting to make sense of it.)

Cheers,
David.




--
http://www.baldwinlinguas.com
translations, localization,
multilingual web development
EN, ES, FR, PT

Re: WordPress on Debian

[davidson]

On Mon, 19 Sep 2016, Kent West wrote:


On Mon, Sep 19, 2016 at 11:53 AM, Tony Baldwin  wrote:


On 09/19/2016 12:26 PM, Miles Fidelman wrote:


On 9/19/16 12:20 PM, Tony Baldwin wrote:

I have always downloaded the latest from wordpress, created a DB  on

my server and basically manually installed the upstream pkg (which I
know is often discouraged here, but if you do it Our Way (ie. the
Debian Way,
aka the Right Way for most stuff), and then ask any questions on
#wordpress on freenode, they get all nasty (I've been banned from the
channel for life!)
I make a new user on the server for each new WP site, and then install
their WP in /home/$user/www . much simpler than having bits of it all
over the machine.
I do the same with dokuwiki installations and other CMS or site
platforms, too, installing from upstream.



That's what I do as well.  For complex software (e.g., WordPress,
Drupal, mailing list managers), I always end up downloading the latest
tarball, unpacking it, and then ./config; make; make test; make
install.  It all just works so much better than relying on out-of-date
packages.

If I want to get ambitious, and keep track of things via the package
manager, I use checkinstall.

Miles Fidelman




I like stuff in git repos (like hubzilla, gnu/social, etc) or with its own
built-in updating mechanism, like WP has (dokuwiki has a plugin for that)
to facilitate updating stuff.
At home (as opposed to my remote servers) I tend to install only Debian
pkgs, except for OmegaT my most used work application, which always install
from upstream (ours is often 2 years behind the latest),
and I wish they'd put it on github, or gitorious, or similar.



--
http://tonybaldwin.me
all tony, all the time



So what I'm hearing is that I should forego using apt/aptitude to install
WordPress, and just install in manually?

Ag, I hate to go that route; I really like having an apt-maintained system.

Is there perhaps a definitive document that explains how WordPress things
are set up in Debian. The /usr/share/wordpress/readme.html starts off by
unpacking the zip file, which tells me that's not the document that
describes The Debian Way. There's no "man wordpress" or "info wordpress".


I don't know anything about wordpress.

But I do know that when I want documentation about package FOO, one
place worth looking is

 /usr/share/doc/FOO/

(Notice the "doc/" element in the path.)


The online docs I have found haven't convinced me that one is more
definitive than the conflicting another, and even if it did, doesn't seem
to have a good explanation of The Debian Way concerning WordPress.


There is also a debian wiki page, which also has not yet been
mentioned, that AFAICT undertakes to describe two methods of
installation.

 https://wiki.debian.org/WordPress

Good luck with your project.

Re: WordPress on Debian

[David Wright]

On Mon 19 Sep 2016 at 13:43:04 (-0500), Kent West wrote:
> On Mon, Sep 19, 2016 at 1:29 PM, Kent West  wrote:
> 
> > On Mon, Sep 19, 2016 at 11:53 AM, Tony Baldwin 
> > wrote:
> >
> >> On 09/19/2016 12:26 PM, Miles Fidelman wrote:
> >>
> >>> On 9/19/16 12:20 PM, Tony Baldwin wrote:
> >>>
> >>> I make a new user on the server for each new WP site, and then install
>  their WP in /home/$user/www . much simpler than having bits of it all
>  over the machine.
> >>>
> >>>
> 
> >
> > So what I'm hearing is that I should forego using apt/aptitude to install
> > WordPress, and just install in manually?

Neither of those people appear to reveal their update policy or how
they deal with security fixes.

> Oh, I forgot to emphasize my broader question: am I correct in thinking
> that pieces of a web server should not be strewn about on the file system,
> simply because it conceptually exposes those parts of the file system to
> *users*?

No. The Debian packaging system is designed to take care of tracking
where files are installed, and updating, or even removing, them correctly.

The files are "scattered" to their appropriate locations, but not in a
careless manner. Take a look at the (recently updated) FHS at
http://refspecs.linuxfoundation.org/fhs.shtml
to see why that is so. (Don't download the text version; you need the
formatting to make sense of it.)

Cheers,
David.

Re: WordPress on Debian

[Kent West]

On Mon, Sep 19, 2016 at 1:29 PM, Kent West  wrote:

> On Mon, Sep 19, 2016 at 11:53 AM, Tony Baldwin 
> wrote:
>
>> On 09/19/2016 12:26 PM, Miles Fidelman wrote:
>>
>>> On 9/19/16 12:20 PM, Tony Baldwin wrote:
>>>
>>> I make a new user on the server for each new WP site, and then install
 their WP in /home/$user/www . much simpler than having bits of it all
 over the machine.
>>>
>>>

>
> So what I'm hearing is that I should forego using apt/aptitude to install
> WordPress, and just install in manually?
>


Oh, I forgot to emphasize my broader question: am I correct in thinking
that pieces of a web server should not be strewn about on the file system,
simply because it conceptually exposes those parts of the file system to
*users*?

Tony, by "$user" ("/home/$user/www"), do you mean something like
"/home/mywidgetfactory/www" for your web site named "My Widget Factory" and
"/home/nutsandbolts/www" for your web site named "Nuts, Bolts, Screws, and
Banana Peels", both sites being served from the same physical (or virtual)
Debian box?

Does each web site need its own complete WordPress installation? (I would
expect some of the WordPress installation to be on various partitions, such
as "/usr/share" and "/usr/lib", but only those portions that are common to
all the WordPress sites, which are configured by the admin once and then
pretty much left alone, but I would expect site-specific info to be away
from those system partitions, and instead be stored some place like
"/home/$user/www", or in my first-attempted case, in
"/home/web/$site_name".)

Thanks!

-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

Re: WordPress on Debian

[Kent West]

On Mon, Sep 19, 2016 at 11:53 AM, Tony Baldwin  wrote:

> On 09/19/2016 12:26 PM, Miles Fidelman wrote:
>
>> On 9/19/16 12:20 PM, Tony Baldwin wrote:
>>
>> I have always downloaded the latest from wordpress, created a DB  on
>>> my server and basically manually installed the upstream pkg (which I
>>> know is often discouraged here, but if you do it Our Way (ie. the
>>> Debian Way,
>>> aka the Right Way for most stuff), and then ask any questions on
>>> #wordpress on freenode, they get all nasty (I've been banned from the
>>> channel for life!)
>>> I make a new user on the server for each new WP site, and then install
>>> their WP in /home/$user/www . much simpler than having bits of it all
>>> over the machine.
>>> I do the same with dokuwiki installations and other CMS or site
>>> platforms, too, installing from upstream.
>>>
>>>
>> That's what I do as well.  For complex software (e.g., WordPress,
>> Drupal, mailing list managers), I always end up downloading the latest
>> tarball, unpacking it, and then ./config; make; make test; make
>> install.  It all just works so much better than relying on out-of-date
>> packages.
>>
>> If I want to get ambitious, and keep track of things via the package
>> manager, I use checkinstall.
>>
>> Miles Fidelman
>>
>>
>>
> I like stuff in git repos (like hubzilla, gnu/social, etc) or with its own
> built-in updating mechanism, like WP has (dokuwiki has a plugin for that)
> to facilitate updating stuff.
> At home (as opposed to my remote servers) I tend to install only Debian
> pkgs, except for OmegaT my most used work application, which always install
> from upstream (ours is often 2 years behind the latest),
> and I wish they'd put it on github, or gitorious, or similar.
>
>
>
> --
> http://tonybaldwin.me
> all tony, all the time
>
>
So what I'm hearing is that I should forego using apt/aptitude to install
WordPress, and just install in manually?

Ag, I hate to go that route; I really like having an apt-maintained system.

Is there perhaps a definitive document that explains how WordPress things
are set up in Debian. The /usr/share/wordpress/readme.html starts off by
unpacking the zip file, which tells me that's not the document that
describes The Debian Way. There's no "man wordpress" or "info wordpress".
The online docs I have found haven't convinced me that one is more
definitive than the conflicting another, and even if it did, doesn't seem
to have a good explanation of The Debian Way concerning WordPress.

Thanks!


-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

Re: WordPress on Debian

[Tony Baldwin]

On 09/19/2016 12:26 PM, Miles Fidelman wrote:

On 9/19/16 12:20 PM, Tony Baldwin wrote:


I have always downloaded the latest from wordpress, created a DB  on
my server and basically manually installed the upstream pkg (which I
know is often discouraged here, but if you do it Our Way (ie. the
Debian Way,
aka the Right Way for most stuff), and then ask any questions on
#wordpress on freenode, they get all nasty (I've been banned from the
channel for life!)
I make a new user on the server for each new WP site, and then install
their WP in /home/$user/www . much simpler than having bits of it all
over the machine.
I do the same with dokuwiki installations and other CMS or site
platforms, too, installing from upstream.



That's what I do as well.  For complex software (e.g., WordPress,
Drupal, mailing list managers), I always end up downloading the latest
tarball, unpacking it, and then ./config; make; make test; make
install.  It all just works so much better than relying on out-of-date
packages.

If I want to get ambitious, and keep track of things via the package
manager, I use checkinstall.

Miles Fidelman




I like stuff in git repos (like hubzilla, gnu/social, etc) or with its 
own built-in updating mechanism, like WP has (dokuwiki has a plugin for 
that) to facilitate updating stuff.
At home (as opposed to my remote servers) I tend to install only Debian 
pkgs, except for OmegaT my most used work application, which always 
install from upstream (ours is often 2 years behind the latest),

and I wish they'd put it on github, or gitorious, or similar.


--
http://tonybaldwin.me
all tony, all the time

Re: WordPress on Debian

[Miles Fidelman]

On 9/19/16 12:20 PM, Tony Baldwin wrote:

I have always downloaded the latest from wordpress, created a DB  on 
my server and basically manually installed the upstream pkg (which I 
know is often discouraged here, but if you do it Our Way (ie. the 
Debian Way,
aka the Right Way for most stuff), and then ask any questions on 
#wordpress on freenode, they get all nasty (I've been banned from the 
channel for life!)
I make a new user on the server for each new WP site, and then install 
their WP in /home/$user/www . much simpler than having bits of it all 
over the machine.
I do the same with dokuwiki installations and other CMS or site 
platforms, too, installing from upstream.




That's what I do as well.  For complex software (e.g., WordPress, 
Drupal, mailing list managers), I always end up downloading the latest 
tarball, unpacking it, and then ./config; make; make test; make 
install.  It all just works so much better than relying on out-of-date 
packages.


If I want to get ambitious, and keep track of things via the package 
manager, I use checkinstall.


Miles Fidelman


--
In theory, there is no difference between theory and practice.
In practice, there is.   Yogi Berra

Re: WordPress on Debian

[Tony Baldwin]

I have always downloaded the latest from wordpress, created a DB  on my 
server and basically manually installed the upstream pkg (which I know 
is often discouraged here, but if you do it Our Way (ie. the Debian Way,
aka the Right Way for most stuff), and then ask any questions on 
#wordpress on freenode, they get all nasty (I've been banned from the 
channel for life!)
I make a new user on the server for each new WP site, and then install 
their WP in /home/$user/www . much simpler than having bits of it all 
over the machine.
I do the same with dokuwiki installations and other CMS or site 
platforms, too, installing from upstream.


tony
http://tonybaldwin.me
all tony, all the time

On 09/19/2016 12:11 PM, Kent West wrote:

There's a lot of conflicting documentation out there for installing
WordPress on Debian, so I thought I'd come to you folks, who generally
have a lot of wisdom and knowledge in all things Debian.

This will wind up being more a theoretical discussion than a specific
question of how-to, I'm afraid

Understand I'm pretty much a novice when it comes to Apache2 and
WordPress and MySQL, etc (and to web stuff in general).

It seems that some docs indicate that the WordPress (WP) should put part
of its installation in /srv, and part in /usr/lib, and part in /var/lib,
and part in /var/www, etc.

On a philosophical/theoretical level, I want all my web-facing stuff on
a single partition, preferably /home (as in /home/web), so that visitors
to the site have no ability to tinker on the other partitions. Why would
the HFS recommend that user-accessible files be on system partitions
instead of on "safer" partitions?

Am I thinking wrongly?

I don't really even know enough to ask the right questions, but I'm
hoping this might stir some conversations that lead me to asking the
right questions. When I try to put my WP stuff on /home/web, I get
confused about what goes where (because of the conflicting
documentation, and not knowing what the various parts of
Apaceh2/WP/mysql do),, and I get varying levels of success (but mostly
failure) depending on what I try.

Thanks for any insight!

--
Kent West <*)))><
http://kentwest.blogspot.com
Praise Yah! \o/




--
http://tonybaldwin.me
all tony, all the time

Re: Wordpress sites overzetten

[Paul van der Vlis]

Op 18-08-16 om 20:07 schreef Paul van der Vlis:
> Weet iemand misschien een manier om er achter te komen of er in een
> database van dergelijke "serialised data" zit?

Je herkent het volgens mij aan dit soort onderdelen in de SQL:
;s:33:"our-team-enhanced/sc_our_team.php";

Die "s" betekend "serialized", die "33" zegt dat de string 33 tekens
lang is. Volgens mij zit het in elke Wordpress site, zal wel sneller zijn.

Groet,
Paul.


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: wordpress from packages - wp-content location not applied?

[Jiri 'Ghormoon' Novak]

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.

Re: wordpress from packages - wp-content location not applied?

[Jean-Louis Mas]

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

Re: wordpress from packages - wp-content location not applied?

[Adam Wilson]

On Sat, 19 Mar 2016 20:27:03 +0100
Jiri 'Ghormoon' Novak  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?


pgpXt2PsjRNAY.pgp
Description: OpenPGP digital signature

Re: wordpress from packages - wp-content location not applied?

[Jiri 'Ghormoon' Novak]

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
>

Re: wordpress from packages - wp-content location not applied?

[arian]

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



signature.asc
Description: OpenPGP digital signature

Re: wordpress, again

[Rick Thomas]

On Nov 27, 2013, at 11:52 PM, Scott Ferguson 
scott.ferguson.debian.u...@gmail.com wrote:

 On 28/11/13 18:31, Rick Thomas wrote:
 
 On Nov 27, 2013, at 8:12 PM, Miles Fidelman
 mfidel...@meetinghouse.net wrote:
 
 Scott Ferguson wrote:
 The OP (in this thread) is asking about the Debian WordPress
 package. It installs WordPress, WordPress keeps itself up-to-date
 - i.e. it's version has nothing to do with the version number of
 the debian installer. On 28/11/13 09:48, Scott Ferguson wrote:
 
 
 snipped
 
 Miles Fidelman
 
 Thanks, Miles.
 
 I'll keep your advice in mind as I go forward with this project.
 
 Your suggestion raises the question, though, of what do I do when I
 want to upgrade from Wheezy to Jessie in a year or so?  Will I get a
 toxic mix of Debian-wordpress and wordpress-upstream?
 
 
 NO!
 
 Ignore the speculation, well intended though it is.
 The debian installer does *not* mean you run an out-dated version of
 WordPress - it immediately upgrades to the current version of WordPress
 (and all your themes and extensions).  When you first login the
 Dashboard shows updates available - click on the icon and you'll soon be
 running the freshly baked latest WordPress which is downloaded from the
 WordPress site.
 
 Upgrading Wheezy to the Jessie when it becomes stable, or indeed,
 upgrading to Testing or Unstable tomorrow won't affect the Debian
 installed WordPress - it will continue to be the most current version
 available from upstream.  This is one of the reasons why it's better to
 use the Debian installed WordPress than downloading the tarball and
 dumping it somewhere.
 
 All the package does is install WordPress into the Debian standard
 locations. WordPress then manages it's own updates.

Good to know.  Though I must admit, it sounds like magic.  I look forward to 
finding out how it's done!

Rick



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e271a765-f504-43b1-acc5-1e5bb4e14...@pobox.com

Re: wordpress, again

[Jerry Stuckle]

On 11/28/2013 2:31 AM, Rick Thomas wrote:



And, for what it's worth, when it comes to all but the most core servers (say 
mysql, apache, postfix), I've found that it always pays to build servers from 
upstream source (particularly mail related stuff - getting antispam, antivirus, 
SMTP, IMAP, and authentication all wired together is a mess; same again for 
list managers).  At least that's been my experience when it comes to running a 
server farm - your mileage may vary.

Miles Fidelman


Thanks, Miles.

I'll keep your advice in mind as I go forward with this project.

Your suggestion raises the question, though, of what do I do when I want to 
upgrade from Wheezy to Jessie in a year or so?  Will I get a toxic mix of 
Debian-wordpress and wordpress-upstream?

In other words, am I stuck on Wheezy until I'm willing to do a complete 
re-install of wordpress from scratch?

Thanks!
Rick



I'm just the opposite.  I need stable servers, which is why I use 
Debian.  If I wanted the latest and greatest, I would go to Ubuntu or 
some other distro.  But I know the stable version of Debian is exactly 
that.  It's done well for me for years, and is a lot more stable than 
the Unix I was running some 20 years ago.


Jerry


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/52972423.60...@attglobal.net

Re: wordpress, again

[Tom H]

On Thu, Nov 28, 2013 at 11:08 AM, Jerry Stuckle jstuc...@attglobal.net wrote:

 I'm just the opposite. I need stable servers, which is why I use Debian.
 If I wanted the latest and greatest, I would go to Ubuntu or some other
 distro.

RHEL and its clones, SUSE, and Ubuntu LTS are just as stable as Debian
so you must have at least one additional reason for using Debian.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=Syga8pexjjPaxdrnBEMn+=N=orBYbS7=unjxhxp09h...@mail.gmail.com

Re: wordpress, again

[Chris Davies]

Chris Davies writes:
 Last time I looked, the wordpress package was a point or two behind
 the current version. Many of these point releases seem to be to fix
 security issues, so I have to question the wisdom of using an older
 version for a potentially Internet-facing server.

John Hasler jhas...@newsguy.com wrote:
 Debian backports security fixes to Stable.  That's why they have a
 security team and it's what they mean when they say that Stable is
 supported.

Duh (smacks head). You are completely correct, and indeed the superb
actions of the Security team are one of the reasons I use Debian Stable
on my production servers. Apologies for misleading (and also to the
Security team).

Cheers,
Chris


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/ts8kmaxbh9@news.roaima.co.uk

Re: wordpress, again

[Chris Davies]

Rick Thomas rbtho...@pobox.com wrote:
 Would you be willing to help me get a wordpress installation up and running?

 I've done aptitude install wordpress which dragged in all the
 necessary other packages, like apache2, mysql, php… etc.  So I *think*
 I've got all the tools I'll need.

Last time I looked, the wordpress package was a point or two behind
the current version. Many of these point releases seem to be to fix
security issues, so I have to question the wisdom of using an older
version for a potentially Internet-facing server.

I ended up using the Debian package as a starting point (it pulled in the
dependencies, gave me a really nice multi-site configuration capability
in /etc/wordpress) but then replacing the guts of it with the latest
tarball from wordpress.org itself.

Chris


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/cd4hmax6qi@news.roaima.co.uk

Re: wordpress, again

[John Hasler]

Chris Davies writes:
 Last time I looked, the wordpress package was a point or two behind
 the current version. Many of these point releases seem to be to fix
 security issues, so I have to question the wisdom of using an older
 version for a potentially Internet-facing server.

Debian backports security fixes to Stable.  That's why they have a
security team and it's what they mean when they say that Stable is
supported.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87r4a1x6ic@thumper.dhh.gt.org

Re: wordpress, again

[Miles Fidelman]

John Hasler wrote:

Chris Davies writes:

Last time I looked, the wordpress package was a point or two behind
the current version. Many of these point releases seem to be to fix
security issues, so I have to question the wisdom of using an older
version for a potentially Internet-facing server.

Debian backports security fixes to Stable.  That's why they have a
security team and it's what they mean when they say that Stable is
supported.
 That's kind of besides the point in this case.  Wordpress has a pretty 
sophisticated mechanism for updating both itself, and installed modules, 
directly from upstream.


Miles Fidelman


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/52961d93.2000...@meetinghouse.net

Re: wordpress, again

[John Hasler]

I wrote:
 Debian backports security fixes to Stable.  That's why they have a
 security team and it's what they mean when they say that Stable is
 supported.
 
Miles Fidelman writes:
 That's kind of besides the point in this case.  Wordpress has a pretty
 sophisticated mechanism for updating both itself, and installed
 modules, directly from upstream.

Ok, but I think it is important to emphasize that using Debian/Stable
does *not* mean that you are stuck with unfixed security bugs.  You get
the best of both worlds: stable interfaces and functionality and
up-to-date security.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87mwkpwytf@thumper.dhh.gt.org

Re: wordpress, again

[Scott Ferguson]

On 27/11/13 23:16, Chris Davies wrote:
 Rick Thomas rbtho...@pobox.com wrote:
 Would you be willing to help me get a wordpress installation up and running?
 
 I've done aptitude install wordpress which dragged in all the
 necessary other packages, like apache2, mysql, php… etc.  So I *think*
 I've got all the tools I'll need.
 
 Last time I looked, the wordpress package was a point or two behind
 the current version. 

Huh?
Where did you look?

The wordpress package installs WordPress.
WordPress updates independant of Debian packagers. Likewise themes and
extensions.


 Many of these point releases seem to be to fix
 security issues, so I have to question the wisdom of using an older
 version for a potentially Internet-facing server.
 
 I ended up using the Debian package as a starting point (it pulled in the
 dependencies, gave me a really nice multi-site configuration capability
 in /etc/wordpress) but then replacing the guts of it with the latest
 tarball from wordpress.org itself.


Please file a bug report with upstream (WordPress) if, after having
reviewed instructions on how to upgrade WordPress (Dashboard - click on
the icon showing 2, being the number of updates - 1 for WordPress and
the other for the Akismet extension).

In my experience the Wheezy Debian package install WordPress 3.6.1 which
then upgrades to the current latest stable WordPress 3.7.1

 
 Chris
 
 


Kind regards.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52966dd0.8050...@gmail.com

Re: wordpress, again

[Scott Ferguson]

On 28/11/13 03:28, Miles Fidelman wrote:
 John Hasler wrote:
 Chris Davies writes:
 Last time I looked, the wordpress package was a point or two behind
 the current version. Many of these point releases seem to be to fix
 security issues, so I have to question the wisdom of using an older
 version for a potentially Internet-facing server.
 Debian backports security fixes to Stable.  That's why they have a
 security team and it's what they mean when they say that Stable is
 supported.
  That's kind of besides the point in this case.  Wordpress has a pretty
 sophisticated mechanism for updating both itself, and installed modules,
 directly from upstream.
 
 Miles Fidelman
 
 

Thankyou. You are correct.
And I'm sure the packagers, Giuseppe Iuculano and Raphaël Hertzog, thank
you also.

Kind regards.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52966ec1.5090...@gmail.com

Re: wordpress, again

[Scott Ferguson]

On 28/11/13 01:29, John Hasler wrote:
 Chris Davies writes:
 Last time I looked, the wordpress package was a point or two behind
 the current version. Many of these point releases seem to be to fix
 security issues, so I have to question the wisdom of using an older
 version for a potentially Internet-facing server.
 
 Debian backports security fixes to Stable.  That's why they have a
 security team and it's what they mean when they say that Stable is
 supported.
 

Yes. And NO.
The installer is Stable. What it installs, WordPress, maintains it's own
upgrades.

It would have been helpful to preface your post with I'm guessing...


Kind regards.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52966f41.80...@gmail.com

Re: wordpress, again

[John Hasler]

Scott Ferguson  
 It would have been helpful to preface your post with I'm guessing...

Why?  What I wrote is true.  The Debian Wordpress package happens to be
an installer package created by the Debian Wordpress maintainers, but
what I wrote applies to it as it does to all Debian packages.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87eh61wjz1@thumper.dhh.gt.org

Re: wordpress, again

[Scott Ferguson]

On 28/11/13 09:36, John Hasler wrote:
 Scott Ferguson  
 It would have been helpful to preface your post with I'm guessing...

Let me rephrase that...
It would have been helpful to preface your post with Nothing to do with
the OPs question, this is on a completely different tangent...

 
 Why?  What I wrote is true.  The Debian Wordpress package happens to be
 an installer package created by the Debian Wordpress maintainers, but
 what I wrote applies to it as it does to all Debian packages.

At best it's ambiguous as it doesn't clarify the difference between the
installer and what is installed. Notice that the OP has no interest in
the version of the installer (because it's irrelevant). Out on a limb much?

 

The OP asks for help installing WordPress using the Debian package.
Chris (and others) suggest not using it because it's out of date (which
is not true).

 Chris Davies writes:
 Last time I looked, the wordpress package was a point or two behind
 the current version. Many of these point releases seem to be to fix
 security issues, so I have to question the wisdom of using an older
 version for a potentially Internet-facing server.
 

You write:-

 Debian backports security fixes to Stable.  That's why they have a
 security team and it's what they mean when they say that Stable is
 supported.


Which has what to do with the currency of WordPress?  Ambiguous?
Deceptive? Off on a tangent? Part of an unrelated thread?

Backports? Where did that come from?
Who said anything about Stable?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/529676cf.8040...@gmail.com

Re: wordpress, again

[Scott Ferguson]

Please accept my apologies John, after giving your original post the
consideration it deserves I should have said:-

Huh?
What 'are' you talking about? Stable? Backports?
I suspect you confused this with another thread about a totally
different thing (blame AP who doesn't understand threads):-

Different thread*
Re: A rookie's query: Want to about Debian and the related
On Wed, Nov 27, 2013 at 4:38 PM, Chris Bannister
cbannis...@slingshot.co.nz wrote:

 Yep, that's pretty much on the nail! Although, it is around three years
 on average, as the testing distribution becomes the new stable.

 Of course, there is backports, but some would argue that then, by
 definition, you are no longer running a stable system.

*End quote from unrelated thread*



The OP (in this thread) is asking about the Debian WordPress package. It
installs WordPress, WordPress keeps itself up-to-date - i.e. it's
version has nothing to do with the version number of the debian installer.



On 28/11/13 09:48, Scott Ferguson wrote:
 
 
 On 28/11/13 09:36, John Hasler wrote:
 Scott Ferguson  
 It would have been helpful to preface your post with I'm guessing...
 
 Let me rephrase that...
 It would have been helpful to preface your post with Nothing to do with
 the OPs question, this is on a completely different tangent...
 
snipped


Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5296843f.4090...@gmail.com

Re: wordpress, again

[Miles Fidelman]

Scott Ferguson wrote:
The OP (in this thread) is asking about the Debian WordPress package. 
It installs WordPress, WordPress keeps itself up-to-date - i.e. it's 
version has nothing to do with the version number of the debian 
installer. On 28/11/13 09:48, Scott Ferguson wrote:


Which is really the point here.

1. Maybe an apt-get install wordpress-xxx will get you a close to 
current version, complete with all dependencies (hasn't been my 
experience - but then again I haven't tried going that route in a LONG 
time - sounds like things have gotten better).


But, and a BIG but - and probably important to the OP:

2. apt-get update; apt-get upgrade is not going to be enough to keep 
your wordpress installation up-to-date - for that, you pretty much have 
to use WordPress' built in update mechanism - accessed through it's 
control panel - which takes into account how you've customized your 
installation (modules, themes).  In fact, I wouldn't be surprised if 
apt-get update/upgrade generated some conflicts with WordPress' own 
update mechanisms - mix and match with extreme caution.


And, for what it's worth, when it comes to all but the most core servers 
(say mysql, apache, postfix), I've found that it always pays to build 
servers from upstream source (particularly mail related stuff - getting 
antispam, antivirus, SMTP, IMAP, and authentication all wired together 
is a mess; same again for list managers).  At least that's been my 
experience when it comes to running a server farm - your mileage may vary.


Miles Fidelman




--
In theory, there is no difference between theory and practice.
In practice, there is.    Yogi Berra


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5296c292.8080...@meetinghouse.net

Re: wordpress, again

[Scott Ferguson]

On 28/11/13 15:12, Miles Fidelman wrote:
 Scott Ferguson wrote:
 The OP (in this thread) is asking about the Debian WordPress package.
 It installs WordPress, WordPress keeps itself up-to-date - i.e. it's
 version has nothing to do with the version number of the debian
 installer. On 28/11/13 09:48, Scott Ferguson wrote:
 
 Which is really the point here.

Yes. Though that xy thing is usually important also.

 
 1. Maybe an apt-get install wordpress-xxx will get you a close to
 current version, complete with all dependencies (hasn't been my
 experience - but then again I haven't tried going that route in a LONG
 time - sounds like things have gotten better).


Currently the Wheezy package installs as 3.6.1 (from memory, my notes
are the wiki page) and on log in your are alerted to 2 upgrades which
take it to the current upstream stable.

 
 But, and a BIG but - and probably important to the OP:
 
 2. apt-get update; apt-get upgrade is not going to be enough to keep
 your wordpress installation up-to-date - for that, you pretty much have
 to use WordPress' built in update mechanism - accessed through it's
 control panel - which takes into account how you've customized your
 installation (modules, themes).  In fact, I wouldn't be surprised if
 apt-get update/upgrade generated some conflicts with WordPress' own
 update mechanisms - mix and match with extreme caution.

Yes - apt-get whatever won't affect the WordPress install, which means
that you are not dependent on the Debian packagers to keep WordPress
(and it's themes and extensions) up-to-date. Which is handy as the
packagers say it's really just done for their own use, and they'd like
some else to help/take over. If I could find the

The main points are:-
;WordPress and it's themes and extensions are kept up to date via it's
own mechanisms (so the installation is always as secure as possible, not
withstanding PEBCAK). The WordPress version you run is not locked to the
version packaged with the installer - the debian package is just an
installer *not* a repackaged version of WordPress a la
Icedove/Thunderbird or Iceweasel/Firefox.
;your WordPress installation is Debian compliant so it will work through
upgrades (and dist-upgrades) to Debian (the OS). Everything lives in the
usual Debian places. No special considerations required for backups.

 
 And, for what it's worth, when it comes to all but the most core servers
 (say mysql,apache, postfix), I've found that it always pays to build
 servers from upstream source (particularly mail related stuff - getting
 antispam, antivirus, SMTP, IMAP, and authentication all wired together
 is a mess; same again for list managers).  At least that's been my
 experience when it comes to running a server farm - your mileage may vary.
 
 Miles Fidelman
 
 
 
 

A bit of both. Where ever possible/feasible I use pure Debian as it's
easier to manage upgrades/replication/backups/documentation etc. It
tends to ensure the whole system works well together.
pays is the crucial point you make - if you can charge for the extra
headaches involved in co-ordinating all that upstream it's worth it (if
the client needs require it).

In general I avoid the cutting edge when it comes to web-facing servers,
but then most of those clients run financial trading applications so I
need to be very conservative, and the amount of testing they require for
their apps ensures the very latest libraries are rarely required.

Sometimes that's not possible e.g. Tryton, OpenERP[*1], Zope etc other
times something like Virtualmin means I have to compromise and use their
version of upstream. I don't do mail stuff so I can't comment and defer
to those who do have experience in those areas.

[*1] though I note the old OpenERP client from the Debian repository
happily works with the latest OpenERP which *doesn't* supply a separate
client for those that wish a separate the server.


Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5296d0d4.7090...@gmail.com

Re: wordpress, again

[Rick Thomas]

On Nov 27, 2013, at 8:12 PM, Miles Fidelman mfidel...@meetinghouse.net wrote:

 Scott Ferguson wrote:
 The OP (in this thread) is asking about the Debian WordPress package. It 
 installs WordPress, WordPress keeps itself up-to-date - i.e. it's version 
 has nothing to do with the version number of the debian installer. On 
 28/11/13 09:48, Scott Ferguson wrote:
 
 Which is really the point here.
 
 1. Maybe an apt-get install wordpress-xxx will get you a close to current 
 version, complete with all dependencies (hasn't been my experience - but then 
 again I haven't tried going that route in a LONG time - sounds like things 
 have gotten better).
 
 But, and a BIG but - and probably important to the OP:
 
 2. apt-get update; apt-get upgrade is not going to be enough to keep your 
 wordpress installation up-to-date - for that, you pretty much have to use 
 WordPress' built in update mechanism - accessed through it's control panel - 
 which takes into account how you've customized your installation (modules, 
 themes).  In fact, I wouldn't be surprised if apt-get update/upgrade 
 generated some conflicts with WordPress' own update mechanisms - mix and 
 match with extreme caution.
 
 And, for what it's worth, when it comes to all but the most core servers (say 
 mysql, apache, postfix), I've found that it always pays to build servers from 
 upstream source (particularly mail related stuff - getting antispam, 
 antivirus, SMTP, IMAP, and authentication all wired together is a mess; same 
 again for list managers).  At least that's been my experience when it comes 
 to running a server farm - your mileage may vary.
 
 Miles Fidelman

Thanks, Miles.

I'll keep your advice in mind as I go forward with this project.

Your suggestion raises the question, though, of what do I do when I want to 
upgrade from Wheezy to Jessie in a year or so?  Will I get a toxic mix of 
Debian-wordpress and wordpress-upstream?

In other words, am I stuck on Wheezy until I'm willing to do a complete 
re-install of wordpress from scratch?

Thanks!
Rick

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/726b521f-bbae-46c2-baad-49a07363e...@pobox.com

Re: wordpress, again

[Scott Ferguson]

On 28/11/13 18:31, Rick Thomas wrote:
 
 On Nov 27, 2013, at 8:12 PM, Miles Fidelman
 mfidel...@meetinghouse.net wrote:
 
 Scott Ferguson wrote:
 The OP (in this thread) is asking about the Debian WordPress
 package. It installs WordPress, WordPress keeps itself up-to-date
 - i.e. it's version has nothing to do with the version number of
 the debian installer. On 28/11/13 09:48, Scott Ferguson wrote:
 

snipped

 Miles Fidelman
 
 Thanks, Miles.
 
 I'll keep your advice in mind as I go forward with this project.
 
 Your suggestion raises the question, though, of what do I do when I
 want to upgrade from Wheezy to Jessie in a year or so?  Will I get a
 toxic mix of Debian-wordpress and wordpress-upstream?


NO!

Ignore the speculation, well intended though it is.
The debian installer does *not* mean you run an out-dated version of
WordPress - it immediately upgrades to the current version of WordPress
(and all your themes and extensions).  When you first login the
Dashboard shows updates available - click on the icon and you'll soon be
running the freshly baked latest WordPress which is downloaded from the
WordPress site.

Upgrading Wheezy to the Jessie when it becomes stable, or indeed,
upgrading to Testing or Unstable tomorrow won't affect the Debian
installed WordPress - it will continue to be the most current version
available from upstream.  This is one of the reasons why it's better to
use the Debian installed WordPress than downloading the tarball and
dumping it somewhere.

All the package does is install WordPress into the Debian standard
locations. WordPress then manages it's own updates.

 
 In other words, am I stuck on Wheezy until I'm willing to do a
 complete re-install of wordpress from scratch?

No.

 
 Thanks! Rick
 

Kind regards.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5296f622.8050...@gmail.com

Re: wordpress, again

[Rick Thomas]

On Jun 21, 2012, at 1:02 PM, Glenn English g...@slsware.com wrote:

 I have a mildly working Debian WordPress install 

Hi Glen,

Would you be willing to help me get a wordpress installation up and running?

I've done aptitude install wordpress which dragged in all the necessary other 
packages, like apache2, mysql, php… etc.  So I *think* I've got all the tools 
I'll need.

But there seems to be a fair amount of configuration that's needed, and I've 
got no clue where to begin.

I've read the stuff in /usr/share/doc/wordpress (README.Debian, and the two 
files in examples/) but they are just hints -- I need a step-by-step for 
dummies.

If you can help me get from 'aptitude install' to a working setup, I'll promise 
to write it all up for the wiki, so the next person doesn't have to start from 
scratch.

Thanks for any help!

Rick

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/637be672-1919-4cf8-a244-14fe8d04a...@pobox.com

Re: Wordpress probleem na update

[Paul van der Vlis]

Op 26-09-13 20:49, Arjen Duinhouwer schreef:

 Hallo Paul,
 
 Normaliter zul je ook nooit de wp-content folder updaten, want dit zou
 betekenen dat je bij een custom/3rd party theme altijd je theme kwijt
 bent, maar ook je plugins, uploads e.d. Dus ik denk dat je per ongeluk
 iets te enthousiast bent geweest bij het updaten.

Ik heb gewoon de security update geinstalleerd met apt-get en daarbij is
een eerder meegeleverd theme verwijderd (twentyeleven).
Custom themes zijn niet verwijderd.

Ik weet niets over plugins omdat ik die bewust niet gebruik.

Naar mijn mening horen dit soort packages niet in in main maar in
backports.  Als zo'n package in main zit en het blijkt niet meer te
handhaven qua security, dan zou het een tag of andere vermelding moeten
krijgen met end of live of zoiets.

Hetzelfde vind ik gelden voor bijvoorbeeld browsers.

Met vriendelijke groet,
Paul van der Vlis.




-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52453898.7010...@vandervlis.nl

Re: Wordpress probleem na update

[BjornW]

Ter aanvulling: De WordPress update (dus niet via apt-get) laat express
de themes staan en zou hier dus geen probleem hebben veroorzaakt.
Persoonlijk neig ik naar het bewust niet gebruiken van packages voor dit
soort webapps, scheelt in mijn ervaring heel wat gezeur.

grtz
BjornW

On 27-09-13 09:58, Paul van der Vlis wrote:
 Op 26-09-13 21:18, Paul Gevers schreef:
 On 26-09-13 20:49, Arjen Duinhouwer wrote:
 Op 26-9-2013 20:44, Paul van der Vlis schreef:
 Op 26-09-13 16:45, Paul van der Vlis schreef:
 Hallo,

 Ik ben er achter wat er aan de hand is. Het theme wat ik heb gebruikt
 (het defaulttheme eerder, twenty-eleven of zoiets) ontbreekt in deze
 nieuwe versie.

 Mocht je hetzelfde probleem hebben, je kunt wel inloggen op wp-admin en
 daar een ander theme kiezen.
 Ik heb nu het oude theme uit een backup teruggehaald en het functioneert
 weer.

 Belangrijk was het nog om hier een symlink te maken:
 /usr/share/wordpress/wp-content/themes/

 Ik vind het maar niets dat er zomaar in een stable release themes
 verwijderd worden!

 Groet,
 Paul.
 Hoi Paul

 Heb je bug 713947 gezien en README.Debian gelezen (laatste paragraaf)?

 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713947
 Nee, maar bedankt voor de link.

 NEWS.Debian.gz is overigens ook interessant.

 De maintainer meldt daar welliswaar niet dat het theme twentyeleven
 verwijderd wordt, maar wel dat blijkbaar al eerder het theme twentyten
 verwijderd is. Met instructies over hoe dit te verhelpen als je nog niet
 geupgraded hebt.

 Groet,
 Paul.











-- 

met vriendelijke groet,
Bjorn Wijers

* b u r o b j o r n .nl *
digitaal vakmanschap | digital craftsmanship

Werkdagen:
Van maandag t/m donderdag vanaf 10:00 
Vrijdag is voor experimenteren en eigen projecten.

Postbus 14145
3508 SE Utrecht
The Netherlands

tel: +31 6 49 74 78 70
http://www.burobjorn.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5245681e.8070...@gmail.com

Re: Wordpress probleem na update

[Paul van der Vlis]

Op 27-09-13 13:12, BjornW schreef:
 Ter aanvulling: De WordPress update (dus niet via apt-get) laat express
 de themes staan en zou hier dus geen probleem hebben veroorzaakt.

Het zou prettig zijn als het package dit ook deed.

 Persoonlijk neig ik naar het bewust niet gebruiken van packages voor dit
 soort webapps, scheelt in mijn ervaring heel wat gezeur.

Ik wil juist wel packages gebruiken, omdat dat het beheer een stuk
eenvoudiger maakt.

Maar wat er nu gebeurd is een flinke discussie waard.

Met vriendelijke groet,
Paul van der Vlis.






-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52456cdd.8010...@vandervlis.nl

Re: Wordpress probleem na update

[Arjen Duinhouwer]

 
 
 Persoonlijk neig ik naar het bewust niet gebruiken van packages voor dit
 soort webapps, scheelt in mijn ervaring heel wat gezeur.
 
 Ik wil juist wel packages gebruiken, omdat dat het beheer een stuk
 eenvoudiger maakt.
 
 Maar wat er nu gebeurd is een flinke discussie waard.
 
 

Ik vind het juist niet zo handig om apt-get te gebruiken omdat je bij dit soort 
zaken precies wilt weten wat er gaat gebeuren, en via FTP inloggen is toch geen 
handeling die zoveel meer tijd kost? Ik zou toch overwegen om bij dit soort 
dingen niet via de repo te werken. Hoe doe je dat met staging processen? Wat 
als je klant wel een keer een plugin installeert? etc.


--
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/805c4741-9665-4645-9e34-7bf279d1c...@chello.nl

Re: Wordpress probleem na update

[Paul van der Vlis]

Op 27-09-13 14:00, Arjen Duinhouwer schreef:

 Persoonlijk neig ik naar het bewust niet gebruiken van packages
 voor dit soort webapps, scheelt in mijn ervaring heel wat
 gezeur.
 
 Ik wil juist wel packages gebruiken, omdat dat het beheer een stuk 
 eenvoudiger maakt.
 
 Maar wat er nu gebeurd is een flinke discussie waard.
 
 
 Ik vind het juist niet zo handig om apt-get te gebruiken omdat je bij
 dit soort zaken precies wilt weten wat er gaat gebeuren, 

Normalerwijze weet ik bij apt-get precies wat er gaat gebeuren.

Kijk naar bijvoorbeeld phpmyadmin, daar gaat het al jaren goed.

 en via FTP
 inloggen is toch geen handeling die zoveel meer tijd kost? 

Ik voer apt-get uit op ca. 40 machines via een script. Op die machines
draait allerlei software. Ik heb heel weinig zin om me specifiek met
Wordpress of de websites daarin bezig te houden tijdens de security updates.

 Ik zou
 toch overwegen om bij dit soort dingen niet via de repo te werken.

Als dat moest, dan zou ik ermee stoppen. Dat vind ik werk voor een
website beheerder. Ik hou me bezig met het beheren van de machines en
niet van de individuele websites.

Uiteraard kunnen mensen ook een website nemen en daar Wordpress
neerzetten met vele plugins. Maar dan beheer ik het niet voor ze.
(Behalve dan dat ik de site sluit als hij te veel problemen of risico's
oplevert.)

 Hoe doe je dat met staging processen? 

Ik weet niet wat je bedoeld.

 Wat als je klant wel een keer een plugin installeert? etc.

Dat kunnen ze niet.

Groet,
Paul.


-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/524582cf.8060...@vandervlis.nl

Re: Wordpress probleem na update

[Paul van der Vlis]

Op 26-09-13 16:45, Paul van der Vlis schreef:
 Hallo,
 
 Ik ben er achter wat er aan de hand is. Het theme wat ik heb gebruikt
 (het defaulttheme eerder, twenty-eleven of zoiets) ontbreekt in deze
 nieuwe versie.
 
 Mocht je hetzelfde probleem hebben, je kunt wel inloggen op wp-admin en
 daar een ander theme kiezen.

Ik heb nu het oude theme uit een backup teruggehaald en het functioneert
weer.

Belangrijk was het nog om hier een symlink te maken:
/usr/share/wordpress/wp-content/themes/

Ik vind het maar niets dat er zomaar in een stable release themes
verwijderd worden!

Groet,
Paul.




-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52448076.7000...@vandervlis.nl

Re: Wordpress probleem na update

[Paul Gevers]

On 26-09-13 20:49, Arjen Duinhouwer wrote:
 Op 26-9-2013 20:44, Paul van der Vlis schreef:
 Op 26-09-13 16:45, Paul van der Vlis schreef:
 Hallo,

 Ik ben er achter wat er aan de hand is. Het theme wat ik heb gebruikt
 (het defaulttheme eerder, twenty-eleven of zoiets) ontbreekt in deze
 nieuwe versie.

 Mocht je hetzelfde probleem hebben, je kunt wel inloggen op wp-admin en
 daar een ander theme kiezen.
 Ik heb nu het oude theme uit een backup teruggehaald en het functioneert
 weer.

 Belangrijk was het nog om hier een symlink te maken:
 /usr/share/wordpress/wp-content/themes/

 Ik vind het maar niets dat er zomaar in een stable release themes
 verwijderd worden!

 Groet,
 Paul.

Hoi Paul

Heb je bug 713947 gezien en README.Debian gelezen (laatste paragraaf)?

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713947

Paul




signature.asc
Description: OpenPGP digital signature

Re: wordpress - interface de gestion inaccessible

[Jean-Luc Bassereau]

Le 05/04/2013 18:44, Christophe Moille a écrit :

Bonjour,

J'ai un serveur qui est encore en oldstable (lenny). J'avais besoin d'une 
version plus récente de wordpress que celle de lenny sans pour autant avoir 
encore le temps de faire un upgrade de debian.
J'ai donc juste installé le paquet wordpress de la version squeeze (ajouté le 
dépot squeeze, mis une preference faible dessus et forcé l'installation du 
paquet squeeze de wordpress)
J'ai donc ainsi la version 3.3.2+dfsg-1~squeeze1 d'installée.
Le site tourne bien, à ceci près que même connecté (que ce soit un compte 
d'administration ou pas, id 1 ou pas) je ne puis accéder à l'interface 
d'administration du CMS.
Il me répond systématiquement Upgrade is needed, please log in with an admin 
account. à chaque tentative.
J'ai cherché un peu (ce qui m'a permis de voir qu'il semblerait qu'il veuille 
que ce soit le suer d'ID 1 pour une première connexion depuis la mise à jour.
Mais je n'ai pas trouvé de cas similaire au mien suite à une mise à jour de 
wordpress lenny-squeeze.

est-ce que quelqu'un-e saurait comment je puis faire ? Merci.



Pour les webapps comme Wordpress, pourquoi ne pas prendre l'archive 
disponible en ligne ?




--
Cordialement.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/51603eb3.6040...@onetoserve.net

Re: wordpress - interface de gestion inaccessible

[Christophe Moille]

Le Sat, Apr 06, 2013 at 05:26:43PM +0200, Jean-Luc Bassereau a écrit :
 
 Pour les webapps comme Wordpress, pourquoi ne pas prendre l'archive
 disponible en ligne ?

Parce que le packaging d'une distribution me permet de ne pas avoir à 
surveiller les mises à jour de sécurité.

-- 
Christophe Moille
09 50 72 75 25

La tolérance n'est pas une concession que je fais à l'autre ; c'est la 
reconnaissance de principe qu'une partie de la vérité m'échappe !


signature.asc
Description: Digital signature

Re: wordpress - interface de gestion inaccessible

[Jean-Luc Bassereau]

Le 06/04/2013 19:13, Christophe Moille a écrit :

Le Sat, Apr 06, 2013 at 05:26:43PM +0200, Jean-Luc Bassereau a écrit :

Pour les webapps comme Wordpress, pourquoi ne pas prendre l'archive
disponible en ligne ?

Parce que le packaging d'une distribution me permet de ne pas avoir à 
surveiller les mises à jour de sécurité.



Oui, effectivement, bonne réponse, j'aurai simplement un peu peur que le 
package mette des fichiers un peu partout ;-)



--
Cordialement.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/516079e9.8070...@onetoserve.net

Re: wordpress i Debian

[Eloi Notario]

El Diumenge 19 Agost 2012 15:09:43 Joan Cervan i Andreu va escriure:
 Ja estem a freeze??? Des de quan??? Això vol dir que aviat
 (excès de cometes?) tindrem la nova estable???

Congelat des de finals de juny.

-- 
Atentament,

Eloi Notario.


--
To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201208200921.05128.entfe...@gmail.com

Re: wordpress i Debian

[Joan Cervan i Andreu]

Ja estem a freeze??? Des de quan??? Això vol dir que aviat (excès 
de cometes?) tindrem la nova estable???

Ja fa temps que tinc ganes de que surti l'stable per resoldre problemes 
congènits amb l'amule, i per la llauna e que pàgines com la de l'Adwords no 
funcionin amb el Iceweasel, perquè google diu que estic passat de moda... Com 
veieu canviar els repositoris de l'estable actual a la propera estable? Millor 
esperar un temps, que acabin de pulir també el procś d'actualització? 

Salut,

Joan Cervan


 Hola,
 
 en general quan wordpress.org publica una nova versió aquesta no entra a
 la estable de Debian de turno ja que a part de resoldre problemes de
 seguretat també sol incloure noves funcionalitats i no és del tot
 backwards-compatible.
 
 Com a molt, l'equip de Debian hi aplicarà algun patch que trobin a les
 noves versions de WP publicades que resolguin problemes de seguretat i
 que funcionin a l'antiga.
 
 Fixa't que a Squeeze hi ha el WordPress 3.3.2, i que ja n'han sortit 3
 de noves (http://wordpress.org/download/release-archive/). La cosa més
 aviat funciona que cada cop que Debian fa un freeze per a treure una
 nova versió, inclou l'últim WP publicat i si en surten de nous allà
 queda. Per això actualment a Squeeze i Sid hi ha la 3.4.1, que si que és
 la última de WP, però si la setmana que vé sortís la 3.4.2 lo més segur
 que ja no s'actualitzaria perquè ara ja estem en estat 'freeze' de Debian.
 
 Bueno, feia temps que no escrivia a la llista, espero no haver-me
 enredat massa.
 
 Salut !!
 Marc ///
 
 Al 19/07/12 00:13, En/na Carles Pina i Estany ha escrit:
  Hola,
  
  He fet aquesta pregunta també a la llista de Wordpress. Disculpes si
  arriba duplicat :-)
  
  Pregunta: Wordpress sempre se m'acut instal·lar-lo de wordpress.org i
  anar fent. Alguna experiència amb el de Debian? Suposo que amb apt-get
  update  apt-get upgrade es va actualitzant amb el sistema (per motius
  de seguretat) i tot bé, no?
  
  Algú ho fa servir? Per què un i no l'altre?
  
  Fins aviat,


--
To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201208191509.43907.j...@calbasi.net

Re: wordpress i Debian

[Marc]

Hola,

en general quan wordpress.org publica una nova versió aquesta no entra a 
la estable de Debian de turno ja que a part de resoldre problemes de 
seguretat també sol incloure noves funcionalitats i no és del tot 
backwards-compatible.


Com a molt, l'equip de Debian hi aplicarà algun patch que trobin a les 
noves versions de WP publicades que resolguin problemes de seguretat i 
que funcionin a l'antiga.


Fixa't que a Squeeze hi ha el WordPress 3.3.2, i que ja n'han sortit 3 
de noves (http://wordpress.org/download/release-archive/). La cosa més 
aviat funciona que cada cop que Debian fa un freeze per a treure una 
nova versió, inclou l'últim WP publicat i si en surten de nous allà 
queda. Per això actualment a Squeeze i Sid hi ha la 3.4.1, que si que és 
la última de WP, però si la setmana que vé sortís la 3.4.2 lo més segur 
que ja no s'actualitzaria perquè ara ja estem en estat 'freeze' de Debian.


Bueno, feia temps que no escrivia a la llista, espero no haver-me 
enredat massa.


Salut !!
Marc ///


Al 19/07/12 00:13, En/na Carles Pina i Estany ha escrit:

Hola,

He fet aquesta pregunta també a la llista de Wordpress. Disculpes si
arriba duplicat :-)

Pregunta: Wordpress sempre se m'acut instal·lar-lo de wordpress.org i
anar fent. Alguna experiència amb el de Debian? Suposo que amb apt-get
update  apt-get upgrade es va actualitzant amb el sistema (per motius
de seguretat) i tot bé, no?

Algú ho fa servir? Per què un i no l'altre?

Fins aviat,




--
To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/502fa9ac.7050...@gmail.com

Re: wordpress, again [SOLVED]

[Glenn English]

WordPress was generating bad URL/pathnames sometimes...

My .htaccess was all screwed up, which broke the Permalinks. 
Wordpress seems to be a very nicely done piece of software 
-- it already knew what was wrong, and when somebody over 
there told me where to look, there was the text, waiting to 
be pasted into my file. 

Finding documentation like I have for my Cisco router is 
still a significant problem, though -- I can't imagine how 
that guy knew what was wrong...

I do wish they'd used C (or equivalent) to write it.

Thanks for your suggestions.

-- 
Glenn English
hand-wrapped from my Apple Mail




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cddfd846-f94b-4d43-9acb-9d6558077...@slsware.com

Re: wordpress, again

[Camaleón]

On Thu, 21 Jun 2012 14:02:20 -0600, Glenn English wrote:

 I have a mildly working Debian WordPress install -- it makes pictures on
 the screen and adds posts and pages. The posts appear on the home page
 of the blog, and the names of the pages show up in the menu (default
 theme). But when I click on the name of the post, test2 for example, I
 get an Apache2 error:
 
 The requested URL /blog/blog/2012/06/21/test2/ was not found on this
 server.

(...)

 My /etc/apache2/conf.d/wp.conf file contains:
 
  Alias /blog /usr/share/wordpress
  Directory /usr/share/wordpress
Options FollowSymLinks
AllowOverride Limit Options FileInfo
DirectoryIndex index.php
  /Directory

(...)

Just a quick note on this... The above should be used (according to the 
provided configuration template located in /usr/share/doc/wordpress/
examples/apache.conf) when you use no virtual hosts and your files are 
placed outside the /blog path. Are these two things true for your 
setup? :-?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/js21ts$5le$1...@dough.gmane.org

Re: wordpress, again

[Glenn English]

On Jun 22, 2012, at 9:10 AM, Camaleón wrote:

 Just a quick note on this... The above should be used (according to the 
 provided configuration template located in /usr/share/doc/wordpress/
 examples/apache.conf) when you use no virtual hosts and your files are 
 placed outside the /blog path. Are these two things true for your 
 setup? :-?

Yes. No virtuals and everything is in the MySQL files and /usr/share... 
/var/www/blog is completely empty. 

I've got virtual websites on the 'real' server. This is a new server, 
on the DMZ, but isolated from the main servers -- I'm trying to do a 
favor for a friend who wants to move his website from HTML to WP.

-- 
Glenn English
hand-wrapped from my Apple Mail




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/2d75661c-eb53-4569-897e-e605590d8...@slsware.com

Re: wordpress, again

[Miles Fidelman]

Glenn,

I notice you're still having problems, so, for what it's worth

I've had Wordpress running on Debian, with Apache for years, and 
recently did a reinstall after getting hacked.  Here's the step by step 
that I jotted down:


0. Caveat, this is running under Lenny, in a Xen VM - that shouldn't 
effect anything, but you never know:


1. Prerequisites
- apache w/ mod_rewrite, php, mysql - all installed from Debian packages 
with apt

- running as www:www

2. Set up DNS records for site

3. Download and install Wordpress (I've never had any luck with the 
packaged version)

- as root
cd /var

wget http://wordpress.org/latest.tar.gz

tar -xzvf latest.tar.gz

mv wordpress gd


- seemed to untar as www-data:www-data, but you may need to

chmod -R www-data:www-data ./site



4. Set up database using mysqladmin (note: php_myadmin makes things 
slightly easier)


mysql -p youradminpassword

CREATE DATABASE sitename;

GRANT ALL PRIVILEGES ON sitename.* to you@localhost IDENTIFIED BY 
'password';


FLUSH PRIVILEGES;


4.  Set up Apache

--- my /etc/apache2/sites/site file (note: provides both http: 
and https: access) ---

--- note: needs to have your site's info inserted

VirtualHost x.x.x.x:80
ServerAdmin webmaster@site.org
ServerName site.org

DocumentRoot /var/site/

Directory /
Options FollowSymLinks
AllowOverride None
/Directory
Directory /var/site/
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
allow from all
   /Directory

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
Directory /usr/lib/cgi-bin
AllowOverride None
Options ExecCGI -MultiViews +SymLinksIfOwnerMatch
Order allow,deny
Allow from all
/Directory

LogLevel warn

CustomLog /var/log/apache2/access.log combined
ServerSignature On

Alias /doc/ /usr/share/doc/
Directory /usr/share/doc/
Options Indexes MultiViews FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
Allow from 127.0.0.0/255.0.0.0 ::1/128
/Directory

/VirtualHost

VirtualHost x.x.x.x:443
ServerAdmin webmaster@site.org
ServerName site.org

DocumentRoot /var/site/

Directory /
Options FollowSymLinks
AllowOverride None
/Directory
Directory /var/site/
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
allow from all
/Directory

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
Directory /usr/lib/cgi-bin
AllowOverride None
Options ExecCGI -MultiViews +SymLinksIfOwnerMatch
Order allow,deny
Allow from all
/Directory

LogLevel warn

CustomLog /var/log/apache2/access.log combined
ServerSignature On

Alias /doc/ /usr/share/doc/
Directory /usr/share/doc/
Options Indexes MultiViews FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
Allow from 127.0.0.0/255.0.0.0 ::1/128
/Directory

 SSLEngine on
 SSLCertificateFile /etc/apache2/ssl/apache.pem
/VirtualHost


a2ensite site
/etc/init.d/apache2 reload

5. Set up Wordpress via installer URL

6. A little hardening
see 
http://www.slideshare.net/williamsba/now-thats-what-i-call-wordpress-security-2010 
for some good guidnace


chmod 644 wp-config.php

mv wp-config.php ../


note: left wp-content directory in its normal place (I think moving it 
screws up my https: setup)


installed, set up, activated:
- Akismet (spam filtering)
- Better WP Security (NOTE: Includes a database backup function)
- Exploit Scanner
- Jetpack
- VSF Simple Block (blocks IP addresses)
- Wordfence (NOT activated, I use it's scanner occasionally)
- Wordpress Firewall 2 (does some automatic blocking of IP addressees 
based on behavior)
- WP Security Scan (also NOT activated, I use it's security scanner 
periodically)


- configure things, including backups (I use Better WP Security for the 
database backup, my overall system backup for the static files in /var)


7. And, of course, update everything through the Wordpress dashboard, 
and then re-run security scans.


Hope this helps.

Miles Fidelman


--
In theory, there is no difference between theory and practice.
In practice, there is.    Yogi Berra


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4fe498a1.7070...@meetinghouse.net

Re: wordpress, again

[Tony Baldwin]

On Thu, Jun 21, 2012 at 02:02:20PM -0600, Glenn English wrote:
 I have a mildly working Debian WordPress install -- it makes 
 pictures on the screen and adds posts and pages. The posts 
 appear on the home page of the blog, and the names of the pages 
 show up in the menu (default theme). But when I click on the 
 name of the post, test2 for example, I get an Apache2 error:
 
  The requested URL /blog/blog/2012/06/21/test2/ was not found on this server.
 
 Grep finds test2 in 2 mySQL files:
 
  Binary file wp_posts.MYD matches
  Binary file wp_posts.MYI matches
 
 Grep doesn't find 'blog/blog' anywhere in /usr/share/wordpress.
 

I would guess that you need to enable apache mod-rewrite.
do (as root, in terminal)
a2enmod rewrite
service apache2 restart

then tell us what happens.

./tony
-- 
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E


signature.asc
Description: Digital signature

Re: wordpress, again

[Glenn English]

On Jun 22, 2012, at 10:46 AM, Tony Baldwin wrote:

 I would guess that you need to enable apache mod-rewrite.
 do (as root, in terminal)
 a2enmod rewrite
 service apache2 restart
 
 then tell us what happens.

Module rewrite already enabled

(I didn't do the restart.) 

In the admin state, the edit button finds the posts fine -- there's 
only a single 'blog/ in the URL to post.php, with a request to edit 
it and a post=n. In view, the repeat of the blog/ shows up again 
in a URL that looks like a directory that looks like an archive.

Do you know what piece of the PHP is creating this wrong URL? Is WP 
supposed to have created a directory called 'blog/', and my config 
is somehow confusing it? Would it be worth the time and effort to 
change /var/www/blog to something else (I tried that, and WP didn't 
care for it -- I needed some other changes that I don't know about...)

-- 
Glenn English
hand-wrapped from my Apple Mail




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/f5eb3873-f409-4b5c-a84d-e92b1f0a6...@slsware.com

Re: wordpress/apache

[Tony Baldwin]

On Tue, Jun 19, 2012 at 10:18:52AM +0100, Chris Davies wrote:
 Tony Baldwin t...@tonybaldwin.org wrote:
  As far as just work, this is generally the case for a lot of stuff,
  but for a web application, you have to consider that not everyone wants
  to use only wordpress as their webroot, which is why such things are
  left to the user to configure, rather than automagical.
 
 I agree with you that it's good that Debian doesn't constrain my
 solution space. What threw me (although I can't speak for the OP)
 was my expectation from other web related packages that there would be
 something like http://localhost//wordpress/; ready and waiting for me
 to customise. Yes, it's easy to add but when someone is unfamiliar with
 an application, the easier the better. (/wordpress/ is clearly not the
 best of choices for a production installation, but who in their right
 mind would install Wordpress - or any other complex application for
 that matter - into a production instance without having first learned
 at least something about it?)
 
 
  Most web applications I install from upstream sources [...]
  I just install them where I want them somewhere in the webroot
  (/var/www/somesubdir).
 
 I tend to install under /home/www/vHost/docroot/ rather than under
 /var/www, as it means I get to keep my log files near my vHosts (/logs
 instead of /docroot) and I can transfer the vHost in its entirely fairly
 cleanly to another host. Re upstream sources vs Debian, I tend to prefer
 the Debian approach as it fits with my system(s) cleanly. But there is
 always a place for a vanilla upstream install. I run Debian's Apache,
 MySQL, Perl, and PHP for instance, as they work. But I customise the
 Apache configuration within individual vHosts quite heavily.
 

Yes, some stuff I install somewhere in /home (often creating distinct
users for this), but I then symlink them in /var/www.
I don't think it's necessarily better, but works for me.
I will do this when, for instance, I have a test server here at home
that used to be a desktop. The /home partition is a lot bigger than the
/root (some 150gb hdd, with like 20gb / and 120ish /home), so there's
more space for stuff.

Also, I do use the debian packages for apache, mysql and php,
just stuff like wiki, blog, etc. (dokuwiki, wordpress, whatever),
I often find are easilier installed and managed from the upstream
sources (and stay more uptodate, although you do have to be careful
about incompatibilitlies with our older pkgs, like php, or whatever).

  I always run Stable on servers, and packages can end up two years old,
 
 Likewise, except I often add backports for newer features that I really
 want.
 
 
  It's funny, I stick with stable for the server os, but run apps on the
  bleeding development edge from git repos all the time, now.
 
 Not really. One just hurts if it breaks, and the other is potentially
 professional stupidity. You have restorable backups, of course...?

always have backups!

./tony
-- 
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E


signature.asc
Description: Digital signature

Re: wordpress/apache

[Chris Davies]

Tony Baldwin t...@tonybaldwin.org wrote:
 As far as just work, this is generally the case for a lot of stuff,
 but for a web application, you have to consider that not everyone wants
 to use only wordpress as their webroot, which is why such things are
 left to the user to configure, rather than automagical.

I agree with you that it's good that Debian doesn't constrain my
solution space. What threw me (although I can't speak for the OP)
was my expectation from other web related packages that there would be
something like http://localhost//wordpress/; ready and waiting for me
to customise. Yes, it's easy to add but when someone is unfamiliar with
an application, the easier the better. (/wordpress/ is clearly not the
best of choices for a production installation, but who in their right
mind would install Wordpress - or any other complex application for
that matter - into a production instance without having first learned
at least something about it?)


 Most web applications I install from upstream sources [...]
 I just install them where I want them somewhere in the webroot
 (/var/www/somesubdir).

I tend to install under /home/www/vHost/docroot/ rather than under
/var/www, as it means I get to keep my log files near my vHosts (/logs
instead of /docroot) and I can transfer the vHost in its entirely fairly
cleanly to another host. Re upstream sources vs Debian, I tend to prefer
the Debian approach as it fits with my system(s) cleanly. But there is
always a place for a vanilla upstream install. I run Debian's Apache,
MySQL, Perl, and PHP for instance, as they work. But I customise the
Apache configuration within individual vHosts quite heavily.


 I always run Stable on servers, and packages can end up two years old,

Likewise, except I often add backports for newer features that I really
want.


 It's funny, I stick with stable for the server os, but run apps on the
 bleeding development edge from git repos all the time, now.

Not really. One just hurts if it breaks, and the other is potentially
professional stupidity. You have restorable backups, of course...?

Thanks for the tips
Chris


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/sos5b9x88c@news.roaima.co.uk

Re: wordpress/apache

[Camaleón]

On Mon, 18 Jun 2012 10:41:05 -0600, Glenn English wrote:

(...)

 I've installed the squeeze Apache, PHP, MySQL, and Wordpress packages
 and there's nothing there when I point a browser at it. If I create a
 PHP file named info.php (with the phpinfo() call in it) and put it in
 /var/www, I see the PHP info. I think I need something to get Apache to
 run the index.php (and its friends) file in /usr/share/wordpress. How do
 I do this?

If you're using Debian stock Wordpress package there has to be 
information for its setting up under the usual path /usr/share/doc/
wordpress/README.Debian :-?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jrnnp5$kvm$2...@dough.gmane.org

Re: wordpress/apache

[Glenn English]

On Jun 18, 2012, at 11:16 AM, Camaleón wrote:

 If you're using Debian stock Wordpress package there has to be 
 information for its setting up under the usual path /usr/share/doc/
 wordpress/README.Debian :-?

I got the WordPress PHP going with an alias config in /etc/apache2/conf.d 
and was at the point of adding debugging prints to figure out why the PHP 
files were aborting without making any pixels. It looks like the 'setup-mysql' 
did something that made the PHP start working. I still don't understand, 
but thanks very much!

-- 
Glenn English
hand-wrapped from my Apple Mail




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/9d4e9797-0213-4d5b-8cca-dbcf66a85...@slsware.com

Re: wordpress/apache

[Chris Davies]

Glenn English g...@slsware.com wrote:
 I've installed the squeeze Apache, PHP, MySQL, and Wordpress 
 packages and there's nothing there when I point a browser at it. 

 I see the PHP info. I think I need something to get Apache to run
 the index.php (and its friends) file in /usr/share/wordpress. How do
 I do this?

I think what I did when trying this out the other day was this:
cd /var/www  sudo ln -s /usr/share/wordpress

Then reference the Wordpress stuff via http://localhost/wordpress/

I remember scratching my head of this and then shrugging my shoulders,
as usually Debian packages just work (or nearly so). There is an
/etc/wordpress/htaccess file that looks like it is supposed to end up
being modified as /var/www/.htaccess, but I couldn't see how that would
work with Wordpress as a subdirectory. If you want http://localhost/
to be your Wordpress system then I'd look at changing the definitions
related to the Document Root in /etc/apache2/sites-enabled/000-default

Chris


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/uh74b9xf9p@news.roaima.co.uk

Re: wordpress/apache

[Glenn English]

On Jun 18, 2012, at 12:10 PM, Chris Davies wrote:

 I think what I did when trying this out the other day was this:
cd /var/www  sudo ln -s /usr/share/wordpress

I did that part by copying to a file called wp.conf in /etc/apache2/conf.d 
from /usr/share/doc/wordpress/examples/apache.conf. The edited version contains:

   Alias /blog /usr/share/wordpress
   Directory /usr/share/wordpress
 Options FollowSymLinks
 AllowOverride Limit Options FileInfo
 DirectoryIndex index.php
   /Directory

And I made a directory called 'blog' in /var/www. That makes Apache think 
the stuff in /usr/share/wordpress is in /var/www/blog. According to my 
Apache2 book, this is better than a soft link (don't remember why).

Then the problem became that setup-mysql hurled because it couldn't ping 
interface.slsware.com, the server WP is on. All it could get to was the 1918 
DMZ net IP -- like it's supposed to. A secondary IP on eth0 fixed that, and it 
seems to be running now. 

WordPress is *not* trivial to set up, as it advertises. Not from the Debian 
package and trying for some security, anyway. I had to do a lot that I 
never needed before, some of which I've been told never to do on the 
Internet. I'm glad I have a dedicated server for it, so I'll have a better 
chance at keeping the badGuys away from it.

There are always a million things to get right before something works. But with 
this, there was very little, except a blank screen, to give me a hint of what 
was still bent.

I don't understand Debian's thinking on this. It's nice that they put the 
config 
files in /etc, and the README was helpful. But when apt's finished installing, 
it 
doesn't work. It's a long way from working. I don't ever remember seeing that 
before 
in a .deb package.

-- 
Glenn English
hand-wrapped from my Apple Mail




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/e63bb77e-a3b5-4235-b8fd-1fc24fea2...@slsware.com

Re: wordpress/apache

[Chris Davies]

Glenn English g...@slsware.com wrote:
 Then the problem became that setup-mysql hurled because it couldn't
 ping interface.slsware.com, the server WP is on. All it could get to
 was the 1918 DMZ net IP -- like it's supposed to. A secondary IP on
 eth0 fixed that, and it seems to be running now.

I think an entry in /etc/hosts would have been my choice, but I can see
that a secondary IP would work pretty well. What about putting it on lo
rather than eth0, though?


 WordPress is *not* trivial to set up, as it advertises. Not from the
 Debian package and trying for some security, anyway.

It was (a little) easier from the official tarball. But how secure
the resulting installation is, I don't know. At least it's still only
on my laptop  ;-)

Chris


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/u4m4b9x43u@news.roaima.co.uk

Re: wordpress/apache

[Glenn English]

On Jun 18, 2012, at 4:19 PM, Chris Davies wrote:

 I think an entry in /etc/hosts would have been my choice, but I can see
 that a secondary IP would work pretty well. What about putting it on lo
 rather than eth0, though?

I hadn't thought of that -- the program said it couldn't ping a FQDN. I 
assumed it was using the IP, but I can see how that might be a much better 
solution. I'll give it a try. Thanks.

 It was (a little) easier from the official tarball. But how secure
 the resulting installation is, I don't know. At least it's still only
 on my laptop  ;-)

I tried several different installs, including the factory recommendation. 
I thought it was easier too, but I wanted the Debian update process behind 
it. And I think your 'hosts' trick will make it more secure -- there's nobody 
responding to the IP given out by DNS. Not on the DMZ, anyway...

-- 
Glenn English
hand-wrapped from my Apple Mail




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/6e41c07a-ef2b-4345-8b42-cf51de719...@slsware.com

Re: wordpress/apache

[Tony Baldwin]

On Mon, Jun 18, 2012 at 07:10:38PM +0100, Chris Davies wrote:
 Glenn English g...@slsware.com wrote:
  I've installed the squeeze Apache, PHP, MySQL, and Wordpress 
  packages and there's nothing there when I point a browser at it. 
 
  I see the PHP info. I think I need something to get Apache to run
  the index.php (and its friends) file in /usr/share/wordpress. How do
  I do this?
 
 I think what I did when trying this out the other day was this:
 cd /var/www  sudo ln -s /usr/share/wordpress
 
 Then reference the Wordpress stuff via http://localhost/wordpress/
 
 I remember scratching my head of this and then shrugging my shoulders,
 as usually Debian packages just work (or nearly so). There is an
 /etc/wordpress/htaccess file that looks like it is supposed to end up
 being modified as /var/www/.htaccess, but I couldn't see how that would
 work with Wordpress as a subdirectory. If you want http://localhost/
 to be your Wordpress system then I'd look at changing the definitions
 related to the Document Root in /etc/apache2/sites-enabled/000-default
 
 Chris

As far as just work, this is generally the case for a lot of stuff,
but for a web application, you have to consider that not everyone wants
to use only wordpress as their webroot, which is why such things are
left to the user to configure, rather than automagical.
Your wordpress will install in /usr/share/wordpress, but you have to
tell apache where it is, of course, which, as indicate above, is
generally done by adding a vhost file in /etc/apache2/sites-available/
(and symlinking that in ../sites-enabled), or just in the
/etc/apache2/httpd.conf or apache2.conf

Frankly, I tried to install wp from the debian pkg before, and it was a
headache.  Most web applications I install from upstream sources, even
when there are debian packages (dokuwiki, wordpress, gallery, and others
I do this way), sometimes especially if the app has a git repo, which
renders keeping them more up-to-date easier.
I just install them where I want them somewhere in the webroot
(/var/www/somesubdir).
I always run Stable on servers, and packages can end up two years old,
as you likely know, and for some stuff, a lot can happen in two years.
But, if you, say, install dokuwiki from the debian package, and then
update it via the built-in updater thingy, you may have problems.
This is why I just install from the upstream sources and use the
package's own updating mechanisms, in general, now.
It's funny, I stick with stable for the server os, but run apps on the
bleeding development edge from git repos all the time, now.  Perhaps
that seems contradictory.  Of course, when you're contributing to a
project in git, you want to run the latest code, anyway, at least if not
on a production server, somewhere on a test server, perhaps.

Just one thing I recommend: don't go to #wordpress @freenode looking for
help. While #debian (and #tcl and #dokuwiki and many other chans) are
full of kind, compassionate, helpful people, if you go to #wordpress
expecting such treatment, you will be sorely disappointed.
All you're likely to get there is, first don't use Debian packages
(okay, I say the same thing, shame on me), and second,I'll help you for
$80/hour.  Seriously.
Of course, I don't begrudge anyone a living, but it just seems terribly
mercenary in there. (I might add, I've been permanently banned from that
channel...so maybe I'm biased)

tony
-- 
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E


signature.asc
Description: Digital signature

Re: Wordpress can't find uploads

[Camaleón]

On Sun, 13 May 2012 17:25:47 -0400, Daniel D Jones wrote:

 I have multiple Wordpress blogs running using Debian's method of
 pointing to different blogs.  I'm posting here and not a Wordpress
 specific list because I believe this is related to Debian's unique
 method of installation.  

Which is described at /usr/share/doc/wordpress/README.Debian.

 On one instance, I'm using the Portfolio Press theme.  Images I upload
 to the portfolio do not show up.  Looking at the source, the image is
 linked as:
 
 /wp-uploads/2012/05/image.jpg
 
 The actual path to the images is:
 
 /wp-uploads/myblog.mydomain.org/2012/05/image.jpg

So, you mean the WP theme you have installed does not detect the full 
path for the stored images of the virtual host site, right?
 
 There is a different directory for each blog I'm running under the
 /wp-uploads/ directory, allowing all the blogs to peacefully coexist.

Looks a sensible approach.
 
 What's puzzling is that the images are being uploaded by the theme and
 instance to the correct location.  It's only the image links on the post
 itself which are incorrect.  Any hints or suggestions appreciated.

Mmm... have you checked if there is any configuration option to control 
this from WordPress control panel settings? I think the main problem can 
be in configuring WP to work with multi-homed sites (aka virtual 
hosting).

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/joremi$a7a$1...@dough.gmane.org

Re: Wordpress no me deja crear páginas

[Santiago Vila]

On Fri, 25 Jun 2010, Gorka wrote:

 Buenas.
 
 He instalado wordpress con permiso 770 usuario usuario:www-data a todas las
 carpetas y archivos.
 Visualizo la página home perfectamente, pero si en el administrador creo una
 nueva página 'PaginaOtra' me aparece en el menú de la home 'PaginaOtra',
 pero no me crea la carpeta '/PaginaOtra/'.
 No entiendo por qué.

Pues porque las páginas de WordPress en realidad no existen como
ficheros y directorios reales, sino que están todas en la base de
datos MySQL. Cuando visitas una página, los scripts en PHP que
conforman WordPress buscan esa página en la base de datos y te la
muestran, pero no la busques en el sistema de ficheros porque no la
encontrarás.

Es todo una ilusión, como en Matrix, o si lo prefieres, como el
directorio /proc.


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.deb.1.10.1006261219330.15...@kolmogorov.unex.es

Re: Wordpress no me deja crear páginas

[Felix Perez]

El día 25 de junio de 2010 08:51, Gorka gorkali...@yahoo.es escribió:
 Buenas.

 He instalado wordpress con permiso 770 usuario usuario:www-data a todas las
 carpetas y archivos.
 Visualizo la página home perfectamente, pero si en el administrador creo una
 nueva página 'PaginaOtra' me aparece en el menú de la home 'PaginaOtra',
 pero no me crea la carpeta '/PaginaOtra/'.
 No entiendo por qué.

 ¿Alguna Idea?


¿qué te dicen en la lista de wordpress?

Suerte

-- 
usuario linux  #274354
normas de la lista:  http://wiki.debian.org/NormasLista
como hacer preguntas inteligentes:
http://www.sindominio.net/ayuda/preguntas-inteligentes.html


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktik-itqo4o_aqyxrxy8xdqhrz89kddivl3xpc...@mail.gmail.com

Re: Wordpress no me deja crear páginas

[Jose Damian Garrido Muñoz]

2010/6/25 Gorka gorkali...@yahoo.es:
 Buenas.

 He instalado wordpress con permiso 770 usuario usuario:www-data a todas las
 carpetas y archivos.
 Visualizo la página home perfectamente, pero si en el administrador creo una
 nueva página 'PaginaOtra' me aparece en el menú de la home 'PaginaOtra',
 pero no me crea la carpeta '/PaginaOtra/'.
 No entiendo por qué.

 ¿Alguna Idea?

porque crees que te debería crear una carpeta con el nombre de la página?
a todo esto, esto es una lista de gnu/debian, no de wordpress (;
lo digo por si te confundiste de lista.


-- 
José Damián Garrido
Programador Web
ciber-humano


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikodzsjz3xxdh11wx1afaa0fcfuwvx9neuvq...@mail.gmail.com

Re: wordpress einrichten

[Daniel Leidert]

Am Freitag, den 21.07.2006, 23:33 +0200 schrieb Bastian Venthur:

 ich würde gerne wordpress testen aber komm auf Anhieb nicht zurecht.

Womit denn genau nicht?

 Kennt jemand eine Schritt-für-Schritt Anleitung für Debian (sid oder
 etch) der man einigermaßen gut folgen kann?

Eigentlich sind die Informationen in /usr/share/doc/wordpress/*
ausreichend. Eine Schritt-für-Schritt-Anletung befindet sich in der
readme.html. Man muss die Anleitung aber dahingehend abändern, dass man
die wp-config-sample.php nach /etc/wordpress als config-$DOMAIN.php
kopiert (und wenn du Aliases im Apache einrichtest, würde ich diese als
Symlinks auf die config-$DOMAIN.php realisieren) und dort dann die Daten
einträgt. Den Rest ganz unten, den man nicht editieren sollte, kann man
IMO löschen, da er auch in der /etc/wordpress/wp-config.php steht.

 Eine kleinere Hürde: ich möchte es erstmal lokal auf meinem Router
 testen, den ich vom LAN aus natürlich nicht mit localhost ansprechen
 kann.

Warum auf dem Router und nicht der Workstation, wenn du eh nur testen
willst?

 Ich hab für den Router eine .dyndns.org-Adresse die leider für das
 mysql-Einrichtskript zu lang ist.

Ist das nicht egal? Soweit ich die setup-mysql verstehe, legt diese dann
die notwendige /etc/wordpress/config-$DOMAIN.php an und benennt die
Datenbank nur dann nach $DOMAIN, falls du nicht die Option -n benutzt
und den Namen selbst festlegst:

setup-mysql [-n NAME] [-h | -d | -b] FQDN

Creates by default a Wordpress mysql configuration depending on required
fully qualified domain name(FQDN).

Options:
-n  name for the mysql user and database
-h  help
-d  destroy and purge
-b  backup

Daher ist die angegebenen Domain selbst schon recht uninteressant, wenn
du den Datenbank-Namen selbst festlegst (dann finde ich nämlich auch
keinen Test auf die Länge von $DOMAIN). Aber selbst wenn, werden alle
MySQL-Daten (Datenbank, Nutzer, Passwort, Prefix etc.) in der
config-$DOMAIN.php festgehalten und die eigentliche Domain selbst wird
nur über die Apache-Konfiguration (und den Namen
der /etc/wordpress/config-$DOMAIN.php) festgelegt. Damit ist das
Argument FQDN, dass du setup-mysql übergibst, eigentlich uninteressant.
Du musst dann halt nur die erstellte Konfigurationsdatei
in /etc/wordpress umbenennen. Aber normalerweise sollte das Skript keine
Fehler melden, wenn du es korrekt benutzt.

MfG Daniel

Re: Wordpress 2 trouble

[Jacob Friis Saxberg]

On 2/2/06, Jacob Friis Saxberg [EMAIL PROTECTED] wrote:
 I have upgraded to Wordpress 2 and have several weblogs that use the same 
 source files.
 Now I am unable to have an unique design for each weblog.
 Others with this problem?

Here's my solution:
http://www.thinklemon.com/weblog/2006/01/15/wordpress-20-cache-is-broken/

Re: Wordpress

[Anthony Campbell]

On 20 Dec 2005, Vicki Stanfield wrote:
  On Mon, Dec 19, 2005 at 08:19:49PM -, Vicki Stanfield wrote:
 
  Have you looked at the readme.html file that comes with the package?
  On my testing system, it is found in /usr/share/wordpres. It gives
  simple instructions, and that might be all you need.
 
  The readme is worthless. It does *not* work with the system without vast
  amounts of tweaking. In the end, I ditched Wordpress in favor of
  NanoBlogger, and that's working beautifully.
 
 Interesting. I use WordPress on my Slackware box, and it works
 beautifully. I don't have it on my Debian box except where I added it to
 see where the readme.html would show up to post to your question. I'll
 have to try it later to see what you mean. I had no trouble with
 config'ing it under Slackware though.
 
 Oh well, experience varies I guess.
 
 Vicki
 

Wordpress is working well here too. However, it isn't the deb package
but the vanilla version from Wordpress. Plenty of documentation on
wordpress.org.

Anthony


-- 
Anthony Campbell - [EMAIL PROTECTED] 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress

[Hugo Vanwoerkom]

Anthony Campbell wrote:

On 20 Dec 2005, Vicki Stanfield wrote:

On Mon, Dec 19, 2005 at 08:19:49PM -, Vicki Stanfield wrote:


Have you looked at the readme.html file that comes with the package?
On my testing system, it is found in /usr/share/wordpres. It gives
simple instructions, and that might be all you need.

The readme is worthless. It does *not* work with the system without vast
amounts of tweaking. In the end, I ditched Wordpress in favor of
NanoBlogger, and that's working beautifully.

Interesting. I use WordPress on my Slackware box, and it works
beautifully. I don't have it on my Debian box except where I added it to
see where the readme.html would show up to post to your question. I'll
have to try it later to see what you mean. I had no trouble with
config'ing it under Slackware though.

Oh well, experience varies I guess.

Vicki



Wordpress is working well here too. However, it isn't the deb package
but the vanilla version from Wordpress. Plenty of documentation on
wordpress.org.



Same here. The only problem I have is upgrading to their new version: I 
made changes to 1.2 and that would entail finding the original 1.2 
installation version, seeing what exactly the changes are that I made 
and making all of those to the new version: too much work, since the 
only complaint I have is that accents don't work right, regardless of 
the advise on their site.


H


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress

[Jon Dowland]

On Sun, Dec 18, 2005 at 10:16:03AM -0800, Todd A. Jacobs wrote:
 I'm trying to install Wordpress on a Debian 3.1 system.

Make sure you make regular visits to wordpress.org, if you are using
their tarball, in order to find out about security releases. They have
an announce list that they do not use. Also you have to be very careful
as they have, in the past, uploaded new versions of the software without
changing the version number (or announcing the upload).

PhpBB are similarly bad in this regard.

-- 
Jon Dowland
http://alcopop.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress

[Todd A. Jacobs]

On Mon, Dec 19, 2005 at 08:19:49PM -, Vicki Stanfield wrote:

 Have you looked at the readme.html file that comes with the package?
 On my testing system, it is found in /usr/share/wordpres. It gives
 simple instructions, and that might be all you need.

The readme is worthless. It does *not* work with the system without vast
amounts of tweaking. In the end, I ditched Wordpress in favor of
NanoBlogger, and that's working beautifully.

-- 
Re-Interpreting Historic Miracles with SED #141: %s/water/wine/g


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress

[Vicki Stanfield]

 On Mon, Dec 19, 2005 at 08:19:49PM -, Vicki Stanfield wrote:

 Have you looked at the readme.html file that comes with the package?
 On my testing system, it is found in /usr/share/wordpres. It gives
 simple instructions, and that might be all you need.

 The readme is worthless. It does *not* work with the system without vast
 amounts of tweaking. In the end, I ditched Wordpress in favor of
 NanoBlogger, and that's working beautifully.

Interesting. I use WordPress on my Slackware box, and it works
beautifully. I don't have it on my Debian box except where I added it to
see where the readme.html would show up to post to your question. I'll
have to try it later to see what you mean. I had no trouble with
config'ing it under Slackware though.

Oh well, experience varies I guess.

Vicki


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress

[Hugo Vanwoerkom]

Todd A. Jacobs wrote:

I'm trying to install Wordpress on a Debian 3.1 system. I have apache
configured with a default virtual host, and even when I get Wordpress to
install, the Debian docs that come with it seem insufficient for getting
it up and running in my environment.

Does anyone know of a step-by-step that would explain how to do this in
my particular environment?



http://wordpress.org/
did you try their wiki or whatever they have for user communication?

Are you using a Debian package or the WP version?

I installed wp 1.2 more than a year ago.
Use it to record what I do with Debian.
Of course it does not have the step by step of how I installed it. :-(

H









--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress

[Vicki Stanfield]

 Todd A. Jacobs wrote:
 I'm trying to install Wordpress on a Debian 3.1 system. I have apache
 configured with a default virtual host, and even when I get Wordpress to
 install, the Debian docs that come with it seem insufficient for getting
 it up and running in my environment.

 Does anyone know of a step-by-step that would explain how to do this in
 my particular environment?


Have you looked at the readme.html file that comes with the package? On my
testing system, it is found in /usr/share/wordpres. It gives simple
instructions, and that might be all you need.

Vicki


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress: Redirect hinter Home

[Stefan Pampel]

 Ich habe mich schon in meinen Einstellungen umgesehen, da finde ich
 nichts passendes. Die Onlinedokumentation und Google waren bisher auch
 nicht hilfreich.


 Kennt einer von Euch dieses oder ein ähnliches Problem? Hat jemand
 eine Idee, wie ich die Ursache besser eingrenzen könnte?
Blöde Frage: Du hast schon mal in der config*.php von Wordpress
nachgesehen? Sonst mal das Verzeichnis nach einer Datei mit Inhalt
'localhost' durchsuchen, dürfte ja nicht allzuviel rauskommen.

MfG

Stefan Pampel

Re: Wordpress: Redirect hinter Home

[Thorsten Haude]

Moin,

* Stefan Pampel wrote (2005-10-28 12:05):
Blöde Frage: Du hast schon mal in der config*.php von Wordpress
nachgesehen? Sonst mal das Verzeichnis nach einer Datei mit Inhalt
'localhost' durchsuchen, dürfte ja nicht allzuviel rauskommen.

Ich finde da überhaupt nichts, was zum Problem paßt. In dieser Datei
wird die Variable DB_HOST auf localhost gesetzt, aber das wird nur für
den Zugriff auf die Datenbank gebraucht.


Thorsten
-- 
Calvin: Who can fathom the feminine mind?
Hobbes: I like 'em anyway


pgpgCzI0zmrYq.pgp
Description: PGP signature

Re: Wordpress: Redirect hinter Home

[Thorsten Strusch]

Moin Namensvetter,

Thorsten Haude schrieb:

Moin,

ich habe gerade Wordpress 1.5.2-0.backports.org.1 installiert. Die
Installation läuft zur Zeit unter tinkerbell.yoo.local/wordpress.

Soweit geht alles glatt, aber ein Fehler nervt zur Zeit besonders:
Wenn ich auf den Link 'Home' (unter Links) klicke, werde ich von der
obigen Adresse nach http://localhost/wordpress/ umgeleitet, was auf
dem Rechner selbst noch funktioniert, auf anderen Rechner sicher
nicht. Das PHP bzw. HTML selbst sieht unverdächtig aus:

lia href=?php bloginfo('url'); ? title=?php bloginfo('name'); ? 
Home/a/li
lia href=http://tinkerbell.yoo.local/wordpress; title=Slightly Addictive 
Home/a/li


Ich habe mich schon in meinen Einstellungen umgesehen, da finde ich
nichts passendes. Die Onlinedokumentation und Google waren bisher auch
nicht hilfreich.


Kennt einer von Euch dieses oder ein ähnliches Problem? Hat jemand
eine Idee, wie ich die Ursache besser eingrenzen könnte?


ich habe auch gestern mein erstes WordPress installiert, von
daher bin ich _ein wenig_ in der Materie drin.

Was steht denn in deiner httpd.conf beim Servernamen bzw.
auch in deiner /etc/hosts? In wordpress kam man soweit ich
es gesehen habe keinen ServerNamen  einstellen. Ich denke
das kommt vom Apachen...

Ich habe auf meinem vserver 2x wordpress laufen, jede in
einer eigenem virtualhost und die 'redirecten' einwandfrei.

hth
Thorsten


--
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/


Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Wordpress, php und mysql

[Klaus Zerwes]

Volker Katz wrote:

Moin,
ich versuche gerade mein Test-Wordpress auf meinen Server umzuziehen. Nur 
leider klappt das nicht so, wie ich mir das Vorgestellt habe. Im Moment hängt 
es wohl irgendwie an der Kombination von php und mysql (beides meine 
Spezialgebiete ;-).

Wenn ich Wordress per Browser aufrufe, bekomme ich folgende Meldung:
Your PHP installation appears to be missing the MySQL which is required for 
WordPress.
Ich habe mysql-server, php4 und php4-mysql installiert. Das Modul php4 ist im 
Apache enabled. 

Ich habe versucht der Sache auf den Grund zu gehen und habe die Code-Zeile, in 
der der Fehler produziert wird, gefunden:

if ( !extension_loaded('mysql') )
Tja, nur leider komme ich damit auch nicht weiter... habt Ihr da einen Tip für 
mich?


Gruß  Danke
  Volker


extension=mysql.so in der php.ini?
apache neu gestartet nach der installation von php4-mysql?

--
Klaus Zerwes
http://www.zero-sys.net


--
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/


Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Wordpress, php und mysql

[Volker Katz]

Moin,
Am Dienstag, 18. Oktober 2005 14:39 schrieb Klaus Zerwes:
  Ich habe mysql-server, php4 und php4-mysql installiert. Das Modul php4
  ist im Apache enabled.
 
  Ich habe versucht der Sache auf den Grund zu gehen und habe die
  Code-Zeile, in der der Fehler produziert wird, gefunden:
  if ( !extension_loaded('mysql') )
  Tja, nur leider komme ich damit auch nicht weiter... habt Ihr da einen
  Tip für mich?
 
  Gruß  Danke
    Volker

 extension=mysql.so in der php.ini?
 apache neu gestartet nach der installation von php4-mysql?
mein Fehler war wohl, dass ich nur den Apachen neu gestartet habe und nicht 
mysql!

Gruß  Danke
  Volker

Re: Wordpress, php und mysql

[Christian Correus]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 extension=mysql.so in der php.ini?
 apache neu gestartet nach der installation von php4-mysql?
 
 mein Fehler war wohl, dass ich nur den Apachen neu gestartet habe und nicht 
 mysql!
 
 Gruß  Danke
   Volker

Der MySQL-Server hat doch nix mit der php{3,4,5}-mysql extension zu
tuen, jedenfalls waere mir das neu. ;)

Gruß,
chris

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFDVRebNNQK9O2o5QgRAnAHAJ9U2Vj3YLuWszkN58QVAk+/hQ+5SwCfc4ii
mXza9LRhhOwxRd7phihB0Tw=
=nV5e
-END PGP SIGNATURE-


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Wordpress Multiple Blog Configuration

[Chris Purves]

On 20/08/05, Chris Purves [EMAIL PROTECTED] wrote:
 Hi,

 I just installed Wordpress and got it running.  In the README.Debian
 file there's a mention that the Debian configuration can support
 multiple blogs, but no instructions as how to accomplish that.

 From README.Debian:

 

  A little more about the (multiple blog) configuration

 The default wp-config.php searches for a (mysql) configuration filename based
 on the blog's host. This allows you to host more than one blog on a Debian
 system.

 

 The little more is all there is as far as I can tell.  Any help would
 be appreciated.  Perhaps I would be better off with the multiuser
 edition (not presently in Debian archive)?

 Thanks.

Okay, I got it working.  Here is what I did:

Apache2 setup:

I renamed /etc/apache2/sites-enabled/000-default to 002-default,
commented out the NameVirtualHost line and changed the VirtualHost *
line to VirtualHost *:80. I also added a line ServerName
www.mysite.com.  First few lines:

#NameVirtualHost *
VirtualHost *:80
ServerName www.mysite.com
ServerAlias mysite.com

ServerAdmin [EMAIL PROTECTED]



Then I added a file /etc/apache2/sites-enabled/001-wordpress (taken
from /usr/share/doc/wordpress/examples/apache.conf), containing

NameVirtualHost *:80

VirtualHost *:80
UseCanonicalNameOff
VirtualDocumentRoot /srv/www/%0
Options All

Directory /
   Options FollowSymLinks
   AllowOverride All
/Directory

/VirtualHost

Then I made sure the vhost_alias.load was included in mods-enabled. 
This allowed the site to work as before at www.mysite.com (and
mysite.com), but anything of the form something.mysite.com would be
handled by the 001-wordpress file.  For each blog I create a softlink
at /srv/www pointing to /usr/share/wordpress.

MySQL:

The /usr/share/doc/wordpress/examples/setup-mysql script was okay, but
it created a new database for every user.  I decided that I wanted to
have only one database with different table name prefixes.  What I
ended up doing was running the scipt once to create the initial
database, then deleting all the tables and and modifying the config
file created by the script. 
/etc/wordpress/config-person1.mysite.com.php looks like this:

?php
define('DB_NAME', 'wordpress');
define('DB_USER', 'wordpress');
define('DB_PASSWORD', 'ak2k3WE');
define('DB_HOST', 'localhost');

$table_prefix  = 'wp_person1_';

$server = DB_HOST;
$loginsql = DB_USER;
$passsql = DB_PASSWORD;
$base = DB_NAME;
?

When I want to add a new user I need only create a new link in
/srv/www, for example /srv/www/person2.mysite.com to point to
/usr/share/wordpress, then copy config-person1.mysite.com.php to
config-person2.mysite.com.php and change $table_prefix from
wp_person1_ to wp_person2_.

Final Considerations:

Now I have a setup that allows me to create a new blog by simply
adding a softlink and copying a file and changing a single parameter. 
I don't have to restart apache or run any scripts and I don't have to
worry about an endless number of databases being created.

Problems:  having one database may be a bit of a security risk and
also if the database is corrupted, it will affect all users, not just
one.  This is acceptable for me, as I plan to have frequent backups of
the file.

Also, allowing uploading is a bit of a problem.  I can set up each
user to point to a different place on the server to store their files,
but if they know the location of someone elses files, they could
change their settings and gain access.  I don't see this as a big
problem, but it's still something I would prefer to do without.

--
Take care, eh.
Chris

Re: Wordpress

[Andy Streich]

On Monday 29 August 2005 11:33 am, Roel Schroeven wrote:
 Either I don't understand what you're saying or you didn't understand 
 the linked website: this mailing list was added to Gmane already a long 
 time ago, and the link above links directly to its blog interface on Gmane.
 

Thanks, that wasn't clear to me.  Sadly, the interface looks so nice but is 
lacking at least 2 features I find essential, especially with the quantity of 
posts involved:

1.  There is not next at the bottom of the page.  Instead you have to go 
back to the top and click on a page number.

2.  Searching for wordpress didn't find anything on this thread.

If it is hard to navigate, doesn't have effective searching, but looks pretty, 
well, that's not a good solution for me.

One nice feature was that I could put in my email address and see what posts 
I've made which is quite useful when you are tracking down information 
related to problems you've been having.

Andy


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress

[Björn Lindström]

Andy Streich [EMAIL PROTECTED] writes:

 Agree. Hence the suggestion entailed a blog and the existing email
 list as two views on exactly the same data.

Gmane has something like this.

http://blog.gmane.org/gmane.linux.debian.user


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress

[Andy Streich]

On Monday 29 August 2005 01:15 am, Björn Lindström wrote:
 Andy Streich [EMAIL PROTECTED] writes:
 
  Agree. Hence the suggestion entailed a blog and the existing email
  list as two views on exactly the same data.
 
 Gmane has something like this.
 
 http://blog.gmane.org/gmane.linux.debian.user
 

Thanks, Bjorn, that's exactly what I had in mind and it was implemented 3 
years ago.

Any reason not to do add this mailing list to Gname?

Who could do it?

Andy

Re: Wordpress

[Roel Schroeven]

Andy Streich wrote:

On Monday 29 August 2005 01:15 am, Björn Lindström wrote:


Andy Streich [EMAIL PROTECTED] writes:



Agree. Hence the suggestion entailed a blog and the existing email
list as two views on exactly the same data.


Gmane has something like this.

http://blog.gmane.org/gmane.linux.debian.user




Thanks, Bjorn, that's exactly what I had in mind and it was implemented 3 
years ago.


Any reason not to do add this mailing list to Gname?

Who could do it?


Either I don't understand what you're saying or you didn't understand 
the linked website: this mailing list was added to Gmane already a long 
time ago, and the link above links directly to its blog interface on Gmane.


--
If I have been able to see further, it was only because I stood
on the shoulders of giants.  -- Isaac Newton

Roel Schroeven


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: wordpress (was Re: FW: call for a vote -- should debian-user mailing list replies go to author or to list?)

[Mark Crean]

On Sun, 2005-08-28 at 17:37 +0100, Jon Dowland wrote:
 On Sat, Aug 27, 2005 at 07:15:25PM -0700, Andy Streich wrote:
  
  Opensource blog software is pretty good these days and simple to set up (at 
 
 Argh wordpress 
 
 1) the WP release model is incompatible with debian's security release
policy, in much the same way mozilla is: http://bugs.debian.org/275814
 2) http://blog.php-security.org/archives/7-WordPress-update.html,
specifically update 2.
 
 -- 
 Jon Dowland   http://jon.dowland.name/
 FD35 0B0A C6DD 5D91 DB7A  83D1 168B 4E71 7032 F238
 
 

How about Drupal? It's available as a standard-issue deb though  more
recent versions are on the Drupal site. Drupal is a cms rather than pure
blogging software but according to their write-ups plugins can be used
to achieve this.

I suspect an important reason for the popularity of web boards is that
they provide a greater sense of community than a mailing list and
become, for some, a place to hang out. At present, though, I don't think
anyone's really cracked the problem with web boards, namely that mailing
lists are fast, simple and don't require a gui to use even though they
are less flexible than the boards in some respects. In addition, web
boards require quite a lot of oversight and maintenance, in my
experience, not to mention server resources. So someone would have to do
a lot of work.

:)

Fish


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: wordpress (was Re: FW: call for a vote -- should debian-user mailing list replies go to author or to list?)

[Andy Streich]

On Sunday 28 August 2005 04:18 pm, Mark Crean wrote:
 I suspect an important reason for the popularity of web boards is that
 they provide a greater sense of community than a mailing list and
 become, for some, a place to hang out. At present, though, I don't think
 anyone's really cracked the problem with web boards, namely that mailing
 lists are fast, simple and don't require a gui to use even though they
 are less flexible than the boards in some respects. 

Agree. Hence the suggestion entailed a blog and the existing email list as two 
views on exactly the same data.

 In addition, web 
 boards require quite a lot of oversight and maintenance, in my
 experience, not to mention server resources. So someone would have to do
 a lot of work.

To me that's the real problem.  

Frankly I have no hope for anything like this being implemented in the near 
future, but still want to advocate for it.  The mailing list is a tremendous 
resource.  For people in remote locations (like me) it's a necessary lifeline 
for using the Debain distro.  And if it is necessary to say, I'm not 
disparraging the mailing list.

Instead I have these dreams sometimes, probably inspired by the thought that 
the 100 or so emails I get on this list each day that contain lots of really 
useful information, and every single user of the list is likely working on a 
computer that individually has more power than all the computers I touched as 
an undergrad combined.  GNU/Linux is a wonderful collection of complex 
software and the Debian distro is magical.  Yet the one thing hasn't changed 
much in 30 years and that's the production of documentation and support 
information.  That sort of work rarely if ever gets the cudos that writting a 
few dozen lines of clever system code does even though it is just as 
(arguably more) critical -- especially at this stage in the GNU/Linux life 
cycle.

We all dream.

Andy


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress Multiple Blog Configuration

[Uwe Dippel]

On Sat, 20 Aug 2005 08:08:17 +0800, Chris Purves wrote:

 I just installed Wordpress and got it running.  In the README.Debian
 file there's a mention that the Debian configuration can support
 multiple blogs, but no instructions as how to accomplish that.

 The default wp-config.php searches for a (mysql) configuration filename based
 on the blog's host. This allows you to host more than one blog on a Debian
 system.

I guess this means something else; this means the one-install-per-user
solution as pointed out on wordpress site.

You might as well look into this for a less-than-one-install-per-user:

http://www.lauchlin.com/2005/05/15/multiple-wordpress-blogs-from-a-single-install/

Uwe




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wordpress Multiple Blog Configuration

[Hugo Vanwoerkom]

Chris Purves wrote:

Hi,

I just installed Wordpress and got it running.  In the README.Debian
file there's a mention that the Debian configuration can support
multiple blogs, but no instructions as how to accomplish that.


From README.Debian:




 A little more about the (multiple blog) configuration

The default wp-config.php searches for a (mysql) configuration filename based
on the blog's host. This allows you to host more than one blog on a Debian
system.



The little more is all there is as far as I can tell.  Any help would
be appreciated.  Perhaps I would be better off with the multiuser
edition (not presently in Debian archive)?



http://wordpress.org/support/topic/10726

HTH
H



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]