adrian

I had the same thought actually - thanks for bringing it up here. I do feel like in particular with module settings that it's something that shouldn't be hard to populate all languages with - it's not the same as new pages added to a site where you really can't enforce a site editor to populate all the alternate language values.

Thanks for testing. I have done the same here and can confirm your results. The problem is that I don't think PW has an inbuilt method for handling fallbacks for module settings. Because modules settings don't return an object you need to explicitly get the required value based on the user's language. I could write something custom in this module but I am curious if any of the ML experts out there have dealt with this when they have module config fields that have: 'useLanguages' => true

Love it ?

I have looked into OpenCollective and even suggested it to @tpr for AOS - the problem is that they require you to have 100 Github stars on a project before they'll accept it. So if you guys want to help out, send some star loving ? Obviously the PW core could get involved, but I don't think there are any modules with 100 stars yet.

Hi @martind - sorry about that. I am not sure when this started happening, but I feel like PW's file compiler is no longer correctly dealing with adding the namespace to classes in modules. Anyway, I have implemented a fix - please check the latest version and let me know how it goes.

Hi @iank - sorry about that - I honestly never tested this in a ML environment. Could you please check if the French values show if they are entered? If so, then we just need to make the fallback to default work if no alternate language values are entered.

Have a go and if it goes well, great, and if not, I'll try to find some time to pick up where you get stuck and get it working.

Hi @masslevel - Table field support could certainly be added to BCE. It already supports other multi-value field types using a separator like: | You could add code for Table fields here: https://github.com/adrianbj/BatchChildEditor/blob/339624b0a14a9f403ae73b37a08f3e0f5f8d6136/BatchChildEditor.module#L1608 You should be able to find the code you need here: https://github.com/adrianbj/TableCsvImportExport/blob/a4e6ad668fd92f668546ba62cf726d29871b6d05/TableCsvImportExport.module#L341 If you can add this, I'd be happy to accept a PR for BCE.

Hi @bernhard - I have upped them to 9999 here locally - I'll commit it to the next version. Hi @rick - that might be possible, but I am curious about why you want this - for me it's about quickly and temporarily getting every Tracy related hidden so I can see what's behind on the main page content.

Check out pw-remove in the Removing elements section of this post: https://processwire.com/blog/posts/processwire-3.0.49-introduces-a-new-template-file-strategy/

Take a look at this post (https://processwire.com/talk/topic/19024-selector-arrays-with-page-reference-fields-with-and-not-or/?do=findComment&comment=165462) and the rest of the thread. I really like the concept of selector arrays and they can make things much more readable and avoid concatenation stuff, but currently they can be a little tricky to get things how you want. Hope that helps.

Thanks @tpr - very generous of you to spend your time doing this! The ".pwcmb--top_push" class is no longer used - it was an option but it never seemed to work, so I removed the config option but never got around to cleaning up the other parts - thanks. Agreed, I don't see that cookieMonster.cfg.block being used anywhere. I have tasked someone else with testing this version - making sure all the GTM events fire as expected, along with the basic functionality, but if anyone here also wants to check, that would be awesome. Once we're sure everything is working, I'll incorporate into my repo (I'll get you to do a PR). Thanks again for this - I am sure many folks will be very appreciative of this new version!

Thanks ? It's a decent start, but I am kinda hoping for some contributions from the community for improving it. It's all available in the docs folder (markdown files) in the repo and anyone can edit and submit PRs. I think a nice Tips & Tricks section would be beneficial, as would improvements to the rest of the docs.

TracyDebugger's Console Panel - https://adrianbj.github.io/TracyDebugger/#/debug-bar?id=console

That should work just fine:

PHP is not properly running on the server. If it's a fully managed server I suggest to submit a ticket to get them to fix it. It could be that the apache handler for php files is not configured, but there could be other issues as well.

I know lots of us enjoy using them and I think it would be a worthwhile addition to Migrator. I bet it would be much quicker to extend Migrator than to look for other options ? Maybe at some point in the future I'll find some time to look at adding it. It supports all the other ProFields, so it makes sense to include it as well.

You can also just use: $this->wire('page') $this->wire('mail') etc inside the hook function.

HI @Karinne Cyphers - glad you narrowed it down to the Repeater Matrix field. The Migrator module was built before that fieldtype existed and I haven't had time to add support for it. It already works for standard repeater fields though, so it might not be a huge amount of work to implement Repeater Matrix, but unfortunately I don't really have the time at the moment. If you have the time / skills, perhaps you could take a look and provide a PR?

Yes - as an example: drwxr-xr-x 9 ajones staff 288 Aug 6 09:36 wire Since you playing around this panel and given your experience the Diagnostics module, I wonder if you have any thought about the Status and Notes that are being returned? Also, have you looked at the Filesystem Files option?

Hi Steve - thanks for finding and debugging this! Testing here on MacOS and it doesn't make any difference for me. Both versions return: but if your version works for you, then it makes sense to replace it. I have changed locally and I'll commit with the next version sometime soon.

Hi @Karinne Cyphers - it's hard to debug that error because I don't know where it is originating from. If you could install TracyDebugger you should get a full stack trace of the error so you can point me to the line in the Migrator module that is the origin of this. I expect it is a fieldtype I haven't tested with, but won't know for sure until you can track this down for me.

Yeah, without a template.php file ProcessWire doesn't know how you want the admin template rendered - what fields do you want to output where and in what structure and with what CSS. Remember that PW doesn't output anything on the frontend by default - which is why it's so flexible rather than fighting against the system.

Hey - sorry about the delay on this. I have looked at your PR and it looks like a useful addition. I am just wondering though - what about if we rather not use the array approach like you have there. I don't really have a preference, although I think moving forward, I'll probably go with this approach: https://github.com/adrianbj/CookieManagementBanner/blob/master/CookieManagementBanner.config.php but at the moment, most of my modules work like this: $f = $this->wire('modules')->get("InputfieldCheckbox"); $f->attr('name', 'enabled'); $f->label = __('Enable Tracy Debugger', __FILE__); $f->description = __('Uncheck to completely disable all Tracy Debugger features.', __FILE__); $f->columnWidth = 50; $f->attr('checked', $data['enabled'] == '1' ? 'checked' : '' ); $fieldset->add($f); Do you think we need a config setting to determine which style is output?

I think the most likely situation is that you haven't created any template files to match the templates of the imported pages. If you are importing a WP blog, then you need something like blogs.php and blog.php in your /site/templates/ folder. You can create these manually yourself, or you could use the blog module http://modules.processwire.com/modules/process-blog/ depending on your needs.