szabesz

Does anybody really like infinite scrolling? I mean it looks fancy, but from the usability point of view infinite scrolling is horrible. Just try to find an image on a looooong page of thumbnail listing after you passed it half a minute ago.

@benbyf Thanks a lot! I really appreciate the work you put into your tutorials.

Wow! If only all my wishes came true that quickly! Both issues are fixed, thanks a lot!

@adrian I'm not saying I can keep up with the pace of the module's development, but trying to... I skipped a few versions, but now I'm checking out the latest (2.7.2 - in sync with PW master, eh? ) and have two issues with the Template Resources panel: #1 issue: when file compiling is on, I get: #2 issue: I have the following list of Included Files: As you can see, files are listed more than once, a lot of them 8 times, but at least 3 times if I'm not mistaken. I use wireRenderFile() to render partials of the page but simple include_once is used too.

This one

The checkerboard pattern creates a sort of interference effect but your slightly colorized noise has no chance of doing that, so no wonder it is a lot better choice. Lesson learnt? Sometimes it is not the best thing to follow the crowd...

100% true. @Hector Nguyen sorry for not paying attention to it.

Hmmm. Hehe, sounds funny indeed! Seeing is believing, so let's give it a try

https://www.wired.com/2015/08/researchers-hacked-model-s-teslas-already/ The more computer you stuff into a car, the more hackable it will be, especially if it is online. And they are doing the same for trains and airplanes too, to name a few... Frightening.

Such features would be wlecome in AOS too

+1

@tony Hi, I have already tried to install the version found in the modules directory, but this one did not work for me either: http://modules.processwire.com/modules/blog-profile/ Instead, try the version posted by Ryan here (this one worked): Note: you might want to install it along with a ProcessWire version close to its release date, or at least ProcessWire 2.7 or 2.8. It might work with 3.x too but I have never tried. One more tip: you might also be interested in this one by @clsource for ProcessWire 3.x:

Great tweaks for the Pagelist thumbs! Although I have not yet found the time to try it out, I will surely do it one day I have an issue to report too: one thing I use a lot is FieldAndTemplateEditLinks. Template links work, but Field links do not. The tooltip appears on hover, but nothing happens on click. It used to work, maybe two versions ago, I'm not really sure when though.

Additional use cases to justify the need for this - one-to-one relationship support. Example: internal only SEO "Pages" (records) attached to one page only, e.g.: - JS slider records, when we need to limit the number of items by design - all sorts of other records when we need to limit the number of records by design... While we are at it, such a limiting capability can be handy in the case of other types too, such as AsmSelect, PageTable to name a few

More on the topic with module recommendations:

Another use case to support this request:

easy peasy lemon squeezy

$like++

You deserve the gold medal anyway! Works fine. Now I can easily create screenshots for forum support too, should I feel the need to (With AOS on it might generate some confusion to demo the admin... so this is just another case to justify the need of this feature...)

So we use this: https://processwire.com/api/ref/wire-array/sort/ , right?

@adrian Non-ProcessWire Template Variables panel question: we have a column labelled "Returns" with object, array, string, etc... in it. However, is it just me who is missing the result of a get_class()call? It would be much more informative to see which class the object is the instance of. Is it possible to implement?

Let's suppose we are absolutely sure that $author->title is unique. In that case your example is a valid one if we do not need the ID in a particular use case (e.g. we just want to use the result once for echoing it out and throw it away afterwards). However, if we have the slightest doubt that this is not the case, then @horst is right I think. The best practice is to always stick to IDs when we can. So, thank you horst for pointing this out!

So we need additional steps anyway, it just depends on our personal preference and/or use case, I suppose.

One more thing: when AOS is used to heavily customize the admin, one can easily see that it is enabled. But what if it's not so prominent? A globally accessible enable/disable button would also indicate in what state the admin is. Is it on steroids or not? It is an especially important question during the Summer Olympics

Yes, that was the basic idea. I'm relatively new to PW, so sometimes I just cannot remember what the original admin looks like but as I mentioned before, if you "do not support" mobile viewports then it can be problematic if we cannot somehow disable the module in that case. Sure, one can always go to module settings, but it might be possible to speed things up... Thanks. I did not realize it was a Reno bug(?).