szabesz

I still think there is no "best" answer, at least we will not have Ryan and a team of "pro devs" at our disposal to decide what is best... Even if someone knowledgeable in the given topic provides a really good answer, that might not be the best approach in all cases. In short: seeking for the best or even just using the word "best" is not a good idea. I would list "solutions" instead, a list of replies under the opening post, linking to the available solutions. Also note that it often happens that the person providing a working solution revisits it, and later on provides a better one ? BTW, not all topics are about solving issues, we have quick tips, tutorials, etc... and even in those cases, some "very useful" comments could be listed under the first post. We also have module support topics. Those would also benefit from such a list whereby module authors could list further feature announcements and such.

There are already various requests to streamline the fragmented blog posts into an integrated doc, and Ryan hinted that he is actually working on that: "...But because so much important stuff ends up in these blog posts, I wanted to have a way to categorize them so that they could be automatically connected with the relevant documentation pages." I just wanted to make sure Tracy will not get left out and takes the prominent position it deserves ? after all, it is the best developer tool for ProcessWire (magnitudes more useful than any other out there), so it is not just an ordinary module.

Sorry for not being clear, I used the word "documentation" but I was actually thinking of the very closely related tutorials for newcomers. I do believe that there should be a place to showcase the best and most useful 3rd party modules used by lots of us, especially when they are maintained.

This is ok after the order has reach the end on its lifecycle, ie. it is shipped or in the case of digital only product/services a given state is reached. However, orders should be editable based on special conditions (eg.: being in predefined – better yet configurable – states) so that shop managers can adjust orders before shipping based on customer's request (in case that request is not too late, ie.: order is not yet shipped, for example) and/or after a failed delivery when there is a need to ship it again. Related question: it will be possible for shop managers to create an order for registered customers on their behalf, won't it?

@ryan Could you please dedicate a page or two in the new documentation to Adrian's Tracy Debugger module? His module has become so powerful that it would be a big oversight not to highlight it in the docs. Just look at this brand new feature: ProcessWire + Adrian's Tracy Debugger combo is second to none!

All those points sound ok to me. I just request a simple addition (maybe you just forgot to add but still...): Since I maintain a webshop which is set to "guest only checkout", I'm pretty sure there is a need for that too ?

I love debates ? Jokes aside, some simple features would do I think: a button to prefix the topic's title with either [open], [solved], [closed], etc... a button to highlight replies which – a forum users thinks – SOLVE the issue, rather than being "the best". What is "best" anyway? Ask the guys at Apple, they'll tell you what best is... ?

It could be done by specifying what user data is deletable and what not. Also, user without an order is deletable but a user with at least one order is not. Are you thinking that we need this because of being able to impose restrictions on this table outside of the scope of the normal PW API? Or because of something else? If I were to implement it, I would "bake" all the data of an order into its "record", meaning not just storing relations but the actual data too, in order not to make it possible to erase order data by deleting users, whether it be PW users or custom ones. We must keep in mind that "abandoned carts" are not contracts just yet, but deletable user data.

Regarding customer's private data: any data which is directly related to (i.e. "required by") the order should be considered as "must have" because legally speaking there is a contract between the seller and the buyer, and the customer cannot ask the shop-owner to delete such data from the system. However, "ordinary user" data – which is not related to a particular order – should only be stored if the customer explicitly agrees to it, and such data should be deletable without breaking the integrity of any order's data.

If ProcessWire allows it, then OK. I seem to recall such a discussion but I don't know what became of it. Maybe @ and . could be replaced with something else, eg: john_example_at_xyzmail_com This way we get a unique name while using first and last names do not guarantee it.

Currently I use customer for registered customers, so I prefer that one. Will these names be configurable? How about usernames based on email address? WP/Woo does that too. I'm very busy this week but I will be happy to get back to these around the weekend.

