Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/09/2020 in all areas

  1. The ecumenical city pilgrim trail in Villingen, Germany is a small trail through the city where you can visit churches and other places of interest. This Progressive Web App is a small website to guide visitors through these places and give additional informations. You can install it on your smartphone or tablet and walk the trail with it. app.stadtpilgerweg-villingen.de Features: Interactive Map Progressive Web App Interactive Map Before entering the map you get a little tutorial where you can choose between two routes, the standard trail or a more accessible trail. You can track your position on the map and click on the markers. Each marker is a view with additional information to the place. The views can contain texts, quotes, images or a chat element. The map was realized with Leaflet and styled with Mapbox. Progressive Web App The website can be installed as Progressive Web App on your smartphone or tablet for a better experience. The PWA remembers the last visited view and has no unnecessary browser navigation. It can also partly work offline and caches almost everything. The PWA was realized with the help of Workbox. Modules used: Repeater Matrix ProCache Map Marker (Google Maps) Sitemap ProcessWire Upgrade TOTP two-factor authentification Tracy Debugger Regards, Andreas
    3 points
  2. A while ago I added an event listener / event queue feature for Wireframe objects: https://github.com/wireframe-framework/Wireframe/blob/master/lib/EventListenerTrait.php. The rough idea is that the object itself keeps track of events and listeners, and if an event is emitted ($this->emit('event-name', $args)), related listeners will be notified. This concept was loosely based on the Vue.js events system. This might be overtly complex for your needs, though. Something as simple as $this->runHooks('event-name', $args) would likely work just fine (though it depends on your use case) 🙂
    2 points
  3. I usually avoid picking up on Alpha/Beta plugins since everybody can spin a plugin with a cool idea and list it on a github. The lack of updates from developer usually don’t inspire too much trust and most of the time the other developers tend to create their own plugins. With this being said, probably there are 100 versions of stripe payment gateways plugins on developers private repos. And that’s bad!!! Processwire and the whole community is AMAZING, but the only thing that I think that is missing... is the part where developers start to create, sell and maintain their plugins. By creating a premium PW plugin marketplace the following scenario will happen: 1. @ryan will/can receive a comision on each sale. This will be a well deserved token of appreciation for all his amazing work invested to build and maintain PW. 2. Plugin creators will be constantly motivated to build, maintain compatibles and improve the quality of their plugins. 3. The developers that will pay and use the premium plugins and they will save thousands in development time. Probably their clients will be happier with smaller project fees and shorter delivery times. I’m suggesting this since I’m always looking in Craft cms plugin marketplace and I have the feeling that they have a plugin for everything. Some are silly some are amazing... i know.. But in the moment you browse it, you always have the feeling that the only thing you have to do in order to create a big project is just to put the puzzles pieces together. I’m paying for some premium plugins that Ryan built. And i would happily pay for SEO, shop/payments, reservations, crm, marketing and integrations with other widely use systems.
    2 points
  4. An SQL "expert" with records with duplicate keys? That starts alarm bells ringing for me. Generally any SQL table should have a primary key which by definition must be unique for each record. Of course it's possible they have some sort of composite key based on multiple fields that needs combining to correspond to a unique page name in ProcessWire. There are certainly cases where I've build SQL tables with composite keys, with one scenario being many-many relationships, and that's something that Processwire doesn't handle too well, although there is a module that makes many-many type relationships possible, although it doesn't compare to what you can do with pure SQL. Processwire does handle One-Many relationships fine via page reference fields or Pagetable fields. If you really must have a direct relationship between SQL commands and table structure and your CMS, I actually wonder whether ProcessWire is your best option. I've been doing a bit of investigation of Directus which looks promising, although it's headless, so no templates for output like ProcessWire, just a REST API, from what I can see, no full text indexing, and being more of a direct SQL - CMS mapping, it also lacks the hierarchical parent-child structure that ProcessWire handles so well, as it doesn't make any assumptions about what sort of data structures you have, whereas ProcessWire, while generally very un-opinionated does treat everything as a page in a page hierarchy. For websites, that's generally a pretty reasonable assumption, but if you really don't want that, and just want pure SQL tables then there are alternatives. While something like Directus will give you a direct SQL to CMS mapping, it won't fix bad SQL data, so if you've already started down the ProcessWire path, you want to be really sure it's worth the effort to change. I come from a pure SQL background myself, and it only took me about 20 minutes of reading the ProcessWire documentation to understand how it works, so I don't think it should be hard for someone from an SQL background to adapt. Maybe there's room for a blog post or tutorial showing how to "do it this way in SQL" and ProcessWire equivalent along with what's different.
    1 point
  5. This is where I started)) Thanks, I'll look into it. But I always try to first use a native solution if it exists) And PW always tried to be all-in-one thing. I am actually thinking about building a module on this feature, so do not want to have an external dependency. The 1st part I didn't understand) But the second looks promising. Could you share an example of this in a template file context?
    1 point
  6. Just to add to the discussion....how Laravel does it: https://laravel.com/docs/7.x/events
    1 point
  7. Generally I think event handling can quite easily happen outside of processwire with something like https://event.thephpleague.com/2.0/.
    1 point
  8. Thank you for the PR and the idea! Of course it's a good think to have the render function hookable. I also like the idea of @horst with an hookable output file. I would definitely like to spend some time soon to refactor / optimize PrivacyWire.
    1 point
  9. https://www.urbandictionary.com/define.php?term=reiska A very beautiful girl with a gorgeous smile, very confident, honest, and smart. Even though others don’t really value her as much, she will be very independent and also not interested in what others say or feel. She must come first regardless of how others treat her. 🙂
    1 point
  10. New release for latest stable PW version 3.0.164
    1 point
  11. Good news! We are live now! AppApi has been approved and now appears in the modules directory: https://modules.processwire.com/modules/app-api/ Thank you for your many reactions to the release - I hope it helps you build the best apis you can imagine!
    1 point
×
×
  • Create New...