No Git repository was detected

Hello,

It’s hard to tell without a little more info on your setup. Is the wp-config.php and “.git” folders in the same folders as wp-admin and wp-content? Or are they somewhere else?

Also, am I correct in assuming that the existing “.git” folder contains an existing repository? If so, are you able to use it otherwise (like through command line, etc?)

Yes, my filetree looks like:

.git
wp-admin
wp-content
wp-includes
…
wp-config.php
…

Yes, I’m able to use it via command line.

I’m searching for answer on my problem many hours and with no result. Would it be possible to co-operate with me for example via TeamViewer? Because I can’t imagine how to solve this problem only via WP forum. Of course, I will pay you for this help.

Thank you.

Sure, feel free to send an email to support at expandedfronts.com with more info so we can get this figured out for you.

Super, thanks a lot. I will send e-mal during next week.

I have find out today, that my hosting doesn’t support git hooks. Is it possible, that this is the reason why Revisr isn’t working correctly on my hosting?

Hello,

So if I understand correctly, you have exec enabled, Git installed, but they’ve somehow limited the Git functionality itself?

Where is the site hosted?

Firstly, I was testing on Blueboard.cz hosting, but I have find out today, that they support Git only very limited – one testing branch and one deploy branch for every project and that’s all.

Now I’m searching for another hostings and I have found one with git support, but without git hooks support, that’s why I asking about git hooks.

Do you know about some hostings where your plugin works on 100%?

Carefully, topics about hosting get closed when found. They just get too spammy. ??

I’m not closing this one but if the conversation does get into selecting or comparing hosting then it will get closed with a note.

ExpandedFronts:
OK, so could you send me info about hostings on my e-mail [ redacted ]?
Thank you.

Sure, I’ll shoot you an email. Marking this as resolved as it was an issue with the hosting provider limiting Git functionality.

OK, super. Thanks.