Yeah, that looks misleading at first sight, however it reads : Buy Jodit Support In the case Ryan would not need technical support - which I presume ? – it looks like a free alternative. Besides, since currently Jodit is a one man show, the developer might welcome serious contribution, see: "This project is maintained by a community of developers. Contributions are welcome and appreciated." Note that I'm still speaking theoretically, just brainstorming and not trying to convince anyone, including myself ?

Licensed under GNU General Public License v2.0 or later: https://github.com/xdan/jodit

I see. That's good to know. There is then time to figure out where to go from here.

I do not see any advantages either besides that it might be quite possible that CKEditor 4.x will not be supported in the future, while an alternative like Jodit might be.

Looks like a nice alternative to CKEditor 4 : https://xdsoft.net/jodit/play.html If you play with the on/off switches you get he appropriate code to initialize the editor that way, eg: var editor = new Jodit("#editor", { "uploader": { "insertImageAsBase64URI": true }, "language": "hu", "enter": "BR", "defaultMode": "1" }); This is a very easy was to customize compared to the convoluted CKEditor 4 configuration. Also, code level customization is possible: https://xdsoft.net/jodit/examples/plugin/custom_plugin.html At first sight, writing modules is good for adding custom content building capabilities: https://xdsoft.net/jodit/examples/plugin/custom_plugin.html Note that the running example at the bottom of this page has a missing icon, so you need to click on the "empty" space next to the I icon in order to add a 100x100 pixel dummy image. I can imagine that it would be useful to be able to write all sorts of predefined HTML snippet blocks with some Lorem Ipsum text which can be inserted by the user and afterwards the user can edit the Lorem Ipsum without the need to style it as it is already styled. Well, this way of creating new content is not a visual page builder feature but a dead simple way to aid the user in producing nice looking content with generated CSS classes to style things properly on the frontend. I wonder how styling inside the editor is possible though, I cannot find too much about that, maybe this is the way to do it: https://xdsoft.net/jodit/examples/theme/dark.html However, I am missing the "Styles" dropdown, so I cannot see how that can be achieved. Maybe by writing custom modules? BTW, among other features it seems to support image uploading: https://xdsoft.net/jodit/doc/methods/

+1, yep, it would be great to be able to decide when to dismiss it. I tend not to heave time to read all such things when they happen to pop-up. Also, if we could copy/paste them, then I could save it into my notes for later inspection.

+1 Bluma looks great too, however, UIkit 3 has more features at first sight, but I admit I never used Bluma so I cannot tell for sure. UIkit 3 both supports LESS and SASS which is great in my humble opinion (I tend to prefer LESS to SASS). Anyway, Ryan had to pick a css framework and UIkit 3 is an actively developed, popular one, full of extendible and configurable features others do not support. It was a good choice I think ?

Thanks for your short summary, it has opened my eyes... No source code editing? No target on a link? Are they serious? I think this Node.js craziness is sucking the fun out of web development. Sometimes a little bit of hacking here and there can solve something just right and the job is done. Why is this movement of over-engineering anything we can? When fiddling with the tool takes more time than doing actual development, then things are getting no longer enjoyable. And on top of all these, they remove features I rely on. I certainly do not need CKEditor 5 if things are going in this direction ?

+1 for optional ?

Hello @renobird, any more news: ?

"Now WireArray can be used on its own with just about any data type. No longer is this base class limited to working with just Wire-derived objects." I've been longing for this for quite a while. Sometimes dreams come true ? Thank you Ryan!

I have not seen SilverStripe's backend since version 3.0 but that version was really centered around intuitive page and content management, so I guess it is still solid at doing so. Drafts and page content versioning of SilverStripe has always been built-in, and that's the only thing I really miss in PW. ProcessWire has this covered with a commercial module, but still... I prefer ProcessWire to SilverStripe because of two things: PW does not introduce breaking changes between mayor versions while SS does because of refactoring how things work. Also, PW does not require a template language while SS relies on its own implementation. Anyone can add a popular templating engine to ProcessWire if one wants to.

It is scattered all around the forum, for example: It just needs to be compiled I guess.

I'm sorry, I did not get it. Here it comes: Note that tooltips of the options are usually informative and helpful.