Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #7102

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Can't access to wiki page with dot in page slug

Closed

Can't access to wiki page with dot in page slug

Created by: kwbt69

GitLab 6.9.2

GitLab Shell 1.9.4

GitLab API v3

Ruby 2.0.0p353

Rails 4.0.5

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: Wachiwi

      Pls provide more information.

      Possible duplicate of #7035 (closed)

      By Administrator on 2014-06-10T08:03:30 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: kwbt69

      Summary: When access to a wiki page with "." in the page slug, "Editing" page shown in stead of the content page. The wiki page was created before upgrading to 6.9.2 from 6.4.1.

      Steps to reproduce: (in GitLab 6.4.1)

      1. Select a repo, and click "Wiki"
      2. Click "New Page"
      3. Put in a title with "." in it e.g. release_v1.0
      4. Click "Build"
      5. Put in some text in the content area e.g. test
      6. Click "Create page", and confirm the page created

      (upgrade to 6.9.2) 7. Upgrade GitLab with GitLab Upgrader

       cd /home/git/gitlab
       sudo systemctl stop gitlab-unicorn gitlab-sidekiq
       sudo -u git -H ruby script/upgrade.rb
       sudo systemctl start gitlab-unicorn gitlab-sidekiq
       sudo systemctl restart nginx
      1. Select the project, and click "Wiki"
      2. Click "Pages" tab
      3. Click the link which was created in step 6

      Expected behavior: Should just show the wiki content page

      Observed behavior: "Editing" page shown. The URL & the title seems correct -- for "release_v1.0", its URL is "gitlab server name/project name/repo name/wikis/release-v1.1" and the titile is "Editing - release v1.1".

      Relevant logs and/or screenshots: screenshot

      Output of checks

      Checking Environment ...
      
      Git configured for git user? ... yes
      
      Checking Environment ... Finished
      
      Checking GitLab Shell ...
      
      GitLab Shell version >= 1.9.4 ? ... OK (1.9.4)
      Repo base directory exists? ... yes
      Repo base directory is a symlink? ... no
      Repo base owned by git:git? ... yes
      Repo base access is drwxrws---? ... yes
      Satellites access is drwxr-x---? ... yes
      update hook up-to-date? ... yes
      update hooks in repos are links: ...
      (snip)
      Running /home/git/gitlab-shell/bin/check
      Check GitLab API access: OK
      Check directories and files:
              /home/git/repositories: OK
              /home/git/.ssh/authorized_keys: OK
      Test redis-cli executable: redis-cli 2.6.16
      Send ping to redis server: PONG
      gitlab-shell self-check successful
      
      Checking GitLab Shell ... Finished
      
      Checking Sidekiq ...
      
      Running? ... yes
      Number of Sidekiq processes ... 1
      
      Checking Sidekiq ... Finished
      
      Checking LDAP ...
      
      LDAP users with access to your GitLab server (only showing the first 100 results)
      (snip)
      
      Checking LDAP ... Finished
      
      Checking GitLab ...
      
      Database config exists? ... yes
      Database is SQLite ... no
      All migrations up? ... yes
      Database contains orphaned UsersGroups? ... no
      GitLab config exists? ... yes
      GitLab config outdated? ... no
      Log directory writable? ... yes
      Tmp directory writable? ... yes
      Init script exists? ... no
        Try fixing it:
        Install the init script
        For more information see:
        doc/install/installation.md in section "Install Init Script"
        Please fix the error above and rerun the checks.
      Init script up-to-date? ... can't check because of previous errors
      projects have namespace: ...
      (snip)
      
      Redis version >= 2.0.0? ... yes
      Your git bin path is "/usr/bin/git"
      Git version >= 1.7.10 ? ... yes (1.8.3)
      
      Checking GitLab ... Finished

      Version of GitLab you are running: 6.9.2

      Add the last commit sha1: e46b644a

      Describe your setup:

      System information
      System:
      Current User:   git
      Using RVM:      no
      Ruby Version:   2.0.0p353
      Gem Version:    2.0.14
      Bundler Version:1.5.2
      Rake Version:   10.3.1
      Sidekiq Version:2.17.0
      
      GitLab information
      Version:        6.9.2
      Revision:       e46b644
      Directory:      /home/git/gitlab
      DB Adapter:     mysql2
      URL:            http://<gitlab url>
      HTTP Clone URL: http://<gitlab url>/some-project.git
      SSH Clone URL:  git@<gitlab url>:some-project.git
      Using LDAP:     yes
      Using Omniauth: no
      
      GitLab Shell
      Version:        1.9.4
      Repositories:   /home/git/repositories/
      Hooks:          /home/git/gitlab-shell/hooks/
      Git:            /usr/bin/git

      Possible fixes: Not sure.

      By Administrator on 2014-06-11T05:10:57 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: kwbt69

      I also reproduced #7035 (closed) in my environment.

      By Administrator on 2014-06-11T05:11:41 (imported from GitLab project)

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: Razer6

      Closing as a duplicate. There is a fix here: There is a fix here https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/156

      By Administrator on 2014-08-07T06:47:24 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference:

    Menu

    Projects Groups Snippets
    Help