Re: Buttons missing in ckeditor, posted by Roland Beyer on Fri Oct 12 11:56:26 2018
|
Dear Stefan,
thanks for your hints. Meanwhile we already solved the problem. I think it was caused by the recovery from a backup version after the server
crash ... and the retirement of the person who did the previous installation. |
Re: Bugs with 2.3.5, posted by Stefan Ritt on Wed Apr 9 13:58:59 2003
|
> Forgot password option generates an error message
Which error? Can you be more specific. I tried it myself with this forum and
|
Re: Bugs with 2.3.5, posted by nickc1 on Wed Apr 9 15:50:38 2003
|
> > Forgot password option generates an error message
>
> Which error? Can you be more specific. I tried it myself with this forum
|
Re: Bugs with 2.3.5, posted by Stefan Ritt on Wed Apr 9 16:06:31 2003
|
> Error sending Email
> Please use your browser's back button to go back
|
Re: Bugs in newer updates w/ Debian install?, posted by Stefan Ritt on Wed Jul 28 21:49:32 2004
|
> I just updated ELOG using the latest elogd.c, and now my Quick Filters seem
> to stop working after the first or second filter attempt.
|
Re: Bugs in newer updates w/ Debian install?, posted by Todd Corsa on Wed Jul 28 22:12:03 2004
|
> > I just updated ELOG using the latest elogd.c, and now my Quick Filters seem
> > to stop working after the first or second filter attempt.
>
|
Re: Bug? Password file location changed, posted by David Spindler on Thu Nov 2 18:10:07 2006
|
[quote="David Spindler"]I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid.
I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password
file in a different location.
|
Re: Bug? Password file location changed, posted by Steve Jones on Thu Nov 2 23:17:10 2006
|
[quote="David Spindler"][quote="David Spindler"]I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my
password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was
creating a new empty password file in a different location.
|