“”

Frequently asked questions

Here you can find FAQ regarding the TYPO3 extension repository.
If you have a question that is not showing up here, please contact the t3o team.

The extension index which acts as the data source for the list on typo3.org is only updated every few minutes, so you might have to wait a little longer.

Maybe you're looking for an extension key like "tx_address"? Then leave out the "tx_" prefix - that's a syntax used in TYPO3 internally. Make sure you're searching for the right extension key!

If all that still doesn't help, please get in contact with the t3o team.

If you never uploaded an extension using a certain extension key, you can delete it using the extension key tool.

For reasons of integrity, you cannot delete used extension keys nor uploaded extensions. If your extension has a security issue, please contact the Security Team.

If you don't want to maintain your extension any more, you can transfer the extension key to the user "abandoned_extensions".

There are two possibilities:

  1. If the owner has not uploaded any version of the extension, you can contact him and ask for the extension key. If there is no reaction by the owner, please get in contact with the t3o team or the Extension Coordination team.
  2. If the owner has uploaded minimum one version (you can find out by searching for the key), all you can do is offer a contribution.

There are two possible causes for the 500:

  1. Please check that your extension is not bigger than 30MB (if you have big libraries in the extension think about composer)
  2. Your file ext_emconf.php has a field which is a concatenated string. Our PHP parser cannot parse it in the moment, so please don't concatenate.

If you are sure no point is throwing the 500 error, please contact the t3o team.

  1. Check that your documentation is located at the right place in your extension. That is ./Documentation/Index.rst or ./README.rst.
  2. If your documentation still is not rendered, there can be an syntax error in your reStructuredText.
    Warnings and errors will be saved to https://docs.typo3.org/typo3cms/extensions/YOUREXTKEY/warnings.txt, so take a look there.
    In addition you can use the extension sphinx to proof if everything is fine on your local system.
  3. Rendering takes time. The documentation is fetched cyclically by docs server

To get an introduction to reStructuredText take the sphinx extension as an example. Further more the format is well documented at sphinx-doc.org/rest.html.
In addition the documentation of the sphinx extension has further information.

On the page https://docs.typo3.org/Extensions/ you get a list of tools and worflows how to best document your extension in reST.

The download counter of the TER for an extension is used by:

  • via TER / Extension Manager (non-composer mode)
  • via Download button (TER pages)

Downloads via TER (composer mode) or Packagist are (currently) not counted.