Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #3299
Closed
Open
Created Aug 29, 2014 by bmortier@bmortierMaintainer

Use relative path for geticon

Some plugins still have absolute path '/fusiondirectory/geticon', which is causing troubles if your installation does not use a fusiondirectory folder. These shoud be replaced by classic relative path simply starting with geticon.

This bug is because the diff from the bb1f62dd commit in 1.0.8.1-fixes removes lots of code in develop and must be checked before a cherry-pick

Cheers

(from redmine: issue id 3299, created on 2014-08-29, closed on 2015-05-05)

  • Relations:
    • copied_to #3297 (closed)
  • Changesets:
    • Revision ec0157d0 by Côme Chilliet on 2014-09-29T20:47:45.000Z:
Fixes #3299 Use relative path for geticon
  • Custom Fields:
    • Bug in version: 1.0.8
  • Uploads:
    • 0001-Fixes-3297-Replace-fusiondirectory-geticon-with-geti.patch
    • 0001-Fixes-3299-Use-relative-path-for-geticon.patch
Assignee
Assign to
Time tracking