adrian

Bit of a longshot, but any chance the 2016 page is not activated for "fr" ? I get the same result as you if I uncheck the "active" checkbox on the settings tab.

Hi @Rudy, It's working for me here on a ML site. Is it actually redirecting to a blank page, or not redirecting at all and just showing no content? Is $page->child()->url returning the correct url to the first child?

Do you have suhosin running on the server? If you do install Tracy, use the PHP Info panel to check for Suhosin.

@vwatson - I assume you got this sorted out - could you explain what you found, or if it's still a problem. Thanks!

All sorted - I published it which actually requires: More > Move https://en.wikipedia.org/wiki/ProcessWire

I am back to the default theme for the moment and just noticed that you can't use Modules > Site > Add New when AoS is installed.

Thanks @tpr for those fixes. I am not sure about the save buttons and search box. Let me think about that. In the meantime there seems to be a problem with ASM and the default theme with AoS enabled. When you drag an item it appears blank until it's been dropped. It seems fine with Reno though.

Then you should be fine

Are you still getting the SQL warning?

Probably would have taken you less time (and therefore less cost to them) to update PW to 2.8 than to debug the issue with 2.3 Sorry to hear their not sticking with ProcessWire Maybe if they saw how the recent versioned worked, they'd be more inclined to stay with it.

Genuinely curious on their reason for this - seems like the opposite of what most people would want.

I would try the session fingerprint config setting. Start by setting it to false and if that works you can try to make it more secure after that: https://github.com/processwire/processwire/blob/36984e4a057268b7a45b848e1b3b6ee757583459/wire/config.php#L241 Obviously make the change in your site/config.php file, not the wire one I pointed to.

Nice work! Just in case you would find it cleaner, you can use this version in your site/init.php file rather than setting up an actual module. Sometimes this approach is nicer than having lots of different little helper modules. $this->addHookAfter("ProcessTemplate::buildEditForm", function(HookEvent $event) { $languages = $this->wire('languages'); $template = $event->arguments[0]; $form = $event->return; $field = $this->modules->get("InputfieldText"); $field->attr('id+name', 'seo_rules'); $field->attr('value', $template->seo_rules); if($languages) { $field->useLanguages = true; foreach($languages as $language) $field->set('value' . $language->id, $template->get('seo_rules' . $language->id)); } $field->label = $this->_('Seo rule'); $field->description = $this->_('If you want to add a custom rule to MarkupSEO'); $field->notes = $this->_('To define a variable use {title} syntax'); $form->insertAfter($field, $form->tags); $event->return = $form; }); $this->addHookBefore("ProcessTemplate::executeSave", function() { $template = $this->templates->get($this->input->post->id); $template->set('seo_rules', $this->input->post->seo_rules); $languages = $this->wire('languages'); if($languages) { foreach($languages as $language) { $template->set('seo_rules'.$language->id, $this->input->post->{"seo_rules__$language->id"}); } } });

I know this is a Reno thing in general, but I wonder if AoS could get rid of the large page titles and put them back in the breadcrumb like they are in the default theme - it just seems like such a waste of vertical space. vs

Thanks again @Robin S - seems like you have looked into this a lot more than me I see now that the sort field in the field is actually correct, but as you said, is not available as a property from the API.

I am not sure exactly what you want to do, but if for example you want to show the 10 most recent posts with their titles and summaries, I would use the selector to get the pages/posts as the children of the Posts parent, so something like this: foreach($page->children("show=1, limit=10, sort=-published_date") as $post) { // output $post->title, $post->summary etc for each post } Is that what you are looking for? BTW, I would use the key of the "show" options field, rather than the label, but it's really up to you.

Apparently I do that without realizing it Thanks for removing the shift hotkey - the ALT+d is good to know.

Wow - you are completely right. It's so weird that the sort db field for the page table field just matches the sort value of the actual pages. When you re-order the entries in the page table field it seems to recreate all the rows in the new order, but without changing the "sort" field value. I wonder if this was intentional or an oversight?

I think you should deal with it now. Take a look at the "modules" database table via PHPMyAdmin (or similar) and see if there are in fact more than one entry in the class field/column for ProcessLogger. You should probably just be able to delete one of them to remove the error, but I would like to know why it happened in the first place. Was this a completely fresh install with a new empty database?

I don't mind it auto-focused on the modules/templates/fields pages, but on the page edit page where there are other fields it suggests that you need to do something in it first. Perhaps it would even be ok auto-focused if they search icon was still displayed so you knew what it was for. On a related note, I am having some frustration with the search box in the Reno compact header autofocusing (or triggered by some key action - I am not sure). I am noticing when using the Tracy console panel and strangely often when I type $page->field etc - it gets to "$page-" and then the cursor moves to the search box and the ">field" end up in there instead. Is it me, or something that can be tweaked?

Yeah, this is what I get where "items" is the name of my pagtable field.

Both of these will find the same pages: $pages->find("show=1")); $pages->find("show.label=CTRL Daily");

You should be able to use the built-in "sort" field exactly the same way.

Sure - perhaps you could show me the code you have so far so it will be easier to modify to add the sort value back in.

Something like this: foreach($page->children() as $child) { echo "<p>{$child->title}</p><p>{$child->text_area}</p>"; } You can also use a selector in the children() method if you want to limit which child pages are shown, or to sort them, etc.