adrian

I think it's probably too rare of a need to add to BatchChildEditor, but happy to have it in AdminActions. Just committed it to the latest version.

Yeah, I guess you must be right. Maybe the ozadje_strani image field is set to return a single image which is why it can't be foreach'd? Actually, I guess it's a repeater field and bgimage is the image field - I don't know ?

I don't really understand why it's working at all - '/home/' is not the path for the home page, it's '/' - try that and things should work without the error.

Just to make things clear in case they aren't, you are getting the selected item - you're actually getting the full $page object for the item. The __toString() method is resulting in the ID of that being being output when you try to echo it as a string. You have to specify what field you want from the page, ->title, ->body, etc.

No there's no way around this really, but my solution is the combination of these two modules: https://modules.processwire.com/modules/email-new-user/ With this, when a new user is created they are automatically assigned a password and this is sent to them via email. https://modules.processwire.com/modules/password-force-change/ This ensures that the next time they login they have to change their password. I think this combination is the easiest way to migrate large numbers of users to PW.

I only see one occurrence of that text: I'm not really sure how this could be browser related because the output is all generated server-side. Just an FYI that you have a couple of JS errors showing up in the browser dev console.

@dragan - I just tested your code here without any problems: But based on the error message, it looks like the images field is corrupted somehow. I have never come across this before, but that is where to start looking.

Yeah, it will cause problems if the name field is not available somewhere. If you enable PW's Advanced mode you can use the "Display 'name' field in content tab?" option in a template's System tab. Or you can do this in a module with: $page->template->nameContentTab = 1; You may also want to do: $form->_pw_page_name->collapsed = Inputfield::collapsedYes; Both of these can be seen in action in: https://github.com/adrianbj/RestrictTabView Hope that helps.

I think several AOS features need to be in the core ? Seriously though, if we could get the most used features in the core, then perhaps the lesser used ones could remain in a trimmed down AOS. I think I'd rather see a module that works on top of a core theme, rather than you creating a separate theme that misses out on new features that Ryan adds until you have a chance to add them to your version of the theme. Does that make sense? I don't think you should being trying to maintain support for multiple themes though - I think going forward PW needs one solid flexible theme which can be restyled via CSS and functionality tweaked by hooks and js overrides. I think having multiple themes with different codebases just makes things difficult for Ryan because he often has to add new functionality to multiple themes - this is why I always stick with his default, which in my mind is UiKit these days. Anyway, I am a little OT now, but hopefully my ramblings make sense.

3.x dev still works: http://kongondo.github.io/ProcessWireAPIGen/pw3dev/

Great! I am curious why your IP address isn't recognized as part of the EU. As you would have noticed, I am using: https://restcountries.eu to determine this. Do you think it's a mistake in their DB that is worth reporting? FYI - using that service means that I could actually extend that option so you could choose which regions or countries see the banner and which don't - not sure if there is demand for that or not though.

Weird - I assume the banner works when you don't have the EU Only option checked? If not, then that's one path we need to go down. If it did work and you clicked I Consent, or the close icon, then have you cleared the browser LocalStorage items that are keeping your acceptance stored?

I tested with this IP address: 85.214.132.117 and it worked as expected. I think what might be happening is session caching of your location / EU status. Can you please click the "Clear Session & Cookies" link in the Tracy PW Info panel and see if that fixes things. If not, could you please try uncommenting line 39 and commenting line 40 and see if it shows then? That will test using that 85.214.132.117 IP address. Thanks!

I had Ryan fix this core "bug" a couple of days ago: https://github.com/processwire/processwire/commit/e5e13c190447ce156d3075683ee8a9ca42931904 Can you update the core and let me know if you still have any problems.

Not related to your problem, but I wouldn't recommend inserting "http://www." like that for a few reasons: 1) A site editor could easily add that part themselves - especially if they copy from their browser address bar and then you would have it twice 2) The site may not work with with the www subdomain - unlikely, but possible 3) They might want to link to a different subdomain rather than the www one 4) The site might be https, not http - most likely it would redirect automatically, but it just feels wrong to try to force this

HI @pandaman - I really don't have any idea why it wouldn't be showing up. I use it on Multilanguage installs regularly. Does it show on the backend, or not at all? Are you on a local dev setup? If not, make sure that Force Superuser into Development mode is checked, or force the Output Mode to Development. Are there any JS errors in the browser dev console?

PS - Looks like California is getting in on this too: https://slate.com/technology/2018/06/california-just-passed-the-strictest-online-privacy-bill-in-the-country.html

Hi all, Introducing a new GDPR Cookie Management Banner module. https://github.com/adrianbj/CookieManagementBanner https://modules.processwire.com/modules/cookie-management-banner/ This module was sponsored by VentureWeb in Squamish, BC, Canada. I converted a Drupal module written by Oliver Walker from VentureWeb into what you see here. The Drupal module requires jQuery so at the moment, this module also requires jQuery. I will probably remove this sometime soon. This module certainly has similarities to MarkupCookieConsent but provides the user with the following features: The user can accept all cookies or they can choose to not accept tracking/marketing cookies. Module config options allow you to: define all text and button labels (multi-language support) manually increment the cookie policy version which forces the user to review their consent again select whether users can manage their cookies, or just accept all option to limit display of banner to users only in European Union (by IP address) position selection (top or bottom overlay, or content pushed down from the top) It comes with basic default styling which is easily overwritten by site CSS The module sets various values to the dataLayer array which works together with Google Tag Manager - please read through the code in /assets/js/CookieManagementBanner.js to get a better idea of how this works and what is made available for GTM. You can wrap your tracking/marketing cookie code in a check for the localstorage key of: pwcmbAllowCookies if(localStorage.getItem('pwcmbAllowCookies') == 'y') You can also provide a link on your site (probably in the footer) like this that will allow the user to show the banner even after they have saved their preferences / accepted. <a href="#cookies" class="js-pwcmb-notice-toggle">Manage Your Cookies</a> Would love to hear feedback from anyone who gives this a go.

Take a read through this thread: https://processwire.com/talk/topic/5397-assigning-fields-to-repeaters-with-the-api/ I think the function by @thetuningspoon does what you need, but please read my comment afterwards - not sure if that change was incorporated or not.

Turns out it's only an issue when I have this module installed: http://modules.processwire.com/modules/restrict-multi-language-branch/ Although that module works by setting the template noLang flag so I expect the same issue could also be replicated by setting that for a template, so I do think this needs some attention still.

I just came across this in PW 3.0.105 Has anyone else also seen this recently? @ryan - any chance there has been a regression regarding this? As soon as I add a second language to the system it works again.

These are two modules that use it: https://github.com/adrianbj/CustomUploadNames/blob/master/ProcessCustomUploadNames.module https://github.com/matjazpotocnik/AutoSmush/blob/master/AutoSmush.module Let me know if you can't figure out what you need from those and I can try to answer more specific questions.

Obviously I don't have your complete code to check, but if you are doing on SaveReady, make sure it doesn't happen on every save - surely you only want it if the tiff has just been uploaded or replaced? Sorry if you have already taken care of this - just wanted to raise it in case. I would probably go with hooking into InputfieldFile::fileAdded

I'm three!

Thanks for noticing that - good catch. It should be fixed in the latest version. Sorry you're not finding it user-friendly - I agree it's become quite the behemoth in terms of config settings - it makes it very flexible it terms of the interface you can craft for your site editors, but I understand it can be a little unwieldy to configure.