Subpage under development, new version coming soon!
Subject: oSokker
But is it enabled or still disabled? The add-on
(edited)
(edited)
Enabled, of course. And I can't see the oSokker in the game
So this workaround works:
type in Firefox url: about:config
search for line: xpinstall.signatures.required
Double click line and true will change into false
because its purpose is to make enabling unsigned add-ons (like oSokker) possible. Unsigned add-ons are disabled automatically in Firefox 43 if this property is not set to false. It wont make oSokker work magically if it didn't work earlier.
You guys probably have wrong/bad/deprecated oSokker version installed.
If You are using new sokker layout install it from here:
https://copy.com/FjGuiODftzfA/oSokker4Chrome/osokker_firefox.xpi
And if You are using old layout install it from here:
https://copy.com/FjGuiODftzfA/oSokker4Chrome/old/osokker_firefox.xpi
type in Firefox url: about:config
search for line: xpinstall.signatures.required
Double click line and true will change into false
because its purpose is to make enabling unsigned add-ons (like oSokker) possible. Unsigned add-ons are disabled automatically in Firefox 43 if this property is not set to false. It wont make oSokker work magically if it didn't work earlier.
You guys probably have wrong/bad/deprecated oSokker version installed.
If You are using new sokker layout install it from here:
https://copy.com/FjGuiODftzfA/oSokker4Chrome/osokker_firefox.xpi
And if You are using old layout install it from here:
https://copy.com/FjGuiODftzfA/oSokker4Chrome/old/osokker_firefox.xpi
Now its working! thanks my firend. That was the problem! ;)
All known info to make oSokker work without problems:
oSokker for NEW layout
Firefox: https://copy.com/FjGuiODftzfA/oSokker4Chrome/osokker_firefox.xpi
Opera 12.x: https://copy.com/FjGuiODftzfA/oSokker4Chrome/osokker_opera.zip
Chrome / Opera 15+: https://copy.com/FjGuiODftzfA/oSokker4Chrome/oSokker4Chrome.crx
oSokker for OLD layout
Firefox: https://copy.com/FjGuiODftzfA/oSokker4Chrome/old/osokker_firefox.xpi
Opera 12.x: https://copy.com/FjGuiODftzfA/oSokker4Chrome/old/osokker_opera.zip
Chrome / Opera 15+: https://copy.com/FjGuiODftzfA/oSokker4Chrome/old/oSokker4Chrome.crx
If add-on still isn't working with Firefox:
Type in Firefox url: about:config
Search for line: xpinstall.signatures.required
Double click line and true will change into false
Restart browser and all should work again. It worked for me :)
(edited)
oSokker for NEW layout
Firefox: https://copy.com/FjGuiODftzfA/oSokker4Chrome/osokker_firefox.xpi
Opera 12.x: https://copy.com/FjGuiODftzfA/oSokker4Chrome/osokker_opera.zip
Chrome / Opera 15+: https://copy.com/FjGuiODftzfA/oSokker4Chrome/oSokker4Chrome.crx
oSokker for OLD layout
Firefox: https://copy.com/FjGuiODftzfA/oSokker4Chrome/old/osokker_firefox.xpi
Opera 12.x: https://copy.com/FjGuiODftzfA/oSokker4Chrome/old/osokker_opera.zip
Chrome / Opera 15+: https://copy.com/FjGuiODftzfA/oSokker4Chrome/old/oSokker4Chrome.crx
If add-on still isn't working with Firefox:
Type in Firefox url: about:config
Search for line: xpinstall.signatures.required
Double click line and true will change into false
Restart browser and all should work again. It worked for me :)
(edited)
That's really cool !!! Thx finally it works with those infos !! :-)
Still don't working with Chrome, because it's not an official add-on...
Anyway, where can I find these foxy-smileys?
Anyway, where can I find these foxy-smileys?
kryminator to
Boczy™
it works on Chrome, the workaround for Google Web Store or whatever it is called is to unzip it into some directory, let's call it X, then open Chrome go to addons site, it was chrome://extensions I believe, and after that check something like "developer mode" near top right corner, click newly shown button "load unpacked extension" and point to directory X there - it should load an addon if everything was done right
kryminator to
Boczy™
Hmm, that's strange. I thought You would have 3 buttons under that "Bovitmenyyek" header. It should look like this:
Boczy™ to
kryminator
Yes I have it, I'm just scrolled down the picture to show you how looks like my oSokker after I did what you advise me. Every time when I install oSokker to my Chrome (if I have lucky and it's working when I install freshly), the next time I start my browser, it says I can't use this addon, because it isn't in the Google fucking Store... :(
kryminator to
Boczy™
Nope, You probably didnt do what I advised. At least, it looks like it. Maybe I wasnt precise enough. Nevertheless, it is possible to use oSokker on Chrome normally.
Every time when I install oSokker to my Chrome (if I have lucky and it's working when I install freshly), the next time I start my browser, it says I can't use this addon, because it isn't in the Google fucking Store... :(
I know how it works and indeed it works as You described BUT only if You try to install it in normal way = install it as standard Chrome crx add-on.
If You want it working on Chrome You need to install it by not-so-normal way. So once again, follow the steps:
1. download this: https://copy.com/FjGuiODftzfA/oSokker4Chrome/old/oSokker4Chrome.crx
2. Next, treat that file like zip archive and unzip it to some directory for example C:/oSokker
After that You should have all oSokker files DIRECTLY inside exactly that directory, so for example path C:/oSokker/oSokker.js would be valid.
If You are unable to unzip it by built-in Windows zip tool, You may try doing it by proper "file archiver" program like 7zip or some "commander" program (like total commander, unreal commander, double commander etc.).
3. Ok now assuming You have unzipped oSokker , open Chrome and go to chrome://extensions
You may even remove the old oSokker installed as *.crx file
4. Click button adequate to "Load unpacked extension..." from my image and select directory when You unzipped oSokker (the one with oSokker.js, no subdirectories etc.)
In example it would be directory C:/oSokker
5. Apart from standard extension information, You should have now something like this under oSokker extension section:
"Loaded from C:/oSokker" - that means the extension files are in that directory
And on image You posted there is no file path shown, so even if I dont understand a word in Hungarian, I suspect that currently (on image) You dont have oSokker installed in the way I just described.
6. Enable that extension if needed
Every time when I install oSokker to my Chrome (if I have lucky and it's working when I install freshly), the next time I start my browser, it says I can't use this addon, because it isn't in the Google fucking Store... :(
I know how it works and indeed it works as You described BUT only if You try to install it in normal way = install it as standard Chrome crx add-on.
If You want it working on Chrome You need to install it by not-so-normal way. So once again, follow the steps:
1. download this: https://copy.com/FjGuiODftzfA/oSokker4Chrome/old/oSokker4Chrome.crx
2. Next, treat that file like zip archive and unzip it to some directory for example C:/oSokker
After that You should have all oSokker files DIRECTLY inside exactly that directory, so for example path C:/oSokker/oSokker.js would be valid.
If You are unable to unzip it by built-in Windows zip tool, You may try doing it by proper "file archiver" program like 7zip or some "commander" program (like total commander, unreal commander, double commander etc.).
3. Ok now assuming You have unzipped oSokker , open Chrome and go to chrome://extensions
You may even remove the old oSokker installed as *.crx file
4. Click button adequate to "Load unpacked extension..." from my image and select directory when You unzipped oSokker (the one with oSokker.js, no subdirectories etc.)
In example it would be directory C:/oSokker
5. Apart from standard extension information, You should have now something like this under oSokker extension section:
"Loaded from C:/oSokker" - that means the extension files are in that directory
And on image You posted there is no file path shown, so even if I dont understand a word in Hungarian, I suspect that currently (on image) You dont have oSokker installed in the way I just described.
6. Enable that extension if needed