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
Refresh keyword from broken status #9927
Comments
Can you maybe add a link to the original issue that you reported re the language? Can you maybe show some screenshots to explain what you mean? |
Dear Thomas Sorry for late reply here is original thread about broken texts I attach the result today to see keywords still broken but it seems new keyword is good. is there any way I can refresh keywords? --------- 원본 메일 --------- |
Please let us know more information about your environment. Which Piwik version are you using? Which PHP version? Which MySQL version? How should the keywords you mentioned there actually look like? |
Hi @mybluepig it would be great if you could provide more info (see our previous comment). |
my piwik version is 2.16.0 here is information from phpMyAdmin in Korean but you will see everything 서버: localhost via TCP/IP Microsoft-IIS/7.0 It should be look like one of these |
@mybluepig could you please post a Referrer Search engine full URL, which contains one of your keywords eg. |
Closing this issue here now. If anyone has any similar problems with search engine detections please create a new issue at https://github.com/piwik/searchengine-and-social-list/issues |
Dear
I reported broken keyword in my language last year and it seems been fixed.
But problem is people keep using same keywords since last year and I still see it broken.
I think this happens database still has broken keywords and new records being added to it.
I can guess what it is but I don't want to just guess it because they are top keywords.
Reverse links to search sites are not working since keywords are broken, links also broken.
Do you have any idea I can fix this?
The text was updated successfully, but these errors were encountered: