Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 786 of 804  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  1613   Thu Jan 19 20:50:29 2006 Cool Mark Coudrietmarkcoudriet@yahoo.comBug report 2.6.0Re: In version 2.6 the themes do not work right on Windows.

Stefan Ritt wrote:

Quote:
The URL is fixed at whichever logbook that is selected (e.g. ELOG 2.5.9-4 is <link rel="stylesheet" type="text/css" href="default.css"> & ELOG 2.6.0-1 is <link rel="stylesheet" type="text/css" href="http://localhost:8080/demo/default.css">).


So what is your problem? Can't you access http://localhost:8080/demo/default.css ?

If so, you could use an
URL = http://{your host}:8080/

option in your config file, where you replace {your host} with your real host name.


No, because they would have to be in every logbook instead of coming out of the theme directory.
But I just updated to your new version 2.6.1 & everything is fine now. Thanks for your help! Big grin
  1614   Thu Jan 19 20:53:01 2006 Reply Stefan Rittstefan.ritt@psi.chBug report 2.6.0Re: In version 2.6 the themes do not work right on Windows.

Mark Coudriet wrote:
But I just updated to your new version 2.6.1 & everything is fine now. Thanks for your help! Big grin


Japp. I switched back to relative links for CSS again, seems to give less trouble. Pleased
  1616   Sat Jan 21 14:02:57 2006 Reply Giorgio Croci Candianig.crocic@libero.itBug report 2.6.1Re: Access to global configuration in v2.6.1
 
> I tried to reproduce your problem, but could not. In my windows installation it looks fine. You only see the
> (save and cancel) buttons only if you go to "Change [global]", otherwise you see the "Change [global]", "Delete
> this logbook" etc. buttons. Have you tried with the default elogd.cfg which comes from the distribution?

Yes, I tried that. Maybe I'll have some other try on other PCs and investigate further, I'll surely let you know. Thanks
for the prompt response and compliments for your very good work! ELog is really a great piece of software.
  1620   Mon Jan 23 17:32:20 2006 Reply mark jamesmark@majames.comQuestion 2.6.0b5Re: Quicklink does not work for one field

Stefan Ritt wrote:

mark james wrote:
I am not so bold as to log this as a bug but one of my Quicklink fields just do not work.


Sorry my late reply, but now I have fixed this problem. The update is under SVN and will be contained in the next release.


Thanks for that. I am now using ver V2.6.1-1622. So I guess that doesn't qualify as a "next release". I wonder if there is anything I could do to work around the issue?

Mark
  1621   Mon Jan 23 18:35:52 2006 Reply mark jamesmark@majames.comQuestion 2.6.0b5Re: Quicklink does not work for one field

mark james wrote:

Stefan Ritt wrote:

mark james wrote:
I am not so bold as to log this as a bug but one of my Quicklink fields just do not work.


Sorry my late reply, but now I have fixed this problem. The update is under SVN and will be contained in the next release.


Thanks for that. I am now using ver V2.6.1-1622. So I guess that doesn't qualify as a "next release". I wonder if there is anything I could do to work around the issue?

Mark

In fact now the dropdown seems to be working but when I 'tick' an entry, it is not being written to the ascii file.
  1622   Tue Jan 24 08:11:13 2006 Reply Stefan Rittstefan.ritt@psi.chQuestion 2.6.0b5Re: Quicklink does not work for one field

mark james wrote:

mark james wrote:

Stefan Ritt wrote:

mark james wrote:
I am not so bold as to log this as a bug but one of my Quicklink fields just do not work.


Sorry my late reply, but now I have fixed this problem. The update is under SVN and will be contained in the next release.


Thanks for that. I am now using ver V2.6.1-1622. So I guess that doesn't qualify as a "next release". I wonder if there is anything I could do to work around the issue?

Mark

In fact now the dropdown seems to be working but when I 'tick' an entry, it is not being written to the ascii file.


Can you try V2.6.1-1634? I fixed several issues with ticking entries coming from "MOptions" lists.
  1626   Wed Jan 25 01:08:06 2006 Reply Giorgio Croci Candianig.crocic@libero.itBug report 2.6.1Re: Access to global configuration in v2.6.1
> > I just installed v.2.6.1 coming from the previous 2.6.0 (on Win2000)
> > When I access the "configuration" function from a logbook, in the cfg page I only see two buttons in the header
> > (save or cancel); in the previous version I saw more buttons there ("global config", "create new logbook" and so
> > on), so here I'm unable to access global configuration or logbook management (except for current logbook options).
> 
> I tried to reproduce your problem, but could not. In my windows installation it looks fine. You only see the
> (save and cancel) buttons only if you go to "Change [global]", otherwise you see the "Change [global]", "Delete
> this logbook" etc. buttons. Have you tried with the default elogd.cfg which comes from the distribution?

Here I am again... I built and installed v2.6.1 also on a different system, this time on linux; i tried both with the
existing cfg file and with the new cfg.
Choosing "configuration", I still only see the current logbook configuration file section with "Save" and "cancel"
buttons, no access to global config whatsoever; the same as I saw on windows version. I tried version 2.6.1-1622.
Regards
Giorgio
  1627   Wed Jan 25 08:24:28 2006 Reply Stefan Rittstefan.ritt@psi.chBug report 2.6.1Re: Access to global configuration in v2.6.1
> Here I am again... I built and installed v2.6.1 also on a different system, this time on linux; i tried both
with the
> existing cfg file and with the new cfg.
> Choosing "configuration", I still only see the current logbook configuration file section with "Save" and "cancel"
> buttons, no access to global config whatsoever; the same as I saw on windows version. I tried version 2.6.1-1622.

I tried again, using the configuration file from the distribution (elog:1627/1). Hitting "config", I see the picture
attached (elog:1627/2). So it's a mystery why it is different in your case...
Attachment 1: elogd.cfg
[global]
port = 8080

[demo]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

Attachment 2: Capture.gif
Capture.gif
ELOG V3.1.5-3fb85fa6