Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Theme resets periodically

Received: by 10.100.131.19 with SMTP id e19mr255607and.9.1299122916003;
        Wed, 02 Mar 2011 19:28:36 -0800 (PST)
X-BeenThere: habari-users@googlegroups.com
Received: by 10.100.56.38 with SMTP id e38ls95583ana.3.p; Wed, 02 Mar 2011
 19:28:34 -0800 (PST)
Received: by 10.100.171.12 with SMTP id t12mr253600ane.42.1299122914606;
        Wed, 02 Mar 2011 19:28:34 -0800 (PST)
Received: by 10.100.171.12 with SMTP id t12mr253599ane.42.1299122914589;
        Wed, 02 Mar 2011 19:28:34 -0800 (PST)
Return-Path: <ch...@doesnthaveone.com>
Received: from smtp115.dfw.emailsrvr.com (smtp115.dfw.emailsrvr.com [67.192.241.115])
        by gmr-mx.google.com with ESMTPS id a26si231620ana.5.2011.03.02.19.28.33
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 02 Mar 2011 19:28:33 -0800 (PST)
Received-SPF: pass (google.com: domain of ch...@doesnthaveone.com designates 67.192.241.115 as permitted sender) client-ip=67.192.241.115;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ch...@doesnthaveone.com designates 67.192.241.115 as permitted sender) smtp.mail=ch...@doesnthaveone.com
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp11.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 417A7D07D5
	for <habari-users@googlegroups.com>; Wed,  2 Mar 2011 22:28:33 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp11.relay.dfw1a.emailsrvr.com (Authenticated sender: chris-AT-doesnthaveone.com) with ESMTPSA id EB3A7D058C
	for <habari-users@googlegroups.com>; Wed,  2 Mar 2011 22:28:32 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: [habari-users] Re: Theme resets periodically
From: Chris Meller <ch...@doesnthaveone.com>
In-Reply-To: <6dbf7e73-1fab-4297-a5bd-dbeaa5854f37@k10g2000prh.googlegroups.com>
Date: Wed, 2 Mar 2011 22:28:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF5D96C2-599B-4A47-95C3-7F6DDD4DBB60@doesnthaveone.com>
References: <d050fd47-d273-4746-ae83-6c40316480bd@n11g2000vbm.googlegroups.com> <BE94B45E-344B-4E66-97D2-83ABDDA1E...@doesnthaveone.com> <6dbf7e73-1fab-4297-a5bd-dbeaa5854...@k10g2000prh.googlegroups.com>
To: habari-users@googlegroups.com
X-Mailer: Apple Mail (2.1082)

I noticed the errors Charcoal throws the other day. When Habari falls =
back to it it's not calling Charcoal's activation hook properly, so its =
options aren't set properly. No bid deal, there's a ticket filed for =
that.

None of those plugins should cause a problem, so I'm perplexed. Are =
there no errors in the log around the time this seems to happen?


On Mar 2, 2011, at 9:38 PM, Brian Ramsay wrote:

> On both the main and development site I have
>=20
> AutoParagraph 0.9
> Core Dash Modules 1.0
> Flickr Media Silo 1.0
> Habari Media Silo 1.0.1
> Pingback 1.0
> Spam Checker 1.0
> a custom one of my own (adds two buttons to edit entry screen)
>=20
> Something I noticed today that may help:
> The Charcoal theme after changing throws a lot of errors.  I think
> it's a long list of 'index xxxx is not set' errors - when it happens
> again I will post the errors.  However, if I manually switch to the
> Charcoal theme it doesn't have any errors.  Not sure what's up there.
>=20
> Thanks,
> Brian
>=20
>=20
>=20
>=20
> On Mar 2, 5:38 pm, Chris Meller <ch...@doesnthaveone.com> wrote:
>> The only time the active theme is deactivated and the default =
substituted in its place should be when the active theme no longer =
exists (or can't be read because of permissions, etc.). I've no idea why =
they might be causing an issue, but let's start with the obvious: What =
plugins do you have activated?
>>=20
>> On Mar 1, 2011, at 6:35 AM, Brian Ramsay wrote:
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>> I am having a strange issue with habari where the theme resets to =
the
>>> Charcoal theme seemingly at random.  Probably once a day I have to
>>> change the theme back to my custom theme.  I have a development site
>>> and a main site, both using the 0.7-rc2 tag and the same version of =
my
>>> custom theme, and I only see this behavior on the main site.
>>=20
>>> Not sure if seeing the site will help, but the one with the problem =
is
>>> http://foont.net, vshttp://dev.foont.netwhich is fine.
>>=20
>>> I thought it might have something to do with whether or not I was
>>> logged in, but after investigating that doesn't seem the case.  =
Could
>>> there be a difference in the database that would matter?  I can't
>>> really think what would cause the theme to stay set for a while, and
>>> then revert.
>>=20
>>> Any ideas?
>>=20
>>> Brian
>>=20
>>> --
>>> To post to this group, send email to habari-users@googlegroups.com
>>> To unsubscribe from this group, send email to =
habari-users-unsubscribe@googlegroups.com
>>> For more options, visit this group =
athttp://groups.google.com/group/habari-users
>=20
> --=20
> To post to this group, send email to habari-users@googlegroups.com
> To unsubscribe from this group, send email to =
habari-users-unsubscribe@googlegroups.com
> For more options, visit this group at =
http://groups.google.com/group/habari-users