I'm currently testing Github-Updater with our self-hosted Bitbucket Server installation. I've noticed that if I add a full url in Plugin URI found in Settings->Github Updater Settings -> Install Plugin Tab it still connects to https://bitbucket.org even though I've added our installation's url.

Is this a bug or is a private self-hosted Bitbucket installation not (yet) supported? If not, what needs to be done to support this? I might be able to send in a PR.

ps: My compliments on your code. My first impression is that it looks well-defined and well-written. and I'm sure I might learn a thing or two from it :)

Could you add new commands to wp-cli for install remote plugins and themes?

https://github.com/wp-cli/wp-cli/wiki/Commands-Cookbook https://github.com/wp-cli/wp-cli/wiki/List-of-community-commands https://github.com/wp-plugins/ewww-image-optimizer/blob/master/iocli.php

Please integrate support for language packs into the plugin. This would allow plugin/ theme developers to host translations also on GitHub/ Bitbucket/ GitLab and offer automatic updates for them, independent from plugin/ theme releases.

For requested integration I would see two alternatives to make it happen:

1. developer sets up a special translations repository with sub folders per plugin/ theme slug and in the plugin/ theme folder have the various language files --> in "GitHub Updater" plugin user just references the repo and plugin will do the rest... :)
2. developer sets up a special translations folder within the plugin/ theme repository and in there hosting the various language files --> GitHub Updater plugin could recognize such folder in the repo automatically and do the rest... :)

There are pros and cons for either alternative -- and maybe there are even more ways of doing it.

However, integrating support for language packs would make it lot easier to host plugins/ themes fully on services like GitHub when also translations could be updated fully automatically without always doing a new plugin release.

I would really hope for such a support sometime soon or at least for a fruitful discussion here. Thanks in advance!

When I've installed a theme using your GitHub Updater plugin from GitLab, I'm not able to switch to any different version - since no earlier tags are shown (see the following screenshot).

This issue might be related to #464

Problem is that most WP developers are used to developing "staging" code in the master branch. Why? Because thats how WP has us do it in the WP.org SVN repo. You do not want the "default" update code to ever pull from the master branch. Bad practice.

Is it possible to use Gitea together with GitHub Updater?

Gitea is a lightweight alternative to GitLab for a self hosted environment. It's small, its fast and it's very similar to GitHub :)

The site the theme is on shows that there is an update for it available, but on MainWP I see 0 theme updates available. I am not sure what I missed. Is there any chance the fact that the repo is private might cause issues with MainWP?

Following the wiki at restful-endpoints-for-remote-management everything works as described (eg. curl related calls). When I push (test or not) to the Gitlab repository the webhook/integration trigger is triggered I get the above mentioned error: Hook execution failed: Net::ReadTimeout

Request URL: POST http://www.domainame.com/wp-admin/admin-ajax.php?action=github-updater-update&key=76bb2b7c819c36ee37292b6978a4ad61&theme=theme-name [internal error]
Trigger: Push Hook
Elapsed time: 3.29 sec

instead using this testing REST endpoint

Request URL: POST http://webhook.site/d6eb13a3-82a5-4385-abc6-91822f508b35 [200]
Trigger: Tag Push Hook
Elapsed time: 0.35 sec

from the GitLab documentation about webhooks, I read:

Your endpoint should send its HTTP response as fast as possible. If you wait too long, GitLab may decide the hook failed and retry it.

Surfing the net i found this other similiar issue (which makes me think that there is a timeout after 3 seconds..)

Is it possible that this is also due to wordpress performance limits? (eg. minimum response time) if so, it would be almost impossible to use this feature with the online version of GitLab...

Any way, thanks for the effort!

I am using your plugin on a staging site currently: https://staging.thebirdthebear.com/ When it works, it's amazing, but I'm having serious issues with it.

When I log in to check for updates I've made, I get this screen even though I've installed a theme and connected to Bitbucket already, and set it up properly:

I found that if I click Save, the page will refresh, and I'll get this page:

I'll click over to the Bitbucket tab and my theme shows, but I have to re-enter everything, and check that it's Private repo again:

I do:

Hit enter, and this screen displays:

At this stage, the new theme changes on Bitbucket haven't been pulled, and I'm pretty much where I started. The last couple changes, I've just uploaded via FTP since this hasn't worked.

Happy to provide any information that would help in resolving this. If you need error logs, or access to the staging site, I'm happy to provide.

Hey there

I just installed your plugin in several ways (git clone, zip, composer) and get multiple notices as in the attached file.

github-updater-notices.txt

So, i have to confirm this, from #474 if you see my last message there, referenced comment I did some digging and experiment. I have created new account on bitbucket and pushed my repo there and let it be Public. After filling bit bucket settings in github updater setting page, i saw notification of new update for my plugin and was able to update successfully my bitbucket hosted plugin with github-updater6.0.0. New version i.e 6.0.2 failed miserably #481 Now, after making the same Repo private i recived the same error mentioned in issue 474 and same error message as shown below in picture.

I now strongly believe my username and password in bitbucket settings of github-updater are correct and In case repo is private, github-updater is having trouble with bitbucket api. Please help.

Many thanks.

Hi! I've updated to the latest version (11.1.8), and my wp-admin console and error logs are being bogged down by the following link throwing a 404 error:

https://example.com/wp-content/themes/example/vendor/afragen/wp-dismiss-notice/js/dismiss-notice.js?ver=6.0.3

I searched for it in my files, and found that the "afragen" reference is in this plugin. Looks like it's not pointing at the right path (going for the theme folder rather than the plugins folder).

Can you fix this? Thanks!

Hey @afragen and thanks for your hard work with Git Updater. I have been following it for the last few years and just recently started digging into things more.

One thing I noticed is the "tooltips" under Settings >> Git Updater >> GitHub tab don't work on mobile. Even when clicking on them nothing displays, even when I changed my mobile device to force load a Desktop version.

Perhaps some layout tweaks would help resolve that. Cheers!

I have a branch oauth where I was working on OAuth authentication for all git hosts. I got to a reasonable place but hit a roadblock as each git host requires the creation of on OAuth app that requires a callback. This callback must be set to a site.

My only recourse would be to create a site whose sole function would be to take the authentication callback and figure out how to return the token to the user. My guess is that I would essentially be displaying OAuth tokens on the site that the user would copy into the appropriate location. This is not what I envisioned for this feature.

I could certainly be wrong but I don't see a way for the plugin to ask for an OAuth token and have the response returned to the user's site.

It looks like #323 and #848 are going to be difficult and I don't have the time or resources at the moment. Sorry.

I have created a Git Updater team for Slack.

Anyone can join and any member can send out invites. Any member may create a new channel.

Please let's keep actual issues here but any other discussion should take place in Slack. Please click here for an invite.

The golden rule applies. Everything is quite unrestricted at the moment. If I find the need to restrict something I will let everyone know.

I hope you all choose to participate. I enjoy the feedback and the engagement.

Git Updater is now dogfooding it's own Language Pack updates. Translation files reside in a separate repo, https://github.com/afragen/git-updater-translations

Translators The main plugin will always contain the most recent POT file, as will the official Language Pack repo.

I'm getting prepared for the next release and many new strings have been added. Please make PRs to afragen/git-updater-translations