API:Edit/es

From MediaWiki.org
Jump to navigation Jump to search
This page is a translated version of the page API:Edit and the translation is 8% complete.

Other languages:
Deutsch • ‎English • ‎Tiếng Việt • ‎dansk • ‎español • ‎français • ‎русский • ‎тоҷикӣ • ‎中文 • ‎日本語
Versión de MediaWiki: 1.13

POST request to edit a page.

API documentation




action=edit

(main | edit)
  • This module requires read rights.
  • This module requires write rights.
  • This module only accepts POST requests.
  • Source: MediaWiki
  • License: GPL-2.0-or-later

Create and edit pages.

Parameters:
title

Title of the page to edit. Cannot be used together with pageid.

pageid

Page ID of the page to edit. Cannot be used together with title.

Type: integer
section

Section number. 0 for the top section, new for a new section.

sectiontitle

The title for a new section.

text

Page content.

summary

Edit summary. Also section title when section=new and sectiontitle is not set.

tags

Change tags to apply to the revision.

Values (separate with | or alternative):
minor

Minor edit.

Type: boolean (details)
notminor

Non-minor edit.

Type: boolean (details)
bot

Mark this edit as a bot edit.

Type: boolean (details)
basetimestamp

Timestamp of the base revision, used to detect edit conflicts. May be obtained through action=query&prop=revisions&rvprop=timestamp.

Type: timestamp (allowed formats)
starttimestamp

Timestamp when the editing process began, used to detect edit conflicts. An appropriate value may be obtained using curtimestamp when beginning the edit process (e.g. when loading the page content to edit).

Type: timestamp (allowed formats)
recreate

Override any errors about the page having been deleted in the meantime.

Type: boolean (details)
createonly

Don't edit the page if it exists already.

Type: boolean (details)
nocreate

Throw an error if the page doesn't exist.

Type: boolean (details)
watch
Deprecated.

Add the page to the current user's watchlist.

Type: boolean (details)
unwatch
Deprecated.

Remove the page from the current user's watchlist.

Type: boolean (details)
watchlist

Unconditionally add or remove the page from the current user's watchlist, use preferences or do not change watch.

One of the following values: watch, unwatch, preferences, nochange
Default: preferences
md5

The MD5 hash of the text parameter, or the prependtext and appendtext parameters concatenated. If set, the edit won't be done unless the hash is correct.

prependtext

Add this text to the beginning of the page. Overrides text.

appendtext

Add this text to the end of the page. Overrides text.

Use section=new to append a new section, rather than this parameter.

undo

Undo this revision. Overrides text, prependtext and appendtext.

The value must be no less than 0.
Type: integer
undoafter

Undo all revisions from undo to this one. If not set, just undo one revision.

The value must be no less than 0.
Type: integer
redirect

Automatically resolve redirects.

Type: boolean (details)
contentformat

Content serialization format used for the input text.

One of the following values: application/json, text/css, text/plain, text/x-wiki, text/javascript
contentmodel

Content model of the new content.

One of the following values: GadgetDefinition, SecurePoll, sanitized-css, MassMessageListContent, flow-board, Scribunto, JsonSchema, NewsletterContent, wikitext, javascript, json, css, text
token

A "csrf" token retrieved from action=query&meta=tokens

The token should always be sent as the last parameter, or at least after the text parameter.

This parameter is required.
captchaword

Answer to the CAPTCHA

captchaid

CAPTCHA ID from previous request

Ejemplo

The sample code in this example is in Python. See API:Edit/Editing with Ajax for examples and responses in Ajax .

POST Request

Making edits, and, indeed, any POST request, is a multi-step process.

1. Log in, via one of the methods described in API:Login . Note that while this is required to correctly attribute the edit to its author, many wikis do allow users to edit without registering or logging into an account.
2. GET a CSRF token :
3. Send a POST request, with the CSRF token, to take action on a page:

The Response section below is for the final POST request, described in Step 4. See the pages on API:Login and API:Tokens for the intermediary JSON responses to earlier steps.

Also note that the tokens in the queries on this page are sample values. Actual tokens are unique to each login session and cross-site request. They are included only to demonstrate how to properly format queries.

Response

{
        "edit":{
        "result":"Success",
        "pageid":94542,
        "title":"Sandbox",
        "contentmodel":"wikitext",
        "oldrevid":371705,
        "newrevid":371707,
        "newtimestamp":"2018-12-18T16:59:42Z"
    }
}

Sample code

edit.py

#!/usr/bin/python3

"""
    edit.py

    MediaWiki Action API Code Samples
    Demo of `Edit` module: POST request to edit a page
    Based on User:Александр Сигачёв, 
    https://www.mediawiki.org/wiki/API:Edit/Editing_with_Python
    MIT license
"""

import requests

S = requests.Session()

URL = "https://test.wikipedia.org/w/api.php"

# Step 1: Retrieve a login token
PARAMS_1 = {
    "action": "query",
    "meta": "tokens",
    "type": "login",
    "format": "json"
}

R = S.get(url=URL, params=PARAMS_1)
DATA = R.json()

LOGIN_TOKEN = DATA["query"]["tokens"]["logintoken"]

