ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 332 of 807

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6454 Entries

Goto page Previous 1, 2, 3 ... 331, 332, 333 ... 805, 806, 807 Next

Mon Dec 17 21:49:54 2012

Hal Proctor wrote:

Stefan Ritt wrote:

Hal Proctor wrote:

Any reason why when I click "Reply" to a previous submission that the body is full of HTML code?

See below:

<p>
<table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;">
<tbody>
<tr>
<td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Hal Proctor wrote:</td></tr>
<tr>
<td cellpadding="10px" style="background-color:#FFFFB0;"><p>
<table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;">
<tbody>
<tr>
<td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Quote:</td></tr>
<tr>
<td cellpadding="10px" style="background-color:#FFFFB0;">removed the thing and the other thing....added this and that!</td>
</tr>
</tbody>
</table>
</p><p> </p>
testing reply</td>
</tr>
</tbody>

Here is my logbook config:

[Logbook]
Theme = default
Comment = Maintenance Logbook
Attributes = Author, Type, Category, Subject, Shift
Options Type = Repair, Routine, Preventative, Other
Options Category = Emergency, General, Change-Over, Other
Options Shift = 1, 2, 3
Extendable Options = Category
Required Attributes = Author, Type
Page Title = Maint Log - $subject
Reverse sort = 1
Preset Author = $long_name
Preset on reply Author = $long_name
Locked Attributes = Author
Quick filter = Date, Type, Category

I don't see any mistake in the configuration file. Did you switch the "Encoding" from HTML to plain? (Radio buttons at the bottom just below the text window). Is there a problem with your FCKEditor? Do you see the formatting menu bar?

I do not get the formatting menu with HTML. I switched to plain and code still exists. The only formatting menu I get is when I choose ELCode. I have no problem with this forum seeing the formatting menu with HTML (although it does take some time to load).

Tested it in Chrome and acts the same as IE8 (just much slower)

It's version issue!! 2.92 does not utilize FCKeditor correctly. Backed off one version and it works fine! 2.91 is GOOD!

67405

Tue Dec 18 12:09:38 2012

Andreas Luedeke

andreas.luedeke@psi.ch

Hal Proctor wrote:

Stefan Ritt wrote:

Hal Proctor wrote:

Any reason why when I click "Reply" to a previous submission that the body is full of HTML code?

See below:

Here is my logbook config:

Tested it in Chrome and acts the same as IE8 (just much slower)

It's version issue!! 2.92 does not utilize FCKeditor correctly. Backed off one version and it works fine! 2.91 is GOOD!

Actually I can confirm a similar issue with 2.9.2:

when I create a new entry with the default "HTML" encoding and then swap to "plain", the text area is cluttered with HTML code (see attachment new_entry.txt)

I did notice it, but I did not pay much attention to it. But I agree is should be fixed. But in my case it could be related to a firefox add-on "It's all text" that uses java script to modify the HTML code.

Andreas

Attachment 1: new_entry.txt

