Ivan Gretsky

Can it be ProcessWire could be listed there? Do we have anything to contribute?

Sorry for resurrecting this topic. But I think my question is related yet (not exactly the same). If I clone a page, set new title and save it under the target parent, that already has a page with a same name as generated from that title, the name doesn't receive an increment. But it rather is set to the name of the default page, that was cloned, with an increment. Let me explain on example: I've got page with a name template under Templates parent page. Then I clone it, set it's name to an empty string, set some title (e.g. example) and save under another page Destination. The cloned page under Destination gets name example. Then I clone another page from template, set it the same title (example), and save it under Destination. I am hoping to see it receive a name example-2, but it is saved as template-2 instead. I guess that is happening because when I clone a page it runs that setupNew method before I assign a title to it. The question is: is there a way to use the same in-built logic for handling duplicate names when cloning pages?

Whoa! I was getting a screen like this so often I thought it is like it should be) Right now I've got a FormBuilderProcessor::formSubmitSuccess hook in ready.php. Inside it i call $this instead of the variable name. And get this behavior. But as I said I was getting it soo many times before... Next time I'll notice it I'll report back again.

Good day! I need to show more than 15 items in the call stack. There must be a setting for this, but I can't find it) I need to see what's there between 14 and 37))

A great thing to have on a to-do list))

Most of us have been through this. You start not knowing anything and do most of things by trial and error. But at the end you come out stronger and more knowledgeable. I do not think there is a shortcut here. To learn something is to find yourself in the place of ignorance first. You should solve your tasks one by one, searching the forum, reading the code, asking the community if you get stuck. I do not think anyone is "too beginner". But everyone has to start from where he is at. There are a lot of docs, great forum posts and other resources spread around. but there is probably not a single tutorial to complete and become a ProcessWire master. Take you time, be patient, have fun along the way)) P.S. And just to address you specific questions a bit, I would recommend you this link... and many more here - just search for "create form")))

That is just awesome! Why did I never seen it in the docs? Is it even there?

Any would do for me) But maybe a border from one side could be enough? Top or left. Another option would be a warning sign icon to the left of the TRACY label with a popup, describing why it is here (kind of like Server Type Indicator).

Thanks for making this video @Jonathan Lahijani! There is a lot to study from it. Let me ask one question right away. How did you changed the block colors? Is that already build in like Ryan said it would, or is it with custom css for now?

Thanks, @adrian and @teppo! This is great way to handle it, as we can override this setting in config-dev.php. By the way, where can we find all the config options available for Tracy? It could be beneficial to have some kind of color indication for this in Tracy bar, so we won't forget to change the setting if we're on prod. Something like a color flag. What do you think?

Welcome to the forums, @Shohan Arafat! If you want it in admin it must be a custom process module. You can learn how to make one here (for example). But I am not sure I really understood your needs. This is your 1st post, and it might be you meant something very different. Please explain your needs better if my link above is too much or completely irrelevant.

By the way, @bernhard, could you please provide an example)

Hey, @teppo! I am back at this great module. Trying to make everything work as it should. I've read your conversation with @bernhard a number of times and think that a lot of issues discussed should make their way into the docs somehow. And answering the question quoted above (about the usage of custom page classes and controllers in Wireframe) would make another great page for Patterns and practices . The great docs are one of the main things that make Wireframe so attractive, as we can easily point to them when working in a team or passing a project to someone else. So keeping them up to date and adding more info is definitely as important (for someone who didn't write the framework in the 1st place))) as adding new features. I would participate in this process if there was a way to. At least I would fix some typos. But as cool as PW backend is it is not as good for open documentation. Is there a chance we can move the content creation to github and populate/update pages in PW via a script? I think someone already done this before...

Here is the way htmx recommends to deal with it. I was thinking, maybe it would be possible to deal with it by emitting document ready on each htmx.onLoad. But that would probably run lots of things that shouldn't run)

There are a few ready-made ways to have composable components in PW: https://processwire.com/api/ref/wire-file-tools/render/ (native built-in) https://wireframe-framework.com/docs/view/components/ https://processwire.com/modules/twack/ https://github.com/wanze/TemplateEngineFactory/blob/master/DOCUMENTATION.md#controllers But they are probably not exactly the same thing as in NuxtJS as this is PHP.

