[Maia-users] digest confirm action and other setting updates

[Munroe]

while I am not against upgrading to the trunk version, I have 2 
questions about that. First this server is a production server is it 
safe? Second how does one do that? :)  While I am pretty competent 
administering a system I have never worked on a collaboration project 
where versioning was important so have not been exposed to either cvs or 
svn, any walk through or how to would be helpful.  Thanx

David Morton wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Nov 30, 2006, at 3:41 PM, Munroe wrote:
>
>> I have noticed a couple quirky things, first I am running 1.0.1:
>>
>> Whenever I receive a digest and click on "confirm all items" it opens up
>> a blank webpage, but it does successfully confirm all of the mail.
>>
>> The url it tries to open is:
>>
>> http://<my.domain.com>/filter/confirm.php?id=4&ts=2006-11-30%2016:36:13&token=d29ef22f8c914cb3b4a6d2498b172595CE4AC44A1XU3QCR3VTIDT623P5TS4JML 
>>
>>
>> is this normal? or should it bring you into the maia interface?
>
>
> Yes, that's normal... the token logs you directly and preforms the 
> action without needinig a password.  It expires immediately after  
> being used, though so you cant use that URL again.
>
>
>>
>> Secondly I notice that when i update various things ( so far I have only
>> noticed in in the admin section), when I click "update settings" it
>> brings me to a url like http://my.domain.com/filter/xadmin.php
>>
>> and the page is blank, if I remove the "x" it loads the admin section
>> again and I can go about my business, I feel like these might be
>> related, everything is working, all of the actions associated with
>
> Yes they are related.   Something is triggering a debug warning, which 
> is usually shown in a popup window, but these two pages are designed 
> to be transient pages which issue an http redirect; they aren't 
> supposed to display anything.   But since they *do* send some data for 
> that debug popup, the http header redirect fails, and you end up with 
> a blank page.
>
> To fix this, we need to look at a couple of things.  First, a recent 
> fix in trunk that fixes debugging and allows you to turn it off. see:
> https://secure.renaissoft.com/maia/ticket/354
> https://secure.renaissoft.com/maia/changeset/1072
> https://secure.renaissoft.com/maia/changeset/1073
>
> For a quick workaround, read: 
> http://www.renaissoft.com/pipermail/maia-users/2006-July/006952.html
>
> Once that is done, I think it should operate ok, though there are some 
> debug notices that we would like to see.  Look in your web server 
> error_log and see if it shows anything useful; we may be able to track 
> down a small bug with that.
>
>
>
>
>
> David Morton
> Maia Mailguard http://www.maiamailguard.com
> mortonda at dgrmm.net
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD4DBQFFb2ShUy30ODPkzl0RAsHVAJj5WG8gTpRxSkpV5YLIHoaLYtf1AKChsk+m
> dD8y4OxlZ3nKobyXi3maTQ==
> =0LLt
> -----END PGP SIGNATURE-----
>
>