Re: Problem with large entry size, posted by Stefan Ritt on Tue Oct 17 14:42:58 2006
|
| Dimitrios Tsirigkas wrote: | | I was wondering what is the cleanest way of changing old entries already submitted in ELCode into plain text. If I do not include ELCode in the allowed encodings does this apply to already submitted entries as well or will they still be treated as ELCode? |
The encoding is stored as an "invisible" attribute in each entry. You can change it in two ways:
1) Select each entry, click "edit", change the encoding with the radio buttons at the bottom and submit it again
2) Go and edit directly the xxxxxxa.log files in your logbook directory. You will see in those files something like
Encoding: ELCode
and you can change it with an editor to
Encoding: plain
Afterwards you have to restart the elogd daemon.
Did you try the new version, would be interesting to see if it's any better... |
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Tue Oct 17 14:47:53 2006
|
Thanks Stefan,
| Stefan Ritt wrote: | | Did you try the new version, would be interesting to see if it's any better... |
I didn't find the time to try it yet but I will do that later today. I will keep you posted - more soon.
Cheers,
Dimitris |
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Mon Oct 23 12:53:08 2006
|
Hi Stefan,
A lot of performance-related trouble for us comes from the ability of users to click on "All" and display thousands of entries on the same page. Is there a way to disable that? Even if the ELCode parsing performance of Elog increases greatly, the combination of "Full" mode and "All" will still cause trouble, will it not?
Thanks,
Dimitris |
|
Re: Problem with large entry size, posted by Stefan Ritt on Tue Oct 24 21:58:54 2006
|
| Dimitrios Tsirigkas wrote: | Hi Stefan,
A lot of performance-related trouble for us comes from the ability of users to click on "All" and display thousands of entries on the same page. Is there a way to disable that? Even if the ELCode parsing performance of Elog increases greatly, the combination of "Full" mode and "All" will still cause trouble, will it not?
Thanks,
Dimitris |
What about a threshold for the "All" display? If a logbook contains less than, let's say, 500 entries, the "All" link is displayed, and above 500 entries it's hidden. Would that make sense? |
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Thu Nov 2 10:14:11 2006
|
| Stefan Ritt wrote: | | What about a threshold for the "All" display? If a logbook contains less than, let's say, 500 entries, the "All" link is displayed, and above 500 entries it's hidden. Would that make sense? |
Hi Stefan,
Sorry for the late response, I was away for a few days. Yes, I think that this would make perfect sense, especially if the maximum number of entries was configurable.
Cheers,
Dimitris |
|
Re: Problem with large entry size, posted by Stefan Ritt on Thu Nov 9 21:22:27 2006
|
| Dimitrios Tsirigkas wrote: |
| Stefan Ritt wrote: | | What about a threshold for the "All" display? If a logbook contains less than, let's say, 500 entries, the "All" link is displayed, and above 500 entries it's hidden. Would that make sense? |
Hi Stefan,
Sorry for the late response, I was away for a few days. Yes, I think that this would make perfect sense, especially if the maximum number of entries was configurable.
Cheers,
Dimitris |
Agree. So I implemented the new config option All display limit. The default is 500. So you can see that at this forum, the All link is not shown any more, since the logbook contains more than 500 entries. The promised performance improvement of the page display will take me some more time, but I will not forget it. |
Re: Problem with konqueror and pulldown menu (in config menu), posted by Stefan Ritt on Tue Sep 10 17:15:15 2002
|
> Hi ,
>
> currently I am running Elog 2.1.1; when using a konqueror browser (ver.
> 2.2.1, kde 2.2.1) the admin user cannot access in the Config menu the Login
> infos for other users except himself. The pulldown menu "Select user" is
> shown, but when the admin selects another user the info fields (Login name,
> full name, email) are not updated. They still show the attribute values for
> the admin user himself.
>
> Is there a solution available?
> Thanks (also for this very useful tool) and regards,
>
> Stefan
This operation is done via Java Script, which has to be enabled in the
browser. If anybody knows a better way, please let me know. |
|
Re: Problem with embedded Iframes, posted by Stefan Ritt on Tue Jan 13 10:10:56 2015
|
This is an issue with CKEditor, not with ELOG.
Maybe this helps:
http://drupal.stackexchange.com/questions/96069/ckeditor-removes-iframes-in-editor-after-update-to-6-x-1-14
| Eric Quintero wrote: |
|
We've upgraded our ELOG installation to v3, and we really like the new CKeditor. However, one of my users has noticed a problem when using Iframe HTML elements with CKeditor; namely that the HTML is not present when trying to edit the post, and saving the post erases the HTML.
I was able to reproduce this fairly simply, by trying to embed a youtube video. I would create a new post, click the "Source" view in CKeditor, and paste something like the following:
<iframe width="420" height="315" src="//www.youtube.com/embed/RzZgFKoIfQI" frameborder="0" allowfullscreen></iframe>
Upon submission, this produces a totally normal .log file in the logbook directory, and the video is viewable on the ELOG page:
Date: Mon, 22 Dec 2014 15:52:20 -0800
Author: test
Type: General
Category: General
Subject: test
Attachment:
Encoding: HTML
========================================
<iframe width="420" height="315" src="//www.youtube.com/embed/RzZgFKoIfQI" frameborder="0" allowfullscreen></iframe>
Then, upon hitting "Edit," I am greeted by a totally empty CKeditor window, and hitting "Source" does not display the original HTML.
Any help is greatly appreciated!
PS: Including the first line of the logfile in this very post would cause the submitted post to be truncated for some reason, although the preview looked fine. Pasting it here also caused the log to end abruptly. The string is "(dollar sign)(at symbol)MID(at symbol)(dollar sign): 9"
|
|
|