And, by the way, polling should be ok too, if SSE will turn out to be too hard)) I guess this way live preview can be implemented really fast.

Just to make it clear. htmx has SSE client built in, but the SSE server part is still to be implemented. @netcarversuggested ReactPHP for that purpose. There are other options to choose from. Or we could invent our own) I didn't quite grasp the "/path/to/page/?change=body" thing. Who is to request that? When doing the SSE thing we send something to the preview without it requesting anything. So it is the SSE server function to generate partial markup depending on the changed fields and pass it to the view. And htmx can handle not the full markup, but parts of it and swap just the piece it receives (with something like this). But it is a on step ahead - we need to have it working with full page swap first? as @ryan said.

This thing looks like an ideal new admin action)

Thanks, @ryan! This year's end seems to be even more interesting than its beginning) If that is required for the live preview it should be in the core, IMHO) If I understand it right, the core of what we need to build is something listening to a page save event and refreshing the preview page when it happens. Now we have an autosave to generate the events. The other part is reacting to that autosave. I can see 2 ways of doing that: ajax polling and sse (we probably do not need WebSockets as the preview doesn't need to send anything to the server... yet?). The latter (sse) seems to be a better fit, as it should use less server resources, but might be harder to implement (maybe not). Anyway, htmx supports sse (and even ws to an extent), which makes it a better fit than unpoly that doesn't (at least it didn't not so long ago when I checked). Actually, we could go without htmx, just taking inspiration from the principle it is based on. Though taking the ready-made library could be easier. The other part where htmx (or unpoly, or turbo or...) could help, is refreshing not the whole preview page, but only a part of it. Regenerating the whole page markup could be a long process (those 2 seconds in the OP are way too optimistic for many of the sites I have seen). For example, we could regenerate only one PM block markup and sent it to the preview for htmx to swap. But that would require either some standardization of the frontend or some hookable architecture for a developer to implement. The former would break the core PW principle of leaving frontent to the developer. The latter should be possible and would work nicely when rendering RM based content builders the standard way or with a Wireframe. Unpoly is complete framework, which could be used to upgrade PW admin as a whole, but would probably require to do everything its way. For a one place thing or for a more-work-more-customization htmx is a better suit, as it is lower level, as both of you @Craigand @kongondoagreed. If we bring in unpoly, we need to be ready to slowly redo all the admin area with it (which might be a nice thing in the long term). But for one task htmx is lighter solution. And we could even go without it only getting inspiration from it.

Love to see those PW related tutorials appear in YouTube search results) Great one, @Jonathan Lahijani! It seems you are using PHP 8 and MySQL 8 for development. Are you using those in production too? I was waiting for something to make a move to PHP 8, but the forum says it is too early. What is you experience?

Love this! If you stay up late enough on Friday night (it is almost midnight here), wonders will happen!

I just re-read the previous post. It is what i did ask for not knowing we already have it) Could you please consider also allowing to put color code in that item headers string, so we can also define a per-type color? That would make different types really stand out)

Super cool! Just amazing) This is what we, the Repeater Matrix lovers are waiting))) Are those type icons already present in the new version, or are you saving them for now?

I do not think they are mutually exclusive. And htmx is adding only 11kb True. Another way to deal with this could be using front-end editing. So RM blocks would get a border on hover with an edit button somewhere. All the configs could go in the popup with the repeater item fields showing on click. This could be probably done with htmx even without changing the Repeater Matrix core. But this is also not a solution for everyone, as it is not in admin. Meanwhile @Robin S recently released a module that changes the RM UI kind of in the ACF Extended direction. It adds colors to the RM types chrome (that is only part of this module's functionality). If we could change the items chrome in some easy way out of the box (like adding color + icons + per type labels) that would already bring us forward a lot. Just a possible 1st step))

I think I remember @ryandid write about implementing something like ProDrafts' live preview in the core everywhere, so we can change a page in one part of the screen and see it dynamically update in the other. I think this might be another way of doing UI for this, maybe even a better one (or complimentary to the one mentioned before), as we can see the changes not in some pseudo-markup, but in a real one. And do not have to create this pseudo-markup and styling in the 1st place. By the way, I can see how htmx can help here too.