Line 12: | Line 12: | ||
<p>We have moved all content from our pages (including igem.org, 2016.igem.org, and parts.igem.org) to a new server, which has allowed us to upgrade to a newer version of MediaWiki. We have upgraded from MediaWiki version 1.16.5 to 1.24.1, providing a higher level of security for the iGEM Wiki pages and offering new features. | <p>We have moved all content from our pages (including igem.org, 2016.igem.org, and parts.igem.org) to a new server, which has allowed us to upgrade to a newer version of MediaWiki. We have upgraded from MediaWiki version 1.16.5 to 1.24.1, providing a higher level of security for the iGEM Wiki pages and offering new features. | ||
<br><br> | <br><br> | ||
− | |||
So, what does this mean for you and your team? | So, what does this mean for you and your team? | ||
<br><br> | <br><br> | ||
Line 19: | Line 18: | ||
<li>We have also implemented a new protection feature for team wiki pages: Only team members listed and approved on the team profile page can edit their team pages. So what does this mean? Simply put: users can no longer edit content that does not belong to their team. This will help protect the content of your wiki page as you start adding content.</li> | <li>We have also implemented a new protection feature for team wiki pages: Only team members listed and approved on the team profile page can edit their team pages. So what does this mean? Simply put: users can no longer edit content that does not belong to their team. This will help protect the content of your wiki page as you start adding content.</li> | ||
<li>Images you upload will also be protected from others over-writing them if you follow this simple naming convention:</li> | <li>Images you upload will also be protected from others over-writing them if you follow this simple naming convention:</li> | ||
− | <ul><li> | + | <ul><li>T--TeamName--filename.fileextension</li> |
− | <li>For example: | + | <li>For example: T--BostonU--Flow_cyto_results.jpeg</li></ul> |
− | </ul | + | </ul> |
<br><br> | <br><br> | ||
− | </html> | + | <h3>Find a bug or problem?</h3> |
+ | <br> | ||
+ | If you have found a software problem on any of the iGEM pages, please send us an email to <i><b>hq AT igem DOT org</i></b> with the following information: | ||
+ | <ul> | ||
+ | <li>Subject line: Bug Report (website URL)</li> | ||
+ | <li>Details about the bug you found. What happened?</li> | ||
+ | <li>What browser were you using when the bug happened?</li> | ||
+ | <li>Were you logged into your iGEM account when it happened?</li> | ||
+ | <li>Include a screenshot of the problem, if possible</li> | ||
+ | <li>Include the time when the bug occurred (this can be estimated, but please indicate time zone!)</li> | ||
+ | </ul> | ||
+ | </html></p> | ||
{{2016Bottom}} | {{2016Bottom}} |
Revision as of 16:01, 8 June 2016
MediaWiki Update
June 7, 2016
We have moved all content from our pages (including igem.org, 2016.igem.org, and parts.igem.org) to a new server, which has allowed us to upgrade to a newer version of MediaWiki. We have upgraded from MediaWiki version 1.16.5 to 1.24.1, providing a higher level of security for the iGEM Wiki pages and offering new features.
So, what does this mean for you and your team?
- The black menu bar, including the login button, is now at the top of all of these pages to make logging in and navigating easier!
- We have also implemented a new protection feature for team wiki pages: Only team members listed and approved on the team profile page can edit their team pages. So what does this mean? Simply put: users can no longer edit content that does not belong to their team. This will help protect the content of your wiki page as you start adding content.
- Images you upload will also be protected from others over-writing them if you follow this simple naming convention:
- T--TeamName--filename.fileextension
- For example: T--BostonU--Flow_cyto_results.jpeg
Find a bug or problem?
If you have found a software problem on any of the iGEM pages, please send us an email to hq AT igem DOT org with the following information:
- Subject line: Bug Report (website URL)
- Details about the bug you found. What happened?
- What browser were you using when the bug happened?
- Were you logged into your iGEM account when it happened?
- Include a screenshot of the problem, if possible
- Include the time when the bug occurred (this can be estimated, but please indicate time zone!)