Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Further improvement of logging for "An unexpected website was found: idsite was set to" #8534

Open
larsen0815 opened this issue Aug 10, 2015 · 9 comments
Open

Further improvement of logging for "An unexpected website was found: idsite was set to" #8534

larsen0815 opened this issue Aug 10, 2015 · 9 comments
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently.
Milestone
Backlog (Help wan...

Comments

@larsen0815
Copy link

As mentioned in #7698, it would be good to get more information about the "unexpected website" as the corresponding entry is removed from the DB, up to now.

One way would be to not remove the DB entries, but to add a field "deleted". As this would have to be considered in various parts of the code (I guess), this might be difficult to implement.

Another way would be to log the referrer if that contains the calling website.
@mattab mattab changed the title Further improvement of logging for "unexpected website" Further improvement of logging for "An unexpected website was found: idsite was set to" Sep 19, 2015
@mattab mattab added the c: Usability For issues that let users achieve a defined goal more effectively or efficiently. label Sep 19, 2015
@mattab mattab added this to the Long term milestone Sep 19, 2015
@mattab mattab modified the milestones: Long term, Mid term Dec 23, 2015
@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016
@tassoman tassoman mentioned this issue Apr 7, 2017
Closed
@larsen0815
Copy link
Author

Still struggling with entries like this. Any chance this might get implemented in the foreseeable future?

@diosmosis
Copy link
Member

Hi @larsen0815, I'm not in charge of prioritization but I suspect this won't be scheduled soon. A possible, if cumbersome, workaround might be to regularly make dumps of the site table so you have access to old data.

@larsen0815
Copy link
Author

Hmm, might be a way. At least it could be automated.

@tsteur
Copy link
Member

tsteur commented Jun 21, 2021

@larsen0815 sorry I'm not quite sure how keeping the site entry would help with the above error message? The error message would still say the same except the entry in the DB would still exist with a deleted flag. Could you maybe let us know what "more information" you are after and when these errors happen currently?

@larsen0815
Copy link
Author

Hi Thomas, the error message could contain the domain name as it's still available from the database which is not the case at this moment.

@tsteur
Copy link
Member

tsteur commented Jun 21, 2021

Does that happen when you bookmark links to a site directly? Or do you have widgets embedded? sorry about the questions just trying to understand more context.

@larsen0815
Copy link
Author

Sorry, does what happen?

@tsteur
Copy link
Member

tsteur commented Jun 21, 2021

I meant what triggers the error message "An unexpected website was found: idsite was set to". Is it a tracking request, a UI request because of a bookmark, or embedded widgets?

@larsen0815
Copy link
Author

I think it's a tracking request. As I can only see these messages in the log, I have no further information on the cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently.
Projects
None yet
Milestone
Backlog (Help wanted)
Development

No branches or pull requests
4 participants
@diosmosis @tsteur @mattab @larsen0815