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
On Thu, Nov 28, 2013 at 11:08 AM, Jerry Stuckle 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 m
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, an
On Nov 27, 2013, at 11:52 PM, Scott Ferguson
wrote:
> On 28/11/13 18:31, Rick Thomas wrote:
>>
>> On Nov 27, 2013, at 8:12 PM, Miles Fidelman
>> wrote:
>>
>>> Scott Ferguson wrote:
The OP (in this thread) is asking about the Debian WordPress
package. It installs WordPress, WordPres
On 28/11/13 18:31, Rick Thomas wrote:
>
> On Nov 27, 2013, at 8:12 PM, 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
On Nov 27, 2013, at 8:12 PM, 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 install
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
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
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):-
***
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..."
>
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.
--
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 potent
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 "ol
On 27/11/13 23:16, Chris Davies wrote:
> Rick Thomas 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 al
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 bo
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.
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 backpo
Rick Thomas 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
On Jun 21, 2012, at 1:02 PM, Glenn English 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,
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
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,
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
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 sh
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" p
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 c
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 Ap
26 matches
Mail list logo