<div style="position: fixed; display: none; z-index: 2147480000; background-color: rgb(255, 255, 204); padding: 6px; color: rgb(0, 0, 0); border-radius: 7px 7px 7px 7px; font-size: 12px; max-width: 400px; font-family: Arial,Helvetica,sans-serif; line-height: 100%; text-align: left; border-style: none; border-width: 1px; border-color: rgb(0, 0, 0); opacity: 1;">&nbsp;</div>
<div style="display: none; position: fixed; max-height: 438px; width: 450px; padding: 3px; border-width: 0px 0px 2px 2px; border-style: dashed; border-color: grey; border-radius: 0px 0px 0px 5px; background-color: rgb(255, 255, 255); overflow: auto; min-height: 200px; z-index: 2147479999; text-align: center; color: rgb(0, 0, 0); right: 0px; top: 0px;"><textarea style="height: 80px; width: 444px; border: 1px solid grey; padding: 2px;" id="itsalltext_generated_id__1"></textarea><img src="chrome://itsalltext/locale/gumdrop.png" title="It's All Text!" style="cursor: pointer ! important; display: none ! important; position: absolute ! important; padding: 0pt ! important; margin: 0pt ! important; border: medium none ! important; width: 28px ! important; height: 14px ! important; opacity: 0.0152174 ! important;" alt="" /><select>
<option value="af">Afrikaans</option>
<option value="sq">Albanian</option>
<option value="ar">Arabic</option>
<option value="hy">Armenian</option>
<option value="az">Azerbaijani</option>
<option value="eu">Basque</option>
<option value="be">Belarusian</option>
<option value="bg">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="zh-CN">Chinese (Simplified)</option>
<option value="zh-TW">Chinese (Traditional)</option>
<option value="hr">Croatian</option>
<option value="cs">Czech</option>
<option value="da">Danish</option>
<option selected="selected" value="auto">Detect language</option>
<option value="nl">Dutch</option>
<option value="en">English</option>
<option value="et">Estonian</option>
<option value="tl">Filipino</option>
<option value="fi">Finnish</option>
<option value="fr">French</option>
<option value="gl">Galician</option>
<option value="ka">Georgian</option>
<option value="de">German</option>
<option value="el">Greek</option>
<option value="ht">Haitian Creole</option>
<option value="iw">Hebrew</option>
<option value="hi">Hindi</option>
<option value="hu">Hungarian</option>
<option value="is">Icelandic</option>
<option value="id">Indonesian</option>
<option value="ga">Irish</option>
<option value="it">Italian</option>
<option value="ja">Japanese</option>
<option value="ko">Korean</option>
<option value="la">Latin</option>
<option value="lv">Latvian</option>
<option value="lt">Lithuanian</option>
<option value="mk">Macedonian</option>
<option value="ms">Malay</option>
<option value="mt">Maltese</option>
<option value="no">Norwegian</option>
<option value="fa">Persian</option>
<option value="pl">Polish</option>
<option value="pt">Portuguese</option>
<option value="ro">Romanian</option>
<option value="ru">Russian</option>
<option value="sr">Serbian</option>
<option value="sk">Slovak</option>
<option value="sl">Slovenian</option>
<option value="es">Spanish</option>
<option value="sw">Swahili</option>
<option value="sv">Swedish</option>
<option value="th">Thai</option>
<option value="tr">Turkish</option>
<option value="uk">Ukrainian</option>
<option value="ur">Urdu</option>
<option value="vi">Vietnamese</option>
<option value="cy">Welsh</option>
<option value="yi">Yiddish</option>
</select><span style="font-weight: bold; cursor: pointer; color: lightgrey;">⇄</span><select>
<option value="af">Afrikaans</option>
<option value="sq">Albanian</option>
<option value="ar">Arabic</option>
<option value="hy">Armenian</option>
<option value="az">Azerbaijani</option>
<option value="eu">Basque</option>
<option value="be">Belarusian</option>
<option value="bg">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="zh-CN">Chinese (Simplified)</option>
<option value="zh-TW">Chinese (Traditional)</option>
<option value="hr">Croatian</option>
<option value="cs">Czech</option>
<option value="da">Danish</option>
<option value="nl">Dutch</option>
<option selected="selected" value="en">English</option>
<option value="et">Estonian</option>
<option value="tl">Filipino</option>
<option value="fi">Finnish</option>
<option value="fr">French</option>
<option value="gl">Galician</option>
<option value="ka">Georgian</option>
<option value="de">German</option>
<option value="el">Greek</option>
<option value="ht">Haitian Creole</option>
<option value="iw">Hebrew</option>
<option value="hi">Hindi</option>
<option value="hu">Hungarian</option>
<option value="is">Icelandic</option>
<option value="id">Indonesian</option>
<option value="ga">Irish</option>
<option value="it">Italian</option>
<option value="ja">Japanese</option>
<option value="ko">Korean</option>
<option value="la">Latin</option>
<option value="lv">Latvian</option>
<option value="lt">Lithuanian</option>
<option value="mk">Macedonian</option>
<option value="ms">Malay</option>
<option value="mt">Maltese</option>
<option value="no">Norwegian</option>
<option value="fa">Persian</option>
<option value="pl">Polish</option>
<option value="pt">Portuguese</option>
<option value="ro">Romanian</option>
<option value="ru">Russian</option>
<option value="sr">Serbian</option>
<option value="sk">Slovak</option>
<option value="sl">Slovenian</option>
<option value="es">Spanish</option>
<option value="sw">Swahili</option>
<option value="sv">Swedish</option>
<option value="th">Thai</option>
<option value="tr">Turkish</option>
<option value="uk">Ukrainian</option>
<option value="ur">Urdu</option>
<option value="vi">Vietnamese</option>
<option value="cy">Welsh</option>
<option value="yi">Yiddish</option>
</select>
<div style="text-align: left; background-color: rgb(235, 239, 249);">Detect language &raquo; English</div>
<div style="width: 444px; max-width: 444px; padding: 2px; min-height: 80px; border-width: 1px; border-style: solid; border-color: grey; background-color: rgb(255, 255, 255); text-align: justify;">&nbsp;</div>
</div>

67114

Mon Sep 5 17:10:19 2011

mike cianci wrote:

I have a logbook with data in it that I need to rename and preserve the the existing data (old book) in the newly named book (i.e. can I move all of the data from one book to a new book and than delete the data from the original book)?

As always thank you for your time.

There are two ways:

1) Create a new logbook, add the "Copy to" command to the old logbook. Select all entries and copy them to the new logbook, and delete the old one.

2) Change the logbook name in elogd.cfg, by manually editing the file, then rename the subdirectory in your file system from the old to the new name, then restart elogd.

