Expanded Fronts

Hi,

Normally the development URL should not have a trailing slash at the end – can you confirm if the “Development URL” field for both staging and production don’t have the trailing slash?

I’m not sure, but it seems like the only way the issue could be caused would be if you had it set to have a trailing slash on one environment and without it on another.

Hi,

It looks like the first one might have been a syntax issue (missing quotes and extra foward slash?).

Are the WordPress files in the “wordpress” directory? If so, you could set it to “/srv/git/” and it would create the repo with the following path “/srv/git/.git”.

Also if you can point out to me any features that I claim this plugin has that it doesn’t have, I’ll gladly remove any references to said feature.

But for the time being I’m confident that I can accurately describe my plugin’s feature set.

Funny how you can edit your original review but I can’t edit my response.

Sorry you had a bad experience with the plugin – but I didn’t see any support threads or emails from you. Perhaps I might’ve been able to help you had you given me the chance.

Plenty of people have been using this plugin without any issues, so please be a little more specific than “it destroyed one of my sites”. The plugin doesn’t do anything by itself!

Hi,

Thanks for the feedback!

It definitely sounds like a permissions issue to me, but it’s hard to know the exact issue without seeing it.

Who are the WordPress files owned by? Is that the same user as the user running Apache?

You may have some luck creating the repository manually ( with “git init .” ), and then using chown and/or chmod as needed to match it up with the same permissions /user as the rest of your WordPress installation.

Hi,

The database prefixes normally just need to be the same – the database name itself shouldn’t matter.

Are you getting any errors? Just to make sure I understand your issue correctly – you have the “Import DB when pulling changes” option checked, and when you do a pull, the DB does not import?

Thanks for the feedback!

We’ve been considering adding support for multiple repos and will likely include that functionality in a future release.

Thanks for the info- glad you were able to get this resolved.

I updated the docs to include some of the things you ran into in case that helps anyone else in the future- https://docs.revisr.io/article/26-error-pushing

Let me know if you run into any further issues or have any feedback on the plugin. Thanks!

Hi @annasgourmetgoodies,

As you can see from this thread, the process for generating or giving SSH keys for the Apache user can vary greatly per specific operating system/distribution.

Depending on your OS, you may have some luck generating the SSH keys for Apache with the following:

sudo -u apache ssh-keygen -t rsa

To answer your other questions, the “Remote Name” is typically “origin”, and the “Remote URL” is the value you get from Bitbucket, without the “git clone” at the front. Applying these values automatically update your .git/config.

I hope that helps, if you run into any further issues please open up a new thread so I see your question faster. Thanks!

Hi,

Feel free to shoot an email with more details to [email protected], I’d be happy to take a look at this further.

Hi,

There’s no permanently stored log (once you run the search/replace it will store the results temporarily and then mark them for deletion. The fact you were getting a 404 error when running a dry/live run seems to indicate that a URL might have been replaced/set incorrectly.

Not sure- you’re the first person to report such an issue. Can you confirm if the 404 issue is repeatable? Does it also happen if you run the search on just one table?

Hi,

Sorry for the delay on this, glad the plugin worked for you!

Yep, any hardcoded values in the wp-config file would be outside the scope of this plugin, but i’ll look into adding a FAQ or something to also check for hardcoded values if things seem like they aren’t updating.

Hi,

Sorry for the delay on this, yes this approach looks correct (although I would get rid of the trailing slash for both the search and replace strings). I would search in wp_options, wp_posts, wp_postmeta, at the least (if not all tables).

Which tables specifically depends as well on your site. There’s no real harm in giving it a shot as long as you’ve backed up your database beforehand.

Let me know if you have any questions on this. Thank you.

Hi,

Can you confirm if the issue continues when pushing to a new (empty) repo on Bitbucket?

Thanks for the recommendation, I’ve updated the docs to include this info in the database configuration section.