Jump to content

ryan

Administrators
  • Posts

    17,393
  • Joined

  • Days Won

    1,781

ryan last won the day on November 15

ryan had the most liked content!

Contact Methods

  • Website URL
    https://processwire.com

Profile Information

  • Gender
    Male
  • Location
    Atlanta, GA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ryan's Achievements

Hero Member

Hero Member (6/6)

28.9k

Reputation

212

Community Answers

  1. This week on the core dev branch we have version 3.0.276. Relative to the previous version, this one has about 20 commits, most of which are issue fixes, as we continue to chip away at the issues repo. As I write this, there's only 1 issue remaining for 2026, 1 for 2025, and all that's left are older issues from 2021 to 2024. So getting the issues repo fully covered is within sight! More next week. I hope you have a great weekend!
  2. Good point on the confusion the current versions could produce. Looks like some good options here. I do worry that adding a digit (like 3.0.260.1) could break some existing things that expect x.x.x type versions. I like the idea of using 3.1.x for the dev branch rather than 3.0.x, though uncertain about scaling that over the long term.
  3. The version numbers on the dev branch aren't tagged, whereas the version numbers on main/master are. Also the dev branch versions have a "dev" suffix where as master branch versions don't. I'm not sure of a better way to do it but always open to ideas
  4. This week we have ProcessWire 3.0.275 on the dev branch. Relative to 3.0.274, this contains more than 90 commits, many related to older issue fixes from our GitHub issues repo. Also released this week is ProcessWire 3.0.260 on the main/master branch. When there is anything potentially security related, I back port those updates from the dev branch to the main/master branch, and bump the master branch version. This maximizes the security and stability of both branches at the same time, so it's become part of the regular work flow these last few months. More next week. Thanks for reading and have a great weekend!
  5. Sorry I wasn't able to provide an update last week, and not really able to provide one this week. I'm all caught up in legal matters with my wife unfortunately, and it's consuming all my time. I still am getting various commits on the dev branch though, and hope to have a new dev version ready for you next week. Thanks and have a great weekend!
  6. @BrendonKoz the current dev branch will become PW4, so a major version, probably around the end of the year.
  7. I'll keep this update short because I'm currently in the airport and headed to Amsterdam. This week we've added official support for nginx and caddy to ProcessWire, among various other updates on the dev branch. I'll be in Amsterdam for a week. If any ProcessWire users are in the area and want to meet up for a coffee, beer, or a walk, please let me know. I'll be located near the Amsterdam Centraal station.
  8. ProcessWire adds SQLite and PostgreSQL support. This week on the dev branch (3.0.274) you can now install and run ProcessWire on SQLite or PostgreSQL, in addition to MySQL. Read more in this blog post: https://processwire.com/blog/posts/sqlite-and-postgresql
  9. I still like using Uikit if I'm otherwise going to be writing the CSS and markup by hand. Due more to comfort than anything else. But if I'm getting AI help (as I did here) then I thought going with plain CSS and CSS vars was preferable. Is it still useful to spend all sorts of time hand coding all the markup and CSS? Probably not. But I still think it's beneficial to have a shared/modular environment like the admin standardized on a framework like Uikit.
  10. This week we have a new AI-based ProcessWire installer committed on the dev branch. Now when you install ProcessWire, you have a choice of “Standard installation” or “AI-Assisted installation”. If you chose the AI option, then the next screen prompts you for your AI model ID, endpoint URL and API key. When the installer finishes installing the ProcessWire core, you are brought to the AI Site Builder where it asks you some questions about what you’d like to build, and then it builds it for you. 🙂 When it finishes, you can see what it did, and continue asking it to make refinements until you are finished. I always thought we needed more site profiles for ProcessWire, but now we have essentially have an unlimited number of potential site profiles when you use the AI installation. Note that the AI installation option also automatically installs the AgentTools module as well. Example of site built by by the installer/site-builder -- it even wrote all the text and documentation!
  11. The commits have continued at a fairly rapid pace again this week, which you can follow in the dev branch commit log. I’m not bumping the version number this week, but likely will next week. At this point, my goal is to clear out our processwire-issues repo, so that the majority of the issues in there are solved and those no longer applicable are closed. We still have around ~160 issues open, but since we’re now working on a lot of older issues, as we go through them, we’re also finding a lot are already solved. In an ideal world, we’d not have more than a dozen open issue reports any given time, so we may just get there!
  12. Well the good news is that it's been a month since this started and I'm a lot better off than I was. I'm eating more, sleeping more, and can function well enough again, even if still sad. I'm mostly back to work. I'm pretty proud of 41 commits this week. Seems like good momentum, and feeling a lot of confidence and enthusiasm for ProcessWire's future. I really appreciate all of you and your support.
  13. Well my personal life news has not been getting better. My Mom had a heart attack, which we believe to be from the stress of my wife leaving (she and my wife were very close). But thankfully, my Mom had good and quick medical attention and is now recovering. Despite the news, it was quite a good week for ProcessWire development, with perhaps the most commits we’ve ever had in a week: 41 of them. This week we solved a large number of core issue reports, including a lot of years-old ones. Lots of improvements have been added to the core as well, plus two PRs from Adrian. What I’ve found is that when it’s hard to focus due to so much change on one’s life, solving issue reports is the perfect diversion. Especially with a little AI assistance. So that’s what I did this week… fixing what can be fixed, taking the focus off of what can’t.
  14. For me it's always been about the design. How it makes its way into the output is an implementation detail. A detail that can change and evolve. A detail that I don't think matters that much in the short term or most users. Though a detail that clearly matters to some more than me. If someone thinks a different implementation would be better, great, then do it. ProcessWire supports multiple ways to theme/style the admin and I think that's a benefit, not a drawback. My aim is for PW to be flexible. AI could probably convert one strategy to another in minutes. I've got enough on my plate and if someone wants to make such a significant contribution as Konkat did, I welcome it. The same has been true with many of bernhards contributions. Both have contributed some of my favorite recent additions to PW. We are all doing the best we can with the time and resources we have. When bernhard submitted his AdminStyle system, I liked what it added and didn't insist that it be implemented in a particular way. Likewise when Konkat submitted their design for the admin. Front end CSS is not one of my strengths. I welcome the help, and prefer to leave these implementation details to the experts. In this case we've got experts that disagree, and one that thinks that's worth abandoning a project for. I personally think bernhard should stick around, and we all should accept that the community isn't always going to agree on everything, but that it is part of collaboration.
  15. @maximus I'm pretty sure it would be configurable in that way. They've always had a different look going on the IP.Board site than what we use here. And the templates, at least in 4.x, are HTML with placeholders, so it's quite configurable. Hopefully that remains the case with 5.x. My assumption is that it would look very similar to how it does now, just updated to be more consistent with the current website design. Headless Shopify.... I hadn't considered that! I'm going to give this a look, thanks!
×
×
  • Create New...