TestEngineering/UI/AMO/Tips and Pointers: Difference between revisions
< TestEngineering | UI
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
=Staging= | =Staging= | ||
To view the revision of AMO you're currently seeing, view-source of any page; in the bottom, you'll see something like <pre><!-- r24322 --></pre><p>This means you're at SVN revision number 24322 -- you can cross-link this to whatever revision number was posted in the checkin comment in the bug. | To view the revision of AMO you're currently seeing, view-source of any page; in the bottom, you'll see something like <pre><!-- r24322 --></pre><p>This means you're at SVN revision number 24322 -- you can cross-link this to whatever revision number was posted in the checkin comment in the bug. | ||
Staging doesn't automatically sync its database to production -- for some features (reviews, ratings, new add-ons, etc.), we'll need to get a fresh DB import from production; development usually files an IT bug requesting this | |||
Revision as of 22:22, 10 April 2009
Caching
AMO uses Zeus, which heavily caches content
If you see some_string_define on AMO, it's either 1) a raw string define, or (more likely) 2) Apache needs to restart to pick up the gettext() changes
Staging
To view the revision of AMO you're currently seeing, view-source of any page; in the bottom, you'll see something like
<!-- r24322 -->
This means you're at SVN revision number 24322 -- you can cross-link this to whatever revision number was posted in the checkin comment in the bug.
Staging doesn't automatically sync its database to production -- for some features (reviews, ratings, new add-ons, etc.), we'll need to get a fresh DB import from production; development usually files an IT bug requesting this