Tech:Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
imported>Addshore No edit summary |
imported>Addshore No edit summary |
||
Line 3: | Line 3: | ||
# If you get the message saying the wiki does not exist see [[Renaming a database]] |
# If you get the message saying the wiki does not exist see [[Renaming a database]] |
||
===Magic Word Exceptions=== |
===Mediawiki Magic Word Exceptions=== |
||
This probably means that the Localisation cache has not updated or someone has enabled an extension on a wiki without it being enabled on extload. |
This probably means that the Localisation cache has not updated or someone has enabled an extension on a wiki without it being enabled on extload. |
||
# Make sure the extension is included on extloadwiki |
# Make sure the extension is included on extloadwiki |
||
# If the issue persists run 'rebuildLocalisationCache.php --wiki extloadwiki' |
# If the issue persists run 'rebuildLocalisationCache.php --wiki extloadwiki' |
||
===Ansible Playbook doesn't appear to be updating=== |
|||
# Is the cronjob for root still there? |
|||
# Check /var/log/ansible-pull.log for erorrs |
|||
# Fix them (best bet is probably reverting the changes on github that broke it!) |
Revision as of 22:21, 29 January 2014
This is a cached copy of the requested page, and may not be up to date (in red)
- Try running 'rebuildFileCache.php' over the wiki
- If you get the message saying the wiki does not exist see Renaming a database
Mediawiki Magic Word Exceptions
This probably means that the Localisation cache has not updated or someone has enabled an extension on a wiki without it being enabled on extload.
- Make sure the extension is included on extloadwiki
- If the issue persists run 'rebuildLocalisationCache.php --wiki extloadwiki'
Ansible Playbook doesn't appear to be updating
- Is the cronjob for root still there?
- Check /var/log/ansible-pull.log for erorrs
- Fix them (best bet is probably reverting the changes on github that broke it!)