Expanded Fronts

Marking this thread as resolved as this this should be fixed with the latest release. If anyone runs into further issues, please open a new thread.

Thank you.

@simonyump That’s absolutely not the case. The database is split up into tables, and then chunks within those tables.

The issue is the server’s PHP memory limit as mentioned above. There is an easy fix for the issue as discussed here: https://codex.www.ads-software.com/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

I’m releasing an update shortly to make the size of the chunks an adjustable feature.

Also if you look at the plugin’s code, you’ll notice that it’s built on top of some seriously battle-tested scripts.

Hi,

It’s likely an issue with your servers PHP memory limit. You can read more about the issue and the fix and a potential workaround here.

Hi,

1. The full path to git in the help tab is actually what has been automatically detected – I see how this can be confusing and this will be made easier with the next release.

It sounds like Revisr is connected to your repository though and that Git is working correctly (since it’s picking up the master branch and not throwing any errors.

There is currently no way to view all files through Revisr, just the ones that have been changed when you make a new commit or view an old commit.

2. When you hit the “Backup Database” button in the dashboard, the files are saved to your wp-content/uploads/revisr-backups folder, and then a new commit is made to save those files. So you shouldn’t need to do anything further to get them into version control in the first place.

3. You would ignore these files for a few reasons. First, if you’re pushing to a public Bitbucket/GitHub repo, you don’t necessarily want others looking at your config files, etc.

Second, if you’re also using Revisr to deploy changes to another server, you will generally want the config files, etc. to stay the same on their environment (so if I pushed from a dev server to a production server, I want the production server to keep it’s wp-config.php file and database credentials, etc).

I hope that helps!

Hi,

If you need to change the path to Git, you can add the following to your wp-config.php:

define( 'REVISR_GIT_PATH', '/path/to/git' );

If you already tried that with setting the path to ‘~/bin/git’, and that didn’t work, try setting the full/absolute path (usually “~” refers to /home/YOUR_USERNAME/, check with your host if you’re not sure what this means or how to find it. )

Once you’ve got that set up, you should be able to create a new repo by going to the revisr dashboard and clicking the prompt to init a new repo, alternatively you can create the repository manually and it should pick it up – see https://docs.revisr.io/article/10-setup-an-existing-repository

Just as an FYI, this entire flow is greatly improved in the next version, which will be released soon.

To answer your other questions, yes, you can use Revisr to push/pull site changes – just make sure you have the wp-config, .htaccess files, etc. ignored in all repos.

And then make sure any commits are pushed out/pulled in asap – for example don’t make a bunch of commits on dev and production at the same time – instead work on your feature on the dev server, push it up to master on Bitbucket, log into live site, pull changes in, etc.

Once you’re comfortable with the process, things like auto push and auto-pull can make things a lot easier, but I recommend taking some time to understand the ideal flow for your environment first.

Revisr currently supports reverts, you can roll back file changes, db changes, or both.

And of course, I do recommend manual backups when testing things out initially. Once it’s running and has been tested with your setup, this obviously is not as big as a deal as backups will likely be going to Bitbucket/Github, etc.

Marking this resolved as it was resolved externally, but please don’t hesitate to let me know if you run into any further issues. Thanks!

Hi,

If you were getting “Error importing database” – the issue is likely with the MySQL Install Path not being found – the fix would be to either add the path to MySQL (recommended) or use the WordPress driver (as I see you’ve already tried).

The WordPress database driver works great for smaller sites, but if you have a larger database it may have some issues due to everything being processed via PHP.

I would give a shot at adding the path to the MySQL binary and seeing if that fixes the issue.

As far as .gitignore – this depends on what you want to track in the repo. At the very least, I’d recommend ignoring the wp-config.php and .htaccess files. You can ignore more than that, but if you want database backups and imports to work, you need the wp-content/uploads/revisr-backups folder included in the repository.

It’s worth mentioning as well that the next version of Revisr will include a few basic .gitignore/repository profiles for quicker/easier setup.

Hi,

That makes sense – rereading this thread with a fresh set of eyes I see that it’s actually failing to create the index.lock in the first place.

When you deleted and recreated the “.git” folder, did you recreate it manually?

If pushing works manually but not via Revisr it’s definitely just a permissions issue – I would make sure that the files are owned by the same user as your Apache user and have the correct numerical permissions.

Failing all that, you could try deleting just the “.git” folder one last time and reinitializing it through Revisr.

Sorry the permissions, etc. are giving you trouble, but it’s a problem with using the Git installation on your server. This will ultimately be addressed in a later version of the plugin.

Hi,

That’s really strange, line 77 normally just returns the “REVISR_GIT_PATH” constant that you already tried defining and apparently didn’t work.

Can you please try adding the “define(‘REVISR_GIT_PATH’, ‘/usr/local/bin/git’);” code to the wp-config.php file above the line that starts with “Absolute path to the WordPress directory”. (Just below the the “WP_DEBUG” constant should work well).

I see that you tried adding this already, but the placement within the wp-config.php is important.

Thanks!

Hi,

Can you remove the “.git/index.lock” file and see if the issue persists?

Good idea- I will add validation to that field for the next release – new issue created here.

If you need to replace any URLs due to the issue, you can use my Better Search Replace plugin (which uses the same URL replacement functionality as Revisr), or any other search/replace script.

Let me know if you have any questions or run into any further issues. Thanks!

Hi,

Can you please paste over the debug info from the Help tab in the Revisr settings?

Are normal files being pulled correctly?

When you do a pull, do you see the “Successfully imported the database.” message?

Sorry for all the questions, but they should help to narrow down the issue. Thanks!

Hi, can you please paste over the debug info from the help tab in the Revisr Settings?

The error details make it seem like Git isn’t installed on the server. Can you confirm that it’s definitely installed?

If so, it’s likely an issue with the installation path to Git not being recognized by Apache.

Glad you were able to get this resolved – I’ve updated the documentation to reflect the proper placement.

Hi,

Thanks for the additional info. I did check that functionality and it’s working as expected for me, even when setting it to a different directory outside of anything related to WordPress.

If you’re OK with debugging this further, temporarily adding the following to your theme’s functions.php should show you the path that Revisr is trying to create the repository at (and by extension, if the REVISR_GIT_DIR constant is working as expected for your environment):

var_dump( revisr()->git->get_git_dir() );

Alternatively, feel free to shoot an email to [email protected] if you want me to take a look at it in further detail. Thank you.