Juergen

Works fine now! Thanks!

Hello Adrian, I have got the following error message after trying to add a child page. Can you check this please. PW 3.0.33, latest PageRename Module version, the child page is excluded in this case. Thanks

Maybe the reason was that I have put the search fields into a string. $downloadfields = "downloadrepeater.downloadfiledesc|downloadrepeater.downloadfieldtitle"; After that I have added this variable to the search tag and then I got the errors. "$downloadfields~=$q" Now I have added it manually to the search string and now everything works fine. "downloadrepeater.downloadfiledesc|downloadrepeater.downloadfieldtitle~=$q"

I have tried to include a repeater field called "downloadrepeater" with the included fields "downloadtitle" and "downloaddesc", but including these fields leads to an error: Exception: Unknown Selector operator: '' -- was your selector value properly escaped? (in /home/.sites/24/site1275/web/wire/core/Selectors.php line 307) I have included these fields like that: "downloadrepeater.downloadfieldtitle|downloadrepeater.downloadfiledesc~=$q" After removing these fields from the search query everthing works fine again.

Oh I understand the functionality behind the scenes ! Thanks for the explanation.

How can I disable some templates from the search? Is this the right way to exclude the template "profile" from the search results? $result = $paginator(array("template!='profile'", "headline~=$q", "introtext~=$q", "body|whatever~=$q" ), $input->pageNum, 25);

It would be great if this kind of search would be possible (like in Joomla Search engines). Fe check first in headlines, second in introtext, third in body. Result order depending on the matches found in the fields. Matches in headlines are higher ranked than in introtext than in body field. Unfortunately I have also no idea how to realize such a search ranking. Maybe someone has found a working solution and will post it here.

Yes!!! Problem is solved! Thank you so much.

Message from Dumps Recorder: Doesnt return anything.

Nothing is returned. Fatal error: Cannot use object of type ProcessWire\LanguagesPageFieldValue as array in /home/.sites/24/site1275/web/site/assets/cache/FileCompiler/site/modules/TracyDebugger/ProcesswireInfoPanel.inc on line 316 Only the line number has changed from 315 to 316.

Hello Adrian, I use Tracy Debugger 3.0.0. Unfortunately there is nothing specific on that pages (the first is the homepage with a slider, and the second ist a page with a pricelist). They have nothing in common.

Hello Adrian, on some of my pages I get the following error message on the frontend: Fatal error: Cannot use object of type ProcessWire\LanguagesPageFieldValue as array in /home/.sites/24/site1275/web/site/assets/cache/FileCompiler/site/modules/TracyDebugger/ProcesswireInfoPanel.inc on line 315 The Tracy bar will not displayed on that pages. Best regards

Yes I have reported it on Github: https://github.com/ryancramerdesign/ProcessWire/issues/2031 Best regards

Hello tpr, I use the latest version of AOS and today I have discovered the same problem with long titles by templates (static header at the top, Reno Theme) As you can see the long headline of the template edit screen floats below the save button. It is the same problem as we have with headlines by articles in the past. You have solved this by limiting the characters of the headline. Best regards Jürgen

Hello Adrian, Tracy makes problems during updates of modules if it is in strict mode (show warnings as errors), because there are several warnings of the PW core files. I use it in strict mode and I always have to disable Tracy Debugger if I want to update a module. Otherwise the module will not be updated if I skip the warning. So it would be a nice addition if you add an enable/disable link for Tracy Debugger at the bottom like AdminOnSteroids module (see image below). This makes the workflow much easier. Best regards

Roland this looks really great!!!

Here is another issue if the headline is very long. As you can see the distance between the save button and the headline is very small. If you add following CSS snippet you can increase the distance a little bit more. #head_button { margin-bottom: 0 !important; } Here is what i looks like after inserting the changes: Its not a big problem but it looks like much better. Best regards

Hello @ all, I use this technique to link directly to a pagetable field. Unfortunately images will be loaded but not be displayed in this case. Can someone confirm this behaviour? Another problem is that you have only a save button without the functionality of the drop down (save and go back to the page on frontend). So the workflow is not so good as loading the whole page. Best regards

Wow! This looks absolutely awesome and is exactly the way I like it.

The editors only translate text and therefore they dont need this feature, because I use language tabs for translations of fields. I use your language switcher fe to check if all the page labels were translated and so on. In general I use it to check if the admin section is understandable for non native speakers as well, because some editors have another mother language and this makes it (only for me as superuser) much easier.

Maybe the opportunity to select userroles which will see the language switcher would be a good addition. Its more important for admins or superuser than others.

Maybe a hook could be an option. Create a module and add a hook "before save". You have to check for the field (fe. body) first. If it is the right field, then check for internal links. After that try it with a foreach loop to grab all installed languages (foreach languages as language). Here it will get tricky. Maybe you could grab the id out of the anchor? Replace the anchors by id if it is present in other languages too. It was just a thought and I dont know how to realize this, but maybe you have an idea.

Hello tpr, z-index man is back with a new z-index issue concerning the date/time inputfield. As you can see the date/time picker div will be overlapped by using the static header. The CSS used for this inputfield: .ui-datepicker {z-index: 100!important} So you have to add this line of code also to your Stylesheet with a higher index than the static header divs and the important addition. This is what it looks like with a much higher index: Best regards the z-index man

Perfect! Maybe its on the time to rename the module as well: TprOnSteroids

Hello Horst, thanks for your prompt answere. The page under Admin > Pages was missing. I have reinstalled the module and now everything works fine. Thanks!!!!