bernhard

First of all thx for that and I'm happy to hear that ? It would be interesting to add things step by step and see when things start going wrong! Maybe you can share a test project so I can have a look. But I'd appreciate if you can find it yourself of course ??

@sz-ligatur I've tried, but I can't reproduce on an installation having RockFrontend + RockMigrations running.

Hi, that's an interesting one. Could you also check the value in different locations please. Eg in site/ready.php or in _main.php before anything else? Maybe that tells us something. Because I have no idea until now..

Thanks for educating me on how I should develop my free and open source modules ? I hope you don't mind that I went a different route and added a check if RockFrontend is installed or not. Everything works without RockFrontend now as of v.1.0.6 Thx for spotting and reporting that issue.

Hey @PWaddict thx for the report. I had a look and you just need to install RockFrontend to make it work. Not sure if we really need that dependency just for this single feature but as a quickfix that is what you can do ?

https://www.mailersend.com/ is also a good option and you can have a look at https://github.com/baumrock/RockMailerSend (no docs at the moment and not officially released yet)

Yeah it's a pity, but I still haven't found a good replacement for it ? tabulator.info has similar features but it's overkill for a simple tabular input..

Today I realised that one of my sites has around 13k rows in the caches db table (20MB in size): The site is powered by RockMigrations automatic deployment so the folder structure on the server looks like this: According to @adrian this issue has nothing to do with TracyDebugger, so I wonder if anybody of you has seen a similar problem before and can help me debug/fix this? Thx! PS: Is it maybe as easy as deleting all FileCompiler_ rows on each RockMigrations deployment? PPS: Seems like a possible solution, or does anybody see a problem with doing this on every deploy? PPPS: Ok found the other bad guy: ProcessJumplinks ? Before: 20MB Removed FileCompiler Cache: 10MB Removed Jumplinks Module: 3MB ?

Thx @zoeck https://github.com/nette/latte/issues/287#issuecomment-1377083605

Version 2.9.0 changes the syntax for repeater fields from this: $rm->createField("my_repeater", "repeater", [ 'label' => 'Test', 'repeaterFields' => [ 'title', ], 'fieldContexts' => [ 'title' => ['label' => 'foo'], ], ]); to that: $rm->createField("my_repeater", "repeater", [ 'label' => 'Test', 'fields' => [ 'title' => ['label' => 'foo'], ], ]); This might be a breaking change in your system so check before updating ?

Thx, that works! I'm working on my pagebuilder and have a mobile preview where the debug bar is a little disturbing I guess. But I might hide it via CSS so that it is still visible on desktop view, I'm not sure: Good to know how to disable the debug bar though - thx!

