I’m not quiet sure if I understand you correctly.
If git is in the root folder of Mamp, revisr won’t obviously be able to recognize it. Git need to be in the install folder of WordPress.
In Mamp this is normally a folder with the domain-name.
Hello,
This is an issue with the MAMP library path. You can fix this by opening the following file:
/Applications/MAMP/Library/bin/envvars
And commenting out the two lines in that file so it looks like this:
if test "x$DYLD_LIBRARY_PATH" != "x" ; then
#DYLD_LIBRARY_PATH="/Applications/MAMP/Library/lib:$DYLD_LIBRARY_PATH"
else
#DYLD_LIBRARY_PATH="/Applications/MAMP/Library/lib"
fi
export DYLD_LIBRARY_PATH
Then save the file and restart MAMP for the changes to take effect. Let me know if you have any further issues.
Thank you.
Hi, thanks for the fast reply!
sorry yes that’s what I meant, git is installed in the root folder of the WordPress install.
I tried commenting out those 2 lines and restarting MAMP but still see the error…
Where is Git installed on your computer? Did you download it directly from Git and install? Or was it installed via command line tools?
Also, please try making a commit and pushing to any remotes through command line if you haven’t already.
Ahh that worked, I normally use Tower as my git client not the command line but did a quick commit and pushed it to the remote via the command line, hit refresh on the dashboard and the warning has gone and it seems Revisr is now picking up any changes!
Thanks so much for the quick replies! Luv your work!
I am having the same problem. After commenting out the two lines as directed and restarting MAMP I get this error:
/Applications/MAMP/Library/bin/envvars: line 23: syntax error near unexpected token `else’
/Applications/MAMP/Library/bin/envvars: line 23: `else’
commenting out the whole if statement including fi returns no error, but still does not work.
Are you using a git app like Tower or the Github app? That was my issue, Tower was using a username and password as authentication rather than the private key so revisr wasn’t picking it up… Doing a commit through the command line sorted it out as it used the key… Hope that helps
I am using git from the command line and I am able to commit and push.
Hi Tommy,
Can you please let me know the following:
– The version of Git you’re running
– The version of OSX
– How you installed Git (where you downloaded it)
– Where is your remote?
– Does the issue happen with a fresh repository, an existing one, or both?
– I know you said you were able to push via terminal, but can you please confirm if this was for the actual repository that you’re setting up with Revisr?
– Does the branches list to the right populate with any branches after commenting out the lines in your envvars and restarting MAMP?
Also, please let me know the version of MAMP as well.
Sorry for all of the questions, but we need as much information as possible to diagnose as it isn’t actually an issue with Revisr but is dependent on the environment. Revisr was primarily built for Linux, but we’d love to support as many environments as possible.
Its working now. I don’t know why.
It works both with the lines in envvars intact and with the whole if statement removed.
Must have been a mistake of mine somewhere… weird.
Right now the lines in envvars are intact and I just restarted MAMP and its working.
if you still want the answers to those questions:
git version 2.0.1
I am using Mavericks 10.9.4
i downloaded git-2.0.1-intel-universal-snow-leopard.pkg
from http://git-scm.com/
after installing I had to:
alias git=”/usr/local/git/bin/git”
because in Mavericks “There is a preinstalled git wrapper in /usr/bin used by Xcode”
I learned this from http://superuser.com/questions/666086/install-git-under-osx-mavericks
my remote is on github
this is a fresh repo
I can confirm that this is the repo that i’m trying to use with Revisr. I’m in the wordpress root folder.
I don’t understand that last question.
Thank you very much for the quick response. Sorry I don’t know where my mistake was.
MAMP 3.0.5
Earlier I did have repo inside the repo. (for a theme) maybe that was it.
Marking this as resolved as it appears to be working for you, but please let me know if you run into any further issues and I’ll be glad to help out.
Thank you.
