Presslabs

Hi @rodricus,

I’m using as well the free version.

https://ibb.co/KWv9fZV

Not sure if this is related, did you enable the 2FA in your bitbucket account?

Best,

Hello @rodricus,

Please see the following screenshots on how I added the key on my workspace to make it work.

https://ibb.co/Ss82yYX
https://ibb.co/THwG8V0
https://ibb.co/47FLnVW
https://ibb.co/P41vZyw
https://ibb.co/QMY4R3z

If you don’t see the workspace settings, maybe you are not the owner of it.

Best,

Hi @rodricus,

I think in the Project Settings the access key is still read-only.

You should add it here https://bitbucket.org/workspace-name/workspace/settings/ssh-keys

Best,

Hi @rodricus,

Gitium then says the following: “Could not create initial commit -> On branch main nothing to commit, working tree clean”.

I think this is normal because you were using a repo which has already content.

I made some edits on my localhost website and committed and push it, but I don’t see them in Gitium anywhere.

What do you see on the status page?

Hi @rodricus,

If you add the key into the workspace(Workspace Settings -> SSH Keys), it seems that there it has write access.

Found this topic: https://community.atlassian.com/t5/Bitbucket-questions/How-to-add-an-Access-Key-with-Write-permission/qaq-p/842539

Best,

Hi @rodricus,

Access keys from bitbucket seems to be read-only.

I’m not familiar with Bitbucket, but you need to grant write access as well.

Hi @rodricus,

Where did you add the ssh key? Did you configure the plugin on the same website which was the previous version of gitium?

Since the status showed that is connected to the repository, can you tell me what do you see on the status page?

The message error indicates that it doesn’t have write permissions.

Thanks,

Hi, @rodricus!

Have you been able to test the new version?

Thanks,

Hello @rodricus,

I’ve discussed internally with the team and this could get complicated because you will have to create symlinks for the wp-content, root files and you should also move the upload folder because they are present in wp-content(so you will have to symlink it as well). I think is best to block the access from .htaccess or nginx.

Best regards,

Hi @rodricus,

You just have to clone/download the repository(press on the green button which have the text code, then download zip). After you have the repository cloned, go inside of the folder and you should see another folder gitium, you can add that folder to your repository or create a archive of this folder and upload it in the wordpress admin area.

Please let me know when you have been able to test it. There is no rush, you can do it when you have time.

Best regards,

Hello,

I will ask the technical team to see what can be done.

Best regards,

Yes, we are looking for a fix to avoid this problem. For the moment, you can add manually in the file /gitium/inc/class-gitium-submenu-status.php, on the function save_changes above this line https://github.com/presslabs/gitium/blob/master/gitium/inc/class-gitium-submenu-status.php#L113 the following code:

gitium_disable_maintenance_mode();

Hello @rodricus,

I have reproduced the problem. It appears to occur only when you try to add changes to the website from the remote. As far as I can tell, you have not configured the webhook.

Could you follow these steps and configure the web book to automatically deploy these changes to your website without the need to click on the save button?

Webook configuration:

Gitium uses the webhook to automatically deploy remote changes to your server. To configure it follow these steps:

1. Go to your WordPress website and go to your Gitium Settings page;
2. Copy the full Webhook URL that Gitium provides;
3. In your Git Manager settings, go to Webhook section, add a new webhook and paste the webhook URL you have copied from Gitium.
4. Press Add, no settings changes needed. The webook simply needs a ping, nothing more. The security key is already embedded in the final URL Gitium has generated for you.

Now when you push to your repo, this webhook will automatically pull the changes to your remote server and deploy them.

I’ll also look for a fix for this case when the webhook isn’t configured. Here is the problematic code:

gitium_enable_maintenance_mode() or wp_die( __( 'Could not enable the maintenance mode!', 'gitium' ) );
		$this->git->add();
		$commitmsg = sprintf( __( 'Merged changes from %s on %s', 'gitium' ), get_site_url(), date( 'm.d.Y' ) );
		if ( isset( $gitium_commit_msg ) && ! empty( $gitium_commit_msg ) ) {
			$commitmsg = $gitium_commit_msg;
		}
		$current_user = wp_get_current_user();
		$commit = $this->git->commit( $commitmsg, $current_user->display_name, $current_user->user_email );
		if ( ! $commit ) {
			$this->redirect( __( 'Could not commit!', 'gitium' ) );
		}

Your branch is behind \'origin/master\' by 1 commit, and can be fast-forwarded.
(use "git pull" to update your local branch)
nothing to commit, working tree clean'/n/n

Commit failed.

According to the above message, the code fails and does not reach the end of the code to disable maintenance.

Hello @rodricus,

We will check this problem and get back to you!

Thanks,

Alright, thank you for your confirmation!