Support/TikiTrunkTestingNotes: Difference between revisions
< Support
Jump to navigation
Jump to search
MarcLaporte (talk | contribs) |
MarcLaporte (talk | contribs) |
||
| Line 10: | Line 10: | ||
*But still no way to login and stay logged in reliably (but better) | *But still no way to login and stay logged in reliably (but better) | ||
**Perhaps we should use .htaccess for bots instead of Tiki closing the site? | **Perhaps we should use .htaccess for bots instead of Tiki closing the site? | ||
*would be nice to have real theme | *would be nice to have [https://bugzilla.mozilla.org/show_bug.cgi?id=537513 real theme] | ||
** Needs to figure out svn externals (or equivalent) | |||
=== 2009-12-28 === | === 2009-12-28 === | ||
Revision as of 22:47, 6 January 2010
Coordination page for tiki-trunk.mozilla.com testers.
Background
http://tiki-trunk.mozilla.com/ contains real SUMO data from November 2009, on a environment similar (same?) to the real thing. The code will soon be updated daily from Tiki trunk
Notes
2010-01-06
- Cron job update should be OK now
- But still no way to login and stay logged in reliably (but better)
- Perhaps we should use .htaccess for bots instead of Tiki closing the site?
- would be nice to have real theme
- Needs to figure out svn externals (or equivalent)
2009-12-28
- http://tiki-trunk.mozilla.com/ is now somewhat testable
- I get logged out every once in a while. Perhaps the load balancers?
- We need a way to change base URL so we don't get sent to subdirectories because of rewrite rules. (ex.: http://tiki-trunk.mozilla.com/en-US/kb/tiki-admin.php)
- Perhaps {literal}<base href="http://tiki-trunk.mozilla.com/" />{/literal} in Admin -> Look & Feel -> General Layout Options -> Custom HTML <head> Content
- Would need to reduce security here because base becomes ba<x>se
- Perhaps {literal}<base href="http://tiki-trunk.mozilla.com/" />{/literal} in Admin -> Look & Feel -> General Layout Options -> Custom HTML <head> Content
- There is cache weirdness. I changed top to "This is the SUMO-Tiki5 testing site." and David is getting the old "We will be performing maintenance tonight at 8pm PDT. During this time the site is expected to be down for approximately an hour"
- tenser: "if you file a bug under the same component/product as the one to get the tiki-trunk server up, IT will look at it"
- Is http/https configured properly?
- What are the settings to tell Tiki for memcached?
- We don't need this just yet, but need to make sure it's not causing some issues because it's not filled in.
Some things to think about/discuss
- plugins need to be re-created (keyboard, etc)
- This should be done in profiles for easy redeployment
- All potentially unsafe plugins become "Plugin execution pending approval" (Need to visit a page for the plugins to appears on http://tiki-trunk.mozilla.com/tiki-plugins.php)
- Here is an example: http://tiki-trunk.mozilla.com/Contributor+Home+Page
- This is a known upgrade annoyance, brought by much better security in Tiki3
- So we would need a bot to visit all page and create the, (or do manually)