error message "Command Config is not allowed" after registering, posted by Mark Bergman on Fri Oct 21 01:09:54 2011
|
After registering, elog displays a page with the message:
Error: Command "Config" is not allowed for user ""
However, the registration is successful. This causes confusion, and results in users registering multiple times. |
Re: error message "Command Config is not allowed" after registering, posted by Mark Bergman on Wed Feb 15 17:13:08 2012
|
Mark Bergman wrote:
After registering, elog displays a page with the message: |
|
Re: error message "Command Config is not allowed" after registering, posted by Mark Bergman on Wed Apr 2 19:17:31 2014
|
Mark Bergman wrote:
After registering, elog displays a page with the message: |
Re: error message "Command Config is not allowed" after registering, posted by Mark Bergman on Tue Sep 6 20:09:07 2016 
|
Mark
Bergman wrote:
After registering, elog displays a page with the message: |
Hilight code, posted by Daniel Sajdyk on Tue Sep 6 13:29:03 2016
|
Hello :)
Is there any way to highlight code (for example php, SQL) in logs entries?
Best Regards |
New elog version 3.1.2, posted by Stefan Ritt on Mon Sep 5 10:31:02 2016
|
A new version 3.1.2 of elog has been released today and can be retrieved through the normal download section. Since it fixes some vulnerabilities, it
is recommended to update to this version.
Stefan |
|
Image source url missing, posted by Antonio Bulgheroni on Thu Jul 21 13:08:44 2016
|
Dear all, sorry for asking you another question, but today after I finally recovered all my logbook entries, I updated to elog 3.1.1 and now I have a
problem uploading images.
This is what I do: |
|
Re: Image source url missing, posted by Antonio Bulgheroni on Mon Aug 22 10:36:17 2016
|
Can anyone help me? I'm really clueless
|
|
Re: Image source url missing, posted by Stefan Ritt on Mon Aug 22 11:24:07 2016
|
I entered this image exactly as you described. When I click OK, the dialog disappears. Can you check if it works for you on this server? Maybe
with different browsers? |
|
Re: Image source url missing, posted by Antonio Bulgheroni on Mon Aug 22 12:00:32 2016
|
Dear Stefan, thanks for your answer.
I tried to add a picture to this reply but I got the same error message with both Firefox and Chrome.
For sure the pictures were not included in the message, but I have the feeling they were not even uploaded to the server. |
|
Re: Image source url missing, posted by Antonio Bulgheroni on Mon Aug 22 17:30:58 2016
|
Dear Stefan, this is to confirm that also from my personal laptop from home I have the same issue. No pictures uploaded to this server from windows 10.
Which OS & Browser are you using?
thanks, |
|
Re: Image source url missing, posted by Andreas Luedeke on Mon Aug 22 18:49:48 2016
|
Okay, I can confirm this bug: with Windows 10 using Firefox 47.0 the dialog hangs as soon as I press "Send it to the server". When it returns,
it did not upload anything. That is why it asks for URL after pressing OK.
Quick fix: just attach the image and use the URL of the attachment. |
|
Re: Image source url missing, posted by Antonio Bulgheroni on Mon Aug 22 21:55:14 2016
|
Thanks Andreas for your contribution and your quick fix. Just a question: how do you get the attachment URL?
Cheers,
Antonio |
|
Re: Image source url missing, posted by Andreas Luedeke on Tue Aug 23 09:05:21 2016
|
If you go on the attached image with the right mouse button, then you'll get a menu. In this menu there should be some entry like "copy image
link" (my PC is unfortunately configured in German, I can't look it up).
This copies the URL in the clipboard and you can just paste it in the URL entry of the image button. |
|
Re: Image source url missing, posted by Antonio Bulgheroni on Tue Aug 23 11:06:49 2016
|
ok... that was easy. I though there was a ELOG specific way to link to attachments.
(my computer is also in German :)
Andreas |
|
Re: Image source url missing, posted by Antonio Bulgheroni on Mon Aug 22 22:09:14 2016
|
Andreas, there is something strange. It looks the problem is "configuration dependent" because I tried to upload a picture on the Linux Demo
logbook and there it works. Can you confirm this too?
Andreas |
|
Re: Image source url missing, posted by Andreas Luedeke on Tue Aug 23 09:01:08 2016
|
Yes, I can confirm that the image button upload does work in the Linux Demo logbook (Windows 10 client host, Firefox 47.0 client) and it still does not
work in this Forum.
Antonio |
|
Re: Image source url missing, posted by Antonio Bulgheroni on Thu Sep 1 08:47:55 2016
|
This is another piece of information to help in the debugging. To my standards logbooks, I have added the "demo". On the demo I can upload
pictures while I can't on the other logbooks.
This is indicating that the bug has something to do with the logbook configuration other than with the editor or the image upload plugin. |
Re: Image source url missing, posted by Antonio Bulgheroni on Thu Sep 1 09:03:51 2016
|
The conflicting option is "Preview attachments". When this is turned off (set to 0), images are not properly uploaded. Could you please confirm
it also on your side?
Antonio |
Wrong time in attachment "Uploaded ..." date, posted by Andreas Luedeke on Wed Aug 31 10:31:19 2016
|
When an attachment is later added to an exisiting entry, we see that the string "Uploaded <date>" has the wrong
time: in our case it is one hour into the future.
I'm testing it now here in the forum.
|
|
elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Fri Aug 19 19:39:50 2016
|
I was setting of a local test copy of my logbooks on my Windows 7 PC to begin testing automation of submissions without spamming the live logbooks. While
trying to make entries from the command line I get an error that I am missing a required attribute. I have multiple attributes that have spaces in them
an the verbose output indicates that the space in the name is being changed to an underscore. Is this the expected behavior or a bug when submitting to |
|
Re: elog client cmd line submission of attributes with spaces., posted by Rudy Taraschi on Fri Aug 19 22:43:21 2016
|
| Try commenting out the Required Attributes line in your elogd.cfg file before submitting. I think it's a bug but this work-around gets around it. |
|
Re: elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Thu Aug 25 18:32:13 2016
|
Thanks for the response. You are indeed correct that the issue disappears when I comment out my required attributes line. If I just remove my "Start Time"
attribute, all the other attributes work as well.
|
|
Re: elog client cmd line submission of attributes with spaces., posted by Rudy Taraschi on Thu Aug 25 18:45:48 2016
|
[quote="Darren Hollinrake"]Thanks for the response. You are indeed correct that the issue disappears when I comment out my required attributes line. If
I just remove my "Start Time" attribute, all the other attributes work as well.[/quote]
I used to just comment out that one field in Required Attributes as well, but it was a pain to edit the CFG file, so I took the lazy approach and just |
|
Re: elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Thu Aug 25 19:04:11 2016
|
Agreed, I just wanted to clarify for anyone else though that the issue seems to be centered on my "Start Time" attribute which is a datetime field. All
the other attributes (with spaces) allowed submission of the entry so long as the "Start Time" attribute wasn't set to required. That appears to be the
one with the actual issue. Giving a valid epoch time when that field isn't required allows the field to be populated correctly. However, if the "Start |
|
Re: elog client cmd line submission of attributes with spaces., posted by Andreas Luedeke on Sat Aug 20 12:17:10 2016
|
If the "Start Time" attribute is of the type "datetime", then you cannot assign a date string to it.
Instead you'll have to assign the seconds of the epoch.
Try assigning a "0", that should be the 1st of January 1970.
|
|
Re: elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Thu Aug 25 18:18:57 2016
|
Thanks for the reply. You're correct that the "Start Time" attribute is a datetime field. I tried your suggestion and placed "0" for that field but it still
returns the same error: Error: Missing required attribute "Start Time"
I tested after commenting out the required attribute line and the command was accepted. However, the datetime field does not display a valid date/time |
|
Quick Filter not searching on Enter, posted by Alan Grant on Wed Aug 10 16:46:09 2016
|
With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press
enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is
that the intended procedure for searching? |
|
Re: Quick Filter not searching on Enter, posted by Andreas Luedeke on Thu Aug 11 09:18:27 2016
|
I've checked for this forum logbook, and pressing "enter" while having focus in the quickfilter text field does initiate the search. Does
it work for you with this logbook?
Alan |
|
Re: Quick Filter not searching on Enter, posted by Alan Grant on Thu Aug 11 16:40:47 2016
|
Yes it works fine in this forum. I also discovered my problem is resolved using Chrome. I'll dig into browser and let you know when I find
something.
|
|
Re: Quick Filter not searching on Enter, posted by Alan Grant on Thu Aug 11 17:09:47 2016
|
Found the problem. I needed to turn on Compatibility View in IE for the site. Regards.
Alan Grant wrote:
Yes it works fine in this forum. |
|
Quick Filter not searching, posted by Alan Grant on Wed Aug 10 15:40:49 2016
|
With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press
enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is
that the intended procedure for searching? |