• Content Count

  • Joined

  • Last visited

  • Days Won


apeisa last won the day on October 7 2016

apeisa had the most liked content!

Community Reputation

3,685 Excellent


About apeisa

  • Rank
    Hero Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Vihti, Finland

Recent Profile Visitors

22,729 profile views
  1. apeisa

    Yep, that would do in many cases - if you want to promote fresh articles!
  2. apeisa

    Haven't tested yet, but it seems that it stores only int value of total sum of all time views? So not possible to use for "most viewed pages this week" for example? Other than that it looks like a perfect module for many use cases!
  3. apeisa

    Most of the page fields (like autocomplete) allow creating new pages on the fly, while editing the actual article page. But I totally see place for modules like this (they are always faster to configure for example).
  4. apeisa

    Same feelings also. I think Teppo really said well how I felt also when read the latest post (and discussion about api examples). That kind of optimization is nice per project, but it is really confusing for a platform that we use to maintain and build hundreds of websites and applications with multiple developers. I'm all in for introducing breaking changes for 4.0. That would get rid of compiler also.
  5. apeisa

    I loved the minimalistic design (no images, just solid typography) on mobile. Scrolling navigation from dot menu didn't work for me. It did scroll, but usually to wrong position.
  6. apeisa

    Thanks @BitPoet! I thought it was something more generic, but now it makes sense why I have missed it
  7. apeisa

    @BitPoet I have totally missed this "field:createdUser.email" syntax. Is this documented somewhere and what are all the places that it can be used? Is it only module/field configs or some other places also?
  8. apeisa

    Craft will tackle this issue in their next version (see "Project Config"): https://craftcms.com/blog/craft-3-1-dev-preview-is-here
  9. apeisa

    I have myself moved to use jumplinks module in our projects. This module is not actively maintained, but for some projects this simplicity just works. Feel free to send pr, I might merge it (not sure if that has any unnecessary side effects?) but at least it is there if someone else has same need.
  10. apeisa

    So happy to follow this reborn of Padloper!
  11. apeisa

    Thanks Teppo, looks great! The bugs I reported earlier were not fixed on these updates. That make me look more careful the server setup and the issue was that PW timezone was not the same that server was using - that caused history tab to work inproperly. Interesting thing is that the field specific compare/restore did work nicely even on bad configuration.
  12. apeisa

    Sorry guys, haven't used (or developed) Fredi in years. I have no idea what it takes to fully support it in latest PW versions. First thing to try is to add <?php namespace ProcessWire; as a first line to each php file in the module to prevent PW from compiling the files. Probably the issue @lpa is describing is something to do with new PW features and requires proper debugging though.
  13. Hi guys As a @sforsman's coworker I'll let him know about this. We do use namespaced version of this module ourselves.
  14. I think profields table would be most suitable for your needs. https://processwire.com/api/modules/profields/table/
  15. apeisa

    Hi @teppo Finding out that there is also few more bugs with PW3: revisions don't work - it always shows the latest version (the sliding preview or /setup/version-control/preview/?pages_id=1328&revision=511 urls). I did debug this quite a bit and this SQL generated by PageSnapshot::snapshot always returns Empty set (although there should be data and database seems to been populated fine): SELECT t1.pages_id, t1.id AS revision, t2.fields_id, t2.property, t2.data FROM ( SELECT MAX(t1.id) id, t1.pages_id, t2.fields_id FROM version_control__revisions AS t1, version_control__data AS t2 WHERE t1.id = 513 AND t1.pages_id IN (1328) AND t1.timestamp <= FROM_UNIXTIME(1511771437) AND t2.revisions_id = t1.id GROUP BY t1.pages_id, t2.fields_id, t2.property ) AS t1 INNER JOIN version_control__data AS t2 ON t2.revisions_id = t1.id AND t2.fields_id = t1.fields_id GROUP BY t1.pages_id, t2.fields_id, t2.property In history tab clicking pagination also changes the tab (minor annoyance) I also updated this to PW3 (well, added namespace to each .module file and changed PDO references to \PDO, but that didn't had any affect to these bugs (didn't test the earlier image test though). Here are those attached if you are interested (didn't test that well and took about a minute or so). ProcessVersionControl.zip