Re: restrict access, posted by Gerald Ebberink on Mon Jul 17 13:20:07 2006
|
| Stefan Ritt wrote: |
| Gerald Ebberink wrote: | | As you can see, I have implemented a temporary fix in the way of allowing only certain hosts access. But where does this Internal error come from. |
I only can identify this error if you send me your current ("de-sensified") elogd.cfg. |
I have just installed the svn version of elog, and the problem has been fixed.
Thank you very much! |
|
Re: restrict a field to upper or lower case, posted by Stefan Ritt on Mon Jan 26 19:48:42 2009
|
| lisa giaime wrote: |
|
Is it possiblet to restrict a field so that when a new record is added, whatever the user types is automatically converted to lower case?
|
No, this is not possible. |
|
Re: resending information confirmation box after refresh interval, posted by Stefan Ritt on Tue Nov 17 08:33:15 2015
|
Start with the demo example configuration, add one line after the other from your config, and figure out which is the offending statement in your config, then post a minimal configuration here which triggers the problem.
| Ken Ludington wrote: |
|
After submitting a new post, if the page is left completely alone,, it will after a few minutes prompt that the page needs to resend information.
This is the same prompt you'd get if you attempt to refresh a page that had session variables passsed to it. Example is attached.
Is there something in my config that could cause this? This is a fresh install of the latest verison however my elogd.cfg file has been migrated throuh many installs over many versions, so it's very possible this is something following along.
thanks.
|
|
|
Re: require smileys to have whitespace on either side?, posted by Stefan Ritt on Mon Mar 6 13:50:07 2006
|
| Glenn Horton-Smith wrote: | It would be nice if elog would only interpret something as a smiley if it is surrounded by whitespace. It can be particularly annoying that an 8 followed by a right paren becomes a "cool" smiley -- e.g., a parenthetical reference to event eighteen (18) becomes mangled... [That was "18" inside the parens.]
Is there already a way to solve this issue (other than always previewing your entries and adding spaces before parans)? Is the feature hard to implement? |
Interpreting smileys only if they are surrounded by whitespace does not solve the problem completely. It will solve it for (1\8), but not if you have (1, \8) (1, 9) in your text. So it's not a good solution. If you have problems with simleys, I would post my text in plain mode, or surround your numbers with [code]...[/code] tags. If you write
[code](1\8)[/code]
then it will look like
(18)
which should be fine. |
|
Re: repository of elog configuration files, posted by Stefan Ritt on Mon Feb 7 10:00:42 2005
|
> Is there a repository of elog configuration files for newbies to lookup and
> learn ? I have seen the 'contributions' elog - useful as it is ... it is not
> much. I would appreciate if someone can point out such a site where people
> have contributed their elog configuration files.
Have a look at the elog:Config+Examples. The configuration of this Forum for
example is there, covering most of the available options.
- Stefan |
|
Re: reply option in elog client not working, posted by Gerald Ebberink on Wed Sep 6 12:02:52 2006
|
| Today I found, I have the same problem with editing the log (with the -e option) |
Re: reply option in elog client not working, posted by Gerald Ebberink on Thu Sep 7 08:01:37 2006 
|
I have made patch witch solves the problem partialy.
If there are not no attachments this patch works.... (But since I have attachments I'll have to dig in deeper in the code.
Attached you will find the diff. |
|
Re: reply option in elog client not working, posted by Gerald Ebberink on Thu Sep 7 17:17:17 2006
|
| Gerald Ebberink wrote: | I have made patch witch solves the problem partialy.
If there are not no attachments this patch works.... (But since I have attachments I'll have to dig in deeper in the code.
Attached you will find the diff. |
Now I am digging deeper, and I have a question:
In the function retrive_elog near line 427 a start is made with putting the attributes in an array.
As far as I can see there is no exception for the Attachment attribute. Where this attribute can be very large (e.g. many files attached) and overrun to the boundary variable (in the function submit_elog function). At least that is where I find end of my attachment string.
Could Mr. Ritt please shine some light on this, becouse I |