ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68208
|
Fri Nov 27 06:53:54 2015 |
| David Dunne | ddunne@seven.com.au | Question | Windows | Other | 3.1.0 | If a Required Attribute starts with a number – No CKEditor | Hello,
Is the below an issue or am I doing something incorrectly?
Creating an attribute starting with a number and then including that attribute in the Required Attribute list prevents access to the CKEditior.
This appears to be the case at least with FreeBSD (10.2 Rel) using Elog V3.1.0 and Windows 7 with Elog V3.1.1-3f311c5.
The problem can be recreated using the Elog supplied sample config and adding the necessary attribute, sample config showing below.
While attribute 7SWM is part of the Required Attributes the CKEditor fails to appear, remove 7SWM from the Required Attributes list and the CKEditor returns.
[global]
port = 8080
[demo]
Theme = default
Comment = General Linux Tips & Tricks
Attributes = Author, Type, Category, Subject, 7SWM
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Options 7SWM = Name-1, Name-2, Name-3
Extendable Options = Category
Required Attributes = Author, Type, 7SWM
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Thank you,
David Dunne |
68209
|
Fri Dec 11 14:30:10 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | Other | 3.1.1-bc8310a | Re: If a Required Attribute starts with a number – No CKEditor | Hi David,
I can confirm a bug: changing the encoding does not work if you have a required attribute starting with a digit. The following minimal config reproduces the bug:
[global]
Default encoding = 1
[test]
Attributes = 7SWM
Options 7SWM = Name
Required Attributes = 7SWM
Whatever you choose as a default encoding you'll be stuck with. If you remove the "Required Attributes" it works again.
The workaround is very simple: do not use any attributes that do start with a digit :-)
Cheers, Andreas
David Dunne wrote: |
Hello, Is the below an issue or am I doing something incorrectly? Creating an attribute starting with a number and then including that attribute in the Required Attribute list prevents access to the CKEditior. This appears to be the case at least with FreeBSD (10.2 Rel) using Elog V3.1.0 and Windows 7 with Elog V3.1.1-3f311c5. The problem can be recreated using the Elog supplied sample config and adding the necessary attribute, sample config showing below. While attribute 7SWM is part of the Required Attributes the CKEditor fails to appear, remove 7SWM from the Required Attributes list and the CKEditor returns. [global] port = 8080 [demo] Theme = default Comment = General Linux Tips & Tricks Attributes = Author, Type, Category, Subject, 7SWM Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other Options Category = General, Hardware, Software, Network, Other Options 7SWM = Name-1, Name-2, Name-3 Extendable Options = Category Required Attributes = Author, Type, 7SWM Page Title = ELOG - $subject Reverse sort = 1 Quick filter = Date, Type Thank you, David Dunne |
|
777
|
Mon Nov 15 13:10:12 2004 |
| Marc Neiger | m.neiger@synergie-inf.com | Info | Windows | All | 2.5.4-6 | Re: Announcement of RSS feeds | Hi Stefan,
The parsing now seems OK, IE downloads the XML and the RSS reader of Avant
Browser
accepts the feed.
I still have a problem however : below the header, only the first 3 items
are displayed and it seems only partially.
I included the HTML result so you can "visualize" what's going on (this may
also be on the avant browser side !).
Cheers,
Marc
> The problems came from the French accents and the German umlauts. I
changed the XML
> charset, so this should be fine now. New version is under CVS. |
Attachment 1: ELOG_Forum.htm
|
784
|
Mon Nov 15 15:43:37 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | All | 2.5.4-6 | Re: Announcement of RSS feeds | > I included the HTML result so you can "visualize" what's going on (this may
> also be on the avant browser side !).
I believe it is on the avant browser side. Below is the same shown in the
SharpReader browser, where everything is displayed correctly. |
Attachment 1: sharpreader.gif
|
|
2209
|
Tue Apr 24 11:00:56 2007 |
| bob | bobgrang@yahoo.fr | Question | Windows | All | last | Import log | Hi,
it is possible to import the file *.log of Elog towards another Elog?
thank you
Bob |
2210
|
Tue Apr 24 12:26:32 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | All | last | Re: Import log |
bob wrote: | Hi,
it is possible to import the file *.log of Elog towards another Elog?
thank you
Bob |
There are three methods:
- Copy over the *.log files from one Elog to the other. Make sure not to have entries with the same ID twice then.
- Set-up mirroring between two servers. This ensures a 1:1 copy of the server
- Export entries in CSV format (comma-separated-values) via 'Find', 'Mode = CSV', and do a 'CSV import' on the other side.
|
2211
|
Tue Apr 24 14:43:07 2007 |
| bob | bobgrang@yahoo.fr | Question | Windows | All | last | Re: Import log |
Stefan Ritt wrote: |
bob wrote: | Hi,
it is possible to import the file *.log of Elog towards another Elog?
thank you
Bob |
There are three methods:
- Copy over the *.log files from one Elog to the other. Make sure not to have entries with the same ID twice then.
- Set-up mirroring between two servers. This ensures a 1:1 copy of the server
- Export entries in CSV format (comma-separated-values) via 'Find', 'Mode = CSV', and do a 'CSV import' on the other side.
|
thank you,
but the last method (simplest for me) does not import the comment.
it's a pity... |
2228
|
Thu May 10 13:03:51 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | All | last | Re: Import log |
bob wrote: | thank you,
but the last method (simplest for me) does not import the comment.
it's a pity... |
Ok, I implemented the XML import which also includes the text body. However there are currently two limitations:
- If you want to import entries which contain replies, it only works if import them into an empty logbook, where the imported entries can obtain the same entry IDs as in the original logbook.
- The names of possible attachments are correctly imported, but not the files themselves. These you have to copy by hand.
|
|