Setup:
A Onepager, SPA
A few RPB fields like rockpagebuilder_events or rockpagebuilder_news ... with blocks assigned.
RPB 5.0.3 PW 3.0.229

In this setup I don't need the title field in my blocks, so I sett them all to 'hideTitle' => true
It worked.
Some time after that I noticed that when adding a new PW page with no RPB blocks, just a simple PW for imprint or privacy ploicy, only the name field shows up, no title field:

Even when creating a new template no default title is added.
After generating a name and saving the new page no error about the required title is thrown. The page will be created with an empty title! After that the title fie3ld is shown.

I commented out //hideTitle => true in a all blocks, but the problem remains.

I manually deleted all cached and compiled files and now I am puzzled with this.
No additional hooks or anything.
Where do I look? What to do? How do I go about this?

Could be connected to another problem I will post next.

My example is events and activities. Events can become active, tickets go on sale, be cancelled, end, etc. This is a block for "Featured Activities"

• Activities are selected by a person editing a page. They can choose as many activities as desired but only 3 are shown on the page
• If the date of an activity passes, or tickets are sold out, it is removed from the featured activities (automatically via hook)
• When one is removed another is rotated in (automatically via hook)
• If there are no more featured activities (all of the dates have past, or tickets are sold out) the block should no longer be output to the page.

These are featured on many pages across the site with a lot of automation and updating them manually would be a very terrible thing 🤣 I have a handful of blocks that do stuff like this.

The idea is a shouldRender() method for Block classes. By default it returns true but may be overridden to control whether a block will show up on the page.

<?php

  /**
   * Whether this block should be rendered. Called before a block is output to the page.
   * @return bool
   */
  public function shouldRender()
  {
    return true;
  }

I have something like this cobbled together already in my code but I have to add an if statement to all of the block views that need this. I also use it for things like image galleries that shouldn't render if the image field is empty. It would be really nice native feature 😎

I just upgraded RPB from v5.x to latest 6.6.0.

The custom thumbnails links are broken, even after a Modules Refresh. They have a wrong path .../modules/RockPageBuilder/...

That path doen't exist and should be .../modules/RockFields/buttons..., I guess.

Problem seems to be in RockFields/buttons/preview.php L5

After changing this to 

it is working

My attempt:

<?php

$settings->add([
    'name' => 'image_location_horizontal',
    'label' => 'Image Location',
    'value' => $field->input('image_location_horizontal', 'select', [
        '*right' => 'Right',
        'left' => 'Left',
        'center' => 'Center',
    ]),
]);

$settings->add([
    'name' => 'body_location_vertical',
    'label' => 'Body Location',
    'value' => $field->input('body_location_vertical', 'select', [
        '*above_feature' => 'Above Feature',
        'below_feature' => 'Below Feature',
    ]),
    'showIf' => 'image_location_horizontal=center',
]);

Tried searching to see if this has come up for anyone else but didn't see anything.

Error:

Call to a member function render() on string search►
RockDevTools LiveReload is active    

File: .../modules/RockPageBuilder/RockPageBuilder.module.php:1596

1586:      }
1587:    
1588:      /**
1589:       * Render content of blocks field
1590:       */
1591:      public function render($renderPlus = true)
1592:      {
1593:        $page = $this->wire->page;
1594:        $field = $page->getFormatted(self::field_blocks);
1595:        if (!$field) return;
1596:        $html = $field->render($renderPlus);
1597:        $rf = $this->wire->rockfrontend;
1598:        if ($rf) return $rf->html($html);
1599:        return $html;
1600:      }

In Latte-Template:

{if $modules->isInstalled('RockPageBuilder')}
<main sortable>
  {$rockpagebuilder->render(true)}
</main>
{else}

If I delete the Content-Element it works like expected.

translations, populated from Fluency (2.1.1), for the title- and text-fields are not getting saved anymore, when they are in a builder block (RPB 6.5.1). An exception is, when it is a TinyMCE field.

When I cut the translated string out and then paste back in (or typing it manual), then it gets also saved - what makes me question if that has maybe something to do with the changes in RPB 6.5 and 6.5.1. Also, when I choose the option to edit the field in a new window - as a "normal" ProcessWire page, then there also everything is working as expected.

On an old version for RPB (5.4.3) and Fluency (1.0.7), everything works normal.

Is there also, for future debugging, a way to "intercept" where the information of the field gets lost? The js-console of the browser seems not very helpful here. Everything looks normal, and the only feedback is the code 200 from the fluence request.

