Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

73 Excellent

About MrSnoozles

  • Rank
    Jr. Member

Recent Profile Visitors

937 profile views
  1. Hey everyone, I was just wondering what is the purpose of autoloading the file wire/core/ProcessWire.php in composer.json? As far as I can see that file gets required again anyway in index.php, around line 32. For me this line has no purpose but one major drawback: When requiring ProcessWire as dependecy in a module (e.g. to write tests against a clean ProcessWire installation), an error is thrown that the class is already in use. Fatal error: Cannot declare class ProcessWire\ProcessWire, because the name is already in use Does this autoloading have any purpose?
  2. Want to add to this rather old discussion, because state of tech changed a bit: No - probably it could have been simplified a lot. It was my first project with Jsviews and I probably didn't use everything it has to offer. Anyway: what caught my attention recently with regard to the ProcessWire backend is https://svelte.dev/. I haven't worked with it yet, but it seems like it could be a nice match for ProcessWire. It compiles to native Javascript, meaning even if there will be a next big thing in the future we don't have to include an outdated framework in the backend. The syntax looks really nice too and very Vue-ish which I personally like a lot.
  3. And the community loves you (two). Thank you for releasing the files, I'll definitely have a look into it after holidays. I'm sure it will be tremendously useful and I hope I will find the time to provide some improvements to it. Thank you so much.🤩
  4. And again, this has nothing to do with the Inputfield that is currently being worked on but what I was wishing for a couple times lately was some kind of "strtotime" support for page selectors when used on date fields. This would for example allow for filtering for users that signed up in the last 6 months, and that list is updated automatically, without any custom code involved. $pages->find('template=user,created>"-6 months"'); I know, this is not related to the Inputfield, but I wanted to bring it up in case it's an easy addition while working on dates.
  5. Wow, just wow. Unique values are going to be so useful, looking forward to it. And login by email sounds exciting too. 💪
  6. Hello Milo and welcome to the forums. $config->userAuthSalt For security reasons this should be different for every page. This value is used to hash your passwords to add an extra layer of security. That means when you change it you won't be able to log in anymore without regenerating the password. $config->httpHosts This should be just the host, without the protocol. So without http/https site/assets/files As far as I know there is no better way to do this, so you would have to delete files that are not needed on the new site manually. I could be wrong tho. As for the title of the topic: try to add a couple more words so people with the same questions will have it easier to find your topic in the future 😉 Best regards and again, welcome to the community
  7. I was struggling with that recently too. It doesn't seem to be too well documented. If I remember correctly you could do the following <?php .... $form->add($f); if($this->input->requestMethod('POST')) { // validate and upload the file to /site/assets/files $form->processInput($this->input->post); // access file $uploadedFile = $form->get('prop_pix_1')->value; }
  8. Please no. 🙂 I've been working with JsViews on a project and as the project became considerably large it became a nightmare to maintain. It's not necessarily JsViews fault though, it does a splendid job at what it does. But attaching event listeners to things based on their ID somewhere in the DOM and then reacting to it isn't really maintainable in a larger scale. In my opinion VueJS (https://vuejs.org) would be a great addition to the ProcessWire backend as they also somewhat follow the same philosophy and are a joy to work with.
  9. Hey Eduardo. Thank you a lot for the honest status update. It's nice to read something about the module again and get some insights why there wasn't an update in a while. I (and probably many others in this community) would love to get my hands on the module. The teaser videos looked just too awesome. For me it definitely looks polished and powerful enough to be a sold as a Pro module.👍 But if you lack the time and resources to support it at the moment, I'm sure the community would be infinitely grateful if you just released it as is.
  10. @elabx@joshuag Are you still planning on releasing the module? It would be a pity and a huge loss if such an awesome module would never see the light of the day. If you currently lack the time to continue on the module maybe you could publish it along with a list of things that still need to be done? I would gladly work on completing it.
  11. Hey everyone, this week I found the time to write some modules and came up with something that I think could be greatly improved in ProcessWire. In my opinion when developing PHP applications today there should barely be the need to manually require files that contain classes anymore. Instead this should be handled by an autoloading function and probably by more strictly following a fixed PSR naming guideline. In ProcessWire as developers we unfortunately still have to manually require files which, besides from feeling somewhat dirty, has two major drawbacks: 1) files get loaded even when not needed to process the current request 2) file includes are all over the place and also have to be considered when refactoring
  12. Super cool, congratulations on the upgraded infrastructure. I definitely would like to read more details about how you two setup ProcessWire in that environment. That would make for a good, enterprise-y tutorial here on the page too.
  13. Hey Mike, is there anything the community could do to support you with v2? The new version is highly anticipated 🙂
  14. If I want to show tens of thousands of rows, but just 100 per page, the only options I have at the moment are: Load all rows and let agGrid handle the pagination (fast navigation, slow initial load) Just show 100 results (fast initial load, but data is incomplete) implement my own server side ajax implementation for pagination (fast, but higher development effort) Is that right? Or does RockFinder already provide a solution for pagination without having to load all the data? If it doesn't: Is that something that falls in the scope of RockFinder and you @bernhard would like it to be implemented?
  15. This is awesome Ryan, keep it up! I can imagine going through the issue reports is not as exciting as developing new features but it's definitely more important in terms of maintainability and long-term user happiness. Happy that these issues are being tackled. I wish you and everyone in the community a great weekend too.
  • Create New...