If I have an include with variables in it. If the value of that variable
changes with each loop, and I call the include in that loop, then the
content of the include will correspondingly change. So I can do a mail-merge
kind of thing.
If my loop is a mail merge and has lots of iterations, I break
Phil Wade at [EMAIL PROTECTED] wrote:
> The @include call limit is PER ACTION. It is 75 PER ACTION in Witango Server
> 5.5.
A 'You got it, wonder boy!' would've sufficed.
Wayne Irvine
Byte Services Pty Ltd
http://www.byteserve.com.au/
[EMAIL PR
Got it. I'm writing emails and wanting to use includes to create the body of
the emails. When I send 100 or more on a FOR loop, it hangs for this error.
If I read the include into a variable before the loop, I can't embed
variables that change in each loop.
I can work around now that I know how t
>>> If I have 2 includes, but they are in a loop that runs 20-100 times,
>>> does that put me over a max? (each loop creates an email)
>>
>> Yes. 2 x 100 = 200 calls to @INCLUDE
>
> If the loop is a For group containing an action repeating 100 times (as
> opposed to a <@FOR> metatag within a Resul
Phil Wade at [EMAIL PROTECTED] wrote:
>> If I have 2 includes, but they are in a loop that runs 20-100 times,
>> does that put me over a max? (each loop creates an email)
>
> Yes. 2 x 100 = 200 calls to @INCLUDE
If the loop is a For group containing an action repeating 100 times (as
opposed to
Roland,
There is an include (@INCLUDE) call limit of 20 PER ACTION in Witango Server
5.0. This is regardless of whether they are cached or not.
This limit was introduced as there were a high proportion of server
lockups linked to looping include files especially when used with
branches between taf
Hmmm Turning cache off didn't work, it turned itself back on whenever I
did a reloadconfig. Had to edit file, shut down witango and restart it to
turn cache off. That cleared the problem, not the include cache, but turning
off the main cache. I didn't realize that cache had become a problem..
Holy cow!
I turned caching off (and cache includes)
Restart witango
I still get these errors and they are cleared by purging cache
Getting errors in tafs that have but one include and don't loop. If I hit a
taf that has 1 include 3-4 times, it starts generating this error.
What's going on??
On
Is there a free upgrade of the Witango Server from v5.0 to v5.5?
Who qualifies?
How does one get the SN?
Thank you.
- Mihai
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
