EXT: objmgr¶

Table of Contents¶

EXT: objmgr 1

Introduction 1

What's new? 1

What does it do? 1

Screenshots 2

Installation 5

Reference Installation 5

Inserting data 8

Inserting data the new way 8

Inserting data the old way 12

Availability Check 14

The result of an availability check. 15

Configuration 15

Reference 16

Appendix 16

Known problems 16

To-Do 16

Supported by 16

Sponsored by 16

FAQ 16

Changelog 17

Introduction¶

Objmgr is an extension based on the extension flatmgr. It allows You to manage different booking objects like vehicles, boats etc. which are rent in a daily manner. Because the extension was derived from flatmgr 1.9.5 I start with version 1.0.0.

Installation¶

The extension objmgr depends on the extension rlmp_dateselectlib from Robert Lemke and on the extension xajax. Therefore it is necessary to install rlmp_dateselectlib and xajax too. Then just install the extension like other extensions from the typo3 extension repository TER. If you want use the TYPO3 history functions in the admin frontend of the objmgr see the “Reference Installation” in this manual.

Create a page where you want to use the plugin.

Create a page where only admins of the objmgr have access to.

Put the new content element on the desired webpage where you want to use the objmgr, 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”.

Create a new subpage in this page, name it for example Admin and put another objmgr-plugin to the adminpage.

Choose in the flexform configuration the displaytype adminpage and hide the page for normal users. Choose also the same starting point as in the normal objmgr page “Ferienwohnungen”.

You can also display an availability check which offers the user an input mask, where he insert his booking data and then check the available booking objects for this time period. If the check is positive, the available objects are shown with links to the booking calendars.

Important:

The layout is css-styled. So insert in the template of the page in “include static (from extension)” the object manager object objmgr.

Reference Installation¶

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 objmgr, 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 object manager object objmgr.

Put another objmgr-plugin into the “admin”-page. Choose in the flexform configuration the displaytype “admin”-page. Choose also the same starting point as in the normal objmgr 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 objmgr 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.

1. Log in the website with frontend login “fewo”.
2. Log in the website with your frontend login.

2. In the “Admin”-page you should see something like this.

3. Click the “CMS Login” button.
4. Now you should see something similarly like that.

5. Change for example the name of the object 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 objmgr booking data.

You can test it if you enable the warnings in the objmgr setup of the “Admin”-page. If all works correct no warning should appear when for example you change the name of a object and save it!

When all works, every change you made you can undo with the normal TYPO3 history functions.

Inserting data¶

There are two ways to insert data to the objmgr. One is done via the old fashioned way in the List-module. The other way is to add a page to the pagetree, name it for example adminflats and insert the plugin here again and choose in the flexform the display option adminpage. To protect this page from all users except the flatsadmins make this page only accessible for special frontend users.

If you plan to work with booking categories, go to the list module and select the page where you store the booking records and add some booking categories (for example “standard”, “family”, “group”...).

Availability Check¶

The availability check offers the possibility to check the booking objects local and external for vacancies in an given time period.

The configuration of the availability check is done via flexforms.

Activating XAJAX to prevent a full page refesh, when the results are shown.

The pageid (Seiten ID des Buchungskalenders) is the id of the page, where the normal objmgr-calendar is shown. This is needed to set the links accordingly.

If show the next vacant time period (zeige nächste Buchungsmöglichkeit) is set, then the next free period is shown if the booking object is not available for the desired time.

In the textarea foreign URL's “Externe URL's (mit ; getrennt)” you can insert URL to other typo3-sites with an installed objmgr and a page where an availabilitycheck is installed. Multiple URL's have to be separated with a semicolon “;”. This is very important! No spaces or newlines allowed.

If all is done correctly your availabiltycheck fetches the data from the desired websites which are set in the textarea and shows the result with the booking objects of this site.

Important: The remote sites to check to have to run objmgr-extension above version 1.6.0. Every availabilitycheck needs time to perform, therefore it is not recommended to check more than 5 external URL's.

Configuration¶

The configuration of the plugin is done with the flexform.

Here you can choose between monthsinglerow- , monthmultirows-, adminpage, availibility check- and efficiency-display. You can configure the calendars to show the shortcuts of the daynames, mark the weekends and show the overbooked legend.

Now choose the startingpoint where you stored the booking datasets of the flat(s).

Important: Choose one of the calendar display modes!

In case of the availability check you can insert the page-id where the normal view of the bookingcalendar is shown, so that the link to the bookingcalendar works correct. If no pageid is given, the actual pageid is used instead.

Reference¶

Options in the template SETUP:

If this options are set in the template setup, they overrule the flexform-settings.

plugin.tx_objmgr_pi1 :

Appendix¶

FAQ¶

• The availability check didn't work on foreign sites – Make sure that on both sites, local and foreign, the same Version of the objmgr ist installed.

• The availability check didn't work on multiple foreign sites – the URL's must be entered in flexform field without newline and use a “;” as separator

• I get a XML response error – there are illegal characters in the response (check the error message). You can either switch your TYPO3 to utf-8 encoding in the installtool and set the correct page.config.locale_all. I tested with utf-8 and iso8859-1. The extension works fine when TYPO3 is set to [BE][forceCharset] = utf-8.

• XML-response error in the availability check – make sure you have set the page.config.locale_all right in the TS page setup. XAJAX of the objmgr uses the page.config.locale_all to switch to the desired encoding. Here is an example of utf-8 setting.

  page {
  ...
  config.metaCharset = utf-8
  config.additionalHeaders = Content-Type:text/html;charset=utf-8
  config.locale_all = de_DE.utf8
  ....
  }
  

  For iso charset you can set

  page.config.locale_all = de_DE.ISO8859-15

• You get warning about an inactive backend user when trying to save a modified data record..

You have to be logged in the backend to get the history tables updated when you change a data record.

I use for this purpose the modified extension dkd_feuser_belogin.

The modifications are made in the file ext_tables.php of the the extension dkd_feuser_belogin.

"foreign_table" => "be_users",

//"foreign_table_where" => "AND be_users.pid=###SITEROOT### ORDER BY be_users.uid",

"foreign_table_where" => "AND be_users.pid=0 ORDER BY be_users.uid",

I also tried to use for the backend login the extension simulatebe. It seems that the backend user created by simulatbe is not instantiated correctly. So I can't manage to get the history tables work correct with simulatebe.

Changelog¶

2007-07-08, version 1.0.0, initial release

EXT: objmgr - 17