Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are many pros and cons but the first question that you should answer yourself to find out what to use is... <strong>Are you looking for an universal content management framework on which you intend to build several websites?</strong></p> <ol> <li><p>If <strong>YES</strong>, then keep considering TYPO3. It has some great benefits, e.g.:</p> <ul> <li>Strict separation of core and site-specific files which greatly easies the management of several websites on one server because you can have one core only which you symlink from several websites. Applying a security update to all the websites is then a matter of minutes.</li> <li>Tree-like structure with pages resembling folders of a filesystem and various content records resembling files within them and the backend that supports working with those elements in a way resembling the work with folders/files - copying and moving content records, pages with content records and even whole trees of pages and records. There's also functionality that resembles symlinking (both for pages and content records) which simplifies management of content on large websites.</li> <li>UNIX-like permission system for pages with the option to have finer permission system using the <a href="http://typo3.org/extensions/repository/view/be_acl">be_acl</a> extension.</li> <li>A configuration (using its own configuration language called Typoscript) that is stored in a single field of one or more template records, that can be edited using a text editor of your choice (I use Notepad++ with Typoscript syntax highlighting + "<a href="https://addons.mozilla.org/en-US/firefox/addon/its-all-text/">It's All Text!</a>" extension for Firefox), that cascades down a page tree, that can be overridden on any page and that can be also stored in a text file on the filesystem which means that you can have configuration files shared by all the websites on a server thus allowing you to quickly change/fix/modify behavior of all of them at once.</li> <li>Ability to handle multilingual websites with both one-tree structure (all the language versions have the same structure) or multi-tree structure (every language version has different structure).</li> <li>Ability to host several websites/domains from within one installation of TYPO3.</li> <li>A development program where there are no changes of functionality within a branch (e.g. 4.5.x) of the system and yet with some of the branches having "long term support" (3 years) and thus receiving security updates - this allows you to have up-to-date websites for a significant period of time without having to do an update that would possibly change/break their functionality.</li> </ul></li> <li><p>If <strong>NO</strong> and you want to use some system for one project only, then... <strong>Is there a single specific functionality that the website is supposed to achieve?</strong></p> <ul> <li>If <strong>yes</strong>, look for a system which is best adapted for that task. If you want to build a blog or a photogallery, use a system which was designed with this specific task in mind. TYPO3 would not be your best option. Not that you cannot build a blog or a photogallery with it but it would take you more work.</li> <li>If <strong>no</strong> and you are just building a casual website, then think whether there is some other good reason to invest the time into learning TYPO3 to make it worth it. TYPO3 (from the point of view of a webdeveloper) is rather hard to learn and for one project might not be worth the effort.</li> </ul></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POTYPO3 versus other systems Drupal, Wordpress, Joomla
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UStmt
    1. UStmt
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTYPO3 versus other systems Drupal, Wordpress, Joomla
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI suppose you meant a shallow (or long) learning curve. Steep learning curve = "quick increment of skill" = easy to learn. Shallow learning curve = slow increment of skill = hard to learn. http://en.wikipedia.org/wiki/Learning_curve#.22Steep_learning_curve.22
      singulars
      1. PO
      1. USMateng
    2. COI'd like to add that the impression of TYPO3 being "chaotic" results from several years of backwards compatibility and therefore a lot of overhead in the code. On the other hand, that's why there are often multiple solutions for one problem in TYPO3.
      singulars
      1. PO
      1. USMateng
    3. CO@Mateng: I've always used it in the traditional meaning (as described in that Wikipedia article) thinking that it comes from "steep" in the sense "rising sharply" - in other words that the amount of new information appearing in the learning process rises sharply. Thanks for the information on correct usage. I'm going to alter my answer.
      singulars
      1. PO
      1. UStmt
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload