Skip to main content
 

Unclassified Cookies Definition NOT saved BUG

Andy Ramirez

This is a BUG! We have been adding definitions into "Empty" cookie definition fields and clicking "Save". The account looks all updated and we log out. 

We will then view our Cookie Declaration Page that has the injected Cookie declaration snippet, everything looks fine. 

Then, couple of days later, the Cookie Declaration Page shows the same cookies that were previously updated as "Unclassified". We log back into our account and the unclassified cookies that we had previously updated are now with a blank field, meaning the definitions we entered are now deleted! 

This is totally unacceptable. It should have saved all the cookie definitions that was previous entered instead of deleting them. 

How can we resolve this?! 

0

Comments

4 comments

Date Votes
  • Spas – vConnect – Community Supporter

    Hi Andy,

    A possible explanation of the described issue is that maybe you have deleted and re-added the domain to the domain list. In that case the cookie descriptions will be deleted as the domain will be treated as a new domain, and that is why all previously entered cookie definitions are removed.
    If this is not the explanation, I will need the domain name to investigate further and help you solve the problem afterwards instead of guessing. If you want you could post the domain here or send it at s.velinov@vconnect.dk

    Regards,
    Spas

    0
  • Andy Ramirez

    I just sent you an email. 

    0
  • Spas – vConnect – Community Supporter

    Hi Andy,

    I have investigated you domain and I can't reproduce the described error. When I look at https://www.smartsheet.com/legal/cookie-table, the "__insp_dct" cookie is correctly classified.
    Could you tell me where does his screen shot come from which shows the cookie as unclassified?
    The domain www.smartsheet.com is registered and scanned twice in two different domaingroups ("smartsheet.com - Explicit (EU)" and "TEST IMPLEMENTATION"). Is it possible that there is a mix-up in domain groups, so that you make changes to the cookie in one domain group but then check on the cookie declaration of the other?

    Regards,
    Spas

    0
  • Andy Ramirez

    Spas,

     

    The reason it's correctly classified at the moment is because I went through yesterday and redefined all cookies across all of our sub-domains. I was told before that I wouldn't have to classify them on all, that when a cookie was set on one it would apply to all, but we did it anyway just to ensure the table had as few unclassifieds as possible. I will post again here when it breaks. We don't really use the test implementation one, so it was not a mixup. 

     

    Cheers,

     

    Andy

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post