Create a page where you want to use the plugin (“Ferienwohnungen”).
Create a page where only special website users have access to (“Admin”).
Put the new content element on the desired webpage where you want to use the flatmgr, in the picture above the page is called “Ferienwohnungen”. Choose in the flexform configuration the displaytype “display months in single row” or “display months in multi rows”.
The layout is css-styled. So insert in the template of the page in “include static (from extension)” the vacation flat manager object flatmgr.
Put another flatmgr-plugin into the “admin”-page. Choose in the flexform configuration the displaytype “admin”-page. Choose also the same starting point as in the normal flatmgr page “Ferienwohnungen”. Hide the page for normal users. This is done via the pagesetup – see 5.
Create a website group named “fewo admin” and a website user named “fewo” and assign the user “fewo” the group “fewo admin”. This can be done in the List module of TYPO3. Website users are stored in a storage folder. If you don't have one – create one. Select in the List module the storage folder and click on the icon of the storage folder and select “new”.
In the page setup of the “Admin”-page select the website group for accessing the “Admin”-page.
If you want to use the history functions of TYPO3 when changing the flatmgr data records, you need to be logged in the Backend. This can be done with an modified extension dkd_feuser_belogin (see FAQ in this manual). I also tested the simulatbe extension, but it seems that the backend user isn't instantiated correctly.
In the List module select the storage folder where your website users are and edit the user “fewo”.
Select a related backend user (which you created before with access rights to Ferienwohnungen) and save it.
Log out from TYPO3 and test it.
a) Log in the website with frontend login “fewo”.
b) Log in the website with your frontend login.
b) In the “Admin”-page you should see something like this.
c) Click the “CMS Login” button.
d) Now you should see something similarly like that.
e) Change for example the name of the flat and save it.
c) Now, if the backend user have enough rights the history tables are filled correctly after changes have been done to any flatmgr booking data.
You can test it if you enable the warnings in the flatmgr setup of the “Admin”-page. If all works correct no warning should appear when for example you change the name of a flat and save it!
When all works, every change you made you can undo with the normal TYPO3 history functions.
