Extension:Push/manual/Dealing with common problems

This is the Push/manual/Dealing with common problems part of the user manual for the Push extension.

Pushing pages between two distinct wikis, that can have different versions and configurations over a network can fail for a number of reasons. This section contains a number of common problems, caused by either misconfiguration, network issues such as timeouts or simple misunderstanding of how the extension works, and their solutions.

The push tab does not show up

• Make sure you are logged in.
• If it never showed up before, you might still need to get the privileges to push from your wikis administrator.

No targets to push to

If you get a message equivalent to "There are no targets to push to. Please add some to your LocalSettings.php file.", it means that the Push extension is not configured on the local wiki yet. This can only be done by an administrator.

Authentication failed

If you get an error stating that authentication failed, it means that either the local configuration for the push user on the target wiki is not correct, or that the remote user simply does not have sufficient privileges to create pages or upload files. Both these problems can only be solved by an administrator. Steps to take:

• Make the $egPushLoginUsers and $egPushLoginPasswords entries for the wiki the pushing fails to are correct. Copy them and try to login into the target wiki.
• Once logged in into the target wiki, try to edit a page, try to create one, and try to upload a file. If one of these fails, give the push user sufficient privileges.

Captcha error

If you get "Could not push to 'target wiki name' due to captcha.", it means that there is a privilege problem for the push user on the target wiki. This user is getting a captcha when either editing or creating a page, or uploading a file. Give the push user sufficient privileges so it doesn't get a captcha anymore. This can only be done by administrators.