Resolution (i think) - Re: Problems with beta 3 (Follow-on to CVS/XML msg 1296), posted by PJ Meyer on Thu Jul 28 04:29:35 2005
|
PJ Meyer wrote: |
Stefan Ritt wrote: |
PJ Meyer wrote: | but something happened to the css.
i'm getting white background and no icons anywhere.
so tried to install in a clean location as it comes out of the box with no changes. get white background, no colour.
tried moving css files, graphic files, etc, around - nothing.
emptied bowser caches (IE and Opera)
deleted appropriate cookies
stop and started many time.
and still at the end of the day - i get a white background only, no colour what so ever.
also get page not found when clicking on a row to edit entry.
example: http://dhsdlj159941.hr.state.or.us/demo/1
is record #1 in demo table, elog can't display it when i click on it in the list window.
any ideas? |
That's strange. Can you check if elog finds it's own host properly? The CSS file should be under
http://dhsdlj159941.hr.state.or.us/demo/default.css
and if you look at the HTML source of you standard page you should see something like:
<link rel="stylesheet" type="text/css" href="http://dhsdlj159941.hr.state.or.us/demo/default.css">
Could it be that elog places something else than "dhsdlj159941.hr.state.or.us" as the host name? If so, you could override this with following statement in elogd.cfg:
URL = http://dhsdlj159941.hr.state.or.us/
That should also fix your other problem. |
OK tried all that and nothing. html source reads like it should.
I can see the discussion/forum here site as it should be
I updated a working setup from 2.54 to 2.60.beta3 and I get the white background with no colours on the restart of Elogd. Going back to 2.54 brought back the colours.
this is the source <link rel="stylesheet" type="text/css" href="http://ISE-DEVEL1-OLD/default.css">.
Works in 2.54, does not seem to work in 2.60beta3
I've tried coping the default.css file to everyplace i could think of and then a few more places. 
This has happened on NT 4 server, 2000 server, and XP client machines. Brand new installs (server never saw elog before), upgrades in place, etc, etc, etc. Wish we could run linux in the shop.
Tried in the cfg file:
Resource dir = c:\e-log
Logbook dir = c:\e-log\logbooks
Theme = default
CSS = default.css
This is so strange.
Any ideas on where to go in trouble shooting this? |
think I figured it out- had to make explict most of the default settings: resource, logbook, url, theme, css and so on.
so this is done. |
Resolution (i think) - Re: Problems with beta 3 (Follow-on to CVS/XML msg 1296), posted by Stefan Ritt on Thu Aug 4 20:35:48 2005
|
PJ Meyer wrote: | think I figured it out- had to make explict most of the default settings: resource, logbook, url, theme, css and so on.
so this is done. |
I'm not satisfied with this solution, I rather would like to fix the problem at the source. So can you remove the explicit directory settings, then stip down the config file to the bare minimum where the problem happens, then send me this file so that I can reproduced it. Do yo use SSL, stunnel or a proxy?
- Stefan |
Reset a user's password, posted by Val Schmidt on Fri Oct 28 16:30:36 2016
|
Is it possible for an administator to reset a user's password?
Thanks,
Val |
Required and {}, posted by bob on Wed Feb 14 16:46:27 2007
|
Hi,
I still have a question,
is it possible to use : Required and {}
here my program :"
.
{run} Required Attributes = Date evenement, Heure evenement, ...
{run} Show Attributes = Date evenement, Heure evenement, ...
.
.
.
{etuvage & ANS} Required Attributes = Date evenement, Heure evenement, ...
{etuvage & ANS} Show Attributes = Date evenement, Heure evenement, ...
"
generally, can one handle "Required" and "{}" or "{ , }", ...
in any case for me, that does not go
this is normal ??
Thanks
Bob |
Required Attributes, posted by Eric Krise on Fri May 14 16:53:54 2010
|
Is there a way to require a certain attribute on reply, but not on an original entry? In some cases info. for these fields only exists on reply. |
Request: make $text available for "subst", posted by Andreas Luedeke on Mon Mar 22 14:56:12 2021
|
Hi Stefan,
I've just tried to read the $text with subst into another field and failed.
It looks like $text is only available for the execution of shell scripts in the "execute new|edit|delete = <script>" command.
Could that be added? I can think of a multitude of applications:
- In my case I want to fill an attribute X either with free text or generated from other fields. The list view will show just X and not how it was generated.
- I could fill an attribute automatically with the character length of the text.
- I could parse the text in a shell script and set other attributes according to the content.
Thank you for considering it.
Cheers, Andreas |
Request: limit size of attachments, posted by Bartjan Wattel on Wed Jul 14 13:58:26 2004
|
hi again,
we have been doing a bit of stress testing for Elog. The most important
thing we found is that Elog stops responding when a user uploads a large
attachment (we used a 240 Mb attachment).
Is it possible to add a flag in the configuration file, to specify the
maximum size of an attachment?
Bartjan Wattel |
Request: elog as a "web service" ? (xml / soap), posted by Willem Koster on Wed Apr 23 10:53:58 2008
|
We're using elog as our CMDB, but now management wants us to employ "web services" and I fear going to another tool (elog is fitting the admins like a glove, so we'd rather keep it)
Is it possible to configure elog to be able to run as a web-service ? (basically getting xml-output according to a specific (SOAP) schema instead of html output)
http://en.wikipedia.org/wiki/Web_services
A 'Web service' (also Web Service) is defined by the W3C as "a software system designed to support interoperable Machine to Machine interaction over a network." Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services.
The W3C Web service definition encompasses many different systems, but in common usage the term refers to clients and servers that communicate using XML messages that follow the SOAP standard. Common in both the field and the terminology is the assumption that there is also a machine readable description of the operations supported by the server written in the Web Services Description Language (WSDL). The latter is not a requirement of a SOAP endpoint, but it is a prerequisite for automated client-side code generation in many Java and .NET SOAP frameworks (frameworks such as Spring and Apache CXF being notable exceptions). Some industry organizations, such as the WS-I, mandate both SOAP and WSDL in their definition of a Web service. |
|