szabesz

Thanks for the late night repy Zeka ? Array of Items. And I do get the array, it's just missing the cropped images, very strange...

Hello, This is the very first time I want to use the built in image crop feature of the admin. I'm using PW 3.0.108 Cropping in the admin is fun, displaying the result on the frontend is not... So I have an Image field named pictures, and let's say I upload one image. Then I crop it and click "Save as Copy". At this stage two images are displayed in the admin; the original and the cropped one. So far so good. And I presumed that outputting both is easy, until I realized that the Pageimages I get by $page->pictures has only one image, the original one. No matter how many new images are generated by cropping, they are never included in the resulting Pageimages array, but why?

Similar discussion:

Hello, Here come a few pointers: payment integration: http://omnipay.thephpleague.com https://www.payrexx.com/en/pricing/pricing/ https://processwire.com/talk/topic/14808-now-my-client-wants-to-add-ecommerce/ https://processwire.com/talk/topic/14511-e-commerce-tutorial-with-processwire-snipcart-your-thoughts/ member restriction: for backend: https://processwire.com/talk/topic/11499-admin-restrict-branch/ https://modules.processwire.com/modules/textformatter-soundmanager/ Subscription management https://processwire.com/talk/topic/16363-recurme-–-processwire-recurring-dates-field-custom-calendar-module/ AJAX front end editing for building playlists & "likes" while PW has frontend editing support: https://processwire.com/blog/posts/front-end-editing-now-in-processwire-3.0-alpha-4/ you might find that rolling out your on frontend solution is more versatile in your case so maybe you want to take a look at this one http://intercoolerjs.org/ or you might want to do it all in the admin: https://processwire.com/blog/posts/building-custom-admin-pages-with-process-modules/ or both frontend AND admin ? related: https://processwire.com/talk/topic/7913-podcast-profile/ https://processwire.com/talk/topic/12752-pw-podcast-theme-for-podcasts/ Hope this helps.

So let's call it a scam as we should not call it web development. Playing dirty tricks is one thing and being honest and helpful is another one. I always stick to the latter. Sure, I will never become a billionaire with my "silly" attitude but at least no hordes of angry people are chasing me my whole life. Instead, I have a bunch of friends who know they can trust me.

Why? It is a very nice Plug&Pray platform. Oh well, yes, that is a skeleton in the cupboard. It is such a bad example of "simplifying" queries that even plugin developers are rolling out their replacements, eg: https://toolset.com/documentation/customizing-sites-using-php/post-relationships-api/ or WooCommerce which nowadays is the same as Automattic: https://woocommerce.wordpress.com/2018/07/17/woocommerce-custom-product-tables-beta/ "This builds on the investment we made in 3.0 which introduced Data Stores and CRUD functionality that provides a uniform way of accessing a store’s data regardless of where it is saved." and even the core WordPress team: http://v2.wp-api.org/ Hordes of talented developers are trying the get rid of the underlying crap but all in different directions. It will be interesting to see how it will turn out... In the meantime, the main effort is to replace the back-end: https://wordpress.org/gutenberg/ However, I have not read anything about getting rid of all the other junk WordPress has in big quantities. BTW, WordPress is the winner in another area: http://blog.insight.sensiolabs.com/2014/11/04/technical-debt-relevant-projects.html

https://github.com/processwire/processwire/blob/dev/wire/modules/Inputfield/InputfieldImage/PWImageResizer.js It has some example code as well. I've never tried to utilize it though... It is based on this one https://github.com/rossturner/HTML5-ImageUploader as described by Ryan here: https://processwire.com/blog/posts/processwire-3.0.63-adds-client-side-image-resizing/ Hope this helps.

I'm glad you could have it fixed, however it is worth to note that the site might also get hit by other mod_security rules in the future, so it is best to turn off mod_security altogether. ProcessWire does not need it.... for example: http://www.amitb.info/dealing-with-a-mod_security-nightmare-with-apache-and-codeigniter/ quote: "First thing, don’t waste your time chatting with your hosting company support staff. The front line support staff is not very equipped with dealing these complicated things. They are usually adept in dealing with normal things which occurs in volumes. So skip them altogether." also: https://stackoverflow.com/questions/12928360/how-can-i-disable-mod-security-in-htaccess-file

