Skip to content
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

Chrome can't install extension #2

Closed
benwerd opened this issue Feb 2, 2015 · 12 comments

Comments

Projects
None yet
3 participants
@benwerd
Copy link

commented Feb 2, 2015

On my system, the plugin generates a .zip. Unfortunately, Chrome refuses to install it on my system (OS X Yosemite), declaring that the archive is invalid.

It may want a .crx archive. There's a guide to building one here:

http://stackoverflow.com/questions/5013263/create-google-chrome-crx-file-with-php

@mapkyca

This comment has been minimized.

Copy link
Owner

commented Feb 3, 2015

Hmmmph...

Is the zip itself valid (i.e. you can open it with whatever it is apples use to read archives)?

Will look into the crx (good for a number of reasons)

@mapkyca mapkyca closed this in b1aa313 Feb 3, 2015

@mapkyca

This comment has been minimized.

Copy link
Owner

commented Feb 3, 2015

Ok, give the latest version a crack... now generates a CRX file.

@benwerd

This comment has been minimized.

Copy link
Author

commented Feb 3, 2015

Works beautifully!

@rikmendes

This comment has been minimized.

Copy link

commented May 1, 2016

Does not work on Dreamhost Shared hosting. ask about a Phar extension ?
ends up on a white page /yourdomain/chrome/download
no problem getting the CRX on a test site on a VPS instance.

screenshot_185

@mapkyca

This comment has been minimized.

Copy link
Owner

commented May 5, 2016

Looks like you're missing the extension...

@rikmendes

This comment has been minimized.

Copy link

commented May 5, 2016

But isn't it also everyone using or trying to use knownChrome from shared
hosting such Dreamhost?

No way to install the Phar extension from what I know at Dreamhost..
Le 5 mai 2016 12:04, "Marcus Povey" notifications@github.com a écrit :

https://github.com/mapkyca/KnownChrome/issues/2Looks like you're
missing the extension...


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#2 (comment)

@mapkyca

This comment has been minimized.

Copy link
Owner

commented May 8, 2016

Phar should be installed for PHP > 5.3, but I suspect the shared hosts are disabling it in config.

Perhaps this is something you can enable on your host?

@rikmendes

This comment has been minimized.

Copy link

commented May 9, 2016

I will contact Dreamhost and see what they say...after all they were doing a
promo to use Known and their shared hosting..

I have 2 accounts at dreamhost and both of them fail at having Phar installed.

thanks for your reply, i'll report what they say here.

Sent from Nylas N1, the extensible, open source
mail client.

On May 8 2016, at 11:09 am, Marcus Povey <notifications@github.com>
wrote:

Phar
should be installed for PHP > 5.3, but I suspect the shared hosts are
disabling it in config.

Perhaps this is something you can enable on your host?


You are receiving this because you commented.
Reply to this email directly or [view it on GitHub](https://github.com/mapkyca
/KnownChrome/issues/2#issuecomment-217704885)![](https://github.com/notificati
ons/beacon/ALl4e0z1PDZCmm0t6L8uXyejm-Alo8inks5p_ahegaJpZM4DaqvK.gif)

@mapkyca

This comment has been minimized.

Copy link
Owner

commented May 10, 2016

Well, the Chrome extension isn't "official" Known, so I'll give them some slack ;)

I'll be interested in what they say, and their reasons (I suspect they just blanket disable extensions that are not commonly used for security reasons), meanwhile I'll see if I can find an alternative/workaround.

@rikmendes

This comment has been minimized.

Copy link

commented May 11, 2016

Just confirmed with Dreamhost, it's easy to fix
just add extension=phar.so into /home/username/.php/5.6/phprc
or the consequent PHP version currently in use.

@rikmendes

This comment has been minimized.

Copy link

commented May 11, 2016

is it intended that after publishing a new post with the Chrome extension the extension refresh to this view ?
screenshot_199

wouldn't be more logical to have a notification sayin it got successfully posted or something else than loading the whole website in "mobile" mode ?

@mapkyca

This comment has been minimized.

Copy link
Owner

commented May 12, 2016

Probably...

It follows the same flow as the firefox endpoint, so this is probably something for upstream Known.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.