[ingo] Sieve scripts not getting activated on save?

[Darrell Budic]

In the fine art of following up on something a year later, I finally located my problem. I had a corrupt prefs.local.conf that was failing to load and caused my preference settings to be unavailable in the ingo module. Removing it has resolved the problem and my scripts activate properly now.

  -Darrell

On Aug 4, 2011, at 3:11 AM, Jan Schneider wrote:

> Please keep discussions on the list.
> 
> Zitat von Darrell Budic <budic at onholyground.com>:
> 
>> On Aug 3, 2011, at 2:46 PM, Jan Schneider wrote:
>> 
>>> 
>>> Zitat von Darrell Budic <budic at onholyground.com>:
>>> 
>>>> On Aug 3, 2011, at 11:40 AM, Jan Schneider wrote:
>>>> 
>>>>> 
>>>>> Zitat von Darrell Budic <budic at onholyground.com>:
>>>>> 
>>>>>> On Jul 28, 2011, at 2:49 AM, Jan Schneider wrote:
>>>>>> 
>>>>>>> 
>>>>>>> Zitat von Darrell Budic <budic at onholyground.com>:
>>>>>>> 
>>>>>>>> Did something change in the last ingo update? I had thought that sieve scripts would upload and activate when you make changes like saving a new vacation script, but in the latest update (2.0.3, using sieve against a cyrus backend) this doesn't seem to happen. You can go into the script and compare the currently active to the currently script, and activate it from there. I don't want to have to train users to do this though. Did I just miss a preference or setting someplace to have this happen automatically?
>>>>>>> 
>>>>>>> It's a preference, but it has always been one, and it seems to still work fine here.
>>>>>>> 
>>>>>>> Jan.
>>>>>> 
>>>>>> Yeah, that's what I thought. I think I have some messed up permissions for Ingo somewhere, but I'm not finding it and not sure where to look. Is this an Administrative setting for Ingo or a User Preference for Ingo?
>>>>> 
>>>>> Why don't you take a look yourself? :) It's a user pref.
>>>>> 
>>>>> Jan.
>>>> 
>>>> Can't quite decipher the code that well yet :) Getting better at it slowly...
>>> 
>>> I was talking about the interface, not the code.
>>> 
>>>> But ingo claims not to have any user prefs on my install, which is why I think I have some corruption in a backend somewhere. Hopefully I can track it down now that I know more where to look.
>>> 
>>> You don't even use a filter backend that uses scripts then. There is no script to activate.
>> 
>> I use sieve. I thought that was script based, and led to my confusion that I could view the script from the script icon, but had to active it manually. Should I send up some screen shots, it sounds like I'm not explaining this well.
> 
> Are you saying you *do* see the script icon or not? If you don't, you are not using a Sieve backend. If you do, but don't have any preferences in Ingo, something is broken.
> 
> Jan.
> 
> -- 
> Do you need professional PHP or Horde consulting?
> http://horde.org/consulting/
> 
> -- 
> Ingo mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org