szabesz

I do not use loginForm so I cannot really test it but after updating I had no issues at all.

This does look really useful if it gets "perfect for all selectors", since it is a great way to get a different point of view of the selectors we write. For example I am very slow at writing SQL since I rarely have to do it (thanks to ProcessWire ) but I can read it so this means I can more easily identify errors in complex selectors just by taking a look at the the actual queries. Also, spotting query related performance issues gets easier. I'm thinking of seeing lots of JOINs and being able to reduce them should they only be a result of a not well written selector. At least this is my understanding right now. Correct me if I'm mistaken...

Hi A VPS (running cPanel perhaps?) might list what is eating up resources. Have you checked that info? Also, it is not free and if you really have not changed anything then it might not be of good use in this case, but it might help: https://processwire.com/api/modules/profiler-pro/

"Sounds" useful Thanks for sharing and caring!

I would vote for this. Users tend not to notice such subtle things like cut-off text in an input box. Looking ugly is better than users having trouble, I think. So I vote for pixels.

One more thing, layout of the input boxes. Is there anything I can do to turn it into a one-liner? Something like:

Works! Thank you very much!

I added a Phone field (called user_mobile) to the user template. I have ListerPro so afterwards I added this field to the Lister of users as an additional column. In this column only the unformatted phone numbers show up and area codes are missing. If I enable country code it is also missing. (I do not need country code right now, I did it for testing purposes only.) Otherwise in Tracy's console echo $page->user_mobile; and echo $page->user_mobile->hungarianV1; etc... work as expected.

https://processwire.com/blog/posts/pw-3.0.86/

Better yet, something like this: I have three different browsers in use: one for regular browsing with plugins installed (Vivaldi with "adblocker", Dark Reader, downloader, etc...), one for development/PW (clean Chrome) and one for logging into 3rd party online accounts only (clean Firefox). Nice and tidy setup

While I generally agree to all the other points raised, I would be cautious with Slack. To tell the truth, I'm barely familiar with Slack but what I've seen so far (and that was about two years ago, so things might have changed) communication in Slack is very fragmented and hard to follow. On the contrary, our current forum has a lot of power in it and is very easy to follow. Maybe Slack can do the same but it is a question whether it is preferable or not.

Very good point! I was in the same boat with SilverStripe. They pushed the system in the direction so that one can practically use their workflow only, major version numbered system updates were not possible because of incompatible modules, etc... Part time developers like me just could not keep up the pace with the changes introduced. In contrast, ProcessWire "just" gets new features, upgrade issues can be sorted out, and breaking API changes are virtually non-existent. You learn it once, use it "forever" For example, I hate that when I need to re-learn M$ Windows/Word just because they completely redesigned the GUI. I'm on Mac$, anyway

Thank you! I have not yet realized it. Good to know

I am about to use this module too (for the first time). The discussed improvements do sound good. Thanks in advance, Adrien!

I have "two" ProcessWire 3.0.88 "versions". One form January the 5th and the other one dowloaded today a few minutes ago. There are a couple of differences in the source code: Is it a common practice to introduce changes without changing the version number? I have not yet noticed such a thing before, but I must admit that this is the first time I checked... I noticed a difference in the ZIP's file size, so I compared the two.

To tell the truth I have not yet used @Robin S's ConnectPageFields module, but maybe he could come up with a solution based on the inner workings of his module to take further this Page Draft module. I'm just wild guessing here and probably daydreaming however, it would be great to see a free alternative to ProDrafts as a draft feature would be welcome, but I do not have a project which needs all the extra features of ProDrafts, I could do with just draft+published states for the "body" field, keeping the already published state intact until it is overwritten with the draft version which can be saved too, independent of the published one.

The logo is so funny, I like it too. If Ryan does not mind that you use it this way, why change it?

Making future website upgrades more error prone and time consuming, I agree. Yes, we should get more organized somehow.

I would like to add something else to this already great discussion, and this is about the rate of new features and changes introduced in ProcessWire. While the last few year's new features are impressive, they keep introducing so many minor issues that – while they are truly minor – they have already accumulated to the point where I cannot see how each of them will get sorted out in the future. Leaving these issues behind in the dust will make ProcessWire less robust in the long run. Do not get me wrong, I do no think ProcessWire is in any sort of trouble just yet but recently I stopped updating to new dev versions fearing that I might break a site. The last stable is v3.0.62 from May 5, 2017. I would love to see a feature freeze so that a new stable and somewhat tested version can be released.

https://processwire.com/talk/topic/3846-how-do-i-create-a-sitemapxml/ Thanks for sharing your implementation!

I use FieldtypeYaml module because it is relatively easy to manually edit Yaml. JSON is easy to read but not so easy to manually edit. It is a good choice using FieldtypeYaml for not too complex config fields , I think.

I recommend dropping classic Default admin theme support. After all, AdminThemeUikit is becoming the new default in the near future.

Thanks in advance anyway

Hi @flydev Me too Any news on it?

In addition to @Robin S's suggestion above, if ProcessWire 3.0.87's new features were extended as brainstormed in the post: also adding the possibility for an Images inputfield to upload to and/or pick images from another one (+ this supercharged Images inputfield being filterable) then we would finally have a very impressive set of image management features built in which have been sought after for years.