Edit the field in a new window - as a "normal" ProcessWire page:

------------- EDIT

With the actual Fluency 2.1.2 and RockPageBuilder 6.7, the problem seems to be fixed.

I have two RPB fields and I'd like to have all of the blocks that were created and located in the original RPB field available to the second field without replicating the block folders themselves.

Field 1 (original field): rockpagebuilder_blocks
Field 2 (additional field): rockpagebuilder_blocks_2

Thus far all of the blocks have been created in the original blocks field, I'd like the same blocks to be available to the second field. I created an empty folder for rockpagebuilder_blocks_2 as blocks_2.

I can't remember if this is possible or if there is a file I need to add to the folder, or rename blocks_2 to something else? I've tried renaming the folder to rockpagebuilder_blocks_2 but no dice. Does it require copying all of the blocks from one directory to another?

Thanks!

I created a new block type `Questions` through the GUI. All files and template `rockpagebuilderblock-questions` were created in that process.

When I deployed that to our staging server, the template for that block was not created.

So I had to add that template `rockpagebuilderblock-questions` to my RockMigrations to make the block work on staging. Is this normal behavior?

Is there an API method that I could use instead of the template migration? Couldn't find it in the docs.

Fields for that block are managed through the migrate method in site/RockPageBuilder/blocks/Questions.php. So the template migration is somewhat redundant. 

I added this mutation observer to InputfieldRockPageBuilder.js to watch for elements that have had the 'InputfieldStateChanged' class added.

// trigger changed event when InputfieldStateChanged is added to elements
$(document).on('ready', function () {
  const rpbItemsObserver = new MutationObserver(mutations => {
    mutations.forEach(mutation => {
      if (mutation.target.classList.contains('InputfieldStateChanged')) {
        RockPageBuilder.changed(mutation);
      }
    });
  });

  $('.rpb-items').each(function (_, rpbItem) {
    rpbItemsObserver.observe(rpbItem, {
      childList: true,
      subtree: true,
      attributes: true,
      attributeFilter: ['class']
    });
  });
});

In my testing this took care of some edge cases where changes aren't visible to RPB. Could be helpful for handling other sneaky inputs as well 👍

I got stuck. Changes that I apply to any RockPageBuilder Block only get stored in frontend editing.
Changes made in the Processwire Backend get ignored. Even as admin.

RockPageBuilder 5.2.0
ProcessWire 3.0.229

Any suggestions for me? I have no further idea.

Thanx a lot

I've been creating new block/widget buttons for the current project I'm working on and wanted to share them in case they may be useful to others. They're SVGs intended to complement the style of buttons that come with RockPageBuilder.

This post has been updated with a link to a Github repository containing all of the buttons currently available. New buttons have been added. Existing buttons have have been tweaked for quality and consistency.

Download from or fork the Builder Buttons Github repository

Rather than keep this post up to date with every button that is added, visit the Github repo to see the most current example and download/clone buttons for use in your projects.

Buttons include:

• Accordion
• Announcement
• Articles
• Audio
• Bios
• Call To Action
• Card Over Image
• Code/Embed
• Events
• Image
• Image Carousel
• Image Mosaic
• Image Roll
• List
• Lists
• Products
• Reviews
• Video
• Weather

Preview (not in order of list)

If you find them useful, let me know what you think!

I'm desperately trying to install RPB. PW 3.0.244 (), RPB 6.2.0 with php 8.2. I followed all instructions (https://www.baumrock.com/en/processwire/modules/rockpagebuilder/docs/setup/).

This is the frontend:

What the… Error: Exception: Method RockFrontend::styles does not exist or is not callable in this context (in wire/core/Wire.php line 563)