# Step 2: Send a post request to log in. For this login 
# method, Obtain credentials by first visiting
# https://www.test.wikipedia.org/wiki/Manual:Bot_passwords
# See https://www.mediawiki.org/wiki/API:Login for more
# information on log in methods.
PARAMS_2 = {
    "action": "login",
    "lgname": "user_name",
    "lgpassword": "password",
    "format": "json",
    "lgtoken": LOGIN_TOKEN
}

R = S.post(URL, data=PARAMS_2)

# Step 3: While logged in, retrieve a CSRF token
PARAMS_3 = {
    "action": "query",
    "meta": "tokens",
    "format": "json"
}

R = S.get(url=URL, params=PARAMS_3)
DATA = R.json()

CSRF_TOKEN = DATA["query"]["tokens"]["csrftoken"]

# Step 4: Send a post request to edit a page
PARAMS_3 = {
    "action": "edit",
    "title": "Sandbox",
    "format": "json",
    "appendtext": "Hello",
    "token": CSRF_TOKEN,
}

R = S.post(URL, data=PARAMS_4)
DATA = R.json()

print(DATA)

Edit conflicts

The Python sample above is a basic implementation, of an edit request by a registered user. In real-world scenarios care should be taken to prevent edit conflicts. These occur when two or more users are attempting to edit the same page at the same time.

Conflicts can be prevented by retrieving the last revision timestamp when we request a CSRF token. Adding prop=info|revisions to the CSRF token request in Step 3 allows us to access the timestamp for the last revision. This timestamp will be used as the basetimestamp when we make our the edit request.

We also need the exact time when we start our edit. This can be retrieved by adding curtimestamp to the CSRF request as well. This value will serve as our starttimestamp.

Finally, in the actual edit request, set the basetimestamp and starttimestamp parameters, like so:

Large edits

POST requests containing large amounts of text content (8000+ characters) should be sent with Content-Type: multipart/form-data indicated in the header. Because multipart/form-data does not need to add HTML escape characters (i.e., percent encoding) for spaces and punctuation, the amount of data passed will subsequently be much smaller than the percent-encoded equivalent.

However, there is still some overhead added by multipart/form-data -- roughly, 160 bytes per parameter. For short messages that don't require adding many escape characters, this amount of overhead can be inefficient, and percent-encoding is preferred[1].

Note that in our Python sample code, the request is percent-encoded by default.

See the MDN web docs for a more technical discussion of content-type and POST requests. See the Python Requests documentation for how to pass multipart/form-data using syntax similar to our Python sample code.

CAPTCHAs

If the wiki you are targeting uses CAPTCHAs , your request may return an error containing an id number and a simple test, such as a question, a math problem, or an URL to an image. In order to complete your edit, you must complete the test, then retry your request with the id and the correct answer(s) appended to the original query string, like so: captchaid=sampleId&captchaword=answer

Other CAPTCHA systems and extensions may use different parameters for similar use. In general, use the field names for the id and test questions as the parameters in your second request.

Possible errors

Código Información
invalidsection El parámetro section debe ser un identificador de sección válido, o bien new.
pagedeleted La página ha sido borrada en algún momento desde que obtuviste su marca de tiempo.
emptypage Crear páginas vacías no está permitido.
emptynewsection Crear secciones vacías no es posible.
undofailure Undo failed due to conflicting intermediate edits
readapidenied Necesitas permiso de lectura para utilizar este módulo.
writeapidenied No tienes permiso para editar este wiki a través de la API.
noapiwrite La edición de este wiki a través de la API está deshabilitada. Asegúrate de que la declaración $wgEnableWriteAPI=true; está incluida en el archivo LocalSettings.php del wiki.
pagecannotexist En este espacio de nombres no se permiten páginas reales.
hookaborted The modification you tried to make was aborted by an extension.
redirect-appendonly You have attempted to edit using the redirect-following mode, which must be used in conjuction with section=new, prependtext, or appendtext.

Parameter history

  • v1.25: Introduced tags
  • v1.21: Introduced contentformat, contentmodel
  • v1.20: Introduced pageid
  • v1.19: Introduced sectiontitle
  • v1.18: Deprecated captchaid, captchaword
  • v1.17: Introduced redirect
  • v1.16: Deprecated watch, unwatch
  • v1.16: Introduced watchlist
  • v1.15: Introduced undo, undoafter
  • v1.14: Introduced starttimestamp

Additional notes

  • Log in is not strictly required by the API, but it is needed to correctly attribute the edit to its author. A successful edit from a user who is not logged in will be attributed to their IP address.
  • Bots that are not logged in may face restrictions on editing and other write requests; see Manual:Creating a bot#Logging in for more details.
  • Users who are not logged in will always be given the empty CSRF token, +\.
  • The process for requesting a token has changed several times across versions. See API:Tokens for more information.
  • ResourceLoader provides a way to access edit tokens when running code within a wiki page.
  • You can use the same login token for all edit operations across the same wiki, during a single login session.
  • It is a good practice to pass any tokens in your request at the end of the query string, or at least after the text parameter. That way, if the connection is interrupted, the token will not be passed and the edit will fail. If you are using the mw.Api object to make requests, this is done automatically.
  • Although captchaid and captchaword have, technically, been removed from API:Edit since v1.18, Extension:ConfirmEdit extends API:Edit to work with CAPTCHAs. Thus, with ConfirmEdit installed, these parameters are still available. ConfirmEdit comes packaged with the MediaWiki software, v1.18+.

Véase también

Referencias