View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004228 | Taler | obsolete component | public | 2016-03-02 17:59 | 2016-03-15 20:16 |
| Reporter | Florian Dold | Assigned To | Marcello Stanisci | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.0 | ||||
| Target Version | 0.0 | Fixed in Version | 0.0 | ||
| Summary | 0004228: public account history should be linked from central page | ||||
| Description | ... right now you can only see the link if you're logged out | ||||
| Tags | No tags attached. | ||||
|
|
Why? I deliberately didn't want that link there, as it is confusing and unusual to have such 'public accounts'. So having them only reachable from the non-personal interface seems fine. |
|
|
A feature whose accessibility is dependent on the login state of the user is highly confusing. It means that somebody who just logged in, withdrew and purchased something has to log out in order to see if the public account balance was updated. If we do not want people (those who try out our demo) to look at the public account balance, then we should not have the link in the interface at all. Your argument would make sense if there was a separate personal area and a landing page, but right now going to https://bank.test.taler.net/ while being logged in gives you the "personal area" and no way to access the public account balances. For the demo that makes definitely sense, it's just a question of whether we want people to look at the public account balance (then it should be available even while logged in) or not (then it shouldn't be there at all). |
|
|
I guess what we really need is some generic navigation that is always present, like what we have on taler.net's main page. In fact, I recall the point being made before that we should have such a navigation across the different *.demo-subsites, so that it is easy to go from bank to shop to blog to bank to documentation. If we had such a menu on top, we could have it include drop-downs, i.e. the structure might be: * about -> wallet / landing page * bank -> login/central page - my account -> main bank page (login/central_page) - public accounts -> accounts page * shop -> main shop subdomain - Web shop -> main shop subdomain - blog -> blog subdomain - drupal -> drupal subdomain (once done) - ... (as many as we have) * help -> about -> wallet / landing page (with 'show more' enabled) |
|
|
Agreed, I really like that suggestion. It would make the {merchant,demo,bank} code less generic (more coupled to our site and demo setup), but it's so simple anyway that it doesn't matter. We should use a generic template for all the frame/navigation stuff (one for Django templating, one for PHP), currently we repeat our layout in many places, so we could fix that in one go as well ;-) |
|
|
reverse proxy SSI might be a neat way to implement this: http://stackoverflow.com/questions/24680989/with-nginx-how-do-i-run-ssi-on-a-page-returned-from-another-server That way, we can do the central menu in one place! |
|
|
The SSI include works, so this issue's main goal has been fulfilled. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-03-02 17:59 | Florian Dold | New Issue | |
| 2016-03-02 17:59 | Florian Dold | Status | new => assigned |
| 2016-03-02 17:59 | Florian Dold | Assigned To | => Marcello Stanisci |
| 2016-03-02 23:40 | Christian Grothoff | Note Added: 0010223 | |
| 2016-03-02 23:40 | Christian Grothoff | Status | assigned => feedback |
| 2016-03-02 23:52 | Florian Dold | Note Added: 0010224 | |
| 2016-03-02 23:52 | Florian Dold | Status | feedback => assigned |
| 2016-03-03 00:13 | Christian Grothoff | Note Added: 0010225 | |
| 2016-03-03 00:22 | Florian Dold | Note Added: 0010226 | |
| 2016-03-03 09:16 | Christian Grothoff | Note Added: 0010227 | |
| 2016-03-08 21:26 | Christian Grothoff | Product Version | => 0.0 |
| 2016-03-08 21:26 | Christian Grothoff | Target Version | => 0.1 |
| 2016-03-15 10:56 | Marcello Stanisci | Note Added: 0010241 | |
| 2016-03-15 10:56 | Marcello Stanisci | Status | assigned => resolved |
| 2016-03-15 10:56 | Marcello Stanisci | Resolution | open => fixed |
| 2016-03-15 20:16 | Christian Grothoff | Status | resolved => closed |
| 2016-03-15 20:16 | Christian Grothoff | Fixed in Version | => 0.0 |
| 2016-03-15 20:16 | Christian Grothoff | Target Version | 0.1 => 0.0 |
| 2022-08-23 20:26 | Christian Grothoff | Category | bank (demonstrator) => py bank (demonstrator, obsolete) |
| 2023-12-03 01:23 | Christian Grothoff | Category | py bank (demonstrator, obsolete) => obsolete componet |
| 2023-12-11 20:08 | Florian Dold | Category | obsolete componet => obsolete component |
