PHPackages                             libeo/pagerating - 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. libeo/pagerating

ActiveTypo3-cms-extension

libeo/pagerating
================

Page rating

v13.0.1(1mo ago)016↑87.5%GPL-2.0-or-laterPHP

Since Apr 8Pushed 1mo agoCompare

[ Source](https://github.com/libeo/lbo_pagerating)[ Packagist](https://packagist.org/packages/libeo/pagerating)[ RSS](/packages/libeo-pagerating/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (3)Dependencies (4)Versions (5)Used By (0)

Page Rating
===========

[](#page-rating)

This extension adds a plugin that shows a comment form about the page, asking if the page was useful, then showing a textarea for a comment. The form is sent by Ajax and a confirmation message is displayed.

The form content is saved in the database.

---

Configuration
-------------

[](#configuration)

1. Add the Site Set `libeo/pagerating` to your Site Package.
2. Define the `plugin.tx_lbopagerating.persistence.storagePid` constant with the page uid where the comments should be saved.

Add the plugin on a page
------------------------

[](#add-the-plugin-on-a-page)

1. On the Page Module, add a content via the `Create new content` button.
2. In the modal, select the `Page Rating` plugin.
3. Define the header (type `Hidden` is preferred).
4. In the `Configuration` tab, set the Title and Confirmation message to display. If none defined, the default will be used.

Add the plugin automatically in a template
------------------------------------------

[](#add-the-plugin-automatically-in-a-template)

The extension add a field named `Display page evaluation block` in the Behavior tab of pages. It can be used to trigger the display of the plugin automatically.

Here is an example of how to do this:

1. Add the plugin somewhere in your site (ex: in a folder with reusable contents)
2. Add a `lib` in your Site Package that look like that: ```
    lib.lbo_pagerating = CONTENT
    lib.lbo_pagerating {
      if.isTrue.field = lbo_pagerating
      table = tt_content
      select.uidInList = 123
      select.pidInList = 0
    }

    ```

    `123` is the uid of the content created a step 1.
3. In your Page Template, add a cObject View Helper: ```

    ```

    `page` is a variable available automatically in the template if a PAGEVIEW is used to render the pages.
4. The cObject `lib.lbo_pagerating` will be displayed if the field `Display page evaluation block` is active on the page.

Labels and translation
----------------------

[](#labels-and-translation)

You can use TypoScript to override the default Title and Confirmation message of the plugin.

```
plugin.tx_lbopagerating._LOCAL_LANG.default.form {
  title = How's your experience?
  saved = Your comments have been saved. Thanks!
}

```

See the `Resources/Private/Language/locallang.xlf` for all the labels.

Maximum comments length
-----------------------

[](#maximum-comments-length)

You can configure the comment maximum length by configuring the constant `plugin.tx_lbopagerating.commentsMaxChar`. The default is 500 characters.

```
plugin.tx_lbopagerating.commentsMaxChar = 750

```

###  Health Score

38

—

LowBetter than 85% of packages

Maintenance94

Actively maintained with recent releases

Popularity8

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity36

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

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

Every ~0 days

Total

4

Last Release

30d ago

Major Versions

v11.x-dev → v13.0.02026-04-09

### Community

Maintainers

![](https://www.gravatar.com/avatar/1dbdff9b4e9c8887797bedbff76a07ca26597c5eb069ac0631442ab3638a44ff?d=identicon)[libeo](/maintainers/libeo)

---

Top Contributors

[![asakurayoh](https://avatars.githubusercontent.com/u/327551?v=4)](https://github.com/asakurayoh "asakurayoh (5 commits)")

### Embed Badge

![Health badge](/badges/libeo-pagerating/health.svg)

```
[![Health](https://phpackages.com/badges/libeo-pagerating/health.svg)](https://phpackages.com/packages/libeo-pagerating)
```

###  Alternatives

[fluidtypo3/vhs

This is a collection of ViewHelpers for performing rendering tasks that are not natively provided by TYPO3's Fluid templating engine.

1954.1M48](/packages/fluidtypo3-vhs)[typo3/testing-framework

The TYPO3 testing framework provides base classes for unit, functional and acceptance testing.

675.0M775](/packages/typo3-testing-framework)[in2code/in2publish_core

Content publishing extension to connect stage and production server

40135.8k](/packages/in2code-in2publish-core)[pagemachine/typo3-formlog

Form log for TYPO3

23225.3k6](/packages/pagemachine-typo3-formlog)[eliashaeussler/typo3-warming

Warming - Warms up Frontend caches based on an XML sitemap. Cache warmup can be triggered via TYPO3 backend or using a console command. Supports multiple languages and custom crawler implementations.

20229.9k](/packages/eliashaeussler-typo3-warming)[eliashaeussler/typo3-form-consent

Extension for TYPO3 CMS that adds double opt-in functionality to EXT:form

1481.0k](/packages/eliashaeussler-typo3-form-consent)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)