netcarver

Hello @yrglx Welcome to the forums. A couple of things come to mind... Have you got any script or adblockers running in your browser? I've had these prevent maps from working properly in my PW sites before. I suggest you disable any blockers on your domain, clear your browser cache and try reloading. Does this help? If I think of anything else, I'll post it. Best wishes, Steve

Hmm, I guess InnoDB may be auto-committing on every insert. Try turning autocommit off for bulk imports - but it might not be a panacea. Reference and another. BTW, that's an interesting article - thanks for the link.

@ryan Seems like you've been addressing my personal wish-list recently - 2FA and InnoDB - I've been an advocate for both for a long time. Thank you!

Hello All, I've been working on a new Fieldtype + Inputfield combination that handles street addresses. I've been using it now for about 3 months on my latest administration system for a charity and, so far, it seems to be working really well for them. It's based on the meta-data from Google's LibAddressInput project and uses the data feeds from that to build a cache of address formats used by various countries. My initial testing was aided by @Macrura and @adrian - and they were later joined by @mel47 and @BFD Calendar - so a big thank-you to them all. You can access the repository on GitHub and the Module Repository. Here's a few images from the project. First up: config screen. Here's an early version... ...and a more recent update... Here's a UK-based address. The module can integrate with my tag parser, if installed. Note that the output is formatted according to the output meta-data from the feed - which should match the preferred postal preferences of the destination country. Which subfields are required, and their regex expressions (if any) are also pulled from the feed and used as validation rules on the input side. Here's an address in the Netherlands - inputfield layout is currently adjusted on save - if you've configured it to adjust based on the destination country. Hopefully this will eventually be ajax driven. Use of the address preview is configurable and the HTML output can include micro-format data. Address sub-fields can also be used in selectors... Back with inputs, if you prefer a table-based input - you can have it... Format hints (unfortunately, I've found that many users need these)... Let me know if you find any issues or if you have any feature requests. So far, I have this from the previous testers... Allow multi-lingual address input for countries that support a multi-lingual postal system (like Canada.)

The diagnostics panel will need more follow-up work in the days to come, but hopefully it's a useful first step. I've just noticed how bad the permission model for my current shared host is *sigh*. Looks like I'll be moving this site to a VPS sooner rather than later.

Just trying the latest version on a shared host and found a bug regarding the config->debug setting. Will fix.

I've just issued a PR to the main repo for a reworked diagnostics panel for Tracy. This... Adds a "Dedicated" server switch via cookies. Adds colour coded cells. Displays file permission flags. Adds checks for existence, ownership, readability by process user, writability by process user, world-accessibility, execute/traversal. Detects installation of the PW Upgrade module. Detects use of non-file session handling. Adds basic checks of the debug, chmodFile and chmodDir config settings. Unifies the colour scheme with the new Tracy constants. Supplies formatted suggestions for chown, chgrp and chmod commands (on non-Windows servers.) Adjusts severity of issues reported based on Local vs Production server and/or Dedicated vs Shared server. Adds links to documentation for some assets. If you want to try it out and let me know any problems you find, please consider using my temporary Fork of Tracy on github until Adrian has had a chance to consider merging the PR.

Hi @tpr I think this looks great! Not so sure about the inverted scheme - but it may work well with a darker admin theme.

Thank you for working on this, Adrian. Looks a lot clearer now.

@cstevensjr Hi Charles, I'm really thinking of the issue repository in this thread. I, too, add a thumbs-up for feature requests that I feel have merit. When it comes the the processwire-issues repository - whilst I agree that thumbs-up don't add noise - it does not unambiguously let either Ryan or myself know that anyone else is experiencing the reported issue. If Ryan were to base his decisions to fix things based on the impact an issue is having on people, then using a thumbs-up may not help the issue get the attention it deserves, whereas clearly replying in the affirmative (possibly adding additional, relevant, information) will.

Hi Teppo, That's a good point. So, perhaps only helpful until the time where Ryan starts dealing with the issue himself. Once he's in the discussion, posting a "Me too" is just adding noise.

...please could you add a comment to the issue confirming that you are also seeing it, and add any additional information that may help. There are several issues that have the report and then some thumbs-up votes on them. This, however, is somewhat ambiguous, as I don't know if the thumbs-up is really saying "This effects me too" or just a "Well done for reporting this" or something else entirely. In order for me to unambiguously tag an issue as impacting multiple users, I either need to reproduce it myself - or I need people to clearly state that they are impacted by it. Whilst I can understand the use of thumbs-up emojis on the processwire-requests repo as a form of up-vote, I don't really think it works for the issues repository. If you have any other suggestions that may work unambiguously in this case, please let me know. Thank you for your consideration. Steve

