kongondo

Actually you don't need this :-). Just need to use Filters -> Show System Fields :-).

Welcome to the forums @guigui, I have no idea but maybe this topic can help?

Alternatively, @franciccio-ITALIANO, given that you are on a local site... echo $pages->get(2)->name; in any template file of a page accessible in the frontend should do it.

Or....imported a huge image maybe?

Which method exactly? It would help us reproduce/test. I don't quite get this. Aren't all hooks called from a class context? Perhaps you meant to say frontend versus backend? What errors? Where are you calling the hook? Some code to look at would help :-).

It is a free ProField. Welcome to the forums and ProcessWire ?.

Could you please show us your code for this bit? Secondly, it is not clear whether you want to store pages from one instance in another instance. If that's the case, maybe this applies to you? https://processwire.com/blog/posts/multi-instance-pw3/#pitfalls-and-considerations

moderator note This seems like a question specific to ListerPro. If you have a current subscription to that module, please ask this question in the ListerPro support forums. Otherwise, please start a new thread in General Support. We strive for one issue per thread please. Thanks.

Hi @ryan, I just noticed that part of the documentation for $user variable refer to Page objects instead of User object. Yes, technically, these are pages as well but I think it might confuse new ProcessWire users. In addition, the $user variable docs clear refer to users as 'users' and not 'pages'. Here's an example of what I mean. $users->delete() Here is the list of docs that need amending (that I could find): https://processwire.com/api/ref/users/add/ https://processwire.com/api/ref/users/added/ https://processwire.com/api/ref/users/delete-ready/ https://processwire.com/api/ref/users/deleted/ https://processwire.com/api/ref/users/find/ https://processwire.com/api/ref/users/save/ https://processwire.com/api/ref/users/save-ready/ (some bits are OK). https://processwire.com/api/ref/users/saved/ The get* methods and setCurrentUser() are all OK, referring to User object instead of Page object. The saveReady() refers to User object in some parts but Page object in others. For instance: But further down... Could you please consider amending these? Thanks.

Works fine for me. In ready.php $this->addHookAfter('Session::logoutSuccess', function(HookEvent $event) { $user = $event->arguments(0); // here, your condition for getting transitory user if($user->id>1025){ // just to confirm wire('log')->save('logged_out',$user->name); // delete the user wire('users')->delete($user); } }); ProcessWire 3.0.159

Which one? ProFields Table? If yes, definitely; Ryan's the author ? (although I am not sure what you mean exactly by proper use of the API).

Hello @ivineet9, Welcome to the forums ?. Most likely using a RESTFUL API or multi-instance ProcessWire if both sites are on the same file system. Mind, these will only get you as far as the data. If you want to 'see' the admin of the other site in the backend site, you will need to develop a Process Module. There are a couple of threads in the forums that discuss how the admin panel can be locked down to 'mimick' not accessible (redirects after login, hard-to-guess-admin-url, ProcessWire outside webroot, etc) but you cannot fully get away from an admin (unless I have missed new a trick or two).

Just to add to the discussion....how Laravel does it: https://laravel.com/docs/7.x/events

The more I read this the more it sounds like what you are after are custom hooks?

I am curious about this as well Was it Joomla? Why did you decide to stop using Joomla? Why ProcessWire?

In that case, what @teppo said should do it (according to the docs in its support board): $pages->find("books.category=something, books.text=$letter");

Glad you find it useful ? Yes, thanks! This has been reported before but I've not yet had time to commit to the repo. Here's the previous post with the recommended fix ?

Hmm. I've never tried this but I am curious ProcessWire didn't complain about a custom field called 'name'. I would've thought that is a reserved word since ProcessWire pages field has a name column. Do you mean Select Options field (fieldtype)?

Great! Glad you got it sorted. Please explain what this means ? Zero? Wrong results? I'll try and replicate when I get a bit of time. Could you please clarify the field types in your selector? What is category and text?

Please explain, what is unusual? You have a data that is structured in an unusual manner or you think ProcessWire's database structure is unusual? If the latter, then many here will beg to differ ? Do you mean a page or module where you can view a page's data in this manner? Like in a spreadsheet? Or, do you mean a database that resembles a spreadsheet in its structure? If the latter, that's akin to a flat file database. ProcessWire uses a relational database. This model is not unusual at all :-). I don't understand this bit. What is the dilemna?

Your topic says 'pipe selector not working' There are two different uses of pipe selectors in your sample code. template=article|blog_post|book - OR selectors: matching one value or another (docs) title|body|author*=$q - OR selectors, matching one field or another (docs) Which one isn't working? Are you not getting any results or is it returning unwanted results? Are you sure it is not the AND selectors (docs) that are 'interfering'? Perhaps you want OR:groups (docs)?

Of course, you are right. I should have read the requirements more carefully :-).

This assumes only one field of type FieltypePageTableExtendedGrid is present on the page, no? ?

Yes, thanks. @horst found out the same and wrote this tutorial ?

Whilst I appreciate the inherent advantages, I'd like to point out that the forum rules/guidelines currently don't allow this. Edit I see @teppo beat me to it :-)