thmsnhl

@kongondo seems to be working without any issues! Thank you!

@kongondo, this is exactly what I would like to do. And yes, if it is a parent page, the whole branch would be invisible but I guess this is self-explanatory and maybe even a wanted behaviour in most cases. If you don't want English users to see the parent, most likely you don't want them to see the children too.

Hi @kongondo, my client (using a multi-language site) just created a page, that is not relevant to anyone outside of Germany and therefore deactivated the english Version with ProcessWires default settings ("Active?"-checkbox behind the page url in settings) and it seems like inactive pages do not disappear in navigations built with MenuBuilder. Is there a way to solve this, that I just didn't see or do I have to work around this? Kind regards, Thomas

Hi cosmicsafari, did you find a solution for this in the meantime? I am currently experiencing similar Problems and have no clue what to do about it.

Thank you Mobiletrooper, I haven't found this earlier but it looks like a solid approach! I will give this a try in the future.

Hi everybody, we started our first Processwire driven project in my new company and for the first time, I was working on one site with more than 2 colleagues on the same site. It didn't take long for us to stumble across some problems when multiple developers work at the same time, conflicts with updating the database on vagrant machines, like duplicate entries for page IDs, errors when setting up fields and stuff like this. We ended up working on a dedicated database server, that we linked to our vagrant machines and most of the problems were gone, but the performance of this constellation is really bad compared to our first approach with database running on vagrant machines. I already tried to find a solution in the forums but I couldn't find anyone with problems like this. So I was wondering: how do you manage projects with multiple developers on vagrant machines in a git-based workflow?

@kongondo First: thank you for your response and sorry for my delayed reply. I had some other projects crashing my work on that one. With your help I was able to render the menu also on localized sites. The code now looks like this: <?php $options = array( 'menu_css_class' => 'menu-lvl-1', 'submenu_css_class' => 'menu-lvl-2', 'current_class' => 'active', 'has_children_class' => 'has_children', 'current_class_level' => 3, 'include_children' => 1 ); ?> <?php echo $menu->render($pages->get("id=1930"), $options); ?> But: The menu does not show the localized page titles, those are still German. Am I missing anything else? Edit: I solved it, I just realised that I was missing the following option to translate the titles. 'default_title' => 1

I am currently getting a fatal error on a multilanguage site. On the german version, there is no problem, the menu is rendering just as expected, but when I try to open the english or dutch version I am getting the following message: Error: Exception: No menu items found! Confirm that such a menu exists and that it has menu items. (in /Applications/MAMP/htdocs/cleaninstall/site/modules/ProcessMenuBuilder/MarkupMenuBuilder.module line 959) #0 /Applications/MAMP/htdocs/cleaninstall/site/modules/ProcessMenuBuilder/MarkupMenuBuilder.module(87): MarkupMenuBuilder->throwError() #1 /Applications/MAMP/htdocs/cleaninstall/site/templates/partials/header.inc(110): MarkupMenuBuilder->render('main', Object(MenuOptions)) #2 /Applications/MAMP/htdocs/cleaninstall/wire/core/TemplateFile.php(259): require('/Applications/M...') #3 /Applications/MAMP/htdocs/cleaninstall/wire/core/Wire.php(380): ProcessWire\TemplateFile->___render() #4 /Applications/MAMP/htdocs/cleaninstall/wire/core/WireHooks.php(698): ProcessWire\Wire->_callMethod('___render', Array) #5 /Applications/MAMP/htdocs/cleaninstall/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\TemplateFile), 'render', Array) #6 The mentioned line 110 of header.inc looks like this: <?php $options = array( 'menu_css_class' => 'menu-lvl-1', 'submenu_css_class' => 'menu-lvl-2', 'current_class' => 'active', 'has_children_class' => 'has_children', 'current_class_level' => 3, 'include_children' => 1 ); ?> <?php echo $menu->render('main', $options); ?> The Processwire version is 3.0.62 and yes, I already checked if there were menu items in there and I also created another menu to confirm that the error persists.

Edit: I just realized there are 18 Pages in this thread and I am pretty sure someone else mentioned it, I will have a look I have just added the module to a new site I am creating and it seems like there are some issues. 1. The API key is not recognized when using the <script>-tag from module page (<script type='text/javascript' src='https://maps.googleapis.com/maps/api/js?sensor=false'></script>) – I had to add <script src="https://maps.googleapis.com/maps/api/js?libraries=places&key={{my API key}}"></script> in order to display the map. 2. The map in frontend does not look like the one in the backend. Instead of green areas for parks I get an all grey version, as you can see on the screenshots below. Has anyone else noticed this? PW Version is ProcessWire 3.0.62 from stable channel.

Well something like this is already possible, by creating a custom site profile and upload it to the server. It is less dynamic – compared to a textfield – but it does the trick. But even this solution does not install the Reno theme, because it's not a part of the site profile.

That's the first thing for me too and I just came up with an other idea: In the installation process, there is already a select field to set the color scheme (which I personally never changed, because the basic colors just fit perfectly). Why isn't there a selectbox to choose the Reno theme, to make it even easier for new users to recognize there is an alternative?

In the past weeks (rather months) I was discussing ProcessWire in our agency and I had some serious trouble convincing my colleagues. The main reason for their criticism was related to the old fashioned website frontend and the older fashioned default admin theme when testing ProcessWire. So I think there is a huge benefit in an overhaul of processwire.com and also in setting RenoTheme as default, but I guess that this won't change because of the upcoming admin theme.

@abdus perfect! That's exactly what I was looking for, thank you!

Thank you @Zeka for this thread I just realized that I had this already open in a tab but waaaaaay too far on the right hand side of the window, I will try to fit the example in to my project. But first I will have a look into GraphQL because this might also help me with future requirements.

Hi everyone, I've recently hired at a new company and here I am evaluating the abilities of ProcessWire for our projects. I was able to meet almost every requirement so far, but there is one point I couldn't find an adequate solution for: outputting data to json. I am aware of modules like https://modules.processwire.com/modules/pages2-json/ (which does not seem to work for me) but I thought with a function like wireEncodeJSON this should be much cleaner. What I would like to achieve is outputting pages with according field values into an array to use this within javascript. My first attempt on this was: $jsontestOne = $pages->find(1001)->children(); echo wireEncodeJSON($jsontestOne); which outputs [{}] and afterwards I tried that one: $jsontest = $pages->find("template=basic-page")->getArray(); echo wireEncodeJSON($jsontest); which outputs [{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},...] Maybe you can point out where my mistake is. Thanks in advance!