Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


dragan last won the day on May 23

dragan had the most liked content!

Community Reputation

1,269 Excellent


About dragan

  • Rank
    Hero Member
  • Birthday 10/18/1969

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

6,362 profile views
  1. I never had to deal with it myself, but check out Ryan's announcement.
  2. If it's just styling, you should first try a CSS-only solution. You can do a lot with just :nth-child or flexbox.
  3. I don't think that would make any impact on filtering and search. If anything, it would only make your setup more complicated than it needs to be. You would have to take care of creating year/month/day parent pages with each new record (or create them ahead of time).
  4. err, I should have googled this before answering... (I had no idea what ESP means). So it's data from one single weather station only? My above post was based on the assumption that you get weather infos from all over the world via some 3rd-party API and you update your site via cron jobs. It's been said time and again that a big number of PW pages will scale well, but a combination of (too many) fields, templates, and pages - plus complex queries - can seriously impact speed. In your case, the setup seems to be quite simple though, so I would go the "native PW route". However: When it comes to loading huge data-sets and visualise them (aggregate a 5-year-span of weather data and create statistics or curve diagrams), I would surely look for RockTabulator or some such. You can fake a future situation yourself with simply creating thousands of dummy data-sets.
  5. The majority (everything?) of the content is automated via imports, and you have practically no use for the whole PW admin backend? If so, I'd surely go the custom-mySQL-tables route. In PW, do your visualisation stuff (pulling raw data from mySQL). Perhaps you'd only have to build 1 page per location, and then use the location-page-id as a foreign key in mySQL. If you expect huge traffic, then a proper caching strategy would be essential. Do you plan to have some sort of search / filter on your site?
  6. @BFD Calendar It's certainly none of my business, but don't you want to optimize your site a bit? For starters, it takes ages to load. It's also not responsive. Your homepage is a whopping 24MB. You're loading JS in the <head> instead of the end of your <body> etc. The pattern backgrounds makes reading content hard. Images don't have an alt attribute. Google doesn't like slow and non-mobile-friendly sites, and chances are, your users won't either. https://search.google.com/test/mobile-friendly?id=Os-IXOq4pmJaFuqLUSb8xQ https://developers.google.com/speed/pagespeed/insights/?hl=de&url=https%3A%2F%2Fwww.birthfactdeathcalendar.net%2F The long homepage e.g. could make use of some lazy loading technique - it ain't that hard to do. I don't know what else is slowing down the site (TTFB is over 7 seconds, which is really bad)... maybe un-optimized PW selectors?
  7. Did you debug it with Tracy? Check whether you need parent or rootParent, and your template and field names.
  8. Did you check the Apache error and access log?
  9. Nice. Apparently, my anti-virus software thinks your demo site is spam.
  10. @ttttim This module was just released yesterday... maybe take it for a test-drive?
  11. Did you try someting like $unifiedMatches = $pages->find("id=$find1, limit=$limit")->add($pages->find("id=$find2, limit=$limit")); ? Seems to work with a quick test here...
  12. Sadly, Google doesn't seem to offer a cached view of such articles... Maybe we should ping @ryan ? Were those tutorials too much out-of-date, or was there any other reason they didn't make it to the redesign pool of content?
  13. Lots of infos here: https://processwire.com/blog/posts/composer-google-calendars-and-processwire/
  14. You have a lot of weird invisible characters in your code - this happens sometimes when you copy-and-paste from forums. Luckily, good text editors / IDEs spot such stuff and give warnings. I cleaned up your code and attached it here (together with two minor hints re: code) kalimati.zip
  • Create New...