Mats

Members
  • Content count

    237
  • Joined

  • Last visited

  • Days Won

    1

Mats last won the day on April 8 2015

Mats had the most liked content!

Community Reputation

225 Excellent

About Mats

  • Rank
    Distinguished Member

Profile Information

  • Gender
    Male
  • Location
    Sweden
  • Interests
    ProcessWire
  1. +1 Bug report: https://github.com/processwire/processwire-issues/issues/452
  2. Interesting read and a very nice PW site: https://www.ancientworldmagazine.com/dev/blog/built-using-processwire/
  3. http://eizocolour.com/ https://processwire.com/about/sites/list/eizo-coloredge-living-breathing-colour/ https://www.kairosfuture.com/
  4. Great module @blynx! Thanks for coding it. Would you consider making a caption option? I can't seem to find any at the moment.
  5. If Jquery is removed i'd like to see plain vanilla js and no framework in between. Just like like there is no PHP framework in PW.
  6. Great News indeed!
  7. Beautiful! Great work @bernhard
  8. @hellomoto Hi! Do you get any console errors?
  9. You're right the module set the dimensions.
  10. Have you set width and height of the map? I always forget that.
  11. I did something similar (if i understand your question correctly) on a calendar on this site: http://eketorp.se/evenemang/?datum=2017-09-29#pickedDate Only dates with events or opening hours are selectable. Active dates are json used by flatpickr: https://github.com/chmln/flatpickr
  12. That sounds like a good solution. Thanks @BitPoet !
  13. I’m building a simple ticket booking system for our events. I’m considering two different solutions: The first approach is creating one page per ticket and a reference to a booking page with the contact info. This should be faster when checking for ticket availability by using $pages->count(). The other one is a one page per booking with an integer field holding the ticket quantity. Downside is having to use $pages->find() but only having to create one page per booking with the API. My biggest concern is listing the events and the ticket availability for each event, loading all bookings. At the most one event has 300 bookings. Any ideas are welcome.