require smileys to have whitespace on either side?, posted by Glenn Horton-Smith on Sat Mar 4 05:17:14 2006
|
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? |
|
Provide option to require smileys to be bracketed a la ELCode?, posted by Glenn Horton-Smith on Mon Mar 6 20:51:57 2006
|
| Stefan Ritt wrote: |
| 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.] ...
|
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...
|
Hmm, you're right. But I like EL Code, and I don't want to give it up just because of the smileys! A better solution would be to provide an option, which when set, would require smileys to be in brackets, e.g., [\8)] would become the cool smiley [8)], rendered without surrounding brackets if the option was set.
I actually just spent some time I didn't really have and modified my copy of elogd to see if it could be done and would work as intended. Eureka, it works! The modification implements an option "use bracketed smileys" which, if set to 1, causes the editor smiley bar to insert smileys with the square brackets around them and causes rsputs_elcode() to only substitute for smileys if there are square brackets around them, suppressing the square brackets.
I like this feature. Maybe others would like it too. I have a patch file (diff -cbw) w.r.t. svn version 1663 if you're interested. |
Synchronizing mirror causes corruption of logbook entries with multiple logbooks defined?, posted by Glenn Horton-Smith on Fri Aug 27 23:11:45 2010
|
We have been experiencing corruption of logbook entries by elogd mirror synchronization. Has anyone else encountered this? Is there a known cause and/or workaround for it?
Details
We have two elog servers set up with identical elogd.cfg and password files, except that one server has "Mirror server" pointing to the other host. There are three logbooks defined. (Their names are DoubleChooz, BigBrotherTable, and FlushingTable.) When the mirror synchronization happens, whether by "Mirror cron" or by an administrator hitting the "Synchronize all logbooks" link, it often happens that entries requiring synchronization are corrupted on both servers (not just the one to which the entry was copied). This is particularly likely to happen if entries have been made on both servers since the previous sync.
Looking at the logbook files themselves, we see that the corrupted entries will have attributes from the wrong logbooks. E.g., we'll see an empty "Barometer: " line in a DoubleChooz logbook file, where "Barometer" is an attribute that is only in the FlushingTable logbook, or we will see there are unexpected DoubleChooz logbook attributes in the FlushingTable files.
Strangely, the entries will not be identical on the two machines after syncing, and they stay non-identical on further syncs.
Most disturbingly, data is lost from entries that were perfectly valid before the sync, on both servers.
This was happening with elogd 2.7.8, and continued to happen after upgrading to 2.8.0. Both servers are running Linux. One is a 32-bit machine and another 64-bit, in case that might matter (but read on).
I made copies of both servers' files and ran two elogd servers on my Mac on different ports, compiled from a fresh checkout of 2.8.0, and the same behavior was observed as I repeatedly made test entries and synchronized. This suggests it isn't specific to Linux architecture, 64-bit or otherwise.
|
Proxy Error, posted by Glen MacLachlan on Wed Nov 5 20:37:37 2008
|
A problem recently developed for our elog...after running without much problem the elog daemon was restarted on an ubuntu server running apache2. Now the server gives 502 Proxy Error messages:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /elog.
Reason: Error reading from remote server
I did a force-reload of apache after making sure the modules are enabled. I also restarted elogd but to no avail. One symptom seems to be that the GET request is empty...that is before it was:
"GET /elog/sample_elog/etcetera HTTP/1.1"
but now it is just
"GET /elog HTTP/1.1"
Just started out of the blue...
Any ideas? |
text area height, posted by Giuseppe Cucinotta on Fri Jun 1 17:08:48 2018
|
Hi,
I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum height of the text box fixed (for instance 500px) is by far more useful of viewing the attachment box (we know it is down scrolling the page :) ). We know it is possible to resize the text box using the mouse but doing this every time one creates a new entry can be annoying. Setting a default minimum size would be more confortable. Is it possible to do this?
Thank you
Beppe |
Re: text area height, posted by Giuseppe Cucinotta on Tue Jun 5 15:06:18 2018 
|
I tried with Message Height = 100 inside the conifguration of my logbook, but nothing changed as you can see in the first picture...
What I'm looking for is a way, if possible, to start by default with a wider message box, someting like fig2. For our purpose, using wide tables, it would be very useful to have a wider message box in order to have a full look to the message content, and also having it by default without modifying it by hand with the mouse every time we submit something to elog.
Beppe
| Stefan Ritt wrote: |
|
Have you tried
Message height = ...
unit is number of text lines.
Stefan
| Giuseppe Cucinotta wrote: |
|
Hi,
I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum height of the text box fixed (for instance 500px) is by far more useful of viewing the attachment box (we know it is down scrolling the page :) ). We know it is possible to resize the text box using the mouse but doing this every time one creates a new entry can be annoying. Setting a default minimum size would be more confortable. Is it possible to do this?
Thank you
Beppe
|
|
|
|
Pinned entry, posted by Giuseppe Cucinotta on Thu Apr 18 12:29:05 2019
|
Hi everybody,
sorry if this question has already been posed (I did a quick search but I didn't found anything): elog sorts entry by ID, I wonder if it is possible to pin an entry in order to be always on top of the page independently on its ID.
Thanks
Giuseppe |
|
Re: Pinned entry, posted by Giuseppe Cucinotta on Tue Apr 23 11:02:32 2019
|
Thank you very much! It worked great!
Beppe
| Stefan Ritt wrote: |
|
This is not directly possible, but you can configure it with a trick. Create an attribute "pinned", make it of type "boolean", and set the start page such that it sorts using the "pinned" attribute:
Atributes = ..., Pinned
Options Pinned = boolean
Start page = ?rsort=Pinned
This move all entries where "Pinned" is true to the top of the list.
Stefan
| Giuseppe Cucinotta wrote: |
|
Hi everybody,
sorry if this question has already been posed (I did a quick search but I didn't found anything): elog sorts entry by ID, I wonder if it is possible to pin an entry in order to be always on top of the page independently on its ID.
Thanks
Giuseppe
|
|
|
|