Re: A new ELOG user wants to register on "127.0.0.1", posted by Stefan Ritt on Thu Jul 14 17:29:42 2005
|
[quote="Emiliano Gabrielli"]A new ELOG user wants to register on "127.0.0.1"
|
|
Re: short/long_name should point the same user, posted by Stefan Ritt on Thu Jul 14 17:34:12 2005
|
[quote="Emiliano Gabrielli"]In my case I changed it by error, people inserted entries and now I restored the correct one .. so now I have to unlock the
attribute and change every Author by hand as admin
:-)[/quote]
|
|
Re: short/long_name should point the same user, posted by Emiliano Gabrielli on Thu Jul 14 19:11:54 2005
|
[quote="Stefan Ritt"][quote="Emiliano Gabrielli"]In my case I changed it by error, people inserted entries and now I restored the correct one .. so now
I have to unlock the attribute and change every Author by hand as admin
:-)[/quote]
|
|
Re: A new ELOG user wants to register on "127.0.0.1", posted by Emiliano Gabrielli on Thu Jul 14 19:16:06 2005
|
[quote="Stefan Ritt"][quote="Emiliano Gabrielli"]A new ELOG user wants to register on "127.0.0.1"
|
|
Re: short/long_name should point the same user, posted by Stefan Ritt on Thu Jul 14 20:24:07 2005
|
[quote="Emiliano Gabrielli"]uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?
|
|
Re: short/long_name should point the same user, posted by Emiliano Gabrielli on Fri Jul 15 15:03:01 2005
|
[quote="Stefan Ritt"][quote="Emiliano Gabrielli"]uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?
|
|
Re: < img > in Display Attribute, posted by Emiliano Gabrielli on Fri Jul 15 17:28:33 2005
|
the very usefull thing my request will enable is the following:
[CODE]
|
|
Re: < img > in Display Attribute, posted by Stefan Ritt on Sat Jul 16 12:30:33 2005
|
[quote="Emiliano Gabrielli"]IMHO the solution may be in allowing html code only in the cfg, not in the value of the field..
i.e., elog has to first allow html in the cfg attribute and then replace every $attribute with their values... this values as to be translated in html
entities in order to solve the problem
|