Just to clarify my request to Adrian, it's not the icons that I'm finding ambiguous - there's nothing wrong with them IMO - it's what the colours are signalling in the current version of Tracy that I find a little confusing. This is what I'm trying to avoid - particularly the part between 24 and 43 seconds... Here's the current state of play... To me - with my now aging eyes - the colours of... 2, 5 & 7 seem to be signalling an error condition or something that needs my attention and that this icon could be another colour when the error is sorted out. 3, D & H are warning me of something and these icons could be another colour at other times. 4, 6, 8, 9, A, (all the green ones) have no error - but they could have warnings or errors at other times. All the grey ones are - well, I don't know - are they OK? Or Off? Or just buttons to press when I need them? 1 & F are signalling something else to me that's different to all the above. Whilst some of the above is correct, I don't think it's clear in the current incarnation. I also think that the decision to colour some icons green rather than grey when there are no warnings or errors, might, arguably, need revisiting. (For example - I think B (Mail interceptor) and C (Module switcher) would probably be better as Grey in the above if there is no interception or disabling going on.) Basically I'd like to have Tracy only use non-grey colour signalling to me if there is something that needs my attention or constant reminder. I think that would stop me feeling a little like Richmond from the IT Crowd. BTW - I'm not dishing Tracy or the work Adrian's put in. I think one of the top modules there are for PW and I'm very pleased that Adrian's produced it and for all the hard work he's put in on it. Hope that clarifies where I'm coming from, Steve

Is mod_deflate actually installed on the server? (You may need to ask your host)

Hi Bernhard, I hit a similar issue with the ReleaseNotes module. If you have a look from line 203 on for about 20 lines, you can see how my module handles it. I hope that gives you something to work with. (Ignore line 214 - it's now unused and I'll remove it from the next release.) Best wishes, Steve PS> Thank-you for all the amazing modules you've produced!

Hi @ren If this is a repeatable problem, please consider opening an issue for it over at processwire/processwire-issues. Thank you.

@louisstephens I really like the answer @horst posted about this but want to ask if you intend using Lazycron for doing this? If so, please be aware of the potentially long processing times associated with doing things this way, especially on the initial read of the feed. Also; there is no facility above for removal of items that no longer appear in the feed but that are stored in PW pages. You might not need to do this though, it all depends on your application. If anyone's interested, the way I've tackled this before, in outline, is to pre-process the feed and essentially do what horst posted about calculating a hash of the content (personally I don't like crc32 which returns an int but prefer the fixed length strings returned by md5 (which is fine for this - and fast)). Do filter out any feed fields that you don't intend to store before you calculate the hash so that insignificant changes in the feed don't trigger un-needed updates. Anyway, this gives a feed_id => hash_value map for each feed item. If we do this for the feed, we end up with a PHP array of these maps. This array can be stored persistently between each read of the feed. Let's call the previously created map, $prev_map, and the map for this read of the feed, $new_map. You simply use PHP's built-in array methods to quickly find the records that have... Been added: $to_be_added = array_diff_key($new_map, $prev_map); Been deleted: $to_be_deleted = array_diff_key($prev_map, $new_map); Been updated: $to_be_updated = array_uintersect_assoc($new_map, $prev_map, 'strcasecmp'); ...all without having to go to the DB layer with selectors. On the first run, when the $prev_map is an empty array, you'll be facing a full import of the feed - potentially a LOT of work for PW to do adding pages. Even reads of the feed that add a lot of new pages or update a lot of pages could require mucho processing, so you'll need to think about how you could handle that - especially if all this is triggered using LazyCron and takes place in the context of a web server process or thread - having that go unresponsive while it adds 100,000 pages to your site may not be considered good. Finally, don't forget to overwrite $prev_map with $new_map and persist it. * NB: I've not done item 3 exactly this way before (I used array_intersect_key()), but I don't see why array_uintersect_assoc() shouldn't work.

Actually, I have been pondering making this more targeted. Let me gather thoughts and I'll either PM you a proof of concept or post more about it here.

@adrian Strange. I'm on a Linux mint - which seems to use the paradigm of creating a group named the same as each user. I'm not sure that MacOS does that. In these cases, the original code always seemed to report the file's group as being the same as the owner - even when it was not. When you ls -al in the terminal you are, presumably, seeing ajones:staff as the owner and group? I wasn't. I was getting sed:www-data in the terminal but sed:sed in Tracy. Maybe others can chime in here - but if the new line isn't introducing a regression, I can verify it fixes a 'bug' for me.

@adrian I think I found a bug in the Diagnostics panel - it incorrectly shows the group name of a given file/directory for me. I think you may need to change line 160 of DiagnosticsPanel.php (which seems to be using the file's owner ID, rather than its group ID) to... $group = !file_exists($path) ? '' : posix_getgrgid(filegroup($path)); Best wishes, Steve

This one's not really new, but I forgot to post about it when I did it, plus there are still some unfinished aspects. I have a minimal personal invoice setup allowing me to have multiple identities for my invoices, to represent the different aspects of what I do (it's not all PW)... The child pages of an identity represent permissible payment methods for that identity... Of course, there are multiple clients under which invoice pages are stored, with highlighted status in the page tree... Invoices use repeater fields to store line-items and expenses. The line subtotal is calculated on save. The whole invoice value is worked out too. Profit and Loss is yet to be finished. And here's the result... I like PW!

@adrian I've been trying out the Custom PHP panel features and it's working really well. There's cake and icing - but I've thought of a cherry. There's still scrolling involved when iterating something in the custom panel when it comes to saving what you are doing - if the panel could be moved right to the bottom of the config inputs, that would put the save button within easy reach (for those who aren't using AOS's feature to fix the submit button on the header.)

@bernhard On the "ProcessWire Info and Links" panel. ...then look near the top of the panel for the version list... ...hit the copy button and then paste as part of any issue you raise on the Processwire-Issues repo.

@adrian That works really well, thank you! My only other suggestion about the version lists I added here. At this stage, it really isn't important - the information is much more visible in this format.

@adrian That's more like it! Thank you.