http://info.tiki.org/demo promotes the demo sites.
And a lot of people use so they are very messy. After a while, they become unusable. And a bad impression of Tiki.
In the past, it was important to keep the demo sites for a certain time because people would use them to demonstrate bugs. But now that we have show.tiki.org, it's no longer important.
Ideally, there would be a pop-up or something indicating when the next refresh will happen. Otherwise, some people may have data reset while they are working on it. But in practice, this is quite rare. As long as hour of refresh is indicated on demo.tiki.org, it's good. So a daily refresh would be OK I think, but it could also be weekly.
Once the demo site is refreshed, the script to set the password to 12345 should be run. And users should not have to go through the admin reset routine. So beyond setting the password to 12345, the script should do what it takes for Tiki not to think the admin password needs to be changed. This is a problem we have on show.tiki.org
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |