Please let me keep lowercase tags and blog names

kseistrup commented

2020-01-13 17:35:46 +00:00

(Migrated from github.com)

Is your feature request related to a problem? Please describe.

I am frustrated that Plume insists on capitalizing my blog names and tags, when I have taken care to enter lowercase words only. The funny thing is that the slug for blog entries are all lowercase, even when one or more words have been capitalized.

Describe the solution you'd like

I would like Plume to use the casing I have entered, instead of second-guessing me.

Describe alternatives you've considered

In my opinion, the entire URL ought to be lowercased, no matter what has been entered. The on-page text should be displayed exactly as entered by the author.

Cheers.

**Is your feature request related to a problem? Please describe.** I am frustrated that Plume insists on capitalizing my blog names and tags, when I have taken care to enter lowercase words only. The funny thing is that the slug for blog entries are all lowercase, even when one or more words have been capitalized. **Describe the solution you'd like** I would like Plume to use the casing I have entered, instead of second-guessing me. **Describe alternatives you've considered** In my opinion, the entire URL ought to be lowercased, no matter what has been entered. The on-page text should be displayed exactly as entered by the author. Cheers.

elegaanz commented

2020-01-13 19:26:39 +00:00

(Migrated from github.com)

Why not, I'm not sure why we changed the case of the tags originally. I just wonder how tags with spaces (for instance) will federate, but I guess we will see…

For blog IDs, we should probably suggest one by default based on the name, but allow to change it.

Why not, I'm not sure why we changed the case of the tags originally. I just wonder how tags with spaces (for instance) will federate, but I guess we will see… For blog IDs, we should probably suggest one by default based on the name, but allow to change it.

👍 1

kseistrup commented

2020-01-13 21:13:27 +00:00

(Migrated from github.com)

I'm fine with suggestions, as long as I get the final say.

👍 1

epsilon-phase commented

2020-01-14 03:14:31 +00:00

(Migrated from github.com)

Alright, it's easy enough to fix the tags, but for the blogs, where is it rejecting your case?

Edit: Sorry, we missed it in your issue text :)

Alright, it's easy enough to fix the tags, but for the blogs, where is it rejecting your case? Edit: Sorry, we missed it in your issue text :)

kseistrup commented

2020-06-21 15:55:08 +00:00

(Migrated from github.com)

Any ETA?

elegaanz commented

2020-06-22 12:22:26 +00:00

(Migrated from github.com)

Not really, sorry… we don't know when an issue will be solved, we just take them as we feel like resolving them. But this one shouldn't be too hard to fix, so it will probably be fixed sooner or later.

👍 1

kseistrup commented

2020-06-22 12:27:51 +00:00

(Migrated from github.com)

Thanks. I figured it would be something like that. But since this is such a small change, at least seen from a user's point of view, I was also somewhat disappointed that it wasn't included in the latest release. It's about the only thing that keeps me from using plume. But each has its time and season.

Happy bug squashing! 🐛

Thanks. I figured it would be something like that. But since this is such a small change, at least seen from a user's point of view, I was also somewhat disappointed that it wasn't included in the latest release. It's about the only thing that keeps me from using plume. But each has its time and season. Happy bug squashing! 🐛

MasterOfTheTiger commented

2020-06-23 06:21:37 +00:00

(Migrated from github.com)

Release early, release often. Whenever this is fix, it won't take such a long time to be released. (As far as I know).

👍 1