#0 wire/core/Wire.php (419): Wire->___callUnknown('styles', Array)
#1 wire/core/WireHooks.php (968): Wire->_callMethod('___callUnknown', Array)
#2 wire/core/Wire.php (484): WireHooks->runHooks(Object(RockFrontend), 'callUnknown', Array)
#3 wire/core/Wire.php (487): Wire->__call('callUnknown', Array)
#4 site/templates/_init.php (9): Wire->__call('styles', Array)
#5 wire/core/TemplateFile.php (314): require('/Users/neophron...')
#6 wire/core/Wire.php (413): TemplateFile->___render()
#7 wire/core/WireHooks.php (968): Wire->_callMethod('___render', Array)
#8 wire/core/Wire.php (484): WireHooks->runHooks(Object(TemplateFile), 'render', Array)
#9 wire/modules/PageRender.module (581): Wire->__call('render', Array)
#10 wire/core/Wire.php (416): PageRender->___renderPage(Object(HookEvent))
#11 wire/core/WireHooks.php (968): Wire->_callMethod('___renderPage', Array)
#12 wire/core/Wire.php (484): WireHooks->runHooks(Object(PageRender), 'renderPage', Array)
#13 wire/core/WireHooks.php (1094): Wire->__call('renderPage', Array)
#14 wire/core/Wire.php (484): WireHooks->runHooks(Object(HomePage), 'render', Array)
#15 wire/modules/Process/ProcessPageView.module (193): Wire->__call('render', Array)
#16 wire/modules/Process/ProcessPageView.module (114): ProcessPageView->renderPage(Object(HomePage), Object(PagesRequest))
#17 wire/core/Wire.php (416): ProcessPageView->___execute(true)
#18 wire/core/WireHooks.php (968): Wire->_callMethod('___execute', Array)
#19 wire/core/Wire.php (484): WireHooks->runHooks(Object(ProcessPageView), 'execute', Array)
#20 index.php (55): Wire->__call('execute', Array)
#21 {main}

This error message was shown because: you are logged in as a Superuser. Error has been logged.

I'm installing the Rockfrontend and Rockmigrations modules by »Add Module from directory«. Since the RPB zip file is too big for the »Add Module from upload«, I'm uploading it to the modules directory. Everything works fine in the backend.

I'm afraid, that I missed something, cause meanwhile there are differences in the installation video and the latest version. Like the field »rockpagebuilder_blocks« is already attached to the home.php.

Just ran into a conflict between RPB and other fields on the page. I'm using a custom inputfield that uses Quill as the editor. There's an event listener that is catching changes in an instance of a Quill input while the field is located outside of RPB blocks.

InputfieldRockPageBuilder.js  L327

// monitor inline ckeditor fields
$(document).on("blur keyup paste input", "[contenteditable]", function (e) {
  RockPageBuilder.changed(e);
});

Quill uses a contenteditable attribute for the editor so an instance of that field anywhere on the page is triggering a RPB field update event.

// monitor inline ckeditor fields
$(document).on("blur keyup paste input", ".rpb-item [contenteditable]", function (e) {
  RockPageBuilder.changed(e);
});

I scoped the event listener selector by adding .rpb-item and that kept it from firing when editing a Quill field, but I don't have any CKEditor fields to test whether that affects other fields.

"That fixed it for me, don't know if it breaks something for someone else." 😆

Get a taste of the future of web development by visiting the demo page at https://pagebuilder.baumrock.com/ and exploring the RockPageBuilder documentation at https://www.baumrock.com/en/processwire/modules/rockpagebuilder/docs/

Don't miss out on this exciting opportunity to elevate your web development game. Get ready to rock with RockPageBuilder! ??️

https://www.baumrock.com/rockpagebuilder/

Here is a quick demo video:

And here is how to install it from scratch in under 5 minutes:

Some showcase projects are already in the pipeline ? So be sure to subscribe to https://processwire.rocks/ or to https://www.baumrock.com/rock-monthly/

Have a great weekend!

----------

Sharing a strategy that I have found useful when working with blocks and block settings.

I use the block settings feature heavily and in many instances most blocks have some of the same settings fields. To help make managing these easier, I created a workflow to help me manage these and it's saved me a good amount of time while being able to reuse settings between projects very easily. In my case, some of these are:

• Spacing between blocks/sections on the page
• Background/accent colors
• Content location within blocks
• Block presentation

My approach is to create a dedicated class with static methods that return a settings array. Example:

<?php
// /site/init.php

/**
 *  This creates a namespace for a /site/templates/RockPageBuilderSupport directory
 */
wire('classLoader')->addNamespace('RockPageBuilderSupport', __DIR__ . '/templates/RockPageBuilderSupport');

This file contains the fast helper methods that create settings fields

<?php

// /site/templates/RockPgeBuilderSupport/BlockSettings.php

namespace RockPageBuilderSupport;

use ProcessWire\RockFieldsField;

/**
 * Reusable block settings
 */
class BlockSettings
{
    public static function sectionPresentation(
        RockFieldsField $field,
        array $config = [],
        array $additionalValues = [],
    ): array {
        $name = 'section_presentation';

        return [
            'name' => $name,
            'label' => 'Section Presentation',
            'value' => $field->input($name, 'select', [
                '*normal' => 'Normal',
                'standalone' => 'Standalone',
                'standalone_drop_shadow' => 'Standalone + Drop Shadow',
                ...$additionalValues,
            ]),
            ...$config,
        ];
    }

