Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 451 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  66114   Sun Dec 14 17:04:24 2008 Question mike ciancimike2.cianci@comcast.netQuestionWindows2.7.5-2140Grouping Logbooks

I really appreciate your help and I hope that my questions warrant your time.

What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.

Three logbooks

Logbook A

Logbook B

Logbook C (just informational, write protected)

Two Groups

Top Group 1 = Logbook A, Logbook C

Top Group 2 = Logbook B, Logbook C

What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.

Actual Code:

;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps

 

 

  66115   Mon Dec 15 09:01:35 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2140Re: Grouping Logbooks

 

mike cianci wrote:

I really appreciate your help and I hope that my questions warrant your time.

What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.

Three logbooks

Logbook A

Logbook B

Logbook C (just informational, write protected)

Two Groups

Top Group 1 = Logbook A, Logbook C

Top Group 2 = Logbook B, Logbook C

What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.

Actual Code:

;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps

You cannot put the same logbook into two groups. All you can do is to define two logbooks C1 and C2, and force their data directories to be the same (via the "Subdir = ..." directive), so they will actually look at the same data.

  66125   Tue Dec 23 11:02:26 2008 Question Stefan Kanitzskmainz@web.deQuestionWindows2.7.5-2140Problems with execute delete

Hi all,

i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?

 

Here is the config:

 

Attributes = Counter, Autor, Adressat, Start, Ende, Mitteilung, TextBeachten

Show Attributes = Counter, Autor, Adressat, Start, Ende, Mitteilung, TextBeachten
Show Attributes Edit = Counter, Autor, Adressat, Start, Ende, Mitteilung, TextBeachten


Type Start = date
Type Ende = date
Required Attributes =  Autor, Adressat, Start, Ende, Mitteilung
Extendable options = Adressat
Preset Autor = $long_name
Preset Counter = SoMi-#####



Locked Attributes = Autor, Counter
Required Attributes =  Adressat, Start, Ende, Mitteilung

Options Adressat = Alle, 1. Semester, 2. Semester, 3. Semester, 4. Semester, 5. Semester, 6. Semester, 7. Semester, 8. Semester
MOptions Textbeachten = Bitte Mitteilungs-Text anzeigen lassen



Execute new = C:\xampp\mysql\bin\mysql.exe -h localhost -u root -p123456 -D screen -e "insert into somi (counter,adressat,start,ende,kumi,mitlami,lami) values ('$Counter', '$Adressat', '$Start', '$Ende', '$Mitteilung',  '$TextBeachten', '$text')"


Execute delete = C:\xampp\mysql\bin\mysql.exe -h localhost -u root -p123456 -D screen -e "delete from somi where counter='$Counter'"

 

 

 

Thanks in advance and Merry Christmas!!

 

Steve

 

  66126   Tue Dec 23 11:34:25 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2140Re: Problems with execute delete

 

Stefan Kanitz wrote:

i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?

 

Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. 

  66127   Tue Dec 23 12:17:06 2008 Reply Stefan Kanitzskmainz@web.deQuestionWindows2.7.5-2140Re: Problems with execute delete

Stefan Ritt wrote:

 

Stefan Kanitz wrote:

i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?

 

Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. 

 This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))

Steve

 

  66128   Tue Dec 23 12:22:51 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2140Re: Problems with execute delete

 

Stefan Kanitz wrote:

 

Stefan Ritt wrote:

 

Stefan Kanitz wrote:

i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?

 

Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. 

 

This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))

 

For 'execute edit' this worked from the beginning. 

  66129   Tue Dec 23 12:31:39 2008 Reply Stefan Kanitzskmainz@web.deQuestionWindows2.7.5-2140Re: Problems with execute delete

Stefan Ritt wrote:

 

Stefan Kanitz wrote:

 

Stefan Ritt wrote:

 

Stefan Kanitz wrote:

i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?

 

Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. 

 

This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))

 

For 'execute edit' this worked from the beginning. 

 Thank you!

  66709   Fri Feb 12 08:31:14 2010 Reply mike ciancimike2.cianci@comcast.netQuestionWindows2.7.5-2140Re: Grouping Logbooks

Stefan Ritt wrote:

 

mike cianci wrote:

I really appreciate your help and I hope that my questions warrant your time.

What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.

Three logbooks

Logbook A

Logbook B

Logbook C (just informational, write protected)

Two Groups

Top Group 1 = Logbook A, Logbook C

Top Group 2 = Logbook B, Logbook C

What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.

Actual Code:

;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps

You cannot put the same logbook into two groups. All you can do is to define two logbooks C1 and C2, and force their data directories to be the same (via the "Subdir = ..." directive), so they will actually look at the same data.

 Stefan, sorry to bother you yet again. but I can not seem to get the "Subdir" to do what I want (user error I am sure). Thanks for any help you can give.

[OnlineHelps]
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0
List Menu commands = New, Find, Config

Thread display = --------------  $Title  --------------

Comment = On-Line Helps
Attributes = Title
Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 1

[OLH.gsh]

Subdir = \\ssoelog\ELOG\logbooks\OnlineHelps
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0
List Menu commands = New, Find, Config

Thread display = --------------  $Title  --------------

Comment = On-Line Helps
Attributes = Title
Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 1

ELOG V3.1.5-3fb85fa6