Sebii

Hi, under each template setup, you can find the "Show in the add-page shortcut menu?" option under the "Family" tab. I think if you disable this for all, the button will also disappear. I hope this helps.

Hi, as the user can have multiple roles, I think you should not check it against a specific role. For dynamic sitemap, $page->viewable() should do it. Telling you if the current user is able to see this page. Or using $user->hasPermission($permission, $page) in case you want to check it from a user other then the current one. Edit: In case you want to do the whole selection of pages from a specific users perspective, I think this should work (untested): $currentUser = $user; $tempUser = $users->get('guest'); $users->setCurrentUser($tempUser); //do your page selection $users->setCurrentUser($currentUser);

Hi, I think your question has already been answered in a different topic here: https://processwire.com/talk/topic/11955-page-field-based-on-parent/ As suggested there, you might even want to use the AJAX way by using the custom selector (instead of custom PHP). In your case that should be something like: parent=page.project_research_field_selector I hope this helps.

Parent might really be a limitation as of few other topics I read trough... Maybe this is the way to go for you, using a hidden field: https://processwire.com/talk/topic/9406-inputfield-dependencies-hide-field-by-path/#entry90591

Hi, I think what you are looking for is available in the configuration screen of the field. (Under Input > Show this field only if...) You should be able to specify also the parent condition here (never tested): parent=123 //or any similar selector for the parent like: parent=/path/to/parent/ Hope this helps

Hi, from technical point I don't see much of a problem for both solutions, however the UserSelect within the pages might need some additional logic to make sure, a user is not selected in multiple pages. I think this question should rather go to the Client to confirm which way they intent to work. (Do they rather want to manage the users per page or do they want to manage page per user?) In extend, with some hooks and some magic it should also be not too hard to implement a combination of both, make it possible to manage it in both, the pages and the user.

When editing the pages (homepage and one of the not-working sub pages), you can go to the "Settings" tab and verify under "Who can access this page?" that the access settings are done right and inherited properly. It should show for both, that at least "guest(everyone)" can "VIEW" the pages. Other then that... I'm out of idea. Could you maybe explain what happens exactly when logged out? You just receive a blank page, or are prompted to login, or smth. else?

As Ivan suggested, did you check if your pages are in "Published" state? (Edit a page and see if you have the Publish button) Other causes could be that you installed a modul that prevents from "guests" to visit any page like the maintenance mode or protected mode modules? Also check if your templates have the correct rights set, so that the guest user is generally allowed to view the template's pages. Hope this helps.

Hi, I think you might want to combine it with: $config->httpHost

Hi, in general, processwire has a very clean an "simple" API. So it has a very easy learning curve and you get result right away. I think after you got the basics of PHP it is very helpful if you just start working with it(and PW). The documentation has so many examples and codesnippets that lots of stuff can really be learned by just doing it. And the more you struggle with a specific problem, the easier it should also be for you to dig into more specific tutorials that help you advance with it. Also the community here is very helpful and friendly and even answering some rather basic PHP questions if they come up from time to time. Ok, enough written, here is also a link of nice page that might help you proceed in writing good php code: www.phptherightway.com Hope this helps you a bit to go on Greetings

You have to place a new CSS file with the overwriting rule in this modules "dynamic script & styles folder" (The new CSS you meantioned in your post). In the configuration screen of the module, you can now select for which Processes these scripts &styles (your new css file) should be included/added to the rendering of the admin page. I'm not 100% sure how the Process is named that you are looking for, but I guess smth like ProcessPageTree or similar is what you need to activate it for. Edit: Actually it should be the ProcessPageList.

That's not necessarily what I meant. Your solution should work too, but I think you don't need to do this extra copying. $items = $pages->find("template=product, title|body|options.title*=$freetext); E.g. if the user searched red, you can search within the fields of the product itself (e.g. title and body), aswell as in the fields of pages from the pageselector (e.g. options.title). This should be what you are looking for or did I miss something? What I meant regarding usage of 3rd party search is mainly regarding typos, result preview text and similar things that are offered e.g. when searching with google and co.

Hi, I always find searching a tricky topic. Depending on the requirements you might even want to consider using a 3rd party search engine for much better results. However, if you have a clear page structure and you only want to search a specific field in a page selector field. You should be able to just use it like this for example: $items = $pages->find("template=product, options.title*='red'"); //assuming "options" is the page selector field and you want to search the title And even if it is more complex you might consider using sub-selector or (since 3.x) even nested selectors as described here: https://processwire.com/api/selectors/#sub-selectors I hope this helps

Hi, unfortunately, I don't have experience with the user template change. But I assume you followed the description of Ryan from here: https://processwire.com/blog/posts/processwire-core-updates-2.5.14/ ? Maybe you can make sure that everything was configured as described, especially the site/config.php part. Also in the hope that everything stayed like that in 3.x However I also had this redirect problem under other circumstances, where a Page could not be created but the error was not properly handled in the code. Did you check the log files, maybe they give you a hint on the error/problem that is happening here?

I think the mentioned change it not part of the discussed module, but really a change of a core module. So that's not the problem. @ottogal: You can try to use the AdminCustomFiles module (https://processwire.com/talk/topic/7588-admin-custom-files/) and just place a CSS file that overwrites this rule as you mentioned in your post already. This should work if I'm not overlooking smth.