Privatebin: Customization improvements (name, tagline, logo, favicon)

[LuckySandwich]

Hi

I have a few small suggestions for improving user customization. One small issue to address, plus a few additional suggestions.

Problem:

If you edit the name configuration setting, it changes the software description too

MyCustomPastebin - _because ignorance is bliss_

MyCustomPastebin is a minimalist, open source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256 bits AES. More information on the project page.

In my opinion, it should not be modifying the description of the software with a new name unless it's a completely different product/fork.

Solution:

Include a "powered-by" style footer message when a custom name is configured.

If modified:

MyCustomPastebin - Powered by PrivateBin
PrivateBin is a minimalist, open source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256 bits AES.

If not modified:

PrivateBin is a minimalist, open source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256 bits AES.

Suggestion/wishlist:
New configuration options:

• tagline = "because taglines should be editable" (hide hyphen between tagline and name if empty)
• customFavicon = true - reads from /userstyles/favicon/
• customLogo = mylogo.svg - reads from /userstyles/mylogo.svg
• Automatically read custom language file edits from /userstyles/i18n/*.json and append to the defaults
• (maybe) customCss = true - reads from /userstyles/user.css, which could be used to override default CSS classes by simply reading the user.css class last
• (maybe) footer = false to disable the footer entirely

Maybe not set up exactly like that, but you get the idea.

Currently, the above changes require modifications to the PHP source, which need to be manually edited again after each software update. Changing via the config file and reading custom files from an optional folder would make software updates easier to manage and allow for greater user customization.

[rugk]

If you edit the name configuration setting, it changes the software description too

Agree, sounds like a bug.

Include a "powered-by" style footer message when a custom name is configured.

Good idea.

Suggestion/wishlist:

Yeah, as long as these are easy to implement, I agree and tend to say these are all useful.
So we'd totally appreciate PR's here. :smiley:

Changing via the config file and reading custom files from an optional folder would make software updates easier to manage and allow for greater user customization.

I agree. I mean technically we have great customizability – the greatest you can have with editing the PHP template –, but your arguments regarding easier upgrades are totally valid.
Maybe it also helps that admins don't get "stuck" on old versions, because they've customized something or so…

But we don't really know why people don't upgrade from v1.2 e.g.. :thinking:

[LuckySandwich]

Maybe I will give it a whirl if I get some time. I haven't touched PHP in over a decade. I don't think it would be too much work. They pretty much all amount to "if set, use custom, if unset, use default".

The custom CSS styling would just be the last CSS file loaded, so it would override any same-named classes automatically. This is how Stylish handles theming, as does protonmail.

It's very simple to make themes using browser's inspector tool this way, and keeps all the theme files detached from the source code.

Thanks for the feedback 👍

[elrido]

Just a short addendum:

If you edit the name configuration setting, it changes the software description too

Agree, sounds like a bug.

This is implemented deliberately in that way, as the intent is for the software name to be replaced in all instances. If you only want a different logo, but keep a "powered by" message with the software name, a custom template would be the currently recommended way to go. Since these rarely change, they should not be a hassle for ugrades, if customized.

But I'm not opposed to splitting the message at all or allowing configurable custom logos and favicons sets. Since we require the GD library for the user icons in the discussions, we might take a single logo and generate the different favicon flavours, if not present on disk, to make it simpler for the admins.

[ZerooCool]

+1 : Problem:
If you edit the name configuration setting, it changes the software description too

I have open the same, today :

641