szabesz

Hello, If it is a fresh ProcessWire install then we are probably talking about a bug. If you have the time, could you please try it with the latest "stable" (3.0.98) too? And based on the results I guess you will be able to decide whether to report it or not.

I have ff Works too and often use it to covert video files. While I like its GUI and ffmpeg too, the fact that ff Work's GUI is not mac OS native makes it a bit cumbersome to use in some cases but for the price/features ratio I have not found a better alternative.

+1 I've been also wondering about this for a while ?

Have you heard of storage quota? ?

Hey @horst n @pwired How could you forget @bernhard's blog post? https://processwire.com/blog/posts/building-custom-admin-pages-with-process-modules/? @TheProcessWireLearner Welcome to the forums! Regarding PHP itself: https://www.tutorialspoint.com/php/php_constants.htm I like recommending this, as reading these tutorial pages is enough for anyone to get started, you do not need to know too much more PHP in order to achieve a lot with ProcessWire. I also recommend keeping an eye on: https://processwire.com/talk/discover/unread/?&view=condensed in order to learn from others.

Pretty good article about jQuery and the craziness of rejecting it "no matter what": https://www.i-programmer.info/news/167-javascript/12017-github-removes-jquery-why.html

A joke? Sounds quite realistic to me ?

I agree that the description is a bit ambiguous, I've been also wondering how to properly interpret it but I came to a similar conclusion, ie. this option is for "front-end API calls only" meaning where output formatting is ON by default: Quote: "pages on the front-end of your site always have output formatting on, unless you've turned it off, with $page->of(false)." Output formatting is always off in a module by default, and the explanation in your screenshot has examples with $page and not $this->page. Also, it is talking about front-end API access checks only. As a result, if it does not affect backend (ie. admin) access checks, then you can use this option for what you are describing, At least I use it that way too ? However, maybe others can put together a better explanation than this one of mine ?

Hi, I always limit PW's Images inputfield to 50 images which is normally just enough for most sites and it also makes sure storage requirement does not skyrocket ... I guess it is not feasible for this site you mention, so you might want to consider using @kongondo's Media Manager module: https://mediamanager.kongondo.com/ sure it is commercial but at the same time feature rich and should not have problems dealing with lots and lots of images.

Exporting is a resource intensive task, if you have a lot to export.... In this case I would recommend cloning the site by copying all files, adjusting config.php and anything else that matters + simply cloning the database too. You can automate it by scripting or using a tool which supports such operations. There are various forum threads discussing it, for example: https://processwire.com/talk/topic/14837-best-practise-to-implement-changes-in-pw-from-development-to-production/ https://processwire.com/talk/topic/3998-your-deployment-process/ https://processwire.com/talk/topic/3113-how-to-transfer-processwire-from-local-installation-to-online/ etc...

I could track it down and reported it as it looks like a bug in the core: https://github.com/processwire/processwire-issues/issues/650 In short: If Inputfiled Images with "Overwrite existing files" is ON then creating a cropped image yields created=1970-01-01 01:00:10, ie. when this option is on, ProcessWire does not update the "created" field in the database. Thanks for the help guys!

I have uninstalled almost all third party stuff to no avail. I also tested another site of mine which was last updated half a year ago or so, and that site has the same issue even though that the "old" site was developed "from scratch" just as this one I am working on. So the relation between the two is that I use similar modules and settings, of course. I also installed a clean PW 3.0.108 which works as expected.

Thanks a lot! I've been hit by this "1970-01-01 01:00:10" issue for sure! If I manually change created in the db table, then all is good. Now I "just" have to track down what causes this. Since I do not even have any hooks added by me just yet, it is probably a module in action. At least this is where I look first. No, it' doesn't sound like that. I just forgot to state that it happens with all sorts of JPGs I tried.

Yep, they do look suspicious but I cannot see where to go from here... @ryan or @horst maybe? ? I need to go to bed now but in the morning I will try it out with a clean install. Thanks for your time!

Yes, that's what you can see in the screenshot. I've been fiddling with this issue for three hours by now ? I also created another one, I have them both along with the original one:

0 or 50, does not matter. Thanks for testing, Robin! This is my result: And I have the cropped copy as the first one, but obviously in my case $page->pictures->first() gets the "second one"... Black magic? ?

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).