Klenkes

Just did that. https://github.com/processwire/processwire-issues/issues/914

This is a weird one... - This is a multilanguage website with PW 3.0.123 (but same problem with 3.0.98) - Default language is german, second language english. - Fieldtype Datetime As soon as I change the Date/Time Input Format to a german format (8. April 2019) the field on a page will only save the value if I set the backend language to german. If set it to english(my default) the field won't save the date! Either the field is empty or it defaults to todays date. (Depending on the setting of the field) It doesn't matter what picker is used. It doesn't matter if "Default to todays date" is set. It also happens on PW 3.0.98 It's a matter of backend language and custom input format. Am I missing something here... Edit: Why is it that as soon as you write the forum post you find a solution? If I leave the fieldsettings at default and only change Date Input Format Code to, lets say: d-m-Y it works. Still... weird.

Thanks again @Macrura I did it exactly like in the post above. Some pages in a loop and the pages in /admin/repeaters/ I changed the status directly in the database. There seem to be no sideeffects... Solved!

Thanks a lot for this hint! I mirrored the complete website(10 GB sigh...) to local. This way I can test without breaking the live site. I will check with a fresh mind tomorrow. Everything I could expect today would be mistakes.

Sorry for the post title, I don't know how to describe it in short, and the problem is difficult to explain. On a clients big website Google WMT pointed out to me that some URLs are not crawlable. I found out that the pages in question end like .../for-page-2095/ WHAT? Some 1.5 years ago I created a repeater for a FAQ, and at that moment PW created pages with the wrong template at the wrong places. I checked the created dates and they match to the second. Those pages have a template baustoff-artikel and are children of the same template which was set to not allow children! The parent is one page among 2000 others and I cannot see why this page was chosen as a parent. The parent should have been in /admin/repeaters/ and some some pages are there, but with the wrong parent as well. However... I am unable to delete those pages, neither through the admintree, nor through the API. I am able to delete the parent page Steinplatte ArtNr 1590, but then I cannot empty the trash! Error message: This page may not be deleted Some screenshots: The parent with the template baustoff-artikel which is not allowed to have children: The pages in /admin/repeaters/ The wrong pages have nothing to do with the repeater locations. I have deleted the Repeater that caused this, and want to delete the orphaned pages. I am extremely puzzled and a bit traumatized and have no idea what to do next. If anyone has any idea or experienced something like that I would be grateful for a hint. (PW version back then pre 3.0.98 and now 3.0.98)

You already said it, it depends... I never go without ListerPro because listing, editing, searching and filtering is so easy, even for inexperienced editors. Since I hate doing forms by myself I use FormBuilder in almost every project. From the ProFields package Table and Multiplier (some of them unfortunately not multilanguage capable)

If you set the HC to PHP, you would have to echo your HTML of course, or concatenate and then echo it. <?php $out .= '<div class="seo-block seo-interviews">'; $out .= "<h2>{$heading}</h2>"; $out .= '<ul>'; foreach( $interviews as $one ){ $out .= "<li> // ... </li>"; } $out .= '</ul>'; $out .= '</div>'; echo $out;

No, wait, I started over. Seems that the only way to collapse groups is through the Tags Manager, and check the Display as collapsed in field list at the bottom. Robin S was right.

mhh... seems to me that an underscore prepended to the tag name colases the group. _Meta But then all tags have to be prepended.... not very user friendly. This makes out of a tag called Meta now Meta_Meta and copies the group, but collapsed. So I ended up with two goups named Meta, one opened and one collapsed.

In the settings of a field, in Advanced tab, we usually could group fields by tags and then prepend a - to a tag. Then the group appeared collapsed in the backend. I recently noticed that this doesn't work anymore. No matter what I try, a -Meta shows a second group named also Meta. In 3.0.98 it still works but not in 3.0.119 AdminTheme doesn't matter. No JS Errors. Was there any change I missed? Forgot... template gouping and collapsing works!

Sometimes I wonder how I tie my shows in the morning... thinking way too complicated So many years and I love Processwire even more every day! Everything I need is already there. I do it in the backend with two fields(text) and FieldtypeRuntimeMarkup generates urlencode($page->encodekey)) and so on... and the result is the complete URL for the editors to copy. And even a button to test it! $prefix = $page->httpUrl . '?'; $l_key = urlencode($page->encodekey); $l_title = urlencode($page->encodetitle); $gclid = '123456789'; $result = '<textarea rows="5">'.$prefix . 'keyword=' . $l_key . '&title=' . $l_title . '&gclid=' . $gclid . '</textarea>'; return $result;

Thanks. The problem is that editors would have to write this in a Google tool?(I don't know...) and I can't urlencode it in a template. Perhaps I write a tool for them or they use an online tool for the encoding. But GET parameter seem the better option.

Yep! Thanks. I forgot about that. Works with Processmodules too.

A client wants to use landing pages coming from Google ads, and needs to hand over a keyword and a title for the landing page. The URL would look like this: ..../l2/keyword/Funny title with løts of special chåracters änd spaces/ (Just an example) I tried to encode the URL in different ways but not even spaces work and result in a "404 Page not found". Then I found this Github issue: https://github.com/processwire/processwire-issues/issues/720 At least I know that I am not the only one with this kind of problem. The client is a very pragmatic fellow and suggested to custom-encode the segments like: (don't try to read it) ..../l2/keyword/Funny_S_title_S_with_S_l_o1_ts_S_of_S_special_S_ch_a2_racters_ae_nd_S_spaces/ and then replace all the _S_ _a2_ with the REAL characters in the template. Mhh... well... sure I could do that, but I don't like it, and editors would have to write the segments with a translation sheet! Anyone have a better idea? PW 3.0.98 PHP 7.x

For now I did the unthinkable... I changed a core file, and it breaks my heart Since the function isn't hookable I had to edit: /wire/modules/Process/ProcessCommentsManager/ProcessCommentsManager.module In function processComments I added twice: $page_to_save = $comment->getPage(); $page_to_save->save(); Poorly done... but I don't know better.