Re: uproot
Pratap Chakravarthy
> Some quick comments:
> 1. Favicon.ico is showing in the bread crumbs!
Yes. The site is not having a default favicon.ico file. I have raised
a ticket on that,
http://zt.devwhiz.net/p/zeta/t/118
> 2. In the homepage, the components is still showing as empty although I have
> created two.
This is a quirk. Policy is to have user definable project home page.
As you might have observed, editing the `homepage` wiki page under
project's wiki will automatically be interpreted as project's home
page. And wiki pages are not translated everytime, they are translated
and cached.
One solution would be to translate wiki pages everytime (or atleast
the homepage) but most of the translation will only be redundant.
To get over this problem, you can see a refresh icon on the top right
corner of the wiki page and home page.Click that, and you will have
your page afresh. And this need to be done only when the cached page
is out-dated.
> 3. When I edited the homepage and saved it is now showing the components
Explained above.
> The same problem for "versions". I created a
> new version for the project and it didnt' show up but after editing the
> homepage, it comes up fine...
Explained above.
> 4. But the formatting is screwed.. Or atleast it's not as it was earlier..
Very much screwed. I have raised a ticket for the same. My initial
guess it is to do with `ElementTree` library that is being used.
http://zt.devwhiz.net/p/zeta/t/109
> 5. When saving a wiki page, there is no indication that it got saved.
> Ideally you could show the newly formatted wiki page or atleast show a link
> to the new page. Or differences between new and old...
Wiki page submit is a AJAX submit. It must flash a message saying that
the page is submitted. If you are not seeing that flash message it is
a bug. On the other hand if you want to go to the page you can use the
``page`` link.
The idea is to encourage user to continue editing the page after the submit ;-)
If you really want a normal submit (i.e) Submit form and go back to
wiki page. Then I can raise a ticket for the same.
> How to create a team? Is it site-wide or project-wide?
It is site-wide. I would suggest that as `admin`, assign `ZETA_ADMIN`
permissions to yourself, that way, you will have the site-admin link
in the meta-navigation bar.
Now, to add teams goto site-admin->site-config tab and add the team
names under `projteamtypes` as comma separated value.
Harshad RJ
To get over this problem, you can see a refresh icon on the top right
corner of the wiki page and home page.Click that, and you will have
your page afresh. And this need to be done only when the cached page
is out-dated.
Ok, that's good enough for now.
Though, maybe you should make it more intelligent on the server side in the future. You could detect whether a wiki page is static or dynamic and then make it uncacheable or implement some kind of cache-coherency ;)
You could have triggers on variables to invalidate the cache.
But I think that is premature optimisation. My suggestion is to keep it simple and simply get rid of the cache on dynamic pages. Accuracy is more important than speed.
Wiki page submit is a AJAX submit. It must flash a message saying that
the page is submitted. If you are not seeing that flash message it is
a bug.
Bug it is then :)
On the other hand if you want to go to the page you can use the
``page`` link.
Ok, hadn't noticed it before...
The idea is to encourage user to continue editing the page after the submit ;-)
In that case, you can have a "save and continue" button in addition to the "submit" button, which I think should be renamed to "save". Most wiki's that I have seen have that choice, and it is very useful.
If you really want a normal submit (i.e) Submit form and go back to
wiki page. Then I can raise a ticket for the same.
My original request was that the indication is missing that the submit has happened. As you say, it might be a bug..
It is site-wide. I would suggest that as `admin`, assign `ZETA_ADMIN`
> How to create a team? Is it site-wide or project-wide?
permissions to yourself, that way, you will have the site-admin link
in the meta-navigation bar.
Ok. I don't prefer that.. I like to have a separate admin user.
Btw, I think you should rename it to SITE_ADMIN instead of ZETA_ADMIN for consistency and clarity.
Now, to add teams goto site-admin->site-config tab and add the team
names under `projteamtypes` as comma separated value.
Ok, but that's very unintuitive. Teams are not site-configurations.. I think you should give them a page of their own.
--
Harshad RJ
http://hrj.wikidot.com
Pratap Chakravarthy
http://zt.devwhiz.net/p/zeta/t/121
http://zt.devwhiz.net/p/zeta/t/122
http://zt.devwhiz.net/p/zeta/t/123
http://zt.devwhiz.net/p/zeta/t/124
--
Pratap.