adrian

Yes, of course I was thrown off by it working on dev server but not live even though both had identical codebase and db content. Thanks for the fix!

Unfortunately a complet ripoff of @benbyf's article: http://www.infoguru.org/2016/07/a-beginners-introduction-to-writing.html This reddit post is a little more positive as actually includes a comment from the @pksullivan15 who started the post you mentioned. https://www.reddit.com/r/web_design/comments/55ri93/ive_used_many_cms_in_the_last_8_years_lately_i/

In this case, Google recommends just in the head, or after the opening body tag:

An amazingly comprehensive survey on what's cool and what's not. http://stateofjs.com/ Here is the Table of Contents for the Results http://stateofjs.com/2016/introduction/ Take a look through all the sections in the above, but if you are in a rush, most PW folks would probably be most interested in the frontend frameworks section: http://stateofjs.com/2016/frontend/

Sorry @justb3a - another small but critical bug for you. Everything was working fine on my PHP 7.1 local dev, but when I updated a live server running 5.4, the Image Extra fields weren't being inserted. I have to replace this line: https://github.com/justb3a/processwire-imageextra/blob/master/ImageExtra.module#L1092 $out = preg_replace('/(<input\sclass=\'InputfieldFileSort\')/', $this->escape_backreference($outAdditional) . '$1', $out); with: $out = preg_replace('/(<input\sclass="InputfieldFileSort")/', $this->escape_backreference($outAdditional) . '$1', $out); Notice the change: \' to " Not sure if there have been some updates to PHP's regex engine between 5.4 and 7.1 that are causing this, but that is my guess. Anyway, that change seems to fix things, but I didn't test the Description field because I have that disabled, so it might be worth checking all regexes. You can see here: https://regex101.com/r/0kTOmt/1 how that initial version fails, but this one: https://regex101.com/r/0kTOmt/2 works. Hope that helps.

But: I am pretty happy with this solution - works for me anyways!

@szabesz - I just did a little thinking about this. I know this isn't what you want, but I wanted to clarify that the module does already correctly display field values in the language of the user. Unfortunately I don't really think it's feasible for this module to handle outputting multiple versions of something in different languages. Same goes for custom PHP - that would go against Ryan's desire for the description and note fields to be Markdown driven. I actually think you should be able to achieve what you are looking for using @kongondo's awesome RuntimeMarkup module. I use it in a lot of situations where I need more complex info for guiding clients. I know it doesn't output directly in the title description like you wanted, but you could place this directly below and it would almost be the same. Hope that sounds reasonable to you.

Thanks for your thoughts on those. I have a couple of weird things for you. Now even with description field rows set to 0 I still get a label for the Description field. Also, the input>text fields are now textarea fields - I think it looks kinda weird when you only want simple setting entries.

Hi John and welcome to PW! To expand on what Tom said, you might be looking for a head.php template file, or perhaps it will be in main.php or something along those lines. PW doesn't control your frontend markup at all, so there is no way to know for certain how the previous developer set things up, but what you are looking for a a template file that is included in all the page specific template files, or one that itself includes the other ones.

I knew I shouldn't have shared this module Let me have a think about these and see what the best options might be.

This looks awesome @justb3a - thank you! While you're on a roll, I don't suppose you'd like to add the ability to define the width of custom fields so we can float them on one line? The other thing that would really help would be an options type field with select/radios/checkbox options. Sorry, I know that's a lot - just a wishlist

Another possible use of this is pointing the user to edit another related page by making use of the ID of the related page, eg: Test link to [Edit Parent](./?id=[page.parent.id]) which looks something like this: Anyway, there are lots of possibilities for enhancing the content of your Description and Notes text.

Thanks @Robin S for looking into this. I am bad about not remembering Windows path issues. For the most part they seem to be handled quite well by PHP and don't actually need "DIRECTORY_SEPARATOR", but I think the issue is when you're doing replacements. Could you please test removing your str_replace line and modifying 303 to the following which uses DIRECTORY_SEPARATOR on the end instead of the forward slash: $compilerCachePath = isset($this->config->fileCompilerOptions['cachePath']) ? $this->config->fileCompilerOptions['cachePath'] : $this->config->paths->cache . 'FileCompiler' . DIRECTORY_SEPARATOR; If that works as expected, I'll try to make similar changes throughout Tracy to deal with the mixed forward/back slash links like in the Template Resources panel.

I have been using this module for a long time and it's been incredibly useful so I thought it was time to share. It's great for fields where you want to instruct content creators to reference something about a the page, its template, or its parent, or grand parent, etc Specify fields/properties of the page in your field's Description or Notes content, eg: [page.parent.url] [page.title] [page.template.label] You can also define a str_replace to be performed on the returned value, eg: [page.name.(-|_)] which will return the page name with the dashes replaced with underscores. An option to allow raw HTML is available. You can also use hanna codes within your description and notes fields - big thanks to @Robin S for this idea. http://modules.processwire.com/modules/dynamic-description-notes/ https://github.com/adrianbj/DynamicDescriptionNotes/ Hope you find it useful.

Working here on Chrome on MacOS, but I should note that I can't get it to find any matches no matter what I check

just try: roles=1015

Yeah, that does work but it does seem weird that the selector using the roles "name" populates the select options properly but just won't save.

I can confirm the same problem here although not sure why at the moment. As a quick fix, I discovered that it works if you use this: return $pages->find("template=user, roles=rider"); in the "Custom PHP code to find selectable pages" option instead. Can you please check that works for you? It would also be great if you'd consider posting an issue report about the custom selector option not working: https://github.com/processwire/processwire-issues

roles.name=rider

Great - I have pushed that version to Github.

Could you try the attached version (just replace this .module file). ProcessCustomUploadNames.module

@JoZ3 - sorry about the trouble - what version of the module did you upgrade from? That curly brace was added for PHP7, and I tested on 5.6, but maybe there is a problem with 5.3. I am sure I can write it a little differently to avoid the problem on 5.3, but just want to make sure that's definitely the issue.

Hi @Juergen - sorry, not sure about your issue, but looking at the contents of your page table, I couldn't help but think this new module by @BitPoet could be a much nicer replacement:

Latest version supports: Column selection and ordering for CSV export. Exported rows also respect the Find filters that have been applied. Should be very handy for clients to be able to extract relevant info from large table datasets.

Have a read about WireCache: http://processwire.com/blog/posts/processwire-core-updates-2.5.28/#wirecache-upgrades