Tag Archives: typo3

By luiscurse [CC-BY-SA-3.0 (http://creativecommons.org/licenses/by-sa/3.0/)], via deviantART

Wonders of Typo3

A lot of people complain about Typo3. They say it is too heavy for a CMS. They may be right, it is complex and it takes some time to get used to it. But it pays!

Today a customer complained, that one of his pages in Typo3 was missing completely. He was right, it was not there any more. What happened? One of his employees accidentally deleted the wrong page … Which is not really a problem of Typo3. If you delete it, it is gone. It does not matter which system you are using … Well, problem for Typo3.

Unfortunately, content versioning was disabled, which made it a little bit more work:

  • open the database
  • find the page (write down the pid)
  • change deleted from 1 to 0
  • repeat those steps for all content entries with that pid
  • return to the administrator of Typo3
  • move the page to its correct location
  • reposition the content inside the page

… done in 5 minutes … with content versioning enabled it would have been a simple click …

Facebooktwittergoogle_plusredditpinterestlinkedintumblrmailFacebooktwittergoogle_plusredditpinterestlinkedintumblrmail

Flattr this!

By Jesus Presley [GFDL (http://www.gnu.org/copyleft/fdl.html) or CC-BY-SA-3.0 (http://creativecommons.org/licenses/by-sa/3.0)], via Wikimedia Commons

Typo3 Sitemap Hacks

The creation of site maps in Typo3 is pretty straight forward. You can either use the built-in site-map function or the extension fl_seo_sitemap. The later has the advantage of being adjustable using CSS.

Have a look at an example for an human readable site map created using the SEO plugin.

For the automatic creation of a site map for Google in XML format, there exists another nice extension mc_googlesitemap. It provides not only functions to create site maps for the individual pages of the Typo3 CMS but also for database content such as news items. At our system, the site maps for content items did not like to work at first. A look at the source code showed the problem. We did not have the news items assigned to a news category. After doing so, the site map worked.

Here are examples for a Google site map for pages and a Google site map for content items.

Facebooktwittergoogle_plusredditpinterestlinkedintumblrmailFacebooktwittergoogle_plusredditpinterestlinkedintumblrmail

Flattr this!