Unable to create new wiki pages

Hi, i can't create new wiki pages in some of my gitlab projects.

I got the following error from the log (gitlab 8.7.0, omnibus installation)

NoMethodError (undefined method `username' for #<Group:0x00000004d6a728>):
 app/models/project_wiki.rb:158:in `default_message'
 app/models/project_wiki.rb:152:in `commit_details'
 app/models/project_wiki.rb:91:in `create_page'
 app/models/wiki_page.rb:183:in `save'
 app/models/wiki_page.rb:143:in `create'
 app/services/wiki_pages/create_service.rb:6:in `execute'
 app/controllers/projects/wikis_controller.rb:58:in `create'
 lib/gitlab/middleware/go.rb:16:in `call

I'm not sure if it's the same error, but I'm getting a 500 when trying to create a wiki page on gitlab.com. From the small amount of testing I've done, it only seems to happen when I try to create a page in a project under a group (both private and public). When I create a project under my username, page creation works fine.

Content doesn't seem to affect the issue. Trying to create the initial home page and a separate page with content a fails after clicking the create page button.

this project does not work

this project does work

Yes, this does look like the same bug in GitLab.com. We're seeing the same exception in Sentry. It looks like somehow the current group is being passed along instead of the current user.

Added wiki label

Added ~12980 label

Added reproduced on GitLab.com label

Also have this issue on my on premises install. Have to create empty files with git access as a workaround, then editing those pages works even trough web interface.

This seems to be a regression in 8.7, right? @stanhu @yorickpeterse

mentioned in issue #15569 (closed)

@connorshea this is the same exact issue and this does happen to me with a project that is nested under a group

Milestone changed to 8.7

mentioned in issue #14939 (closed)

This was broken in b255cbf3

@rymai Can you take a look at this?

I think this is a big issue. Do you have any idea when it'll be fixed and relased?

Reassigned to @rymai

@gpad I'm on it.

mentioned in merge request !3924 (merged)

Fixed by !3924 (merged).

Don't forget we can create pages from git git clone git@url:group/project.wiki.git

mentioned in issue #15630 (closed)

mentioned in issue #15623 (closed)

mentioned in issue #15653 (closed)

Might not be the right place to ask, but Is the git clone of the wiki a work-around for this bug until the fix drops?

If so, on a new project with no wiki pages (yet) I clone and have an empty local repository what would I name the first filename to bootstrap the wiki?

@basictheprogram I am doing it by cloning the wiki repo and adding the file named Home.md and all the other files that I will be needing (for example: how-to-setup.md) and push them all back.

mentioned in issue #13603 (closed)

mentioned in issue #16558 (closed)

mentioned in issue #16987 (closed)

Added regression label

mentioned in commit 3811eb0b

Not sure if it's the same problem or not, or related.

Unlike @Rfvgyhn , if I already have a wikis/home page that has content, I can still create new pages from it. But if my wikis/home page doesn't have content already, then I can't modify it or create new wiki pages (both result in a 500).

Since this appears to only effect unused wikis, I did try turning off a wiki, then turning it back on. It made no difference at all.

FWIW: All my testing was done in the same group namespace.

mentioned in issue #16875 (closed)

mentioned in issue #15870 (closed)

Duplicates:

• #15569 (closed)
• #16558 (closed)
• #15637 (closed)
• #15630 (closed)
• #16875 (closed)
• #15653 (closed)
• #16987 (closed)
• #17016 (closed)

mentioned in issue #17016 (closed)

@connorshea - I was well aware of those before posting and I intentionally picked the issue that seemed to be the most active and inclusive of the known issues.

My comment started off by saying I wasn't sure if it was the same or a related issue, and then I detailed a specific observation that I had not seen mentioned in the threads I read through.

I assumed it was a related issue, which is exactly why I posted it in this thread. Because of the detail I observed and without knowing if the fix had been pushed up to gitlab.org, I didn't know whether this was a new problem because of the fix.

@metasean I was just collecting all the duplicates so they could be closed once this issue is closed, it wasn't targeted at anyone in particular. Apologies for the misunderstanding.

@connorshea - Thank you for clarifying, and apologies for reading too much into your post.

Out of curiosity, why don't you close the others as duplicates now?

@metasean I don't have the privileges necessary to close them :D

@connorshea - That makes perfect sense. :thumbs_up_reverse: I've seen you post around here enough that I assumed you were an official team member.

@metasean that's what everyone says :P I will be soon :D

mentioned in issue gitlab-com/support-forum#674 (closed)

Status changed to closed by merge request !3924 (merged)

Status changed to closed by commit 3811eb0b

mentioned in commit 0652d925

mentioned in commit aa664af3