Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save Failed: fatal: empty ident name (for ) not allowed #2030

Open
Ribero opened this issue Jan 21, 2021 · 11 comments
Open

Save Failed: fatal: empty ident name (for ) not allowed #2030

Ribero opened this issue Jan 21, 2021 · 11 comments

Comments

@Ribero
Copy link

Ribero commented Jan 21, 2021

Grav v1.7.1 - Admin v1.10.1

When I try to change the publication status of a page I get this error:
image

At then end the page is correctly Published or not

@mahagr
Copy link
Member

mahagr commented Jan 21, 2021

I cannot reproduce. Could be a field or a plugin causing this?

@Ribero
Copy link
Author

Ribero commented Jan 21, 2021

May be, but where to start ? The plugins I use are the one related to learn2-gitsync + nextgen editor + admin revision.

@mahagr
Copy link
Member

mahagr commented Jan 21, 2021

Start by searching ident name from the page / blueprints. It is supposed to be empty?

@Ribero
Copy link
Author

Ribero commented Jan 25, 2021

I removed the support for multiple languages (in the main configuration) and the problem disappeared.

@mahagr
Copy link
Member

mahagr commented Jan 26, 2021

If you enable debugger (use clockwork and install it to your browser), it should have a tab for exceptions, which should have a backtrace where that error happens.

@mahagr
Copy link
Member

mahagr commented Apr 23, 2021

@Ribero Check if you can still reproduce this error, hopefully in a minimal installation and instructions, thanks!

@Ribero
Copy link
Author

Ribero commented Apr 23, 2021

Will try to test it asap.

@0x01af
Copy link

0x01af commented May 28, 2021

Hi at all

I had the same issue. The error message is not thrown by Admin, it's from the Grav GitSync plugin. Typically, GitSync pushes changes to the repository by default. I had to configure my SSH-Private-Key in the GitSync plugin configuration page. After that, the error message disappeared for all changes.

I hope, my finding helps you.

@boomam
Copy link

boomam commented Jun 21, 2022

I get this issue too, with the container.
Tried generating the ssh-keys as noted by @0x01af and having the path to it listed in the GitSync config, same issue.

@JasperCiti
Copy link

Did anyone find a solution yet? I also have the same problem. I used a clean installation from the woo template.

@nemchik
Copy link

nemchik commented Aug 23, 2022

Found a fix that worked for me.

I'm running in a docker container, and I believe the issue is the git user is not picked up because the user running the service inside the container does not have a .gitconfig.

Rather than trying to force the user inside the container to have a .gitconfig, I went to /admin/plugins/git-sync and set Commits Author to Use GitSync Committer Name, which is configured on the same page with the default value GitSync. Side note; I did NOT use a Private SSH Key in the settings (left blank).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants