szabesz

@kongondo's Media Manager module offers a lot more than this module would offer even with the child pages feature, so as far as I can see it you are not working on something like that. The suggested child pages feature would be welcome but if you stick to the one page only solution than that is great too.

If @gebeer has time to add additional features to this module, I would vote for something like this, because it sounds simple enough. The simpler the better ?

Please read this: https://processwire.com/blog/posts/pw-3.0.80/#pro-module-faqs then contact Ryan directly.

Pinging should be optional of course, and not just because of "personal preference" but also because ideally one site should only report usage once, and when the superuser switches it on/of for testing or whatever purposes, then there should be no multiple reports of using it. For this reason, I would put a another checkbox next to the "enable" one, with a label of "please report usage of this quick fix" or something like that.

It would be, but as we all know, life is not as straightforward like that ? There are issues Ryan solves pretty fast after being reported, there are others that take more time and there are some which seem to take forever... and the worst category is in which he is only marginally interested. Also, what we might provide as a "fix" via a PR can easily turn out to be just a workaround and there is no point in submitting such a PR. For example, in all of my use-cases PageTable without an "add new" bottom at the TOP of the table is a UX nightmare, so I have a JS hack to clone the button from the bottom to the top. In my point of view I "fixed" this is issue, but in reality it is just a hack which would be a good fit for this module, I think. Maybe we should call this module PwQuickFixes which might better reflect its intended purpose: temporary workarounds until they get properly fixed. We just need stats to see how many of us is using a particular quick fix, and another way to make our voice heard is to add a kind nudge by asking the user to go to the related Github issue in order to make her/his voice heard too.

Hi Bernhard, I like the idea A LOT ? However, since it is your module, you should be the one to audit – at least from the security point of view – any PRs before accepting. Will you have time for that?

They do it all the time. No matter how many accounts exists... most of the time all people use just one. I always try to convince clients not to share accounts, but in some cases they flatly express that they will indeed use "shared accounts" no matter what. Their excuse usually boils down to laziness: they do not want to deal with managing users at all. In such a case I ask them at least to call such a user as "shared editor" or similar so that at least we know how to treat that account in question. So for the reasons outlined above, some support for this would be welcome, maybe with some additional logging options so that we can track down such activities even days after...

@ryanIt is strange you say that as the SystemNotifications module can do it. I've been using SystemNotifications module only because – at least on "my" sites – it does detect the case of same pages opened in different tabs. I am using SystemNotifications even though it has an anoyying bug: https://processwire.com/talk/topic/9526-strange-errors-following-upgrade/?do=findComment&comment=95893 and it is hard to remove once installed: https://processwire.com/talk/topic/19834-how-to-deinstall-system-notifications-module/

@ryan I also have an idea which is somewhat related: is there a possibility to build upon UserActivity so that one can build a module which is made for logging – saving into the database – what (given) users performed in the PW admin? I am thinking of (re)implementing something like Reno's MarkupActivityLog module https://modules.processwire.com/modules/markup-activity-log/ Could some API features of UserActivity be useful when developing such a 3rd party module?

Yep, it must be installed. It is called Page Path History module, found among the core ones.

Pretty cool, thanks for sharing!

Maybe it's also: long time no sea? ?

Or just use Tracy Debugger's (by @adrian) Mail Interceptor feature: https://adrianbj.github.io/TracyDebugger/#/debug-bar?id=mail-interceptor I always rely on it, it has never let me down so far ?

Welcome to the forums! There is no such thing unfortunately, but the tutorials section of the doc pages is a good start: https://processwire.com/docs/tutorials/ Also worth noting: https://www.youtube.com/watch?v=K6eQGGk9xOA&list=PLjfImzZuFeJ-iZ0K7WVDwSeTrQQHmt7a8 https://mauricius.dev/basic-processwire-website-workflow-part-one/ (Step-by-step guide, 4 part tutorial) https://processwire.com/talk/topic/3579-tutorial-approaches-to-categorising-site-content/ Hope this helps. Edit: +1 ? https://www.youtube.com/watch?v=kSLhay7msTI&list=PLOrdUWNK38ibz8U_5Vq4zSPZfvFKzUuiT

