Jump to content

Double_d

Members
 View Profile  See their activity

  • Posts

    8

  • Joined

 Content Type 

Posts posted by Double_d

    Chrome enforcement of 'Misleading functionality' report for <domain> starts on Mar 1, 2020

    in Business Discussion

    Posted

    Last week I received this email from Google.

    To the owner of <domain>,

The Google systems have found misleading functionality on your site. To protect the visitors of your site, Google Chrome prevents from 1-Mar-2020 that the site can open new windows or tabs. In addition, Chrome then starts deleting all ads unless the issues are resolved.
You can solve the problem as follows:
1

Identify the misleading functionality

Go to the "Misleading functionality" report to identify the found functionality that violates the policy.
2

Remove the misleading functionality

Together with your web development team, develop a strategy to solve these problems.
3

Request an assessment

As soon as your site no longer contains misleading functionality, request a review. Add details or documentation to help us understand the changes you have made.
Need more help?
• View more information about misleading functionality and requesting assessments in the Web Tools Help Center.

    I know what the problem is that is my popunder, but this form of advertisement I pay all server costs. I'm a bit worried now "how am I going to solve this", has someone a good idea / solution, otherwise this is the end of mine hobby.

    Thanks in advance for your answer.

    Kind regards,

    Jaco

    KVS 5.2.0 development

    in Announcements

    Posted

    File upload from local disk was completely re-written to use chunked upload method. This means that there will be no more need to use subdomain to workaround CloudFlare upload size limit set to 100mb - instead KVS will upload files in smaller chunks one by one.

     

    [ATTACH=JSON]{"data-align":"none","data-size":"full","title":"upload_progress.png","data-attachmentid":1097}[/ATTACH]

     

    Changing this also allowed us to modify how max filesize limit is being configured. Previously it was only possible to configure filesize limit for files that are uploaded from URLs, because KVS could not control limit for files uploaded from disk (this limit was managed by PHP / nginx config options). Now we changed it to single limit option that affects both files uploaded from disk or URLs:

     

    [ATTACH=JSON]{"data-align":"none","data-size":"full","title":"upload_size_limit.png","data-attachmentid":1098}[/ATTACH]

     

    This is good news.

    Well done!

×
×
  • Create New...