kongondo

Hi @Eric7, Welcome to ProcessWire and the forums. Have a read here:

There's a couple of approaches Unpublish you block pages: You will still be access them via the API with include=all in your -Page template. You would have to handle 404s in this case Redirect: Redirect access to block pages to -Page. SEO issues? Etc...(I've gone totally blank but there should be another strategy, I think )

Hmm...Tracy would have caught it, I believe .

I assume then that you did not have a debugger on then? . Would have saved you some headache.

Did you remember to activate pagination for the template of the page where you are using pagination?

So there's your problem then; $adresse_id is not being passed to callAdresse.php, for some reason. I've tested and it works just fine in my case. Edit Not sure where to go from here. Do you have a typo somewhere maybe? Debug errors?

Well that's strange. Hard to tell what's happening without seeing the whole context. Just to confirm, when the form is displayed, is the value of $adresse_id correctly output?

I was not referring to the display since you clearly stated the form displays. The issue is the other side, the server-side. I have never tried it, but I am not sure you can post to a relative URL like that. What is the server response (dev tools) after you post? What happens if you post to the full URL instead? i.e. /something/adressdaten/

Your form's action value does not look right: <form name="myform" id="myform" method="post" action="../adressdaten"> What is adressdaten?

Did u see this as well?

Hi all. For a while now been wondering how many would be interested in a backend and frontend shop catalogue built on top of PadLoper? I've previously spoken to @apeisa about this and his take is that there are no plans to develop PadLoper in this direction but he's happy to support such efforts. The gist of the backend shop catalogue is to provide one place (think ProcessModule) where you can manage your PadLoper products - add, edit, delete, track sales, etc without having to set up the underlying structure yourself. The frontend would be like a shop/webstore profile, a frontend cart basically, that's customisable. The shop would be 100% powered by PadLoper. This means that to use the 'shop catalogue' would require that PadLoper is installed. These are just loose ideas at the moment for a pro module. This might or might not see the light of day depending on feedback. Anyway, would love to hear thoughts, thanks.

ProcessWire will not allow you to directly access .php files in various folders, including /site/... See that post for the options available to you.

I'll let others, especially @apeisa, chime in with more thoughts but I can attest that: Yes I am not sure, but I think it can be done Yes For all of the above, you would need to write some code. Nothing out of the box. For #3, see example here.

There's a couple of showcased sites in the forums. RE frontend, there's nothing really like this is how a PadLoper shop would look like. This is because PadLoper is like ProcessWire - it gives you the tools to build whatever you want. My shop (see sig) uses PadLoper...but that is not a PadLoper template since nothing like that exists (although PadLoper ships with example template files to get you started). Backend: There's a couple of stuff that need to be setup (shipping, etc), but also, no, there is no online demo, to the best of my knowledge.

Yes. You have 30 days

Yes and Yes (last updated 12 Jan 17) .

Nothing dumb about the question. Of course you can still manipulate the $pages query per click. That's what you do here: if($config->ajax) { // process $trainingDetail here.. // ...some code // you page query here $results = $pages->find("template=basic-page, limit=10, sort=$trainingDetail"); foreach($results as $r) $array[] = $r->title; echo json_encode($array); exit; } // in JavaScript, do something with the JSON You need to be careful though about the server load in case there will be lots of ajax requests. Caching, client and/or server-side mitigates against that. Example Ajax request + $pages query in the Gif here.

This is a multi-part question, so lets try to break it down. The normal workflow resembles the following: Data is requested on the client-side. In your case, this is via ajax. You'll need JavaScript code to send the ajax request The request is either sent to the current page or to a named url, i.e. you could have a dedicated page to receive the ajax request You process the ajax request by sanitizing and whitelisting the inputs You send a response back, normally as JSON, but could be xml, or whatever JavaScript code receives the response and manipulates the DOM (aka updating the page without refresh) How Tos How to Work with Ajax Driven Content: 1, 2 See #1 See input, sanitize, + search forums using these terms for more examples . See #1 See #1

Depends on what you mean by... What do you mean by 'doesn't publish'? Are you talking about the backend, in the PW admin? If yes, then the code has to go in a Hook, either in an autoload module or somewhere like admin.php

@MaryMatlow, Have a look at this, this and this post plus the ensuing discussions.

@jmn817 The answer is right there 2 posts above yours . If Center_Image is a single image field, then yes, you could have accessed it like you do. If it is a multi-image field, then you need to access it OR them using a different approach. Further reading.

Here's a complete example from the module Blog.

Let's throw in one more... How about using created_users_id/createdUser? It depends on your workflow though. Who creates the users? How are they created? Same for their respective pages. Doing it manually would mean your client heading over to settings tab when editing a page and changing the created user there (would have to be first enabled in the template). This may not be ideal. You could automatically change the created user ID using the API via an autoload module, but that depends on how the users are created since you want to synchronise the two actions. The advantage of this approach is that you can give your user pages whatever name you want to give them. You would use it like: if($page->createdUser->id != $user->id) {// @note: here you'd also need to add logic to let superadmin and some editor to have access :-) // don't allow access } // in a selector $userPage = $pages->get("template=members, created_users_id={$user->id}");

Hi @jmn817, Welcome to ProcessWire and the forums. I am assuming all these are separate pages ('folders)': politics, 2017, 01 and 17? In other words, your tree looks like/will look like? politics 2017 01// child of year 17// child of month 18 19 02 01 02 // etc 2018 If you 'day' pages are created chronologically, and not too much in advance (e.g. no day 21 before day 18), and if they have their own exclusive template, the following should achieve what you want I think. <ul id="trending"> <?php //$root = $pages->get("/politics/2017/01/17/"); // get the 'day' page that was created last. @note the -created. $root = $pages->get('template=name-of-day-template, sort=-created'); $children = $root->children("limit=5"); $children->prepend($root); foreach($children as $child) { echo "<li><a href='{$child->url}'>{$child->title}</a></li>"; } ?> </ul>