LostKobrakai

PW-Moderators
  • Content count

    4,556
  • Joined

  • Last visited

  • Days Won

    92

LostKobrakai last won the day on June 20 2017

LostKobrakai had the most liked content!

Community Reputation

4,450 Excellent

3 Followers

About LostKobrakai

  • Rank
    Excited Member
  • Birthday 11/29/1991

Contact Methods

  • Website URL
    http://www.kobrakai.de

Profile Information

  • Gender
    Male
  • Location
    Augsburg, Germany

Recent Profile Visitors

14,359 profile views
  1. Congrats. Another very well crafted website of yours. I don't really like the scroll-jacking, but I really really like the menu. You also might want to look into hiding the video pop out button on opera.
  2. That's really a strange way for the host to answer, because ssl is really not related to the cms (besides maybe generating https links and redirecting). But enabling ssl does need to be setup on the webserver. For redirection to https see the .htaccess file and urls in processwire are most often relative ones, so there's probably not much to do on the url generation side.
  3. This thread is literally years old. See here for the options regarding disabling the session: https://processwire.com/blog/posts/multi-instance-pw3/#more-session-control
  4. If you don't need sessions on your frontend you can disable them. Otherwise this seems fine.
  5. You're correct that data string values are only translated for find queries, but not runtime selectors. But processwire just uses `strtotime` so you can easily use that on your own: strtotime('today')
  6. This might be a quick fix, but for me this rather looks like a FieldtypeUnit, which fully deals with the fact that you're storing an amount of a unit. With the unit being available alongside the integer at runtime would give you the additional ability to handle the value to it's full extend like being able to converting weeks to days or grams to kilograms. A integer is just a single number but e.g. 60 seconds are just a different representation of the same value of 1 minute.
  7. Imo the overall backlash on jQuery is less about jQuery vs. vanilla, but jQuery vs. less messy abstractions. For ajax there's no need for jQuery anymore with other libraries taking their turn being just as good without being bundled with all the other jQuery stuff. And for DOM manipulations I feel twofold: For simple stuff jQuery is hardly shorter/easier to write than vanilla js + 2 or 3 small helper libraries (e.g. for event delegation) and for everything more advanced jQuery code most of the time is just a mess of one-off manipulations and implementation details mixed with a bunch of event callbacks. These are the places where I feel react / vue / ember or for a really vanilla feel svelte are far better equipped.
  8. Just look at the modules code. It's just a few handful of code and a single hook.
  9. http://modules.processwire.com/modules/process-page-list-multiple-sorting/
  10. The problem is that those issues are a hard problem to deal with, which is why there are dedicated software solutions out there just dealing with search. Especially the spelling mistakes are really difficult to come by. Also generalised solutions mean this is a issue of the database, so MySQL for processwire, but in your case (small scale) you could also try to improve things from the PHP side.
  11. And be sure to use https as always
  12. Fuzzy matching like one is expecting nowadays of a good search field is actually quite difficult to do with mysql. If you need a fast search returning relevant content for such short search terms you're most often better served using something like elasticsearch or angolia.
  13. The best thing with it are all the pull-requests happening for this piece of code, which won't probably be run anymore.
  14. In ProcessWire each page is defined in a single db table, while each field you create does have a own table, where data is linked to a page. So "denormalization" to having each image be a single page with image/description/notes/… will still be stored kinda like in your old setup. The page-tree / templates don't actually represent any db based normalization as they're basically the pages, pages_parents, templates tables in the db. They've no influence at all about how actual data is stored.
  15. It's ProcessPageView::getPage(), but it's a protected function and therefore not for public consumption as per right now.