Login / Status
developer.Resource
Home . Documentation . Document Library . Extension Manuals
Sponsors
hosted by punkt.deTYPO3 and Open Source MagazineAOE Media

1.5. Debug Mode

How to set up the extension

If you don't know, how to set up the extension "SEO dynamic tag", or if there will be any failure, it is very helpful to activate the debug mode.

You will receive a lot of information like in our illustration above (page 9) about

  1. your typoscript code,

  2. the typoscript code changed by the extension,

  3. the success of substituting the used variables,

  4. the array with the available globals,

  5. the query string in the SQL database and

  6. the result.

Turn the debug mode on:

plugin.tx_seodynamictag_pi1.debug = 1

Or in our tutorial examples above

temp.seo = COA

temp.seo {

  10 < plugin.tx_seodynamictag_pi1

  10 {

    # Example for the page title

    special = title

    debug = 1

    query {

      ...

Everything is ok but there is a failure

If you have a failure like no effect in the page title, but everything in the report is ok, than there will be only one cause:

The extension "SEO dynamic tag" isn't the last page element, another page element is overriding the page title or <meta>-tags.

Example code for page element:

page {

  ...

  10 < your_content

  # The seo-plugin have to be the last content element

  1000 < plugin.tx_seodynamictag_pi1

  1000 {

    # Example for the page title

    special = title

    query {

      ...

Or in our tutorial examples above

page {

  ...

  10 {

    subparts {

      content = COA

      # Single view of a news in tt_news

      content.20 < temp.single

      # The seo-plugin have to be the last content element

      content.1000 < temp.seo

    }

  }

}

Screenshots

Example Page Title

Illustration 11: Values of the fields title and short of a tt_newsand the page title

The values of the fields title (1) and short (2) of a tt_news and the values in the page title.

The debug Report

Illustration 12: Report in the debug mode

The same in the report.

Report structure

  1. Your typoscript code.

  2. The typoscript code changed by the extension.

  3. The result of Substitution:

    1. There is an "OK", if the global variable is available.

    2. There is an "DANGER", if the global variable isn't available.

  1. The array with the available globals.

  2. The SQL query string. If you don't know, if the query has the valid syntax, copy the query to PhpMyAdmin e.g. and test it.

  3. The result value. In this example:

  4. tt_news.title and

  5. tt_news.short

SQL error message

If there is any syntax error in your query, you get an SQL error message, but only in debug mode.

Illustration 13: SQL error message