checkbox, posted by deletoille on Tue Oct 31 14:45:05 2006 
|
Hello,
I found a small Bug when I create an entry. I activate a checkbox (attachement1) but when I upload a file, the activation disappears (attachement 2). I have to activate again the checkbox.
Is it something I can do?
Thanks in advance,
Xavier Deletoille |
Re: checkbox, posted by Steve Jones on Tue Oct 31 22:10:11 2006
|
| deletoille wrote: | Hello,
I found a small Bug when I create an entry. I activate a checkbox (attachement1) but when I upload a file, the activation disappears (attachement 2). I have to activate again the checkbox.
Is it something I can do?
Thanks in advance,
Xavier Deletoille |
| Steve Jones wrote: |
Xavier, your version number does not indicate the full SVN (it is cutoff at '172') but your screenshot indicates 'SVN1723'. This is an identified problem and looks to be fixed in SVN1740. I have verified with the checkbox "Suppress Email Notification" -- it likely effects all checkboxes.
|
|
|
Re: checkbox, posted by deletoille on Thu Nov 2 08:41:34 2006
|
| Steve Jones wrote: |
| deletoille wrote: | Hello,
I found a small Bug when I create an entry. I activate a checkbox (attachement1) but when I upload a file, the activation disappears (attachement 2). I have to activate again the checkbox.
Is it something I can do?
Thanks in advance,
Xavier Deletoille |
| Steve Jones wrote: |
Xavier, your version number does not indicate the full SVN (it is cutoff at '172') but your screenshot indicates 'SVN1723'. This is an identified problem and looks to be fixed in SVN1740. I have verified with the checkbox "Suppress Email Notification" -- it likely effects all checkboxes.
|
|
OK ,
sorry for the version number. My SVN numbers is 1723 like in screenshot.
I'm waiting SVN1740 .
thanks in advance |
|
Re: checkbox, posted by Stefan Ritt on Wed Nov 8 07:59:01 2006
|
| deletoille wrote: | I found a small Bug when I create an entry. I activate a checkbox (attachement1) but when I upload a file, the activation disappears (attachement 2). I have to activate again the checkbox.
Is it something I can do? |
I tried with V2.6.2-1741 and the problem was not there. It was fixed some time ago, so it should have worked in 1723 as well. Can you try the minimal example coming with the distribution, just by adding one MOptions attribute, like:
[global]
port = 8080
[demo]
Attributes = Author, Type
MOptions Type = Routine, Software Installation, Problem Fixed, Configuration, Other
and see if it work there? If it works correctly there but not with your config file, please send me your config file and I will try to reproduce the problem. |
Retain original ELOG id when moving an entry to an archive weblog, posted by Fergus Lynch on Wed Aug 9 12:25:57 2006
|
Hi There,
We have a number of weblogs where we regular archive off 'completed' entries to a separate archive weblog:
Is it possible to retain the original ELOG id when moving an entry to an archive weblog, or have a locked field which holds the original id which we could subsequently reference in the archive?
Many Thanks
Fergus |
|
Re: Retain original ELOG id when moving an entry to an archive weblog, posted by Stefan Ritt on Wed Aug 9 19:40:42 2006
|
| Fergus Lynch wrote: | We have a number of weblogs where we regular archive off 'completed' entries to a separate archive weblog:
Is it possible to retain the original ELOG id when moving an entry to an archive weblog, or have a locked field which holds the original id which we could subsequently reference in the archive? |
First of all, a reference to the original ELOG entry would not help if it's moved into another logbook (archive). Keeping the id is not possible technically, since it severs as a kind of primary key, which must be unique etc. There is however the possibility to create a "secondary" ID, using the Preset xxx = ### functionality. The attribute xxx will have increasing numbers just like the primary ID. You even can combine this with the current year or month (see documentation). The problem now is how to reference such an entry. You cannot just type elog:123 as this only references the primary ID. You would have to do a "hidden" search such as
http://midas.psi.ch/elogs/Forum/?xxx=###
where ### is your secondary id. This will of course be slower because if you click on such a reference, your whole archive will be searched for. |
How to setup Change attributes in detail view/edit mode ?, posted by Holger Mundhahs on Wed Feb 22 16:27:39 2006
|
Hello @all,
because I've got a very quick response on my 1st question regarding
"Change attributes" here is anonther one:
I've defined 2 attributes with "Change attribute" / "List Change attribute" (see configuration).
Because this values are build on other attributes I want to hide these attributes in
NEW / EDIT mode. How is this possible?
Regards
Holger
---
CONFIGURATION:
Comment = DEMO
Attributes = Admin, Hostname, IP-Adresse, Funktion, RIB Hostname, RIB IP, RIB http, ELOGs http
Change RIB http = <a href="https://$RIB Hostname/" target="_new">RIB-Board</a>
List Change RIB http = <a href="https://$RIB Hostname/" target="_new">RIB-Board</a>
Change ELOGs http = <a href="http://elogs/$Hostname/">ELOG</a>
List Change ELOGs http = <a href="http://elogs/$Hostname/">ELOG</a>
Preset Admin = DEMO
Locked Attributes = Admin, RIB http, ELOGs http
Fixed Attributes Edit = RIB http, ELOGs http
Display search = ID, Date, Admin, Hostname, RIB http, ELOGs http
List Display = ID, Date, Admin, Hostname, RIB http, ELOGs http
Link Display = ID |
|
Re: How to setup Change attributes in detail view/edit mode ?, posted by Stefan Ritt on Wed Feb 22 20:36:53 2006
|
> because I've got a very quick response on my 1st question regarding
> "Change attributes" here is anonther one:
Don't stress it too much ;-)
> I've defined 2 attributes with "Change attribute" / "List Change attribute" (see configuration).
> Because this values are build on other attributes I want to hide these attributes in
> NEW / EDIT mode. How is this possible?
Show Attributes = Admin, Hostname, IP-Adresse, Funktion, RIB Hostname, RIB IP
hides the attributes in the New/edit mode, but unfortunately also in the detailed view. |
|