texnixe
November 16, 2017, 9:07pm
4
I think it would actually make sense to reroute one of them to the other in order to avoid duplicate content. You can do so in your server config or .htaccess.
Here are some more links that might be useful:
Htaccess would be one solution. Another would be PHP.
If you don’t find any better solution, maybe you can try this plugin:
https://github.com/jenstornell/kirby-redirect-to-slash
It works the other way around, redirect from no slash to slash. If you have PHP skills maybe you can modify it to work the other way?
Hey guys, I just realized that the Facebook button treats URLs differently when they end or don’t end with trailing slashes, in regards to maintaining Likes and comments. The best solution I can think of to handle this is to force my website to always be one or the other.
I tried using .htaccess to force trailing slashes but then it caused errors with the Kirby Panel that prevented me from saving changes to pages.
Any ideas?
opened 12:53AM - 03 Jul 18 UTC
closed 10:51AM - 16 Jul 18 UTC
The structure field table layout looks great already, but as of now (when having… multiple fields, especially number fields) one can not distinguish what a value in a certain table column stands for without opening it.
Since it's about sizes in this example, one could guess that all three columns stand for dimensions:
![structure-fields_now](https://user-images.githubusercontent.com/2584674/42192111-ff60581e-7e66-11e8-8d06-b16c28d6b26a.png)
But actually one is the price :smile:
![bildschirmfoto von 2018-07-03 01-42-31](https://user-images.githubusercontent.com/2584674/42192896-ee84adba-7e6b-11e8-95de-653df811fa48.png)
---
In Kirby 2 there was a table headline with the field labels. Thereby it was possible (but not always optimal with a lot of entries) to see what each column contained.
**So propably you should think about adding back a table head**
But at least (and maybe also if a table head returns) I feel you should display the **before** and **after** options in the table overview, too:
![structure-fields](https://user-images.githubusercontent.com/2584674/42192142-53e52d6a-7e67-11e8-8af2-82520e4683e3.jpg)
Optionally, the value could be simply aligned by the existence of before and after options:
- **nothing / before only** = align left (default)
- **after only** = align right
- **before & after** = align center