@larsen0815 opened this Issue on August 10th 2015

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.

@larsen0815 commented on June 10th 2021

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

@diosmosis commented on June 11th 2021 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 commented on June 11th 2021

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

@tsteur commented on June 21st 2021 Member

@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 commented on June 21st 2021

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 commented on June 21st 2021 Member

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 commented on June 21st 2021

Sorry, does what happen?

@tsteur commented on June 21st 2021 Member

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 commented on June 22nd 2021

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.

Powered by GitHub Issue Mirror