DEPRECATION WARNING
This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
EXT: Readable name of your extension¶
| Created: | 2010-02-18T17:33:18 |
|---|---|
| Changed: | 2012-05-16T23:29:11.960000000 |
| Classification: | extensionkey |
| Description: | The keywords help with categorizing and tagging of the manuals. You can combine two or more keywords and add additional keywords yourself. Please use at least one keyword from both lists. If your manual is NOT in english, see next tab "language" ---- forEditors (use this for editors / german "Redakteure") forAdmins (use this for Administrators) forDevelopers (use this for Developers) forBeginners (manuals covering TYPO3 basics) forIntermediates (manuals going into more depth) forAdvanced (covering the most advanced TYPO3 topics) see more: http://wiki.typo3.org/doc_template#tags ---- |
| Keywords: | keywords comma-separated |
| Author: | Author Name |
| Email: | your@email.com |
| Info 4: | |
| Language: | en |
EXT:Content with pagebrowser- ws_contentpagebrowser
EXT: Content with PageBrowser¶
Extension Key: ws_contentpagebrowser
Language: en
Keywords: content, pagebrowser, integrator
Copyright 2000-2010, Nikolay Orlenko, <info@web-spectr.com>
This document is published under the Open Content License
available from http://www.opencontent.org/opl.shtml
The content of this document is related to TYPO3
- a GNU/GPL CMS/Framework available from www.typo3.org
Table of Contents¶
EXT: Content with PageBrowser 1
`Introduction 3 <#__RefHeading__29129_568008793>`_
`Users manual 4 <#__RefHeading__29133_568008793>`_
`Configuration 5 <#__RefHeading__29135_568008793>`_
Inserting plugin like usual content element 5
Inserting plugin via TypoScript 5
`To-Do list 7 <#__RefHeading__29141_568008793>`_
Introduction¶
What does it do?¶
Very often we do not need to create and manage special content it is better to use standard TYPO3 content elements such as Text, Text&Pictures, Images, etc. But all standard elements are shown on one page and there is no pagebrowser for them in TYPO3.This extension tries to solve problem and separates content elements from one page into many pages using pagebrowser.
Users manual¶
- Extension uses “ pagevrowse ” extension by D. Dulepov for link generation.
- Extension works like standard plugin. In this case you need to set storage pid where content elements are
- You can also use extension in your TypoScript. In this case extension will get current page where plugin is invoke and render all current content elements.
Configuration¶
Install “pagebrowse” extension by D.Dulepov
Install extension “ws_contentpagebrowser” in Extension Manager
Include static template “Content pagebrowser” in main TypoScript Template
Inserting plugin like usual content element¶
Insert plugin “Content pagebrowser” on that page where you want to have content with page browser
Set value for storage folder. This folder or page should store all you needed content
Set limit content elements value per one page.
Inserting plugin via TypoScript¶
This method you should use when you want to render content elements in some FE pages, but not in System folders.
In normal situations we use following TypoScript code:
page.10 < styles.content.get
But for pagebrowser implementation you should write the following:
page.10 < plugin.tx_wscontentpagebrowser_pi1
Example¶
plugin.tx_wscontentpagebrowser_pi1 {
limit = 5
content = CONTENT
content {
table = tt_content
select {
pidInList = this
orderBy = sorting
languageField = sys_language_uid
where = CType IN ("text","textpic","image","multimedia","media")
}
}
}
Reference¶
Possible subsections: Reference (TypoScript)
storagePid¶
Property
storagePid
Data type
int
Description
Storage Pid Folder where should be content elements for redering
Default
this
limit¶
Property
limit
Data type
int
Description
Limitation per page.
Default
10
content¶
Property
content
Data type
CObject
Description
Main configuration of content rendering. Should has the same configuration with CONTENT Ctype.Here you can set any table what you want, not only tt_content. But also tx_*, tt_*, fe_*, user_* and static_*
Default
[tsref:(cObject).TEST]
((generated))¶
Example 1¶
If you want to render content only from one column, then indicate this column in where section of select configuration:
plugin.tx_wscontentpagebrowser_pi1 {
content = CONTENT
content {
table = tt_content
select {
pidInList = this
orderBy = sorting
languageField = sys_language_uid
where = CType IN ("text","textpic") AND colPos=0
}
renderObj = COA
renderObj {
wrap = <li> | </li>
10 = TEXT
10 {
required = 1
wrap = <div><strong> | </strong></div>
field = title
}
20 = TEXT
20 {
required = 1
wrap = <div> | </div>
field = bodytext
}
}
}
Example 2¶
Content specific column from all subpages of the current site (provided by Robert Wildling)
plugin.tx_wscontentpagebrowser_pi1 {
storagePid = {$plugin.tx_wscontentpagebrowser_pi1.storagePid}
limit = {$plugin.tx_wscontentpagebrowser_pi1.limit}
content >
content = CONTENT
content {
table = pages
select {
pidInList = this
orderBy = sorting
}
renderObj = COA
renderObj {
# save current uid of page
10 = LOAD_REGISTER
10.site_uid.field = uid
20 = CONTENT
20 {
table = tt_content
select {
# get pid value from the stored uid value
pidInList.data = register:site_uid
# define the column with the contents to list
where = colPos=0
andWhere = CType IN ("text","textpic","image","multimedia","media")
}
renderObj = COA
renderObj {
10 = TEXT
10.field = header
10.wrap = <h3>|</h3>
20 = TEXT
20.field = bodytext
20.wrap = <p>|
30 = TEXT
30.value = ...mehr
30.typolink.parameter.data = register:site_uid
30.wrap = |</p>
}
}
# clear the register
99 = RESTORE_REGISTER
}
}
}
To-Do list¶
- Create hook for supporting of custom page browser generation method
- Improve documentation with better examples and screenshots.
8