Azərbaycan dili Bahasa Indonesia Bosanski Català Čeština Dansk Deutsch Eesti English Español Français Galego Hrvatski Italiano Latviešu Lietuvių Magyar Malti Mакедонски Nederlands Norsk Polski Português Português BR Românã Slovenčina Srpski Suomi Svenska Tiếng Việt Türkçe Ελληνικά Български Русский Українська Հայերեն ქართული ენა 中文
Subpage under development, new version coming soon!

Subject: oSokker

2020-05-04 11:11:37
Please let us know when you will fix SkUnk.

Many thanks in advance for your work!
2020-05-05 11:15:24
it's hard for me to get along without osokker but at some point in the distance I might have made it! therefore I will no longer need a tool to avoid a new dependency. the same could happen at some point.
2020-05-05 14:48:29
regarding oSokker there is solution on Polish forum

just replace manifest.json content with this (added thing are bold font)
{
"manifest_version": 2,
"permissions": [ "https://sokker.org/*", "http://sokker.org/*", "http://www.sokker.cz/*" ],
"content_scripts": [ {
"exclude_globs": [ ],
"include_globs": [ "*" ],
"js": [ "jquery-1.5.2.min.js",
"jquery.textarea.resizer.js",
"os-functions.js",
"oSokker_cis.js",
"os-nations.js",
"os-iColorPicker.js",
"os-language-az.js",
"os-language-bg.js",
"os-language-br.js",
"os-language-bs.js",
"os-language-ca.js",
"os-language-cz.js",
"os-language-de.js",
"os-language-dk.js",
"os-language-ee.js",
"os-language-el.js",
"os-language-en.js",
"os-language-es.js",
"os-language-fi.js",
"os-language-fr.js",
"os-language-fy.js",
"os-language-gl.js",
"os-language-hr.js",
"os-language-hu.js",
"os-language-hy.js",
"os-language-id.js",
"os-language-it.js",
"os-language-lt.js",
"os-language-mk.js",
"os-language-mt.js",
"os-language-nl.js",
"os-language-no.js",
"os-language-pl.js",
"os-language-pt.js",
"os-language-ro.js",
"os-language-ru.js",
"os-language-sk.js",
"os-language-sl.js",
"os-language-sr.js",
"os-language-sv.js",
"os-language-tr.js",
"os-language-uk.js",
"os-language-vi.js",
"os-language-zh.js",
"oSokker.js" ],
"matches": [ "https://sokker.org/*", "http://sokker.org/*" ],
"run_at": "document_idle",
"all_frames": true
} ],
"description": "oSokker addon port for Google Chrome browser",
"name": "oSokker",
"version": "0.3",
"update_url": "https://copy.com/FjGuiODftzfA/oSokker4Chrome/updates.xml"
}

and reload extension

hmm, maybe I already wrote about it
2020-05-07 10:16:08
Message deleted

2020-05-07 11:04:24
Thanks

i dont get time at now to search and input that..
(edited)
2020-05-07 21:27:01
Hi,
When editing and packing the manifest.json file, firefox plugin gives corrupt error.
Can you provide a link to the edited and working plugin?
Thanks. :)

2020-05-07 21:52:33
I can't. This combination with changing manifest.json will NOT work for Firefox.

To make it work with Firefox You have to prepare directory with extension and use Mozilla tools to validate and sign the extension which is what I am just not going to do. It is not my extension, it is obsolete, I don't have tools to build it and there is very similar extension which doesn't have the aforementioned issues.

So, I suggest You to use SkUnk if You are unable to fix oSokker for FF.
2020-05-07 23:09:09
Thanks . Best regards :)
2020-05-10 15:35:56
Does anyone know where oSokker for Google Chrome can be downloaded ? Unfortunately I have only oSokker for firefox, so the above mentioned bugfix doesn't work for me.
2020-05-10 16:43:19
Pagina 1
2020-05-10 16:50:00
Give us feedback if it helps.

In my case for Chrome still not working.
2020-05-13 10:03:00
Don't work...file damaged
2020-05-13 20:28:43
regarding oSokker there is solution on Polish forum

just replace manifest.json content with this (added thing are bold font)


Where should I go to access this content? I cannot find that option
2020-05-13 20:57:49
well, first of all, I see that in the quoted message I forgot about adding information that it could be done for oSokker for Chrome and not for Firefox

If You have oSokker for Chrome then:
* if it is .crx file (extensions in Chrome-like browser might be just directories or .crx files, but the latter does not work on Chrome on Windows)
1. use 7-zip or other app to extract contents of that file into some directory, for example c:/osokker
* if You have the directory with contents
1. look for manifest.json there (it would be in c:/osokker/manifest.json)
2. open that file for editing
3. paste the content I displayed in earlier posts
4. go to chrome://extensions in Chrome
5. switch on developer mode if it is disabled
6. click load unpacked extension
7. point to directory c:/osokker (the directory c:/osokker is just an example, it can have any name)

BUT THAT IS POSSIBLE ONLY FOR CHROME AND OTHER CHROME-BASED BROWSERS
2020-05-14 23:31:10
Skunk dosent work for me, it seems i dont know how to find osokker on my pc

i think it is time to quit this game

p.s. it seems i managed to make skunk work somehow, but i dont know how to fix osokker, and thats the very important thing i need

so i guess its still the time to quit this game :D
(edited)
2020-05-14 23:46:15
Message deleted