Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

102 Excellent

About isellsoap

  • Rank
    Full Member

Profile Information

  • Gender
    Not Telling
  • Location
    Munich, Germany

Recent Profile Visitors

4,610 profile views
  1. Thanks! I wanted to start small and simple. I like that a simple version of the charts also works without any JavaScript. As I want to also link to specific runs, this seems to be quite cumbersome with ChartJS. Working directly with SVG feels a lot more robust and simpler for me in that regard.
  2. Hello fellow ProcessWire people! I published an article explaining how I migrated three years worth of running data from Garmin to ProcessWire: https://francescoschwarz.com/articles/running-on-my-own/ Have a great day! Cheers.
  3. Hi @cb2004, I solved this with this code: $news = $page->children("limit=5"); $pager = $modules->get('MarkupPagerNav'); // this is required in order for getUrl to work // see https://processwire.com/api/ref/markup-pager-nav/get-u-r-l/ $pager->render($news); $paginationMarkup = ''; if ($news->hasPrevPagination() || $news->hasNextPagination()) { $paginationMarkup .= '<ul>'; if ($news->hasPrevPagination()) { $paginationMarkup .= "<li><a href='{$pager->getUrl($pager->pageNum - 1)}'>prev</a></li>"; } if ($news->hasNextPagination()) { $paginationMarkup .= "<li><a href='{$pager->getUrl($pager->pageNum + 1)}'>next</a></li>"; } $paginationMarkup .= '</ul>'; } echo $paginationMarkup;
  4. Hi @a-ok, i solved this with this code: $news = $page->children("limit=5"); $pager = $modules->get('MarkupPagerNav'); // this is required in order for getUrl to work // see https://processwire.com/api/ref/markup-pager-nav/get-u-r-l/ $pager->render($news); $paginationMarkup = ''; if ($news->hasPrevPagination() || $news->hasNextPagination()) { $paginationMarkup .= '<ul>'; if ($news->hasPrevPagination()) { $paginationMarkup .= "<li><a href='{$pager->getUrl($pager->pageNum - 1)}'>prev</a></li>"; } if ($news->hasNextPagination()) { $paginationMarkup .= "<li><a href='{$pager->getUrl($pager->pageNum + 1)}'>next</a></li>"; } $paginationMarkup .= '</ul>'; } echo $paginationMarkup;
  5. I created a feature request for this: https://github.com/processwire/processwire-requests/issues/367
  6. Thanks so much for this module, @gRegor!
  7. I have the following page structure in my PW installation: Projects Project A Project phase 1 Event 1 Event 2 … Project phase 2 … … … A PW user should have the ability to "sign up" to a project, the project phases and the events. So a user can "sign up" to, say, "Project A" as a whole, but that doesn’t mean he attends every project phase or event inside the project. He could choose to only attend "Event 2" and not "Event 1" inside of project "Project A". So far the functional aspect. Now I don’t know exactly how I can accomplish this with ProcessWire. The end result should be that a user with a PW account has an overview of all projects and all its sub-pages in the front-end of the website and he can select the projects, project phases and events inside of the project he/she wants to attend (e.g. by checking checkboxes), hits save and that information (the PW pages he "signed up" to) gets stored in the back-end. How would I store that information data-model-structure-wise? Should I have separate pages for every single registration to an event? But how would I connect that information to the technical PW user in the back-end? Any help and suggestion is highly appreciated. Thanks.
  8. Here’s the news article on my employee’s website which talks about the article: https://www.jambit.com/en/latest-info/news/processwire-alternative-to-wordpress-and-co/
  9. I wrote an article about ProcessWire for the German print magazine t3n (total circulation around 38k). Translated title is: "Flexible like frameworks: why the CMS ProcessWire is a real alternative to WordPress". The article will eventually also be available online (here), but for now you can only see the title and the teaser there. It’s an overview article that talks about content management (fields, pages, templates), the API, multi-lingual content and front-end editing in ProcessWire.
  10. I analyzed the GitHub issues and PRs situation again and it is getting worse and worse. We have now 525 open issues and 48 open PRs. I searched through the labels which could IMHO be (quite immediately) closed, and I found this: 2 already fixed 1 can be closed 24 completed 2 feature not a bug 7 fixed! please confirm 64 fixed 11 not a bug 37 can't reproduce So around 150 of the issues/PRs could be closed. Doesn’t this situation concern anyone? I think what to do is clear: either Ryan himself immediately closes issues/PRs once they are fixed in his view, or a dedicated team does this for him. If nothing is done, the open issues list will grow and grow and grow and soon we'll have 1000+ open issues. That just doesn’t look right to me. :-(
  11. PW 3.0.8 Setup: delayed output strategy with _main.php beginning with <?php namespace ProcessWire; ?><!doctype html> <html> <head> <meta charset="utf-8" /> <title><?php echo $page->title; ?></title> <link rel="stylesheet" href="<?php echo someFunction($config->urls->templates . "dist/app.css"); ?>" /> </head> In the _init.php file I include a _functions.php file with include_once($config->urls->templates . "_functions.php"); In _functions.php the someFunction is defined. The _init.php and _functions.php file begin with <?php namespace ProcessWire; Wenn I try to access the home page in the front-end I get this error: <!doctype html> <html lang="en"> <head> <meta charset="utf-8" /> <title>Home</title> <link rel="stylesheet" href=" <p style='background:crimson;color:white;padding:0.5em;font-family:sans-serif;'><b>Error: Call to undefined function ProcessWire\someFunction() (line 8 of /some/path/site/templates/_main.php) </b><br /><br /><small>This error message was shown because: you are logged in as a Superuser. Error has been logged. </small></p> The setting in the home template at "Use compiled file?" is set to "Yes (and include files)". Why do I get this error?
  12. I filed a bug for this issue. Also, I found another bug during the research and filed it.
  13. Current status: I can reproduce this issue on two fresh installations (latest 2.7.3 and latest 3.0.8). But I made one more discovery that was missing to reproduce the issue: the page field inside of the repeater field must be declared as required, than you can reproduce the issue (this is also the case in the original problematic page described in my first post). So, again, to reproduce this issue: Create a repeater field, which has a page field inside (page field must be marked as required). Create a pagetable field, allowing any template to be generated within it (like basic-page). Add the two fields to a template (like basic-page). Edit a page with the template basic-page. Add two entries to the pagetable field and save the page. Add a repeater item and select the current page in the page field. Add another repeater item and select not the current page in the page field. Save the page. Try to change the order of the pagetable entries and hit save. The re-ordering should not work. To get the ordering working: Change the selected page of the first repeater item from the current page to another page. Save the page. Re-order the pagetable items and hit save. Now the re-ordering should work. I think I found a bug.
  14. Oh my goodness, now it’s getting really weird. I narrowed the problem down. I have a repeater field on said problematic page. I use the repeater to generate a subnavigation for the page in the front-end. The repeater field has a page field in it (called subnav_page). I have 4 or 5 repeater list items in total. When the page field in at least one repeater item points to the problematic page (in the case of the problematic page the page field of every repeater item must point to the problematic page [which is the one I am editing right now], because the subnavigation should only consist of anchors pointing to specific sections on the page in the front-end) than the ordering does not work, like described. If the page field of every repeater item points to any page except the problematic page, than the ordering works. I double and triple checked this. Also I checked, that the subnav_page page field is only used in the context of the repeater field, nowhere else. There is really no evident connection between the repeater field and the fields inside of the repeater field, and the PageTable field. But apparently, there is. I have to take a break, this is just too weird …
  • Create New...