Config: Title of the search page must be set based on the site title

[edwinclement08]

1. What is not working as documented?

When setting the PHOTOPRISM_SITE_TITLE environmental variable via PHOTOPRISM_SITE_TITLE, the search page still shows 'Photoprism'.
The other pages like Albums and Favourites show the ' - ' as expected.

2. How can we reproduce it?

Steps to reproduce the behavior:

Run the docker container with PHOTOPRISM_SITE_TITLE env variable set to anything other than Photoprism

3. What behavior do you expect?

The Title of the page to be when on home page

4. What could be the cause of your problem?

Not sure

5. Can you provide us with example files for testing, error logs, or screenshots?

6. Which software versions do you use?

(a) PhotoPrism Architecture & Build Number: PhotoPrism® CE Build [230514-0b780defb]

(b) Database Type & Version: SQLite

(c) Operating System Types & Versions: Windows

(d) Browser Types & Versions: Firefox, Chrome

(e) Ad Blockers, Browser Plugins, and/or Firewall Software?
No

7. On what kind of device is PhotoPrism installed?

Unraid

(a) Device / Processor Type:
Intel Core i7-3770

(b) Physical Memory & Swap Space in GB
16 GB, 1 GB

(c) Storage Type: HDD

(d) Anything else that might be helpful to know?

Did try to edit options.yml and got the same result.

8. Do you use a Reverse Proxy, Firewall, VPN, or CDN?

No

[lastzero]

While I recognize that there is room for improvement, this seems to work more or less as intended. Could you additionally try setting PHOTOPRISM_SITE_CAPTION and PHOTOPRISM_APP_NAME to see if/how that changes the title of the page? I'm in a hurry and can't check the code in detail right now, but I remember there is logic that uses all of these values to generate both the toolbar and HTML page titles.

[edwinclement08]

I tried PHOTOPRISM_APP_NAME as well, but that didn't seem to effect the name on the browser. The PHOTOPRISM_SITE_CAPTION I have kept as Browse Your Life and that is not what is shown.
The reason I wanted this functionality is that I have multiple instances of photoprism for my family and it becomes a bit confusing when more than a couple of them are open. All of the pages are titled PhotoPrism.

[lastzero]

Yeah, so it is possible that overwriting the title with PHOTOPRISM_APP_NAME currently only works in our Plus version, since this might be implemented as a "proof of concept" in the extension we provide to our members. If so, we may eventually add this tiny tweak to our regular version as well.

In the short term, you can also achieve the behavior by adding a line or two of Go if you are comfortable with building from source.

[lastzero]

@edwinclement08 Thanks to your report, I found a line in our frontend code that should not be there and caused a different behavior in our community edition. I apologize for that. After removing this line, I tested it again. For this I started the server as follows (of course you can use environment variables instead):

photoprism --site-title="TITLE" --site-caption="CAPTION" start

To verify the effect of the config values, I've then used this command, which confirms that the site title was applied to the app name:

photoprism --site-title="TITLE" --site-caption="CAPTION" config | grep TITLE 
| app-name               | TITLE            |
| site-title             | TITLE            |

If a site-caption is set, it will be used as page title on the (default) search page:

Otherwise, and on all other pages, the configured site title will be used:

I would appreciate if you could test it again with this change. An updated development preview build will be available soon!

[lastzero]

The release notes have been updated to mention this issue:

https://docs.photoprism.app/release-notes/#development-preview

These docs explain how to use our preview build:

https://docs.photoprism.app/getting-started/updates/#development-preview

[edwinclement08]

Hey @lastzero, thanks for your quick fix. Updating Caption and Title to the same value resolved the issue.

[lastzero]

Thank you very much for testing! We will try to release a new stable version with this fix in the next few days. In the meantime, our development preview is generally safe to use, as it does not contain any breaking changes or known issues.

[edwinclement08]

Thanks a lot😄.