Hello,
Can you please confirm if the path to git been set on the server? Are you able to do a git commit from command line in that directory?
Currently Revisr versions a single sql dump of the file through git. You can read more about it on the FAQs page:
https://wordpress.org/plugins/revisr/faq/
OK, the path thing seems to have fixed the problem, thx. I’m still having an issue with not being able to commit with Revisr. Monitoring the status of the repo with git, I can see that the files get staged but when I hit the “commit files” button, revisr says the files got committed but I can see that they haven’t. Is there a way I can attach screenshots?
Can you please try doing an initial commit and pushing to the remote through SSH and seeing if that corrects the issue?
If not, feel free to email support at expandedfronts.com so we can look into the issue further.
Thank you.
I got the files committed via git bash so that’s a reasonable work around until I’ve got more time, but now I have another question – I’ve installed git on our live server and have been able to use git’s command line to clone the remote. When I try to view the site I get a “error establishing a database connection”, which is natural because the DB that exists on the live site has different pathnames. So where do I go from here? I can manually edit the DB for it to work on the live server, but I obviously don’t want to do that every time…
If I understand the issue correctly, you could add the wp-config.php file to the .gitignore on the repo so it’s no longer tracked and pulled down. This would prevent you from having to update it manually when pushing/pulling.
If you’re running into a different issue, please let me know. thanks!
Thanks for the quick response. No, I understand about the gitignore file. What I’m saying is that in a wordpress installation the sql database has path references that need to be updated for that particular installation (ex, “localhost” vs “some other URL”). I was hoping that Revisr would automate that process.
Currently the database host is pulled directly from the wp-config.php. I will look into adding this as a dynamic setting for the next release.
OK, thanks for that clarification. I just updated my WP installation to the latest version and now I cannot get into the Revisr dashboard, is this a known bug? I’ve reset the WAMP server.
Hello,
The issue is likely the remote settings. A slight bug with WAMP is that when Revisr can’t communicate with a remote (for example, if it fails due to authentication), Revisr will freeze on the dashboard page.
You can fix this by making sure you have the correct remote URL and username set on the settings page. It may be worth trying the ‘https://’ method of authenticating with Bitbucket or Github, as it allows you to specify the password.
In the next release, settings will be validated upon save so you’ll know right away if one of the settings are wrong.
Let me know if you run into any further issues.
OK, maybe I’ve just got the format wrong. Can you please help me with the following settings (generic examples would be very helpful):
– Remote Name: is this (as the note alludes) the name of the remote branch, or what exactly?
– Remote URL: is this the URL of the login screen, the remote repo? I use bitbucket.
– Path to MySql: to the mysql root, the executable, or what? We’re running on both LAMP and WAMP servers.
Thanks for the information!
I’m also having the issue that Revisr is putting changes that should be ignored (because of .gitignore) into the staging area.
Nevermind that last one, the gitignore file got deleted in (I think) a bad pull because I don’t have Revisr set up properly.
Revisr broke my local repo today, took me the afternoon to figure out that it writes to the .git/config file. Some better documentation is really in order, maybe I can help you with that.
Can you please provide more details on what and how it broke? It writes to the .git/config file as this is the default functionality with git. Does the Apache user running Revisr have permissions to write to the .git directory?
Better documentation is almost finished and will be released this weekend.
before installing and configuring revisr, I started with a working repo. then I installed and configured revisr (in hindsight obviously improperly) and attempted to pull/commit/push etc with only partial success. stopped using revisr to perform git operations using the command line and got fatal errors about the remote not being found. edited the .git/config file per the code blocks and command line operations started working again.
this first code block is what revisr wrote to the config file
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
[remote "origin"]
url = https://git@bitbucket.org:user/repo
fetch = +refs/heads/*:refs/remotes/origin/*
pushurl = https://git@bitbucket.org:user/repo
[branch "master"]
remote = origin
merge = refs/heads/master
[user]
[user]
name = Anthony Dobaj
email = apdobaj@facetapp.com
this second one is what actually works
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = git@bitbucket.org:user/repo
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
