Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 337 of 808  Not logged in ELOG logo
icon5.gif   Auto-Generate new logbook daily, posted by Ryan Blakeslee on Fri Apr 26 22:29:50 2013 
Hello,
I am currently using ELOG as a daily logbook for work performed for customers.  This is a critical tool  and process for 1. Showing customers
work history 2. having a searchable knowledge base for future reference.   
    icon2.gif   Re: Auto-Generate new logbook daily, posted by Stefan Ritt on Sat Apr 27 11:53:41 2013 


    
        
            Ryan Blakeslee wrote:
        
        
            
            Hello,
    icon2.gif   Re: Auto-Generate new logbook daily, posted by David Pilgram on Sat Apr 27 13:21:38 2013 


    
        
            Stefan Ritt wrote:
        
        
            
            
            
    icon2.gif   Re: Auto-Generate new logbook daily, posted by Stefan Ritt on Sat Apr 27 15:30:28 2013 


    
        
            David Pilgram wrote:
        
        
            
            Mind you, my log files have the format yymmdda.log, whereas you state yours are mmddyya.log, which strikes
    icon2.gif   Re: Auto-Generate new logbook daily, posted by Andreas Luedeke on Mon Apr 29 10:17:54 2013 


    
        
            David Pilgram wrote:
        
        
            
            
            
              
    icon2.gif   Re: Auto-Generate new logbook daily, posted by Ryan Blakeslee on Tue May 7 04:57:37 2013 


    
        
            Andreas  Luedeke wrote:
        
        
            
            
            
    icon2.gif   Re: Auto-Generate new logbook daily, posted by David Pilgram on Tue May 7 11:54:23 2013 


    
        
            Ryan Blakeslee wrote:
        
        
            
            
            
              
icon5.gif   some menu commands formed with broken links, posted by Ken Ludington on Tue May 7 22:15:37 2013 
On many of my logbooks when I specify the menu commands to appear i will get one, usually 'List', which has a
link not back to the logbook itself but to the root of the elog web server i.e. http:/hostname.domain:8080 
But nothing will respond without the logbook name after the port number.  This also seems to be happening to the
ELOG V3.1.5-3fb85fa6