I would go for it. As Ryan pointed out, sending a Mac to a repair shop can cost a lot of money and I think the "safest" Apple laptops these days are the end of the line 2015 models. Generally speaking, end of the line models always suffer from less factory issues than brand new designs (which is the case with the 2017 line).

Apple has a long record of producing brand new hardware design with various issues. However, in the past they used to repair them for free. These days they produce non-reparable machines in order to make them as flat as possible. This move is very concerning to say the least ? I only buy Macs because of mac OS. I would never use Windows. If mac OS dies for some reason, for me the only choice left is Linux.

As I quoted you, I have the 2015 MBP, 16GB RAM and 256GB SSG. This is the standard model which became cheaper ($1600) when the 2017 model was released. I've been using it for almost 2 years without any issues.

Watching some youtubers describing the faulty key issue, it appears to me that those dead keys are not covered by warranty but I might be wrong. Regarding displays, I used to get one replaced still covered by the standard one year warranty. It's just those new key issues is the one that Apple tries to ignore... No, I do not. I only render still 3D images and by using the CPU – also not too often – so I do not need more in this field.

I'm working on this one. I like it a lot. Macs have speedy SSDs so multitasking is NOT an issue, even if you use Adobe programs parallel. In the past I could even work on a Air with 4GB RAM but to speed up 3D rendering (which I do sometimes) I had to switch. I do not know about Docker as I have MAMP Pro, but running NetBeans, 4 or more Adobe programs, 3 browsers, MAMP Pro, Mail app and 10 or more utilities is not an issue for me. It just runs fine. Also, 2017 MacBook Pros have bad record of keys of the keyboard becoming faulty and not working anymore. For this reason I would never buy a 2017 MBP. I hope this year's new keyboard update solves this issue. We'll see... BTW, I guess it is more like a Dev Talk than a General Support as it is not really ProcessWire related.

I guess Ryan updates it from time-to-time. Up-to-date and with more info is grabbed from the source code for those who have the API Explorer module of Ryan's ProDevTools: See: Introducing the API Explorer module

I would never rely on such online services. I also never let browsers save passwords nor credit card info (even worse). What I use is: https://keepassxc.org/download/ Original project: https://keepass.info/download.html

From the blog post: "This will enable us to support different types 2-factor authentication and different providers. Much in the same way that we support different types of email providers with WireMail modules." I think there must be API based support to make individual authentication methods easier to implement.

Hey guys, @jmartsch's initial post has 10 likes but the Github request only 5 thumbs-ups. Those who really want to support the request please do not forget to perform that click either.

I reckon superusers will have the option to force 2FA upon all users, won't they? So far it sounds like this bit is not yet implemented, quote: "Once enabled, individual users CAN ENABLE 2-factor authentication for their account in the ProcessWire user profile editor."

Hello, Related thread: https://processwire.com/talk/topic/1751-cant-get-pw-to-output-german-month-names/ you might also want to check out the first few results of this search: https://www.google.hu/search?q=admin+language+date+input+field+site%3Aprocesswire.com%2Ftalk Hope this helps.

Generally speaking ProcessWire v2 modules should work under ProcessWire 3.x. The big change was to use namespaces in ProcessWire 3 but PW's "compiler" should take care of it in case of PW v2 modules. https://processwire.com/blog/posts/processwire-3.0.14-updates-file-compiler-fields-and-more/#file-compiler-updates If a module doesn't have a namespace, then FileCompiler will compile it to make it run under ProcessWire 3. Sure, there could be other issues as well, but it looks like a basic module using the PW API and was coded by Ryan, so I guess it works. Give it a try ?

Thanks for the tip @LMD It is worth to note the new "tags for fields" search "shortcut" of ProcessWire 3.0.106: https://processwire.com/blog/posts/pw-3.0.106/ I guess title|field_a|field_b in your example could be simplified too by using this new feature. Provided it supports "named selectors".

Hi, have you solved it yet? I'm asking this because if not, can you please clarify what you are after? I'm not following you...

What if that required image one day becomes non-required? Usually I try not to rely on such settings.

If I'n not wrong, @kongondo's VisualPageSelector module (commercial) should solve such an issue as it uses lister and its filters to select the related page: quote: "electable pages as per page field settings + Lister filters" see more: Or you might want to implement your own InputField which also uses ProcessWire's Lister and its user customizable page filter to select the page.

I am yet to check out this module so I am for sure not the best person to answer this questions, however I think if you just write a short manual migration guide and prevent accidental upgrading then it should be enough for us developers.