anyway

That works! Simple, as always. Thank you!

Hi, I'm trying to exclude a field on a certain page in the backend using the "field dendencies", but I don't succeed. I need something like this: Show this field only if the page ID is NOT 1001 Variants of this do not work: page_id!=1001 Thanks!

Thanks a lot for the hints, Soma! Everything works now as expected. I misunderstood the concept of' show_root' => true,

Okay, thanks a lot for your help, bernhard!

Hi, I have a tree with 3 sublevels and I'm trying to build a sidebar navigation that shows the children when there are children and the siblings when there are no children. The code below doesn't seem to work for me.... the output is alway the complete tree, on every page. <?php //sideBarMenuNav change items to view if($page->hasChildren) { //we are on a first level parent page so show sencond level $entries = $page->children; } else { //we are on second level so show siblings to actual page $entries = $page->siblings; }; $sideBarMenu = $modules->get("MarkupSimpleNavigation"); $options = array( 'current_class' => 'current-menu-item', 'has_children_class' => 'has_children', 'max_levels' => 2, 'collapsed' => false, 'show_root' => true, 'outer_tpl' => '<ul class="menu vertical sidebar_menu">||</ul>', 'inner_tpl' => '<ul class="menu vertical nested">||</ul>', 'item_tpl' => '<a href="{url}">{title}</a>', 'item_current_tpl' => '<a href="{url}">{title}</a>', ); echo $sideBarMenu->render($options, null, $entries ); It is the approach of mr-fan, from here: What's wrong with my code? The contents of the variable "entries" are correct, for each page level. Thanks!

Thank you bernhard! You're right, it's a general problem related to touch and non-touch devices and with javascript you can prevent clicking on the "real" link. However, I am still confused about the page structure. Don't I need a page in the tree to provide the trigger link and then another one for the first link in the dropdown, which would actually be one and the same? I don't know how to explain this differently than by the two trees I have shown above. What I'm trying to figure out is: Do I need the parent page twice in the tree, which is probably a bit of nonsense, or can the menu be built that the parent link appears twice - once as a trigger and once as a link in the drop-down list. I'm sorry if I express myself in a complicated way and ... my PHP skills are somewhere between beginner and intermediate level

I have now spent a few hours doing some research in the forum, but I can't get any further with a fundamental question. What is the best practice in Processwire with regard to trigger links for dropdowns, as can be found for example in mobile navigation. With desktop navigation, I can use a link as a hover for triggering the drop-down, as well as a click that leads to the linked page. The question is, if this is good in a view of usability, because it doesn't work with a mobile drilldown navigation and some users don't realize that you can also click the trigger link. The tap always triggers the submenu. The question arises if it is not better to place the parent link always at the top of the drop-down list, too. This would then work in both desktop and mobile navigation. What would the best practice solution in Processwire be? Is there a way to place the parent link at the top of the drop-down list? I had already asked this question in the MarkupSimpleNavigation module area, but I didn't get an answer there. Maybe this cannot be realized with this module? And which page structure would make the most sense for this? Should the parent page be hidden for the trigger? It probably wouldn't be so nice. Wouldn't it be best if all pages in the page tree containing content? So my question is two-part: Which page structure is necessary for navigation where the parent is in the dropdown and how do you build such a navigation? There are certainly already robust concepts for this. It's probably just a matter of my understanding. I'm currently building a page tree, what partly schematically looks like this: |-- Link +-- Parent |-- Child |-- Child +-- Parent |-- Child |-- Child +-- Parent |-- Child |-- Child Is it possible to repeat the triggering link of the drop-downs (which should not link to the parent page) inside the dropdowns, where it links to the corresponding page of course? |-- Link +-- Parent (Trigger) |-- Parent |-- Child |-- Child +-- Parent (Trigger) |-- Parent |-- Child |-- Child +-- Parent (Trigger) |-- Parent |-- Child |-- Child Thanks for your advice!

Hi guys, I'm currently building a dropdown navigation to map the page tree, what schematically looks like this: |-- Link +-- Parent |-- Child |-- Child +-- Parent |-- Child |-- Child +-- Parent |-- Child |-- Child Is it possible to repeat the triggering link of the drop-downs (which should not link to the parent page) inside the dropdowns? The parent link for each submenu should appear again at the top of each submenu. |-- Link +-- Parent (Trigger) |-- Parent |-- Child |-- Child +-- Parent (Trigger) |-- Parent |-- Child |-- Child +-- Parent (Trigger) |-- Parent |-- Child |-- Child It would be great if this could be solved with MarkupSimpleNavigation? Thank you!

You're right, it looks like a javascript error, but the console does not show any errors. After the click, the elements appear to open (the three dots disappear), but the accordions doesn't drop down.

@gmclelland Thanks for your reply! Yes, the user's role has the page-edit permission. In the meantime, I've been able to "solve" the problem by giving page-view access to the system template "admin" to the user role Page-View, which is probably not optimal. @Robin S Unfortunately, your code doesn't work for me. The repeater elements can no longer be opened. There is only a short twitch when you click on the elements. Any idea? ProcessWire 3.0.62

I have completely uninstalled and reinstalled the module, now. I also emptied the module cache. The error still exists. I'm greatly appreciated for any hint.

Strange thing: If I give the user the same rights as the superuser, the error will still persist! There is also a second error: ProcessWire: The requested process does not exist

Hi, I'm using the module "AssistedURL Field" inside a repeater. It works fine when I'm logged in as superuser. When I'm logged in with restricted rights (user account), I get this error when I click the button to select a URL: Modules: Error initializing module: ProcessPageEditLink - You don't have access to this page The error appears within the appearing modal window of "AssistedURL Field" in which the URL or page can be selected. What am I missing?

Hey, that worked! The page is now displayed and all error messages are gone. 1,000 karma points for you, dragan, you saved my weekend!

Thanks for your superfast reply dragan! FTP upload should be complete. I have repeated the upload 4-5 times. How can I explicitly refresh the module cache? Thanks for the codesnippet!