We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
#206 - Editable meta data
This is a spacer post for a website comment topic. The content this topic relates to: #206 - Editable meta data
Customisable URL moniker also be allowed to put a leading slash on it to define the full URL relative to the base URL.
Example...
you have a news post, Test
which auto-generates a moniker 'test'
which has a URL /site/news/view/test.htm
you want to be able to change the moniker to 'example', for /site/news/view/example.htm, or even to '/example' for /example.htm
Composr would need to check any of these monikers to ensure the given names don't cause conflicts.
Composr would need to of course have support for these new "trailing /" monikers.
^ Not relative to the base URL, relative to the zone. That makes it more flexible, in terms of allowing the same URL stems to run out of multiple zones (via a transparent redirect on the owner pages). Simultaneously it makes it more robust - you don't really want URLs coming out of a zone that don't have that zone in the URL (if you want it coming off the root, add it to the welcome zone of a single-public-zone site).
All edit screens should have a little "?" icon somewhere on the form which shows you behind-the-scenes information (date added, ID, author/owner) when clicked or hovered over. Consider only showing this icon & information to admins.
This would make it a lot easier for people to find out the specific IDs of pieces of content.
Example...
you have a news post, Test
which auto-generates a moniker 'test'
which has a URL /site/news/view/test.htm
you want to be able to change the moniker to 'example', for /site/news/view/example.htm, or even to '/example' for /example.htm
Composr would need to check any of these monikers to ensure the given names don't cause conflicts.
Composr would need to of course have support for these new "trailing /" monikers.
This would make it a lot easier for people to find out the specific IDs of pieces of content.