This Documentation was written for version 5.0.x of the extension.
What does it do?
Managing your books:
Purpose of this extension is to manage few to a lot of books. There is a list-
and a singleview for the frontend. In listview a pagebrowser and a searchfield
makes book finding an ease.
Books can have category, serie, number, title, author, ISBN-Number, Description,
Cover and Extras.
In listview number, title, author and isbn-number are possible sortfields.
Searching books is done on fields title, author, isbn-number and description.
Installation
Download via Extension Manager
In the TYPO3 Backend go to Admin Tools > Extensions. Change in the dropdown on
the top left to 'Get Extensions', enter the extension key 'sf_books' in the
text field below the headline 'Get Extensions' and hit go. In the result list
install the extension by hitting the action for that.
Download via Composer
Add evoweb/sf-books to the require in your composer.json.
Enter on shell
composer require evoweb/sf-books
Copied!
Include TypoScript
Include static file "Book Library" in your typoscript record or import in your
sitepackage and modify the constants to match the page setup you have added.
Include Routing configuration
To have speaking urls you need to add the following import in your site config.
This allows each of the plugins to render seo friendly urls.
There are configurations for listView and singleView and more general parts
like templateFile or pidList. In all fields related stdWraps fields from
tx_sfbooks_books are available for field and data like uid.
Used to define several paths for templates, which will be tried in reversed
order (the paths are searched from bottom to top). The first folder where
the desired layout is found, is used. If the array keys are numeric, they
are first sorted and then tried in reversed order.
Allows to configure what pagination class should be used. If no class name
is given or the given class does not implement the PaginationInterface, the
default SimplePagination gets used.
Rename TypoScript parameter settings.limit into settings.itemsPerPage.
This also relates to the plugin settings where limit is renamed into itemsPerPage to.
Drop ViewHelper
As of version 8.x the SortViewHelper is dropped because its never used.
13. March 2021
Replace pagination widget by pagination API
Usage of f:widget.paginate is replaced with paginator and pagination objects with usage of Paginator.html partials.
Routes configuration
Routes configuration files are moved from /Configuration/Yaml to /Configuration/Routes
03. May 2020
Cleanup of plugins
Due to a more restricted handling of resolving controllers and actions in links every plugin is reduced to it's main
data models. The following plugins are modified:
n consequence you need to check whether your pages are still displaying all informat
here are settings for the link generation authorPageId, bookPageId, categoryPageId,
educed flexibility. Have a look into the TypoScript constants editor.
leanup of flexforms
-------------------
he field settings.templatePath got removed with view.templateRootPaths.200. By this
emplates is necessary anymore. But the new field needs to be filled to get it workin
7. April 2017
=============
emove viewhelper
----------------
n favor of the core the widget viewhelper was dropped. Please replace 'sfb:widget.pa
nd check if configuration still works.
emplate behaviour
-----------------
nly valid template file type since version 4 are html files. Every other template fi
Updating
Add path_segment information
Since version 6.0 of sf_books the extension support route generation.
There in the tables author, books, categories and series got path_segment fields
added. These fields need to be filled for the url generation. To automatize this process
there are four upgrade wizards available, which can be executed in the
Admin Tools > Upgrade > Upgrade Wizard.
Testing
Sitemap
Reference to the headline
Copy and freely share the link
This link target has no permanent anchor assigned.The link below can be used, but is prone to change if the page gets moved.