Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 493 of 808  Not logged in ELOG logo
icon5.gif   Howto force users to supply an email address when registering?, posted by Johan Nyberg on Thu Oct 20 14:15:14 2005 
Hi,

Today I noticed that a user had registered without supplying an email address. I am using Self Register = 3, which means I recieve an email from elogd
    icon2.gif   Re: Howto force users to supply an email address when registering?, posted by Johan Nyberg on Sat Oct 22 00:21:03 2005 
[quote="Stefan Ritt"][quote="Johan Nyberg"]Is there a way to force the users to supply an email address when they register?[/quote]

I will happily implement such an email check if you supply me further information. Presume you enter an email address in the form user#domain.com (# instead
icon3.gif   Prefill attributes for new post, posted by Johan Forsberg on Tue Jan 12 11:35:55 2016 
Hi all,

I have a use case for ELOG where I need to be able to "prefill" some attributes in the "cmd=new" form, based on the URL.

To illustrate, imagine a link that takes the user directly to the form for creating a new post, with the "Subsystem" attribute already
    icon2.gif   Re: Prefill attributes for new post, posted by Johan Forsberg on Tue Jan 12 14:05:55 2016 
Wow, than you both for the quick response! I agree it's quite a hidden gem, but the most important thing is that it works, thanks!




Stefan
Ritt wrote:



Put a "p" in front of the attribute, like "&pSubsystem=Vacuum".
icon3.gif   Monitoring a logbook for changes, posted by Johan Forsberg on Tue Jan 12 15:06:42 2016 
Hi again!

I've another need that you probably already thought of :)

I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so
    icon2.gif   Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 10:27:21 2016 
Yeah, I found the RSS feed feature, but I could not get ETags/Last-Modified header fields which meant that I'd have to read and parse the entire
feed every time. Maybe I made a mistake and they do work, but if not, I think it would make sense to implement as it should save work for both the server
and the client.
    icon2.gif   Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 10:29:54 2016 
Yeah, I suppose something like that would be both faster and more efficient than polling ELOG itself. Fortunately the ELOG disk format looks easily parsed.

Thanks for the pointer!




Tamas
    icon2.gif   Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 20:08:04 2016 
Aha, that's interesting too! I'll have to look more carefully through the documentation... :)




Stefan
Ritt wrote:



You guys know that there is the possibility to execute an arbitrary
ELOG V3.1.5-3fb85fa6