Yeah I understand that and I agree, but I was asking for benefits other than that? I thought there are maybe other benefits as well ? I'm always happy to hear that (1) anybody is using my modules at all and even better (2) if they are using it differently and (3) share their findings so that I can see other approaches ? I could use {include ...} instead of $rockfrontend->render(...), but the non-existing early exit is really a show-stopper for me. Do you have any other approach to that? I don't see a drawback with the panel (that's why I added it). It's just the missing renderIf() or early exit feature that I lose when using {include ...}. But using {include ...} is necessary to get a meaningful latte panel. I'm looking forward to hearing what you find out ?

@zoeck I wonder if it could make sense to make our own debug panel for RockFrontend that keeps track of all $rockfrontend->render() calls (and also renderIf)?! Is the latte debug panel helpful for you as is? I think for me it has more drawbacks than benefits. What are actually the benefits other than to get a list of rendered latte files?

Hey @zoeck thx! I've added it to the latest version ? Only thing to mention is that this: Will result in only showing "header.latte" in the bar: In order to make it work you need to render default.latte instead of default.php: Nice! The problem here is though that we are losing nice RockFrontend features like "renderIf(...)" and there is no early exit feature in latte at the moment ?

Hey @adrian I have this hook in place: $wire->addHookAfter("/foo", function () { return "foo"; }); And the page shows "foo" as expected. But it also shows the debug bar and I did not find an easy solution for disabling it... Is there (or could there be ? ) something like this: $wire->addHookAfter("/foo", function () { $this->wire->tracy->noBar = true; return "foo"; });

Hi @Java and welcome to the bright side ? I have the same background and switched in 2014 nd could not be happier with that decision (and couldn't thank @gebeer enough) ? I hope you enjoy it as much as I do ? It's kind of funny that people are still using joomla + seblod. It seems that things have not really changed since 2014... For me that was a terrible time - If I had a question and got stuck somewhere my only hope was the seblod forum. But you never knew when (or if at all) you got an answer. Usually it took two weeks and the answers where not even near as helpful as what I'm used to in the PW forum ? It also makes me smile when I read this: I can still remember that I've read that statement back then and I was a little afraid as ProcessWire really looked a little bit too simple for what I was looking for. I was so wrong ? ProcessWire is just really, really good at hiding complexity and making simple things simple but providing the power under the hood to help you build whatever you can think of. @Java so what is your experience of the seblod community at the moment? Is the project dead? Is there any progress? Are maybe more people there looking for an alternative? Mabe we could help them find ProcessWire ? PS: Hey google, can you please let people know, that ProcessWire is a great alternative to Joomla + Seblod in 2023?! ?

Hey @Juergen thx for sharing ? It looks like you have put a lot of work into that module so I'm a little afraid of asking ? And I hope you don't take me wrong: 1) How are you using your module? Who is it built for? Is it for building quick mockups that you show your clients? Or is it intended to show placeholders to real website users if clients don't upload images? 2) I wonder if an SVG based solution would be better (easier, more efficient)? You could easily create an SVG placeholder and write some custom text into it: https://www.mediaevent.de/tutorial/svg-text-alignment.html Not sure how that would work with different fonts, but I guess that works with webfonts?!

@kongondo do you know why or when that flag is applied to a field? I'm working on my pagebuilder that will save all field and template settings to YAML so you can use the GUI for everything ? I've edited a template, then created a new datetime field and added it to the template. The field has flag=0. Then I edit the field in the field editor and once I save it it has flag 32768 (flagSystemOverride). It does not seem to do any harm though. But I wonder if there's an issue? Not understanding what is going on is not the best in gerneral ?

Not exactly my strength but looks like a worthwhile addition to me ? This is off topic but would you mind explaining why you are trying to avoid SMTP and what your preferred alternative is? I just found it really cumbersome to setup all the time. And complicated to use. And a pain to switch between live and development. I'm just setting um my server correctly to get 10/10 on mail-tester using plain WireMail() without installing any additional libraries. Then sending an email ist just 5 lines of code away and it works well on DDEV (gets caught by mailcatcher) and once pushed to live it sends real emails without changing anything.

No, the idea is that RockFrontend is unobtrusive. That means you should be able to install it without any unwanted side effects happening. If you find anything that violates this concept let me know ? But if you update and check that box for "footerlinks" you'll be able to call $rockfrontend->footerlinks() in your template files ?

If you are using custom page classes since v206 there is the "getPageListLabel()" method: https://processwire.com/blog/posts/user-activity-v6/#core-updates

Thx, makes sense ? Didn't think of SMTP as I try to avoid it, but that's just a personal thing.

Note: This feature has been moved to RockSettings --------- Every site that I create needs some kind of links in the footer. It's not much work to create a page reference field for that, but it's not much fun as well ? That's why RockFrontend creates a "footerlinks" field and adds it to the home template for you: With the latest commit you can easily access those pages in your template file: <ul> <li n:foreach="$rockfrontend->footerlinks() as $link"> <a href="{$link->url}">{$link->title}</a> </li> </ul>

Would be curious why you prefer PHPMailer over WireMail?

Just pushed v1.1.0 - actually it is not a "color" picker any more ? // custom CSS + HTML example $event->object->setColors('site_bgcolor', [ // custom css 'custom' => [ 'background: rgb(34,0,255); background: linear-gradient(90deg, rgba(34,0,255,1) 0%, rgba(0,0,0,1) 100%);', 'Blue to black gradient' ], // custom html 'custom2' => [ '<div style="width:200px;"> custom html demo ? </div>', 'Custom HTML demo :)' ], ]);