szabesz

+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(?).

I was about to report/ask for these. You saved me some typing Thanks a lot!

What if we have the same number of articles? It will overwrite the previous one, won't it?

And a simple logo for $3,050, that's cool too! I would be rich by now if I could charge like that... Anyway I like the site. It's just perfect to scare the hell out of my clients so that they can be pleased by my prices...

As a simple example, let me show you the basic setup of a blog (simplified diagram of the blog profile I recommended above): It is a "UML like" diagram, where the yellow boxes are the templates, the blue ones are sample pages (they must be created in the Page Tree) based on the templates. Generally speaking whenever you can, you should set up parent/child relationships, because this is something ProcessWire handles well, out of the box. However, it is not possible to force all the required relationships into a tree, so we can also have "simple" one-to-one and one-to-many relationships via Attributes (Fields). A Field in ProcessWire has its associated "Input field type" (found under the Input tab of the field), which sets up the UI element used by the admin for the field. Quote: "Input field type: The type of field that will be used to select a page. Select one that is consistent with the single page vs. multi-page needs you chose in the "details" tab of this field..." Hope this helps. If not, I can mock up a similar diagram about your use case too. Answers to your questions: A1. Generally yes, but I recommend implementing something like you see above: parent/child for Books/Book, Categories/Category, Chapters/Chapter, etc.. and you can connect these via Attribute (Field) / InputField relationships. This is a much more flexible setup. A2. If I understand you correctly, you can do it if you use Attribute (Field) / InputField relationship, and by setting the field to "required". A3. Yes, a field. The simplest way to implement it is using the Options type: https://processwire.com/api/modules/select-options-fieldtype/ https://processwire.com/blog/posts/new-options-fieldtype-processwire-2.5.17/ Of course, you can also setup just another Field/InputField relationship, if you need more than a simple select. A4: Sure, it can: https://processwire.com/api/variables/ BTW, one more reading on the topic: https://medium.com/@clsource/understanding-processwire-templates-fields-and-pages-201aecd0a1a4#.gd0w6u9qw

Hello, Here is some theoretical background to start with: How to actually setup parent/child(ren) relationships: Best general introductory tutorials: http://blog.mauriziobonani.com/processwire-basic-website-workflow-part-1/ https://www.smashingmagazine.com/2016/07/the-aesthetic-of-non-opinionated-content-management-a-beginners-guide-to-processwire/ If you already have a little bit of developer backgound, I recommend checking out this profile: Even if you do not want to deal with the "Wire Render Pattern" implemented for the front-end, checking out the templates/fields of the profile demonstrates a great deal about how to set things up.

Sure, it's a gfx only design clone to demonstrate @clsource's Wire Render Pattern:

The search inputfield starts to cover the System Notification indicator under 1040px, and yes, below 960px the search inputfiled is gone. I think it is just quite ok if you focus on a viewport wider than 959px, however, it would be nice to have an easy to access (toggle-) button which can be clicked on mobile to disable/enable the module "temporarily". It can even be useful on a desktop, in order to quickly check out the unmodified admin or vice versa.

@tpr I just want to say a big thank you! I'm back from holidays so I could actually update the module and it works fine so far. The new appearance of the normal Sticky Header (not the compact one) with the always show search field is my most favorite setting.The "dropdown" version of System Notifications is great improvement too. Just one issue I have: with the above mentioned normalSticky Header + always show search field setting I do not have access to the search field in narrow viewport, the search field simply disappears. All in all, you managed to improve the Reno Theme in such an extent that there is no more reason to prefer the classic admin theme to it.

I haven't used XAMPP not AMPPS for ages, however I've been using MAMP Pro for a while without any serious issues. Something worth mentioning is that MAMP Pro's PHP Mode called "Individual PHP version for every host (CGI)" does not work in the case of "some sort of AJAX responses", which I have not yet tried to figure out why, but most of the time it works and when it does not, I just switch to the other option temporarily ("no CGI" i.e. module).

I tried Chrome's "Empty Cache and Hard reload", Incognito and another browser too. Maybe not the best, but with a _blank target it should do. I support the icon idea too, that is something obvious and normally we have enough room for it, I suppose. I just always forget long clicks, modifiers and such. I use so many of them anyway, that I find hard to remember those I do not use often, and this is such a case (at leas for me).