sebibu

Any idea why editing blocks does not open up in a modal anymore for editors and superusers on both websites I'm using RPB? Seems like for the first milliseconds it opens a modal but then follows a normal pagerequest to the RockPageBuilderBlocks-site. I browsed my configuration, the docs the last days and editors do have the permission `page-edit-front`. I'm without further ideas..?

I agree with that. Thanks @Stefanowitschfor the first impressions. Looks great. I am looking forward to your whole showcase! Thanks also for showing the block-actions-setting-syntax! That would have been the next thing i would have asked, I didn't find that in the docs. Did I missed it or otherwise could you please add it, @bernhard? A search function on your site for the docs would be convenient and probably saves you a few questions.

Thanks for the in-depth knowledge to this, @bernhard! I used this before but tried to avoid it for security reasons. The background is.. At one time the block-actions were not visible, so I suspected it could be the noescape-filter. Yesterday I realized by chance, that block-actions are not visible when using the „hide topbar“-button in the RockFrontend Topbar. I don't find that logical. Can you please separate this two functions in two topbar-buttons?

Thanks for the valuable clarification, @bernhard! I'm still a newbie to PW and the API. One last question for today?: What could be the reason the RPB-content is outputted like this?? <section id="b1672" class="rpb-text" data-rpbblock=1672 alfred='{"icons":[{"icon":"edit","tooltip":"Edit Block #1672","href":"\/rs\/page\/edit\/?id=1672&language=1062","class":"pw-modal alfred-edit","suffix":"data-buttons=\"button.ui-button[type=submit]\" data-autoclose data-reload"},{"icon":"up","label":"","tooltip":"vSpace top default","type":"vspacetop","widget":1672},{"icon":"down","label":"","tooltip":"vSpace bottom default","type":"vspacebottom","widget":1672},{"icon":"clone","label":"","tooltip":"Clone Block #1672","href":"\/rs\/rockpagebuilder\/clone …

Okay, I had a board in front of my head.? <div class="uk-child-width-1-2@s" uk-grid> <div>{$block->rpb_left->render()}</div> <div>{$block->rpb_right->render()}</div> </div>

While testing I tried your version, too @bernhard but getting this.. Unknown Selector operator: '[empty]' -- was your selector value properly escaped? field='1672', value='', selector: '1672' in block #1671 (rockpagebuilderblock-twocolumns) This syntax works: ☺️ {$pages->get("$block->rpb_left")->text()} Looking forward to the insights @Stefanowitsch might have.? Any idea on how to output all possible blocktypes (like text, image,..) clever for both columns?

Thx for your quick answer, @bernhard! This is exactly what I tried ( My blocks name is only TwoColumns instead of layout.?), but unfortunately it's from the backend-side not that intuitive then in the CMS/screenshot above. However.. how can I get the content of the blocks inside a block with LATTE? I tried this but curly brackets in curly brackets are not allowed.? {$pages->get({$block->rpb_left})->text()} Thanks in advance!

@bernhard I love your Modules for the well structured and OOP-way with lots of possibilities for advanced users to hook in and extend functionalities. In RockPageBuilder I'm still missing a way to visual integrate two and more-columns layout simple and intuitive in blocks (not templates!) like this in MODX. Can I achive this in any way? Thx and greetings to Vienna?

Oh, that helps a lot! Thanks @AndZyk!!??

Thanks @bernhard! Yesterday I was asking myself if my client has been active in the new system as promised and tried to find and filter a managerlog like in my CMS I used before PW. Now I installed ProcessLoginHistory for the future, but the passed data isn't there. Having that functionality in the core from the installation on would make sense for this case, GDPR and system security in general.. in my opinion. Otherwise or maybe anyway I have to use PW-profiles or similar for my new projects to have the basic extensions and customizations directly at hand.

Indeed!??

Directly another question.? To save the editor the trouble of entering a dropdown field, I would like to determine the value of a dropdown field in the next (and probably only) pagetree-upper page having a template with template-id e.g. = 50. Is this also possible only with Latte or do I have to determine the value in PHP first?? Thx!?

Thanks to all three of you! Learned something new again. I'm on PHP8 and because the $page object should be existent on every page, this should be sufficient and works great: <body n:class="$page->category?->value"> ??

I am also already in love with Latte, but curiously enough can't find a solution to output a fieldvalue only if it exists. Ideally with short code and output class-tag only if the value exists. What I tried: <body n:class="$page->category->value !== '' ? $page->category->value"> // Unexpected end, expecting for element started on line 46 at column 5 (in '.../sections/header.latte' on line 120 at column 26) {if $page->category->value !== ''}{$page->category->value}{/if} or <body n:class="$page->category->value !== '' ? $page->category->value"> // 2 x PHP Warning: Attempt to read property "value" on null in .../Latte/templates-sections-header.latte--27db76d0dd.php:53 I'm sure it's so easy.? Can you help me out?

I just installed and played around with AdminStyleRock and AdminThemeBoss to be a little bit prepared. Good points! I agree with you. I think it makes sense to design all action related things (mostly buttons) with the same striking color. Normal mode and dark mode should IMO be separated from the color contrast topic. Normal mode bright and friendly. Dark mode to work more relaxed in the dark and to generate less ambient light. Just seen.. with AdminStyleRock the Offcanvas mobile menu looks as if it was not styled. Is that intentional? In any case, the colors are very contrasting. Looking forward to see in a few minutes! Sebastian

Okay, changing a template with same RPB-fields preserves content. But changing the template of a page to a template without the former RPB-field deletes the content. Even if you change the template back. Hope that helps for this topic, which is obviously and unfortunately not of interest for you.

? So let's go!? For editors who prefer to change content in the backend, editing content/blocks already in 2 or 3 columns is way more natural. Moreover, when selecting "2-column layout" then there are still 3 RPB-fields of which you are not allowed to use the last one, if I understand you right.?

I see it the same way. With the dropdown, two dimensions of the function (action and position) are accommodated together (it's easy to get lost), which can be separated and visually simplified. Action via cut/copy and paste icon. The paste position could be determined by selecting the paste icon before and after each block. This is intuitive for me and is also used by other pagebuilders. But that would mean that it must also be possible to insert new blocks above and below. Which I would very much welcome.?

Great the API is already there.? A cut and copy icon in the context menu in top right of every block would be intuitive, I think. And when having already cutted or copied a block a paste icon in the context menu in top right of every block. If you have a RPB field on template1 and template2 and you have to change the template while having content in the RPB field, the content should not get deleted. Also when having e.g. 1 and 2 column-templates and the editor wants to change the layout on a page from 2 to 1 columns and simply changes the template while having content in RPB fields, the content should not get deleted. If the RPB field on the old template is also in the new template, the content should be preserved (moved in the background/db), if the RPB field does not exists on the new template RPB should asking if/where to paste the content to.? I can now think of two more functions: Drag and drop blocks from on RPB field to another RPB field on the same page. Cut/copy fields in blocks from on page to another.?

Good Morning @bernhard, even though I'm not a trained designer, I'm interested in the topic and I can certainly contribute constructive criticism. And new to Processwire it's also good to get in touch with you and other enthusiasts via video call. If nothing comes up, I'd be there on Friday preferred between 2 - 3 pm (or else 11 - 12 am)! Sebastian

Good morning @bernhard, thx for creating RockPageBuilder! Now I finally have the first real project to work and playing around with it.☺️ If you don't already have this features on your roadmap, I would love to see them added: Cut/Copy and paste blocks between fields from type RockPageBuilder. Persist content (i.e. blocks) when changing the template of a page and asking where to paste content if there are fields missing in the new template (for example changing from 3 column-template to 2 column-template. I can imagine that this is not so easy to implement. In my opinion, however, the functions would be of great added value, especially for large websites with a lot of content. Cheers Sebastian

@kongondo I just switched for the last project from MODX to Processwire and for the next bigger project a media manager is crucial. Your screencast, the ideas and conversations look very promising and I would love to buy and use the new version already. But unfortunately no progress on this for a long time. Can you surprise us?? Can I test or buy the current/old version of the media manager? Your shop seems to be in maintenance mode for a long time, if I‘m not wrong!? Thanks in advance & Cheers Sebastian

That's a good point! Default elements <strong> and <em> are styled in my UIkit-frontend, so I didn't thought about that. In the JSON-file „wire/modules/Inputfield/InputfieldTinyMCE/defaults.json“ I can see that the CSS-classes for text-aligning of elements p,h1,h2,h3,h4,h5,h6,td,th,div,(table,)img,figure,audio,video is also defined via placeholder {alignleft}, {aligncenter}, {alignright} and {alignfull}, but I wasn't able to find the place were the values of these placeholders are defined so far.? I suspected in module-configuration of InputfieldTinyMCE, but that's not the case. Via „Default setting overrides JSON (text/file)“ it is certainly possible to overwrite the placeholders, but I am still struggling with the syntax.?

Thanks so much, @7Studio! This works. Now it makes sense, that I saw the placeholders {alignleft}, {aligncenter} and {alignright} in the JSON-file „wire/modules/Inputfield/InputfieldTinyMCE/defaults.json“. Thread-topic solved.? Yes, @AndZyks links are really helpful, but i still have to make friends with the syntax.? What are you trying to accomplish? Maybe me or someone more experienced can help.

@Boost I have the exact same need to see TinyMCE generating the uk-text-left class, instead the align_left one. I tried dozents of JSON-instructions in Default setting overrides JSON text, i.e. { "replace_alignleft": { "classes": "uk-align-left", "selector": "img" }, "replace_aligncenter": { "classes": "uk-align-center", "selector": "img" }, "replace_alignright": { "classes": "uk-align-right", "selector": "img" } } and changed the whitelist (.., img[class=uk-align-left|uk-align-right|uk-align-center], ..) to accept the new classes, but no effect. Did you get it done and if, can you please share your JSON???