szabesz

Yeah, we've been missing you welcome back to the best community support forum on Earth.

Good point To me, in the case of ProcessWire it means that ProcessWire "never" becomes obsolete, at least not in my life. That is why I have the same concerns as you have, see: Becoming a tiny bit more popular could attract more dedicated developers who could form a strong dev team behind ProcessWire in the long run (stronger then we have now, 'cos we sure have one it is just not so obvious as they partially work behind the scenes). Maybe I'm just daydreaming, I dunno

Sounds off topic but may not be so. As pointed out earlier and above, documentation is an important part of the success. Everyone knows that (probably...) And building front-end logins, forms, admins, dashboards, modules and stuff like that is not documented, except for module and core code comments and hard to scan blog posts, of course. But those are hidden bits of information and kinda time consuming to dig up. Also, basic frontend design tutorials are outdated. I propose to make 2018 the year of the documentation, so to speak. What if we could stop hunting for new features for a while and concentrate on the following in 2018: new processwire.com new UIkit admin theme documentation: updated basic frontend design tutorials and lots of real world form API tutorials for the masses. Just my two cents here

I told you we are in the same boat I have basic git knowledge level because I work on my own and found it time consuming to use it when I have other ways to manage my own code. But those tools are only for a singe developer, of course. But hey, they do work for me (only). I'm always willing to but currently I have no extra time. This is what holds back ProcessWire's growth. We are all busy working for the living, hard to take a break for a while. My own blog is crying for more too...

It is possible to merge the two to your advantage. I have not find a thorough guide/tutorial/example-site for this though. I am missing the experience too so I am slowly learning ProcessWire tiny bits-by-bits every day. At least I'm enjoying it We are in the same boat in this area

Just one more thing. Personally I will not give a damm about the guidelines you linked to. I want to adhere to standards only. If Apple (aka Jony Ive) wants to cut off part of my design then it is his choice. I will tell my clients that it is Apple's fault. They should stick to industry standards but they deviated. I'm strong with the Force in this Either way, it is good to know Apple has gone mad, thanks for the post!

It is not rumbling at all, I call it common sense which is missing from Apple these days. I have always used a Mac for work, I never worked on anything else because Apple makes the desktop OS I like the best. However, I have never had the urge to buy an iOS device because I'm terrified by iOS. You've just showed one prime example why but there are lots of others as well. They want to force us to "think different", you know: the way THEY think. I hate that.

Let's do it! There is enough of us interested: https://weekly.pw/polls/ Probably in Finland as you have shown us Just kidding. But somewhere in Europe where most of us can drive or fly to "cheap".

I have never thought of it but it is so obvious. We are simply trained to do it the other way round. Anyway, my NetBeans marks such an issue on the fly which is hard to miss, and that is why I do not make this mistake these days, otherwise...

Thanks for your detailed answer! You are being very generous, thank you! In the meantime I did install your fork and did not run into any issues. This filed should be in the core, btw... Let's see what @sforsman has to say. He has not logged in for a while, but one never knows

Cool, good to know, thanks! I have not yet tried TracyCaptainHook – to tell the truth – so I guess that is why I did not notice it. Thanks. It might be useful to have it as a separate module but I do not think editors should use it, so probably it is a good fit for Tracy. Let's see what others say.

I wish, I wish... ProcessWire had loooooots of @ryans behind it. As it stands, we all depend on him. As long as he is with us, all is good though...

Do not forget that WordPress is click-and-play and can be easily pimped by googling around the web and pasting some hooks into functions.php. You can't beat that! WordPress is not even a CMS, by the way it is a blog engine with a nice GUI.

Just an idea: could you please implement it in @Soma'Clear Cache Admin and create a pull request for it? You might also want to pull up your sleeves and try to persuade him to register it in the Modules Directory Or you might just want to integrate his module into Tracy? (At least its features.) I hope I'm not asking for too much. Thanks for all your great community service as always!!!

It's hard to tell just by taking a closer look at the forum or github because a lot of developers hardly ever post anything there nor they register at the forum. A better indicator would be some statistics on PW's downloads. If it grows, the platform grows too, I guess. At least this could be a useful conclusion even if it is a basic one Hm, it is always hard to tell what search engines are actually "measuring", but it is better then nothing, I think

By the way, the new way of previewing post is rather misleading, at least most of the time, eg: Here, I wanted to recommend @LostKobrakai's post which is about API variable access and was written as a side note, not as the actual reply to the topic. Including – even worse highlighting! – the topic makes the false impression that my intention was to link to the topic "Custom PHP code selector" but it is not the case. And this situation will not be rare. This new feature will not be helpful in a lot of cases, rather it will add confusion

Here is a related very good post I keep recommending from time to time.

It did happen to me a few times too, but after a while the like icon appeared and since then it stays like that.

Right now it does it for me too but it did not, I swear

For me too but I hate that fact that user names are no longer displayed initially. We need to lick and wait to see even the first users who have already reacted. Is it possible to get back the previous behavior? I also vote for "like" only

Hi @arjen Does the module work without issues with PW 3.x? I'm planning to use your fork: https://github.com/arjenblokzijl/FieldtypeDecimal I'm wondering if you are willing to add PW namespace so that it does not need the compiler anymore (people can still download old version for PW 2.x from GitHub). Also, you might want to take over maintenance as @sforsman does not seem to be doing it anymore. What do you think?

How about using a counter or a flag to signal that the page has already been rendered? If you store the rendered output in the first iteration then you can just output it later on without calling render again. Or am I misunderstanding something?

Hi, Just do not forget: https://processwire.com/api/ref/wire-array/ Quote: "Nearly all collections of items in ProcessWire are derived from the WireArray type. This includes collections of pages, fields, templates, modules and more." Meaning if your WireArray/PageArray is sorted the way you need, you can just use first() to get the page. + one more tip: It is a bit ambiguous, isn't it? foreach($page->product_repeat as $repeater_item) { or similar (eg. $product) would be easier to follow.

Thanks for the fix and the explanation.

I see. I cannot seem to be able track these changes these days... Mine is different because I use Reno's default Color Set and most importantly as I described above I hid the confusing upload button and renamed the not so confusing upload button by (technically speaking) "translating" its label with PW's translate feature.