# OP
I created a fresh site and configured it to use a private file area (files outside of the DocumentRoot). If I create content with an attachment, one can download the attachment via the generated link (/system/files?file=filename.ext). If I try to add a site logo for a theme, the file is uploaded to the private files directory, but the logo is not visible. I've manually set the logo URL to the same format as the attchment mentioned previously, but the system does not allow access to this file (I'm guessing that the attchment is registered as 'downloadable').

CommentFileSizeAuthor
#22 logo-and-favicon-to-public-47709-8_7_1.patch1.2 KBnicothezulu
#18 logo-and-favicon-to-public-47709-18-do-not-test.patch984 byteskevib

Comments

Egon Bianchet’s picture

Egon Bianchet commented
Version: 4.7.0-beta4 » 4.7.0

Still valid with 4.7.0

magico’s picture

magico commented
Version: 4.7.0 » x.y.z

1. ?q=admin/settings/file-system - choose private
2. ?q=admin/build/themes/settings - upload custom logo
3. it does not set the correct path neither it downloads the correct logo if we set the dynamic path

ricabrantes’s picture

ricabrantes commented
Version: x.y.z » 5.x-dev
Status: Active » Fixed

This bug are fixed in D5.x.. Moving to fixed..

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

darumaki’s picture

darumaki commented
Status: Closed (fixed) » Active

I'm experiencing the same thing, custom logo and shortcut do not work when set to private

savedario’s picture

savedario commented
Version: 5.x-dev » 6.14

I have the same problem using Garland theme.

The HTML line that should display the logo shows:

<h1><a href="/" title="My site"><img src="//home/..<user folder where files are stored>.../files/garland_logo.gif" alt="My site" id="logo" /><span>My site</span></a></h1>

(note the double '/' at the beginning of the path).

The path there is exactly the same that is shown in the theme configuration.
If I remove the first slash, the logo path is not accepted, obviously...

lifepillar’s picture

lifepillar commented

subscribe.

LadyAnna’s picture

LadyAnna commented
Version: 6.14 » 6.15

I have this problem with a custom theme using this as code to get the logo:
<img src="<?php print $logo; ?>" alt="<?php print t('Home'); ?>" id="logo-image" />

Resulting HTML output:
<img src="/./images/site-logo.png" alt="Home" id="logo-image">

Uploaded doesn't work either, using private files.

anonymous07’s picture

anonymous07 commented
Version: 6.15 » 5.20

Subscribe

ben coleman’s picture

ben coleman commented

subscribe

dpearcefl’s picture

dpearcefl commented
Status: Active » Closed (won't fix)

Considering the lack of activity on this issue and that Drupal v5 is no longer supported by fixes or patches, I am going to close this ticket. If this issue still exists and you want to continue to ask for technical support, please reopen and update this ticket.

Jeff Burnz’s picture

Jeff Burnz commented
Title: Custom theme logo not working when using private files » private://logo.png gets a 403 for custom logos
Version: 5.20 » 8.1.x-dev
Component: theme system » file system
Issue summary: View changes
Status: Closed (won't fix) » Active

Reviving this 10 year old issue, because it is still an issue.

Jeff Burnz’s picture

Jeff Burnz commented
Issue summary: View changes

Set file system to private, then upload a custom logo in theme settings, the file will be uploaded, the path looks fine, but you get a 403 so the browser won't display the logo.

jontheil@gmail.com’s picture

jontheil@gmail.com commented
Issue summary: View changes

Subscribe

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

kevib’s picture

kevib commented
Issue summary: View changes
StatusFileSize
new logo-and-favicon-to-public-47709-18-do-not-test.patch984 bytes

Hello,

I've changed the download method by default of my Drupal to use private locals files.
But, I don't think it's important to have favicon and logo in private files since by default they come from the theme and they are already public.
So it's just a hotfix tested on a Drupal 8.3.4. to force favicon and logo in public files not really a proposed solution.

BR,

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

hgoto’s picture

hgoto commented
Related issues: +#1087250: Custom logo and favicon stored in private filesystem if it is the default
nicothezulu’s picture

nicothezulu commented
StatusFileSize
new logo-and-favicon-to-public-47709-8_7_1.patch1.2 KB

Hi!

Here is the same patch, which applies for 8.7.1

UPDATE:
I just missed the patch provided here already by donaldp against 8.6.x https://www.drupal.org/project/drupal/issues/1087250#comment-13100204
... So this may be a duplicate/obsolete ...

nicothezulu’s picture

nicothezulu commented
Version: 8.6.x-dev » 8.7.x-dev

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.9 was released on November 6 and is the final full bugfix release for the Drupal 8.7.x series. Drupal 8.7.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.8.0 on December 4, 2019. (Drupal 8.8.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

quietone commented
Status: Active » Closed (duplicate)
Issue tags: +Bug Smash Initiative

Thanks everyone for working on this!

This a duplicate of #1087250: Custom logo and favicon stored in private filesystem if it is the default. Moving credit to that issue.