szabesz

Sure, the example does not cover "everything" but some part of the screen. On a PW edit page, the most important bits of information are usually at the very top, so anything covering that area "automatically" is not something I prefer. Sure, when we start typing results start to cover that area but I'm not fond of covering anything just by getting the focus into the search box.

What about a command AND the icon too? Maybe optionally. I do not like panels automatically covering anything.

You linked to two completely different codebases: The "original" looks ProcessWire based: https://whatcms.org/?s=http%3A%2F%2Fwww.livius.org%2F https://builtwith.com/livius.org while this one is a table based – just look at the htlm source – oldschool site: https://whatcms.org/?s=http%3A%2F%2Fwww.witteneushoorn.nl%2F https://builtwith.com/witteneushoorn.nl

Let's say you have custom "non-pw" db tables. +1 This sprung into my mind too when reading the post. What about being configurable? For example, I would prefer: --?

Slightly OT but worth a read: Open Source GraphQL Engine Launched https://www.i-programmer.info/news/197-data-mining/11962-graphql-engine-launched.html quotes: "The GraphQL community can harness our lightweight GraphQL-as-a-Service engine and turbocharge any of their new or existing Postgres applications." "While this release focuses on Postgres, the plan is to add support for other databases in the future."

https://www.i-programmer.info/news/83-mobliephone/11963-ten-years-of-the-apple-app-store.html some highlights for TL;DR readers: "...if it was a free market, then Apple would not have made more than an estimated $100 billion over the time, but programmers would be that much better off." "No right of appeal and if you talk to journalists then Apple has no intention of helping you at all. That this is an authoritarian regime isn't a point that you can argue against." "Windows Apps are almost as locked down as iOS apps. Only Google made the stupid mistake of letting Android go open source and it has been working steadily to take control back ever since. Assuming Android is still around in ten years time, my bet would be that the Play store will be just as much a walled garden as the others." "The App Store is mostly full of small apps that do frivolous things - it's a trinket store. Let's get back to real computing."

A short but good summary on isset() / empty() / is_null(): https://www.virendrachandak.com/techtalk/php-isset-vs-empty-vs-is_null/

This sounds awesome! I can offer my humble testing skills even though I'm not having too much free time these days but this project is more important than ever (thinking of GDPR compliant backups, ie. encryption for backups). Last time Flydev could not reach out to too many active testers, so now I encourage anyone reading these lines to join in and offer testing – maybe even development – help to Flydev in advance if you can really do it when he needs it. Also, please do not just hit the like button but reply with suggestions too ? BTW, my first suggestions is: besides being GUI friendly, the new module could also be cli friendly: meaning wireshell integration.

Featured in ProcessWire Weekly #215. Thanks a lot for sharing @bernhard!

Hello, I'm just kinda shooting in the dark, but your issue sounds like it is being cookie related. For example, you might want to check things like: "I could not log in because the session.refere r_check in php.ini was set to the wrong domain." [source] Maybe both PW instances create the same cookie somehow? [source]

In that case you have two options: client-side image resizing ImageMagick if supported by already or can be added to PHP as your php is probably using GD currently, right?

Great! There might be cases when updating a system with "field name == tag name". Is there any warning implemented fur such a scenario? EDIT: or tags/fields are created via the API rather than the admin.

Maybe it is mod_security in action again? Here are some other tips: also, you can search like this: https://www.google.hu/search?q=mod_security+JSON+Parse+error+site%3Aprocesswire.com%2Ftalk Hope this helps, if not, please tell us what you have tried so far to find the cause of the issue.

Thanks for the new features Ryan! Just one question though regarding the new $pages->find tag search feature: what happens if there is a field and a tag having the same name (ie name collision)? Does field name take precedence?

Well, sort of. Let's look at the example of Artisjus which is the official authority in Hungary dealing with licensing music. Over here, popular artists profit from this system while not so popular artists suffer from the bureaucracy, not profiting from it at all. Taking this a step further into just "quoting bits of text with proper credits included" is just ridiculous. Also, forcing content providers to implement software and hardware to automatically filter content which might probably need licensing is short sighted and arrogant. Also, who is going to pay for the implementation and maintenance of such "system-add-ons"? It is just so easy to come up with new taxes but seeing the consequences is a different matter.

This is great! Thanks a million for sharing!

I put together my very first website about 22 years ago. It was all <tr><td> and images but I could only concentrate on the visual aspects, no one really cared about anything else than that (except for file size of course...). Yep, those were the golden days for sure.

The EU is supposed to be all that or am I mistaken?

Currently I do not have to pay for publishing this: "...seeks to impose a link-tax: which would establish a special copyright-like fee to be paid by websites to news publishers, in exchange for the privilege of using short snippets of quoted text as part of a link to the original news article but also to make this an inalienable right, i.e. one that cannot be waived by the publishers even when they choose to do so." But if those money hungry idiots push this thorough, I will. Or I will just simply stop cross-linking: http://www.i-programmer.info/news/81-web-general/11893-why-article-13-must-be-stopped.html Money talks. Insane.

Hello, Welcome to the ProcessWire forum! Here is a thread discussing such errors:

Just one seemingly unrelated global company comes to my mind: https://en.wikipedia.org/wiki/Volkswagen_emissions_scandal They "did take the risk"... Also, car makers put AI into cars without taking security seriously: https://www.wired.com/2015/07/hackers-remotely-kill-jeep-highway/ A few months ago Apple developers forgot to remove the "empty password" root login from the system, releasing it to the public. Should I try to come up with more examples of how careless we can be? Even "big companies". Size does not matter in this case.

I will never understand why people are happy to buy and deploy things like this spying on them. We are living in crazy times when some of us even pay for such things. After Spectre and Meltdown, Intel Management Engine a backdoor and things like that it is just ignorant to assume that such a thing can be "secure". Just hook it up to your wifi router and you'll never know what the future will hold.

.test https://webdevstudios.com/2017/12/12/google-chrome-63/ https://en.wikipedia.org/wiki/Top-level_domain "RFC 6761 reserves the following four top-level domain names to avoid confusion and conflict.[18] Any such reserved usage of those TLDs should not occur in production networks that utilize the global domain name system: example: reserved for use in examples invalid: reserved for use in obviously invalid domain names localhost: reserved to avoid conflict with the traditional use of localhost as a hostname test: reserved for use in tests"

PW is MIT & MIT2: https://processwire.com/about/license/mit/ https://processwire.com/about/license/mpl/ In short: https://choosealicense.com/licenses/mit/ Distribution is granted but include license and copyright notice. You might want to state that your own work is MIT too. And of course, check what each module or any other library says about licensing. Generally speaking I think you will be ok to share it like that.

Great intro @tpr thanks!