The second solution is much simpler, but you have to manipulate files and directories yourself.

Whatever you do, make sure to back up you files before any operation.

67125

Fri Sep 23 01:16:30 2011

mike cianci

mike2.cianci@comcast.net

Stefan Ritt wrote:

mike cianci wrote:

As always thank you for your time.

There are two ways:

1) Create a new logbook, add the "Copy to" command to the old logbook. Select all entries and copy them to the new logbook, and delete the old one.

2) Change the logbook name in elogd.cfg, by manually editing the file, then rename the subdirectory in your file system from the old to the new name, then restart elogd.

The second solution is much simpler, but you have to manipulate files and directories yourself.

Whatever you do, make sure to back up you files before any operation.

Sorry, about this dumb question but with "Copy to = <logbook list> " what is the format of <logbook list>?

Is it just the "logbook Name" or is it the actual path name "http://something/somethingelse"?

67126

Fri Sep 23 10:46:58 2011

David Pilgram

David.Pilgram@epost.org.uk

mike cianci wrote:

Stefan Ritt wrote:

mike cianci wrote:

As always thank you for your time.

There are two ways:

1) Create a new logbook, add the "Copy to" command to the old logbook. Select all entries and copy them to the new logbook, and delete the old one.

2) Change the logbook name in elogd.cfg, by manually editing the file, then rename the subdirectory in your file system from the old to the new name, then restart elogd.

The second solution is much simpler, but you have to manipulate files and directories yourself.

Whatever you do, make sure to back up you files before any operation.

Sorry, about this dumb question but with "Copy to = <logbook list> " what is the format of <logbook list>?

Is it just the "logbook Name" or is it the actual path name "http://something/somethingelse"?

In order to copy (or move) files from one logbook to another, you first need to ensure that the
appropriate commands are in the section of elogd.cfg of the logbook the files move *from* (called 'current')

- made up elogd.cfg to show this, and obviously only the pertinant lines

[Global]

Group = current, Y2011, Y2010, Y2009...

...

[current]
...
Menu commands = New, ... Copy to, ...
...
Copy to = Y2011, Y2010, Y2009 ...
...
- end of made up example.

So to solve your problem, the <logbook list> is simply the list of logbooks in
this part of elogd.cfg after the 'Copy to =' line in the elogd.cfg file (Y2011, Y2010, Y2009...)

You also need to ensure that the directory to which the entries are to be copied to exists!

('Move to' would be faster if you are going to delete the entries in 'current' afterwards, but as always, it depends on

your perception of risk.)

For the user, the logbook list is the set of logbooks that appear in the
drop-down menu by the side of "Copy to" in the menu bar, and it allows you to
move that entry (or thread of entries if more than one) to the selected destination.

---

My reason for answering this is because I have actually done this operation 'in
anger' some time ago and regularly since, and would have answered before if Stafan had not beaten me
to it. I used what was Stefan's second method, which, for those who are
reasonably confident with file manipulation, is far faster, and, dare I say,
less prone to 'unexpected' issues - some here will know what I'm
getting at.

So I say, "Back up your files and take the plunge", I would have put something
else but this is a family friendly forum.

But you must bear in mind my views are those seen through the filter of a
regular Elog ab-user, which may be why Stefan worked so hard to answer before
me ;-)

Anyway, Stefan <i>et al</i> have got CERN's faster-than-light particle problem to deal with this morning.

67130

Mon Sep 26 11:34:36 2011

David Pilgram wrote:

Anyway, Stefan <i>et al</i> have got CERN's faster-than-light particle problem to deal with this morning.

I would be too lucky if I just could fix this as I fix some ELOG problems! I guess hundreds of physicists right now are pondering about what could have gone wrong in data taking, because nobody really believes that this is a real effect.

67135

Fri Sep 30 22:38:43 2011

mike cianci

mike2.cianci@comcast.net

Stefan Ritt wrote:

David Pilgram wrote:

Anyway, Stefan <i>et al</i> have got CERN's faster-than-light particle problem to deal with this morning.

Got it to work, manipulating the files was not that hard once I got over the FEAR factor. Good luck with the speed of light thing.

67136

Fri Sep 30 22:55:01 2011

David Pilgram

David.Pilgram@epost.org.uk

mike cianci wrote:

Stefan Ritt wrote:

David Pilgram wrote:

Anyway, Stefan <i>et al</i> have got CERN's faster-than-light particle problem to deal with this morning.

Got it to work, manipulating the files was not that hard once I got over the FEAR factor. Good luck with the speed of light thing.

Well done Mike!

One result is that I've also learnt things, realised that there are some known unknowns and perhaps some unknown unknowns in my

understanding of Elog.

Goto page Previous 1, 2, 3 ... 331, 332, 333 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6