    public static function bodyWidth(
        RockFieldsField $field,
        array $config = [],
        array $additionalValues = [],
    ): array {
        $name = 'body_width';

        return [
            'name' => $name,
            'label' => 'Body Width',
            'value' => $field->input($name, 'select', [
                '*constrained' => 'Constrained',
                'full' => 'Full',
                ...$additionalValues,
            ]),
            ...$config,
        ];
    }

    public static function backgroundColor(
        RockFieldsField $field,
        array $config = [],
        array $additionalValues = [],
    ): array {
        $name = 'background_color';

        return [
            'name' => $name,
            'label' => 'Background Color',
            'value' => $field->input($name, 'select', [
                '*white' => 'White',
                'seafoam' => 'Seafoam',
                'champagne' => 'Champagne',
                'none' => 'None',
                ...$additionalValues,
            ]),
            ...$config,
        ];
    }

    // ...as many commonly used settings methods as you need
}

Settings are easily reusable in any block.

<?php

declare(strict_types=1);

namespace RockPageBuilderBlock;

use ProcessWire\RockFieldsField;
use RockPageBuilder\{Block, BlockSettingsArray};
use RockPageBuilderSupport\BlockSettings;

class BlogFeed extends Block {

    const prefix = "rpb_blogfeed_";

    /**
     * Block config info
     */
    public function info(): array
    {
        return [
            'title' => 'News Article Feed',
            'description' => 'An array of blog posts',
            // ...other info
        ];
    }

    /**
     * Runtime block settings
     */
    public function settingsTable(RockFieldsField $field): BlockSettingsArray
    {
        $settings = $this->getDefaultSettings($field);

        $settings->add(
            BlockSettings::bodyWidth($field)
        );

        $settings->add(
            BlockSettings::bodyLocationVertical($field)
        );

        $settings->add(
            BlockSettings::actionLocationVertical($field, config: [
                'label' => "Below 'view all' link"
            ])
        );

        $settings->add(
            BlockSettings::sectionPresentation($field, additionalValues: [
                'full' => 'Full news feed design',
            ])
        );

        return $settings;
    }

    // ... ommitted for brevity
}

This has helped me easily manage common settings for 20 different blocks by editing the settings in one place. By adding the $config and $additionalValues parameters to the BlockSettings methods, overrides can be added when individual blocks need customization. Thanks to the runtime nature of block settings, making these changes on the fly is extremely easy.

This has saved me a lot of time and helps keep things organized. I was able to carry over the bulk of my work with settings from one project to another and it really helped out a lot.

Would love to hear if others out there have developed some tips and tricks that help you build your sites!

so i wonder if there's a way to combine all these resources (as the minifiy option in rockfrondend) and to avoid the many roundups for each css or js-file and make them cachable as well:

  <link href='/site/templates/bundle/main.min.css?m=1737183638' rel='stylesheet'>
  <link href='/site/modules/RockFields/assets/RockPageBuilder.min.css?m=1728917624' rel='stylesheet'>
  <link href='/site/templates/RockPageBuilder/blocks/Accordion/Accordion.min.css?m=1731931045' rel='stylesheet'>
  <link href='/site/templates/RockPageBuilder/blocks/Accordion/Accordion.min.css?m=1731931045' rel='stylesheet'>
  <link href='/site/templates/RockPageBuilder/blocks/ArtikelMitBild/ArtikelMitBild.min.css?m=1731931045' rel='stylesheet'>
  <link href='/site/templates/RockPageBuilder/blocks/ArtikelMitBild/ArtikelMitBild.min.css?m=1731931045' rel='stylesheet'>
  <link href='/site/templates/RockPageBuilder/blocks/Hero/Hero.min.css?m=1731931045' rel='stylesheet'>
  <link href='/site/templates/RockPageBuilder/blocks/Hero/Hero.min.css?m=1731931045' rel='stylesheet'>
  <link href='/site/templates/RockPageBuilder/blocks/Text/Text.min.css?m=1731931045' rel='stylesheet'>
  <link href='/site/templates/RockPageBuilder/blocks/Text/Text.min.css?m=1731931045' rel='stylesheet'>
  <link href='/site/templates/styles/admin.min.css?m=1731931045' rel='stylesheet'>
  <link href='/site/templates/styles/admin.min.css?m=1731931045' rel='stylesheet'>
  <link href='/site/templates/styles/main.min.css?m=1732860349' rel='stylesheet'>
  <link href='/site/templates/styles/main.min.css?m=1732860349' rel='stylesheet'>
  <link href='/site/templates/less/_global.min.css?m=1732859882' rel='stylesheet'>
  <link href='/site/templates/less/_global.min.css?m=1732859882' rel='stylesheet'>
  <link href='/site/templates/webfonts/webfonts.min.css?m=1731931045' rel='stylesheet'>
  <script src='/site/templates/uikit/dist/js/uikit.min.js?m=1727317894'></script>
  <script src='/site/templates/uikit/dist/js/uikit-icons.min.js?m=1727317894'></script>
  <script src='/site/templates/scripts/main.min.js?m=1731931045' defer></script>

