Does anyone know how to stop wordpress.org from checking for updates on a theme, but still keep custom auto-updates for the theme? I use this http://w-shadow.com/blog/2011/06/02/automatic-updates-for-commercial-themes/ for our theme’s auto-updates, but there is now a theme on wordpress.org with the same name that our user’s are being prompted to update to… which has been causing a bunch of issues.
I’m wondering if I can just change the name of the theme within the style.css file of the theme, or if I need to change the directory name of the theme… I’m not exactly sure what wordpress.org references in order to match up a theme with one that resides in the repository.
Or, I’m wondering if there’s a setting to stop wordpress.org from checking, but still keep the update checker running in order to update with the custom updater.
Thanks for any help!
No, I haven’t found a solution to this issue yet… I’ve given up on it for now and am just storing my versions on Github.
Let me know if you happen to come across a solution.
I’ve been using GitHub to push WP plugins to the WP repository for awhile now, though, I still don’t know a whole lot about GitHub.
Today when trying to update my plugins I am able to push the updates to WordPress using:
git svn dcommit
And that works fine, but when I try to add a new tag to the svn using:
git svn tag 1.0.2
I get the following error:
Authorization failed: POST of '/!svn/me': authorization failed: Could not authenticate to server: rejected Basic challenge (http://plugins.svn.wordpress.org) at /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core/git-svn line 1220.
I’ve tried to research answers to this, but am not having any luck finding a solutions (or completely understanding them).
Has anyone run into this before, or have any suggestions as to what I need to do to resolve this?
What exactly is Envato’s best rate (for authors)?
Currently I’m seeing: 17.5% of the Item Price is the author fee we’re currently charging you. You’ve hit our best rate!
But, I also know other authors who have: 12.5% of the Item Price is the author fee we’re currently charging you. You’ve hit our best rate!
To get out of this state… pick the branch that you believe is the most correct (local, Github, SVN) and then (assuming you’ve chosen your local) you can force-push (git push origin master—force to completely overwrite the remote.
I have been using the “git push origin master—force” and it has resolved my issues. Thank you very much for the help!
Thank you very much for the in-depth response! I greatly appreciate it… I’m fairly new to any type of SVN or GIt workflow, so even trying to Google search this stuff is somewhat confusing.
To clarify a bit on what I was doing, I only started trying to use the rebase after I was getting the fast forward errors… just to try something different to see if I could get it to work. There must be something that gets modified on Github after the push to the WP SVN. I do have a handful of other projects I’m syncing with Github that are not being synced to the WP SVN which work seemlessly (I have never run into the Fast Forward issue).
My normal workflow is:
1. Make changes to my project locally, then in Terminal 2. $ git status (to double-check the changed files 3. $ git commit -am “Put my note here” 4. $ git push
At this point, my non-WP SVN projects update on GItHub as expected, but this is where my WP SVN projects run into the Fast Forward error.
But, I will take a look through the links you provided and try the force push to GitHub as I am the only one working with the repository and my projects.