netcarver

In addition to Ryan's work in the codebase, I'd like to mention @matjazp, @Robin S and @adrian for their activity in the issue repo! (I know there are others - but these three stand out to me.) Six weeks ago there were 230+ open issues, we just dipped under 100.

@britnell You can also take a look at my twilio module if that helps.

I remember there being a Caddy container with PW somewhere. You could try searching on hub.docker.com and pulling the image to see how it's set up. Sorry, I don't have any resources to help here.

@ethanbeyer I can't address the "better way" part of your post, but you can use NGINX if you want, although it isn't officially part of the codebase. There are several people who have successfully converted the ruleset to NGINX and you should be able to find the settings here in the forum if you want to review them. Another option is to just pull down a pre-configured LEMP + PW stack from docker hub.

Have you tried hooking page::cloned()?

Yeah, I can understand that, but I was going for a pretty opinionated input look - in part to try and provide a slick (fast) keyboard entry method for users at the charity - that really mimics an address label. Please feel free to share your "vanilla" CSS and whatever your findings are regarding getting it working with map marker modules - I know there will be some others in here who are interested in such an integration.

@modifiedcontent Thanks for the post. Circular answer: It assumes it will be used for postal mailings because that's exactly what it was developed for. It was something I wrote for myself and a charity I'm involved with. Ironically, we use it for postal addresses that appear in other places, not just printed matter, including emails. Works just fine. If you need to prevent the address-label-like format preview, you can simply turn it off in the field settings. Not sure I understand. As all address subfields are accessible via the api, you can easily pull any, and format them as needed for whatever purposes within your own templates or hook functions. As I pointed out earlier in the thread, this was written as a compromise between straight textarea input and a form based approach. I've never come across an address input field that I actually liked - until I wrote this one. I am open to considering a PR that allows different skins for the module, if you're interested in helping. Otherwise I can only suggest customising the CSS file that appears inside the module if you'd like to revert to the default fonts/inputfield look. You could also try switching the input of the field over to the "Fixed data table" option under the Select Input Format section of the settings, to see if that suits your requirements better.

Great, thanks @gebeer , I've added that to the codebase locally and it should be in the next release. @thlinna and anyone else using this module, could you please try out the localisation branch in Form Builder and let me know what works (or not) for you - I'd appreciate some feedback before merging these changes into master. Please also try it with LibLocalisation if you want to make use of localisation of the country names in the country select lists and resultant formatted address. Many thanks.

@gebeer Could you try replacing getMatchQuery(...) in FieldtypeStreeAddress.module with the following and let me know if it fixes things for you... public function getMatchQuery($query, $table, $subfield, $operator, $value) { $subfields = StreetAddress::getAddressFieldNames(); if ($subfield == 'country_iso') { $subfield = 'data'; } else if (in_array($subfield, $subfields)) { $subfield = 'data_' . $subfield; } if ($operator == '%=') { $ft = new DatabaseQuerySelectFulltext($query); $ft->match($table, $subfield, $operator, $value); return $query; } return parent::getMatchQuery($query, $table, $subfield, $operator, $value); } Thank you.

Hello all, I've just pushed a rather alpha version of this module to a new branch on github. The localisation branch adds a few new features that might be of interest. Update default countries list (in English) with names from the country-list project. Use LibLocalisation (if installed) to localise country select lists in the Inputfield. Allow localisation of config and inputfield select lists to the language of the user's browser. Switch to storing ISOs in uppercase, can still handle stored lowercase ISO codes. Unify country list loading code. Detect changes to input address when saving page. Add compatibility with FormBuilder. You'll need to do a manual update from the new branch to try this out. Backup first please. I'm pushing this now in its alpha-state, as I've had a few health problems recently and don't want to hold off making this available any longer.

Hi All, I realise there is work that still needs doing on this module. This includes supporting a full set of selector operators and publishing the support for use in Form Builder. Unfortunately I'm buried deep in some non-PW development at the moment and can't put the time in that's needed, this also explains my absence from the forum for the past month. It is on my radar though and I'll get back to it when I can - probably in late Jan. ?

Nice, thank you for working on the GitLab side of things. Would you mind if I used your code as the basis of a GitLab adaptor for the Release Notes module? PS> There is already code in ReleaseNotes for both Github and BitBucket, so adding the GitLab adaptor would give some nice closure to ReleaseNotes.

Hi Robin, I originally envisioned PW Gems as casting a wider net than it currently does, with search methods for additional PW sources including Google, github gists, code snippets embedded here in forum posts, as well as public gitlab and bitbucket repos. I only got around to doing the PW repo, github and packagist searches in the end and, of these, only the PW Repo search extracts version information. There's no reason these searches couldn't dive deeper and look for versions from well known files, but I've not done it. Of course, not all the projects turned up are modules. Many of the repos are people's PW site boilerplates for example, though they may have a published tag or release that contains a version number.

I do have a script that trawls github and packagist for projects that are not in the PW repo. It's poor quality, but it does the job. In the screenshot below, it's found 1,224 projects - only 557 of which are in the PW Repo. Filtering of results is pretty nice, too. By adding some timestamps (when project is first seen and then last modified) this could be used as the basis for detecting changes to unregistered modules and projects.

@benbyf I use this in my config.php file... setlocale(LC_ALL,'en_GB.UTF-8');

All good here - Any update on this, @elabx?

@PWaddict You could try calling date_default_timezone_set() in config.php.

Try adding... au BufRead,BufNewFile *.module set filetype=php at the end of your .vimrc file and re-launch vim.

Hi @zoeck Sorry I missed your post previously. If you are still looking for LDAP integrations there are 3 that I know of... LdapSignIn from Conclurer. KreativMonkey's LDAP Helper. JimYost's LDAP Authentication module posting on the forum, though you might want to go with Apeisa's implementation further down the thread. ...but I suspect you've written your own by now ? Hope that helps.

My vote would be not to colour the cells at all, or use a really light difference between the two because, as Bernhard already pointed out, there is no correct answer here - sometimes you want a role to have a permission - in which case the "tick" mark is correct - and sometimes you don't, in which case the "cross" is correct. @adrian there is a "Note" colour from the diagnostics panel that might work as a possibility here. Edited to add: just read the updates on empty cells for no-access. Even better!

My wishes for a speedy recovery Ryan.

@videokid Thanks for the report, what version of PW and my module are you using? Also, do you have Form Builder installed?

Hi @Martijn Geerts, ran into an issue with ACF issuing notices on L123 of AdminCustomFiles.module due to unguarded access of the "theme" and "process" indexes on the index array. Changed code to: if (isset($this->index['theme'])) { foreach ($this->index['theme'] as $prop) $config->get($prop['type'])->add($prop['url']); } if (isset($this->index['process'])) { foreach ($this->index['process'] as $prop) $config->get($prop['type'])->add($prop['url']); } to fix this.

@thlinna I have my development copy using LibLocalisation and working with Form Builder now - though it needs some more testing on my part. I'm also not 100% happy with the config controls for the localisation yet, so I'm going to wait a week or so before I release it.

Hi @adrian thanks for the latest update to add autoload support (and to Ryan for putting it into the core this week) as I can now use Tracy in the preview tab in FormBuilder to do a little StreetAddress work. Much appreciated!