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

JS Not Loaded on GitHub Enterprise #43

Closed
rianrainey opened this issue Sep 20, 2016 · 17 comments
Closed

JS Not Loaded on GitHub Enterprise #43

rianrainey opened this issue Sep 20, 2016 · 17 comments

Comments

@rianrainey
Copy link
Contributor

First of all, great plugin!

This worked well for me for a couple weeks and now I'm unable to get the js to load on GH enterprise pages. It works as expected on non-GHE pages.

I've disabled all other plugins and I still can't get GHE PR files to toggle. When I use the dev tools inspector I can see that the plugin never loads its js/css. However, regular GH pages load the js/css correctly.

I get prompted for new permissions when I enter the GHE url in the options, but I see no change in functionality. I'm wondering if other GHE users have experienced recent degradation.

Thanks for any help. This plugin helps very well w/ managing PRs.

@rianrainey
Copy link
Contributor Author

rianrainey commented Sep 20, 2016

I decided to download different versions of the app and load them manually as extensions w/ developer mode turned on. Checked sha: c6f02dd and it works correctly for me. 4fd610f broke GHE support. b4b3c26 did not restore GHE functionality for me. Hope this helps somebody else.

@ghost
Copy link

ghost commented Sep 20, 2016

Thanks @rianrainey, I was able to test the prompting for new permissions, but I was unable to test the content script being loaded and working properly because I don't have github enterprise. It is pretty simple code, especially given that the permissions are being requested... would you care to take a shot at a PR to solve this issue?

It does have the potential to turn into something much more difficult... as maybe we can't conditionally load the content script based on the optional permissions... we'll have to see. If you don't think you can figure it out or don't care to, I will certainly attempt to fix it, but I won't be able to look at it for a week as I'm about to leave on holidays.

Thanks for logging the bug!

@lzelevinsky
Copy link

Same thing for me too - the app used to work for me and stopped working on github enterprise

@ghost
Copy link

ghost commented Oct 7, 2016

OK, as I mentioned, I was able to test that the permissions prompting still works, but I will either have to get creative to see if I can find out how to fix the rest, or accept a PR from someone who uses github enterprise (which is how this extension ended up supporting enterprise in the first place).

It looks like I can start a free trial of enterprise... so that could be an option for me.

@lzelevinsky
Copy link

I'm happy to try something sometime, but don't have any experience with developing chrome extensions, so would need to climb the learning curve a bit.

@ghost
Copy link

ghost commented Oct 31, 2016

I finally started looking into this this weekend. I believe the problem is that the content script is never told to load. Since switching to the optional permissions, the content script would have to be programatically injected into those pages, and I'm not seeing that happen anywhere.

I have what SHOULD be the fix in place but it wasn't quite working and I ran out of time... but it should be fixable from here, and I shouldn't have to widen any permissions which is great.

@lzelevinsky
Copy link

👍

@ghost
Copy link

ghost commented Nov 2, 2016

Hey all,

I just pushed up version 2.10.1 that SHOULD address this issue. I tested it using my own trial version of Github Enterprise, and found several issues that I addressed. I also found even more corner cases and bugs of how the plugin loads, but those are somewhat unrelated to Github Enterprise and more to github's mixed use of full page reloads and client templating.

I am going to do a complete rewrite of this extension soon (I was hoping the need for this extension would have died soon after, but Github apparently has no interest in adding it), so I'll address the corner bugs then, but GHE functionality SHOULD be returned.

Can you guys test it and let me know... and if we are good I'll close the bug!

@lzelevinsky
Copy link

Will do! 2.10.1 not showing up in the store for me yet.

Very much appreciate your work on this - thanks. I miss the collapsing files functionality every day :).

@lzelevinsky
Copy link

Got latest version.

Collapsing / expanding files works - which is awesome and is mostly what I wanted.

The checkboxes to show/hide added and deleted lines are there but don't work.

Tried them on github.com and they work fine but not on the enterprise page - checking and unchecking them doesn't do anything that I can see.

Thanks a lot.

@Nilegfx
Copy link

Nilegfx commented Dec 15, 2016

It had this issue with Version: 2.10.3

An easier solution is to do the following:

  • install the extension
  • add your GHE URL
  • go to chrome extensions page
  • disable the extension and enable it back again

@ghost
Copy link

ghost commented Dec 18, 2016

Hey @lzelevinsky, sorry, I somehow missed your comment about the checkboxes. I assume they are still not working?

I just removed my github enterprise VM a few days ago too, ugh, and my free trial is probably over. I probably won't fix this feature soon, but I will try and fix it sometime after the holidays. Thanks for letting me know!

@ghostlandr
Copy link
Collaborator

If one of you with GitHub Enterprise wants to try out the changes in #47 , that'd be awesome.

@Nilegfx @lzelevinsky @rianrainey ?

@rianrainey
Copy link
Contributor Author

I just tried #47 and I'm still not able to get it to work. Here is my error:

screen shot 2017-05-03 at 8 30 15 am

@ghostlandr
Copy link
Collaborator

Oh boy. Yeah that's a typo.

@ghostlandr
Copy link
Collaborator

@rianrainey I fixed that, if you'd like to try again.

@ghost
Copy link

ghost commented May 4, 2017

As soon as he confirms it, we can get it into the released version!

@ghost ghost closed this as completed in #49 Aug 19, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants