szabesz

I was also thinking of mentioning it, however, Unipoly seems to implement a lot "more features" and its more advanced, soon to be released new version can be expected in weeks: http://triskweline.de/unpoly2-slides/#1 Note, that while these libraries are similar, but they are far from being the "same". Unipoly is opinionated while HTMX "is not" (at least not that much...), which is a big difference. However, Unipoly offers a lot more out of the box, so I'm myself thinking of using Unipoly v2 in the future. Unipoly v2 also – optionally – supports Bootstrap which is good for even more rapid development. I'm not a big fun of Bootstrap, but Bootstrap 5 and Unipoly 2 looks like a good combo, so I will definitely find some time to test them together in the near future.

Is it in the requests repo yet? If not, if you add it I'm happy to give it a thumbs-up ? From now on, GitHub thumbs-ups are the way to go: Ryan says: "Please use the thumbs-up votes on GitHub for issue reports and feature requests that you value the most, and going forward, that will help us to cover them in a useful order." I guess it also means we should not use the heart or any other positive looking reaction as GitHub seems to be able to sort on one reaction only, that is why it is only useful to stick to thumbs-up.

Interesting approach. It deserves further investigation, I think. If I understand it correctly, you propose another set of children – separated from the current set – which is used for layout only perhaps? Reading other's comments, I think most of us do not ask for a "Gutemberg only like" feature, instead, most of us need a way to implement a builder which is similar to the current repeater(matrix) based solutions others have presented in the forum, but geared towards layout + building. Editor.js could simply be another fieldtype, just an alternative to CKEditor. You and/or your client could decide which one to build upon your "RTE editing needs".

We sort of have this already - take a look at the Custom Links section of the settings for the Processwire Info panel. You can add links to any page on the site, including items under Admin > Setup. Of course this doesn't allow for external links. For external links, I could add an additional settings field for storing these, or we could go with a separate Shortcuts Panel. Semantically it would be strange having external links under the PW Info panel, but maybe that's OK? Any thoughts? I use the Custom PHP code panel for such a thing ? eg.: return ' <a href="/admin/module/edit?name=ProcessPageAdd&collapse_info=1" target="_blank">Disable automatic publishing conf</a><br> <a href="/admin/module/edit?name=ProcessPageEditImageSelect&collapse_info=1" target="_blank">Image handling conf</a><br> <a href="/admin/module/edit?name=ProcessPageEditLink&collapse_info=1" target="_blank">Link generation of InputFields conf</a><br> <a href="/admin/module/edit?name=FieldtypePage&collapse_info=1" target="_blank">Orphaned page references check</a> ';

How did you fix the "paragraph turning into a header" issue? I cannot seem to spot it in the screencast. BTW, such an issue is a prime example when a non-tech-savvy editor gets stuck.

Another, somewhat similar story: https://medium.com/vimeo-engineering-blog/its-not-legacy-code-it-s-php-1f0ee0462580

I do not want to pollute this thread with my silly issues with Tampermonkey. Enough to say, I got stuck again.... I will read its docs and watch its tutos when I have time to do so. Certianly looks powerful...

Thanks, I do not know why I overlooked it. It is a relatively recent feature? I have not installed new extensions for a long time, so I did not bother looking for things like these... And Firefox has been my main browser for development for quite a while as I prefer its dev tools over Chrome's.

I installed Tampermonkey but its icon does not show up so I cannot use it. I also googled a bit for some info on why it does not show up but could not find any useful guidance.

This is probably because the module's defaults are mainly your preferences ? which is quite OK, but I do venture further. Sure, I do not change to much either but my "favorite" options are scattered "all over the place". I was not clear when mentioning AOS, sorry. I like his column layout and the blocks in it – except for that the jump-links themselves are cogwheels which is a bit strange – as opposed to a simple list. Hiding the sections is unnecessary. Back to Tracy's settings: I like the fact that all the settings are on one long page, I just wish for some well organized jump-links section, and maybe a quick search filter with suggestions built in (something more advanced than the bowser's built-in page content search).

Drag and drop is only easy as long as the target is in the visible viewport. As soon as one needs to scroll while dragging, it becomes a really challenging thing to do, even in native applications running in modern operating systems, not to mention JavaScript based GUI apps. Providing both means of reordering should be the "solution", if possible. At first sight, my clients think they can deal with it as it does look familiar indeed. However, it has rather quirky behaviors when adding/removing list items, adding/removing line-breaks, and last but not least the horrid feature of injecting styles when pasting (which can be partially dealt with but never properly). So in the end my clients are always confused by the quirky way of using CKEditor. And we should go beyond the basics, so currently personally I prefer Berhard's approach, simply beause it looks like that it is a more realistic project in the long run.

+1 Maybe @tpr's solution in AOS can be implemented? I like his "jump links section" a lot.

I guess you meant "copied over to" instead of "uploaded to", correct? Anyway, I like this idea. If there was a central and configurable image browser (the image sources could be defined by the developer), so that admin users can re-use images by copying over images of a page to another page than that would help. Such a feature has its cons of duplicating the image, but on the positive side there would be no need to manage dependencies.

Thanks for the great write-up, Ivan! Good point! We totally forgot about our long standing portability shortcomings. The current "manual" import/export feature of fields and templates is a basic one, I rarely use it for this reason. Maybe Ryan should start this builder project by designing and implementing our sought-after migrating subsystem, which would also be the bases of portable builder components (components which can be managed by version control). See: https://processwire.com/talk/topic/21212-rockmigrations-easy-migrations-from-devstaging-to-live-server/?do=findComment&comment=183572

@arjen forked it because, quote: "We needed an option to determine whether 0 or empty should be regarded as equivalent. I copied the method + config from FieldTypeFloat. In my testing it seems to work fine." Others wanted to convert Float fields to Decimal but I guess your "combo" solution would solve that out of the box. Last but not least there was interest in "number spinner" which would be nice to have for all number fields, provided that the "values of increments" are configurable. BTW, I forgot about all this,but @apeisa joined in the discussion at some point, quote: "As a @sforsman's coworker I'll let him know about this. We do use namespaced version of this module ourselves." So maybe you and Apeisa could also discuss what their current extra needs are, if any.

I think most of us are thinking along this line in addition to more complex "custom components" as what we love ProcessWire for (among other things...) is that we devs can decide on the final output, and not the system is the one to dictate that in any way. However, ProcessWire could help us by providing a "builder" which renders semantic HTML which is in turn somehow also customizable by the developer. In other words: we need a layout tool so that our own "custom" components can be managed like LEGO blocks, either by us or by our clients. Allowing clients to customize styling could be "just" an additional feature but I would not venture too far in this area, as most of the time it is not a good I idea to let clients style anything (there are surely exceptions to this, of course, but still...).

I agree that something like the YOOtheme Pro Builder would be the way to go. Maybe the next admin theme could be implemented form scratch, along with ProcessWire's frontend content builder, based on something like Alpine.js perhaps? See: https://www.youtube.com/watch?v=M3fY0E60cM0 Some sort of reactive JS library is surely needed for such a builder, especially if more that one person start working on its implementation. However, the issue is that locking the admin and the builder to the future of a JS framework is problematic, to say the least.

That would be awesome. The one who developed that module has been away for more that two years. @arjen stated that he is happy to maintain his fork but it is not an ideal situation that I always have to point people to Arjens's fork instead of the no longer maintained module in the Directory. Anyway, it is a common need and as far as I know the core concept is that ProcessWire should support features most of us need. I think this is such a thing, based on the popularity of my request: https://github.com/processwire/processwire-requests/issues/126 where there is already a discussion in which others explain why they think it should be part of ProcessWire.

At least the most popular requests should be reconsidered I think, such as: https://github.com/processwire/processwire-requests/issues/126 It is hard to build ecommecre solution without adequate precisions of numbers. In countries like Hungary, a price of 1000000.00+ is quite common. The limit of 9999.99 is _always_ an issue.

A BIG +1 from me ?

Thanks for the explanation, now it all makes sense to me ?

@Robin S I cannot figure out how to style the preview. Have you already done that? Looks like the option named "previewClass" should be used somehow but I do not get what exactly this means: "previewClass: A string or array of strings that will be applied to the preview screen when activated. Defaults to "editor-preview". Also, the example provided does not help much either: previewClass: "my-custom-styling", previewClass: ["my-custom-styling", "more-custom-styling"], my-custom-styling it says, but where is it defined and how?

You might want to add that using the Markdown/Parsedown Extra textformatter is needed as well. It might be obvious to some, but first time I tried without it ?

This is great! Finally it is easily possible to ditch CKEditor. Thank you so much Robin!

Hello, Ryan mentioned that he had updated CKEditor , see https://processwire.com/blog/posts/pw-3.0.155/#updated-ckeditor-version-to-4.14.0 I would try a hard refresh / complete cache cleaning of the browser.