IMO it would be helpfull if the admin log also would show where it discovered the error or on what the notification is based. I think it would save time in investigating the cause of the notification shown.

In the above case, I search where I use CGSI, looked at the parameters, they all have either src or src1, and sometime src1 and src2 -no src-, so at the moment I have no clue what is causing the notification. I expect CGSI wants src, src1, src2, meaning one has to start with src and not with src1 when one has several src-parameters.

Share On:

Rolf

Post subject: Re: Admin log: more details

Posted: Thu Dec 14, 2017 10:07 am

Dev Team Member

Joined: Wed Apr 23, 2008 7:53 amPosts: 7636Location: The Netherlands

The use of the Admin Log depends on the module developer. He/she can add more check and log lines to the code OR not... The dev-team can't force people to do that. What you can do is raise a feature request for a certain module, and ask to add to log a problem separately.

Share On:

Who is online

Users browsing this forum: No registered users

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum