adrian

Hi @ukyo - thanks for those details. Unfortunately I can't reproduce the problem here. I put this Tracy dump call just before line 139 (as reported in the error): bd($pagefile->getCrop($suffix)->url); and it is correctly reporting the url to the cropped version of the file. Perhaps there is a certain sequence of events that is required to trigger the error. Could you please detail exactly the steps involved starting from a new images field, including the crop settings you have configured for the field.

I'll take a look, but can you first post a screenshot of your settings for this module and also any dev console Network tab errors coming from the upload ajax request?

What you are looking for is: Pages::cloned Take a look at @BitPoet's module: https://github.com/BitPoet/ProcessPageCloneAdaptUrls/blob/master/ProcessPageCloneAdaptUrls.module#L30

Neither of those are designed for maintenance operations. You might be better off with: http://modules.processwire.com/modules/maintenance-mode/ - unfortunately is currently doesn't throw a 503 either, but it should be a very simple change - perhaps you could send a PR to @Pete if you decide to use it and add that?

I think this is a PW issue in general. I think there has been some discussion on it (but can't find it right now), so I am not sure why it was decided to not support utf8 filenames but that was before PW supportedUTF8 page names, so maybe it is time to revisit?

Have you read the API instructions for adding rows to tables in the Profields Table support board? Are you trying to update existing rows, or insert new ones? The first thing I notice though is that you are overwriting the $pages variable to one specific page and also getting that page in every step of your loop. Also, please don't reply here, but rather re-post this question in the Table support board with some more details as I mention above.

Just wanted to let you know you guys know that there have been a few tweaks to the console panel of late - nothing major, but improvements to error handling, and also notes that say "Processing" and "Completed" so you know that your script is running and when it has completed which is very handy when you are running a script that manipulates content, but doesn't output anything. I was also just reminded of the outstanding issues with the AJAX bar and the PW SessionHandlerDB module - I was testing something on an older site (built when I used to install SessionHandlerDB as a matter of course) and couldn't figure out why bd() calls from the console panel weren't triggering the ajax bar to load. I usually use d() from the console panel so the results are right there and you don't need to refer to the dumps/dumps recorder panel, seeing the bd() reminded me that it's still not sorted. Anyway, just wanted to remind everyone who uses SessionHandlerDB about this in case you didn't know / forgot like I did

The template for that page has a "requiredIf" dependency on a field that requires that requires some value from the "feature_image" field, but that doesn't exist in the template, so you either need to add that field to the template or remove the requiredif dependency. You are looking for something like this on one of the other fields on that page's template:

This ancient PR (https://github.com/ryancramerdesign/ProcessWire/pull/954/files?w=1) makes several changes to the comment field for logged in users, including using local profile image, and hiding (and autofilling) the name and the email field. I know it doesn't really help you, but does let you know that others have similar needs I should maybe resubmit the PR to the new Github repo.

TracyDebugger - use the Dumps Recorder panel and if you have to, use the "Preserve Dumps" checkbox (although you probably won't need it). Then insert a bd($var) call into your code - easy as pie PS Who uses var_dump anymore

CkEditor itself has been around for a very long time and the default editor in PW since July 2014 Before you do anything else, go grab the latest version of PW here: https://github.com/processwire/processwire

I know this is ancient, but I just had to do this and discovered a very simple way $pages->emptyTrash(); Maybe this is newish?

Just for your own clarity, it might be better to use addHookAfter, because addHook can actually be used to add your own method to a class. https://processwire.com/api/hooks/

Namespace issue? Is the template being processed by the file compiler, but this module isn't?

Just to clarify, I think @Konrad is talking about this: https://bitnami.com/stack/processwire You might want to consider just downloading the version from Github as the Bitnami one is now out of date.

@Juergen - If you have a few moments, I think it would be helpful if you could test @BitPoet's changes to confirm they work so that these changes might be incorporated into the core. Thanks!

Am I seeing things, or are you actually running the TinyMCE module instead of the default CKEditor? What version of PW?

No, you shouldn't leave it deactivated - it is designed to reduce dictionary login attacks. I have just messaged Ryan to see if I can find out more about the behavior of the module also recording successful logins. If that can't be changed, then you may need to set up your own access control if you want to give all users just one login account. Stay tuned - I don't want to send you down the path of setting up something else until I hear from Ryan about the behavior of this module.

Actually now that I think about it - I actually wonder if there is a bug in the throttle module because I thought it should only record failed login attempts, not successful ones - just investigating now. I can trigger the ban by successfully logging in out quickly several times.

If everyone has the same login username, then absolutely - that is what the session login throttle is designed to do. I think your quickest solution will be to disable the SessionLoginThrottle module. Just wanted to get that option to you quickly - I'll post some better solutions in a minute.

Ok, well let me know when you can test again later. I am guessing the error was appropriate at the time, and not related to this module. Don't worry about the session_login_throttle database table at this stage.

Silly question, but are you using the same username on frontend and admin logins? What happens if you wait 35 seconds - can you then login successfully? Any sign of weirdness in your session_login_throttle database table? Perhaps you could empty that table?

Does this error happen repeatably on the frontend, but not via the normal admin login?

Nice work Steve! Sounds like a perfect use case for the log viewer in Tracy

I definitely try to use the Options fieldtype when I can - I just try to think through fully what flexibility I might be giving up. Unless I am missing something, I don't think there is a way for site editors to add new items to an Options field, so wouldn't that be one of the biggest difference right there? One of the other key reasons I used Pages for years in that one project was because I wanted the year pages to drive the rows in @kongondo's excellent Matrix fieldtype. Although since he introduced the custom php code option, it might actually be possible to do that with an Options fieldtype now