Worth noting: https://processwire.com/talk/topic/19912-future-of-padloper-new-project-lead-announcement/ TL;DR: https://processwire.com/talk/topic/19912-future-of-padloper-new-project-lead-announcement/?do=findComment&comment=187487

Your proposal of adding toggle to the bar can take up lots of space too, if there are lots of languages in the system, so perhaps another way of solving the issue would be more feasible. Anyway, I get your point and the feature itself would be welcome, of course. BTW, while we are talking about the horizontal bar of a repeater matrix item, I find it annoying that the open-close toggle (the arrow icon) is not on the far right, because there is the case of the "Show settings?" cog icon appearing between the "arrow" and the "duplicate page" icons, and when that happens the arrow of the open-close toggle moves upon clicking on it. So in that case it is not possible to quickly open and close a repeater item, one has to reposition the mouse pointer all the time.

Hi, There is a similar thread over here: https://processwire.com/talk/topic/19180-error-loading-github-branches/ Maybe it is related, maybe it is not, I do not know, however I also use MAMP Pro without issues, but I am running 5.5.1. Maybe try upgrading MAMP Pro if not yet running 5.5.1, or try using an older version of PHP. I use 7.1.x as it is still supported till 1 Dec 2019 ? Anyway, I always play safe and only upgrade whenever there is real need for it.

I see. Thanks for clarifying! Side-note: I did have a strong feeling that the module would not see too much maintenance, if any. That is why two years ago – when it was released – my first reaction to it was asking for adding it to the core. However, I did not know that the codebase in its current state just does not cut it...

My experience with google searches is that they do not care about keywords. What matters the most is CONTENT: one or two regular authentic posts a week (or even more) presented in semantic HTML will lead to good search result postitions in the long run. Anything else can be considered to be fine tunig.

Could you please share it via Github? If you were to maintain it publicly that would be graceful to say the least. It would probably be a good idea to rename it first, though. Thanks for considering!

Another survey I stumbled upon yesterday: https://www.gwhitworth.com/surveys/controls-components/

Looks interesting, thanks for sharing! I put it on my todo list to take a closer look. Interestingly, I have just recently set up a workflow based on CodeKit and its "Kit" file compiling capabilities (Kit == HTML + import features + variables) in order to craft my own site. I boosted the whole thing by also adding Fat-Free PHP to the mix. I use Beyond Compare for syncing to the server. All this is about producing "flat files". Since I also sprinkle PHP here-and-there, I actually invented my own Semi Flat File website approach ? My whole setup is all about using desktop GUI apps, as opposed to (say) npm based cli stuff which can be quite unreliable at times (actually, unreliable too frequently to my liking). All in all, what I like about Publii is that it is a "technically minded" / developer oriented solution, still, components are integrated as a desktop app, so there is no need to experience the pain of npm/webpack/and-similar as all the burden of such things are on the developers of Publiit, and not on the developer of the website(s). After all, I'm a creative guy who likes to create, but I dislike dealing with fixing CLI tools, fighting incompatibility issues and such. That is why I chose ProcessWire in the first place, btw. ?

Updates ? https://2017.stateofjs.com https://2018.stateofjs.com/ https://2019.stateofcss.com/

article: The perils of functional CSS (sometimes referred to as atomic CSS) https://www.browserlondon.com/blog/2019/06/10/functional-css-perils/ Quote: "...if you don’t have a dedicated front-end team to handle this end of things, I can see how functional CSS would be useful. I don’t think it’s a coincidence that back-end developers have written most functional CSS libraries."

+1 I did something similar recently, which was surely easier than learning a system I was not really interested in. My trick was to inject the "old record ids" of the old system into its markup (so I only had to understand a little bit its templating), afterwards complete page contents were grabbed and were saved into PW's CKEditor fields and from then on I performed some careful planning and PW template/field works – based on the required relations – and lastly I used php-html-parser to turn the static CKEditor field markups into relations.