QutEcoacoustics / baw-server

The acoustic workbench server for storing and managing ecoacoustic data. Manages the structure and audio data. Provides an API for clients access.
Apache License 2.0
9 stars 4 forks source link

[TRACKING] Cms page bugs/issues #500

Closed Allcharles closed 4 years ago

Allcharles commented 4 years ago

Tracking the list of incorrect links and broken formatting in the cms pages so they can be fixed:

atruskie commented 4 years ago
  1. Remember the current cms content is serving live content for the rails site. For the site it is not broken. We'll update the link when the new client is deployed
  2. that content is instance specific and is not related to this repo or issue tracker
Allcharles commented 4 years ago

The page is "send audio". The view fragment that was replaced was called "data_upload" and the name was kept for consistency. The route is also /data_upload. I believe the discrepancy was raised during a feedback session and the title "send audio" was deemed clearer

Can we properly clean this up and use a consistent naming scheme? Also, on the website, this is displayed as the "Send Audio" link, however when you access the page the CMS page displays Data Upload. This may cause confusion for users

  1. Remember the current cms content is serving live content for the rails site. For the site it is not broken. We'll update the link when the new client is deployed

Then this should remain an open issue so that the problems aren't forgotten when we deploy the new client?

  1. that content is instance specific and is not related to this repo or issue tracker

Where would you like me to track theses cms related issues instead?

atruskie commented 4 years ago

Can we properly clean this up and use a consistent naming scheme? Also, on the website, this is displayed as the "Send Audio" link, however when you access the page the CMS page displays Data Upload. This may cause confusion for users

Url: /data_upload Name: Send audio

Everything else should be changed via CMS

Then this should remain an open issue so that the problems aren't forgotten when we deploy the new client?

Maybe. But this issue included a lot of not-relevant noise.

Where would you like me to track theses cms related issues instead?

Content related to an instance can be fixed using the /admin/cms interface for each instance. The baw-private repo could be used for this purpose but I'd suggest just fixing it.

Allcharles commented 4 years ago

~Contact us links for the deployed service are also broken btw~

Edit: Issue seams to have been resolved? Before, the links to contact us had messed up formatting like https://ecosounds.org/%contact_us%

atruskie commented 4 years ago

how?