Expanded Fronts

Sorry, should be as follows:

mysqldump -u YOURUSERNAME -pYOURPASSWORD YOURDB >revisr_db_backup.sql

Sorry, should be as follows:

mysqldump -u YOURUSERNAME -pYOURPASSWORD YOURDB >revisr_db_backup.sql

Hi Adam,

Can you please try running the following from command line?

mysqldump -u YOURUSERNAME -pYOURPASSWORD YOURDB . " >revisr_db_backup.sql

If it works, it may be a permissions error. Also, just to confirm, you’re using the latest version of revisr?

Hello,

We pushed out an update last night that should address the undefined offset if got hasn’t been configured. Regarding the second issue, please let me know if you’re still seeing this issue, and if you do, the version of WordPress and revisr you’re running. Does it occur on both environments?

Can you please post more details on your environment?

Yes, Revisr shows diffs for the local repository against whatever branch is checked out.

So if you pull master and make a bunch of changes to the local repository, you’re viewing the diffs for those local changes. You could also create a local branch independent of Bitbucket or Github and commit all of your changes to that branch, and go back and view previous commits and diffs without ever pushing to a remote.

@Forboding Angel-

You bring up some good points, and I definitely encourage you to use the plugin however you see fit to make sure it works best with your workflow.

With that being said, Ihor brings up a good point, and that is that Revisr will show you at a glance if those core files have been modified. While you can simply upload the latest core files over your entire installation, you won’t necessarily know when you need to do it since those files aren’t being tracked.

I’ve seen plenty of WordPress sites (not as much recently, but still some) where the hack may be hard to find (such as a hacked 404 page with a small bit of encoded Javascript). Since you are tracking the 404 page as it is in your themes directory, it is easy enough to remove the result of the hack, but often there will be other malicious files uploaded to other directories on the site, which may or may not be in the wp-content folder.

Hi Ihor,

We’re working on the documentation as we speak and I’ll be sure to include your suggestions above and credit where necessary. Thanks for your feedback!

Hi Ihor,

We’re working on the documentation as we speak and I’ll be sure to include your suggestions above and credit where necessary. Thanks for your feedback!

Hello,

Updated documentation is on the way and I’ll let you know as soon as that’s been posted. I’ll also be sure to test on MAMP to make sure there are no compatibility issues there and will push out updates as needed.

Thanks for the feedback!

Also, if you wanted to only track the wp-content/themes/ directory, you could add something like the following to the gitignore settings:

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

Hello,

You can configure files to be ignored from the repository (and Github) by adding the files or directories to the .gitignore settings on the plugin settings page.

For wp-config, simply add this line (paths are relative from the root repository folder/WordPress installation) :
wp-config.php

And save the settings.

Additionally, the wp-config file can also be saved in the directory directly above the root of the WordPress installation, which would prevent it from being part of the repository at all.

Hello,

We’ve just pushed out a minor release that adds error handling to pushes/pulls, commits the .gitignore to prevent confusion, and adds an option to automatically push commits or push them manually. This should help to make things more straightforward.

Thank you for your feedback. These issues will be addressed in the next release.