PHPackages ribase/ribaseforms - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. ribase/ribaseforms ActiveTypo3-cms-extension[Utility & Helpers](/categories/utility) ribase/ribaseforms ================== todo 2.0.0(8y ago)0337GPL-2.0+HTMLPHP >=5.5.0 Since Jul 5Pushed 8y ago1 watchersCompare [ Source](https://github.com/ribase/ribaseForms)[ Packagist](https://packagist.org/packages/ribase/ribaseforms)[ RSS](/packages/ribase-ribaseforms/feed)WikiDiscussions master Synced 2w ago READMEChangelogDependencies (1)Versions (2)Used By (0) \#Ribase Forms \##The death of Formhandler At this point we got a big problem because Formhandler was not fully usable and with TYPO3 7.6.5 it was impossible to use. (They changed the flexform handling) So at this point we got two options left, settle to powermail or build something own. \##Building this extension At this point of "we have to decide now" i started to develop a simple formextension with fluid. The first release is more or less nothing where you can customize your inputs, they came directly from ready build up fluidtemplates. But as time goes on a while there were more needs to cover up with this extension so the decision was to implement a backend to build up custom forms. In the next section you will get a kickstart to use it in a simple way. \#Quickstart \##Composer install ``` $ composer require ribase/ribaseforms:2.* && composer update ``` Please note that minimum Version should be 2.\* \##Manual install No Support! \##Activate in TYPO3 ####With TYPO3 console ``` $ cd to/your/webroot ; ./typo3cms extension:activate ribase_forms ``` \####Without TYPO3 console ``` $ cd to/your/webroot ; ./typo3/cli_dispatch.phpsh extbase extension:install ribase_forms ``` \####In Extension Manager No Support! \##Plugin usage 1. Add new CE (content element) 2. Go to Plugins 3. Choose "Ribase Form Display" \###Create input elements ####Input Textfield As you can see below there is an Input Textfield [![alt text](https://raw.githubusercontent.com/ribase/RibaseForms/master/docs/img/textfield.png "Textfield")](https://raw.githubusercontent.com/ribase/RibaseForms/master/docs/img/textfield.png) FieldDescriptionNameThe name is used for an identification of this field later in mailtext [placeholders](#placeholders).LabelA label for the frontend displayPlaceholderSets a placeholder to the fieldInputtypeIn some cases you need something else than a "text", maybe for a telephone input you can use a tel field or for an email field you can use an email type.RequiredMakes the field required\####Input Textarea As you can see below there is an Input Textarea. [![alt text](https://raw.githubusercontent.com/ribase/RibaseForms/master/docs/img/textarea.png "Textarea")](https://raw.githubusercontent.com/ribase/RibaseForms/master/docs/img/textarea.png) FieldDescriptionNameThe name is used for an identification of this field later in mailtext [placeholders](#placeholders).LabelA label for the frontend displayPlaceholderSets a placeholder to the fieldRequiredMakes the field required\####Radiobutton As you can see below there is an Input Textfield [![alt text](https://raw.githubusercontent.com/ribase/RibaseForms/master/docs/img/radiobutton.png "Radiobutton")](https://raw.githubusercontent.com/ribase/RibaseForms/master/docs/img/radiobutton.png) FieldDescriptionNameWith radiobuttons we got a little special behaviour. In first the name is used for grouping the radiobuttons. The other usage is - if you read carefully - for placeholders in mailtexts later. [placeholders](#placeholders).LabelA label for the frontend displayRequiredMakes the field required\#Advanced usage @todo \#Placeholder usage in replymails ##How do they work? \#Credits [Sebastian Thadewald](https://github.com/ribase) \#Issues? [Click here to drop an issue!](https://github.com/ribase/RibaseForms/issues) \#Donate If you like it, donate! But not to me, donate it TYPO3, without extension wont exist! [Donate TYPO3](https://typo3.org/donate/online-donation/) ### Health Score 27 — LowBetter than 47% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity12 Limited adoption so far Community4 Small or concentrated contributor base Maturity58 Maturing project, gaining track record How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 3283d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/9ccaeb709372a88c8f9d1684ce30638f2d2eb185daa069456fa409804b3aefa3?d=identicon)[ribase](/maintainers/ribase) --- Tags TYPO3 CMSribaseforms ### Embed Badge ![Health badge](/badges/ribase-ribaseforms/health.svg) ``` [![Health](https://phpackages.com/badges/ribase-ribaseforms/health.svg)](https://phpackages.com/packages/ribase-ribaseforms) ``` ### Alternatives [ichhabrecht/content-defender Define allowed or denied content element types in your backend layouts 903.1M24](/packages/ichhabrecht-content-defender)[yoast-seo-for-typo3/yoast_seo Yoast SEO for TYPO3 511.7M9](/packages/yoast-seo-for-typo3-yoast-seo)[derhansen/sf_event_mgt Event management and registration - Configurable event management and registration extension based on ExtBase and Fluid 65329.4k9](/packages/derhansen-sf-event-mgt)[lochmueller/calendarize Create a structure for timely controlled tables (e.g. events) and one plugin for the different output of calendar views (list, detail, month, year, day, week...). The extension is shipped with one default event table, but you can also 'calendarize' your own table/model. It is completely independent and configurable! Use your own models as event items in this calender. Development on https://github.com/lochmueller/calendarize 77166.2k13](/packages/lochmueller-calendarize)[brotkrueml/schema Embedding schema.org vocabulary - API and view helpers for schema.org markup 34653.7k14](/packages/brotkrueml-schema)[gridelementsteam/gridelements Be part of the future of TYPO3! Support Gridelements now and unlock exclusive early access to Version 13! The well-established Gridelements Version 12 elevates TYPO3 by bringing grid-based layouts to content elements, with powerful features like advanced drag & drop and real references. Supercharge your backend workflow and make daily tasks easier. Join us in creating the next exciting version: https://coders.care/for/crowdfunding/gridelements 162.4M27](/packages/gridelementsteam-gridelements) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)