Expanded Fronts

Hi All,

You can make Revisr work with MAMP by opening the following file:
/Applications/MAMP/Library/bin/envvars

And commenting out the two lines 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

This will be included in the documentation today, so I’m marking this as resolved.

Let me know if you run into any further issues. Thank you.

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 Valerio,

Thanks for trying out Revisr and leaving your feedback!

Hi Andrew,

It’s something we’re looking into, although the issues with MAMP support are beyond simple plugin configuration and require making sure that the environment paths to Git are set correctly for MAMP.

When we find a good solution that seems to work for everybody, we’ll update the plugin and/or documentation as necessary.

Hi Adam,

I haven’t head back from you on this so I’m marking this as resolved as we have tested on multiple systems and confirmed that this functionality is working (provided that the permissions are set correctly and the full path is provided if on windows).

If you run into any further issues, please let me know and I will be glad to address them.

Thank you.

Does anything show up in your error logs regarding the white screen issue? I’ve tested in multiple environments and have not been able to replicate, but would like to get this fixed for you.

Hello,

I haven’t heard back from you, but we just pushed out another update that should address the other issue you mentioned above. Please check and let me know if you run into any further issues.

Thank you.

Hello,

Revisr was designed to work with the WordPress installation being in the root of the git repository. Any structure changes inside of that shouldn’t affect that, but in this case it looks like the WordPress installation is in a “core” subdirectory.

If it is not compatible with your structure, you will be notified with an error on the Revisr dashboard.

Also, we just pushed out a release that should address most errors on Windows installations. Please let me know if you have any further questions.

Thank you.

Hi Adam,

We just rolled out an update that may address this issue depending on the environment. If the backup still is empty for you, please try the following:

– Verify that the correct permissions are set on the uploads folder
– If using windows, set the path for mysqldump. This link should point you in the right direction.

Hello,

Just pushed out an update that should address the errors above. Also updated “Pending Files” to “Untracked Files” as per your suggestion.

Please check and let me know if you run into any further issues. Thank you.

Sorry, to clarify on this:

Since Revisr allows you to optionally keep a separate version of each branch…

I meant to say that Revisr allows you to keep a separate version of the files and the database for each branch in Git.

Or you can just track files. Ultimately, it’s however you want to use it and I look forward to seeing new/different implementations.

Hello,

We decided to allow the entire repository to be tracked to allow for complete backups & restore points of a website if so desired.

Another major benefit is that you could perform a major core/plugin upgrade on a new branch without affecting the main branch/production website. Since Revisr allows you to optionally keep a separate version of each branch, you could test out a core upgrade on a new branch and switch back if it causes any issues, and not have to worry about the differences in the database.

However, you have the ability to add files or entire directories to the gitignore through the plugin settings page.

This way, if you want to track the entire repository, or just themes/plugins, you can.

As mentioned in this thread, you could use something like the following to only track your themes directory:

/*
/*/
!/wp-content/themes/

I’m marking this as resolved since it has been discussed and it is not required to track the entire repository, only that the parent WordPress installation is installed in one.

Please feel free to post any follow up comments/questions to this thread and I’ll be glad to address them.

Thank you.

Hi Adam,

Did some more testing on Mac OSX with MAMP and confirmed the issue is specific to MAMP. It appears that MAMP forces a different path for Git than the default path.

So instead of the default path, in my case usr/bin/.., it was pushing through to a path specific to MAMP. See here and here for more information and some possible fixes.

Thanks for trying out Revisr and for posting such a detailed report.

We’ve tested on several machines and have not been able to replicate. Are you seeing the issue consistently? Do the pending files work?

Noted on your feedback regarding UI. This is something we will be continuing to improve over the coming months as more people sound off on it.

Thanks again!

Rolling out a possible fix for this tonight.