best

karsten

Now I wondered why my Headlines lost their multilanguage settings and saw that log:

Fields: Deleted field "title" data in 0 row(s) from 0 page(s) using template "rockpagebuilderblock-logos". [page-by-page] +2

I'm not sure how that template does that and where?

Where I was stuck currently is how the get the blocks working with multilingual fields.

For example I simply wanted to have the /RockPageBuilder/blocks/Text example block to show the TinyMCE Inline field as Multilanguage Textarea.

// from RockPageBuilder/blocks/Text/Text.php..
public function migrate()
  {
    $rm = $this->rockmigrations();
    $rm->migrate([
      'fields' => [
        self::field_text => [
          'type' => 'textarea',
          'inputfieldClass' => 'InputfieldTinyMCE',
          'contentType' => FieldtypeTextarea::contentTypeHTML,
          'label' => 'Text',
          'rows' => 5,
          'icon' => 'align-left',
          'inlineMode' => true,
          // 'rpb-nolabel' => true, // hide label in backend
          'settingsFile' => '/site/modules/RockMigrations/TinyMCE/text.json',
          'textformatters' => [
            'TextformatterRockFrontend',
          ],
        ],
      ],
      'templates' => [
        $this->getTplName() => [
          'fields' => [
            RockPageBuilder::field_eyebrow,
            'title' => [
              'label' => 'Headline',
              'icon' => 'header',
            ],
            self::field_text,
          ],
        ],
      ],
    ]);
  }

in the Accordion example block is the easy solution:

'type' => $this->wire->languages ? 'textareaLanguage' : 'textarea',

Maybe this should be in every example block and in the vs code snippets, cause that would've saved me some time.

I removed all of my block markup but still getting the error.

It looks like the {alfred($block)} call is inserting JSON into the element

I feel like there's something I'm missing but can't figure out what would be causing it and not sure where to start looking.

Anybody interested in more details or is that something nobody needs? How did/do you solve that?

Php 8.1.29
MySQL: 5.4.44
SQL Port: 3306

Ever tried this? Seems to have lost my progression 😞

Dangit… Fatal Error: Trait "RockMigrations\MagicPage" not found (line 11 of site/classes/HomePage.php)

I have a block that contains a Custom Field. That custom field contains a Page Reference field (single), Page Reference field (multiple), and a number input. When I create several blocks containing this field the values become unmanageable. They all appear in all blocks and can't be ordered in any of them.

I have several of these blocks and each should have only 3 or 4, but they are all rendered with all of them.

I did do some digging and found that the custom fields are not prefixed as a repeater field in the request data when saving the page, so each of these Page Reference field with multiple pages selected are all returned as a single variable array.
 

I've attached a txt file with the POST request parameters and it shows the following variable repeated without a repeater suffix:

event_activities_select_activities[]

Which may need to be handled as something like:

event_activities_select_activities_repeater5783[]

This is just a guess... I could be off on that, but the only constant that I could see in the issues when rendering is that every block has the same event_activities_select_activities variable without a way for it to be processed individually by block.

That's what I could pull together while experimenting.

Something that's fixable? I have to determine if I need to rewrite the blocks to use different fields 😵‍💫

rpb_blocks_custom_fields_request.txt

I'm struggeling to view the TinyMCE menu en toolbar in the different rpb blocks (in backend and frontend)

• PW 3.0.242 en rpb 5.9.1
• TineMCE 6.1.8
• Front-end-page-editor (Core)

In rpb_text_text: 

in rpb_accordion_item_content 

d  

and so on

Hopefully someone can point out what I'm missing here?  I suspect (as usual) it will be something minor.

And know what to do?