adrian

Sorry @ukyo - I can't reproduce here. Could you please try dumping $pagefile, $suffix, and $pagefile->getCrop($suffix) just before line 139 to see what we are dealing with. Thanks!

Hi @tkaranka - sorry about that. However, I am not seeing the problem here, so I might need a little more info from you. That error comes from code dealing with field types that extend Multi - the most common one being images so I am wondering if there is something specific about the setup of that field. Could you please try to dump the value of: $fieldName just before line 159. And also, the value of: count($p->$fieldName) Tracy's bd() will be the easiest way to do this if you have it installed. Thanks!

FYI, I have posted a github request about this name of the Delete tab in the hopes that we can get a little better consistency: https://github.com/processwire/processwire-requests/issues/36

Hi everyone, I have just updated this module to support insertion of Hanna codes, and renamed it to DynamicDescriptionNotes. It passes the $page (for the current page being edited) and $field (for the $field where the Description or Notes text is referencing the Hanna code, so you can use $page and $hanna->field in your Hanna code to refer to these. This opens up lots of possibilities for dynamic content. Please let me know if you have any problems or suggestions. A big thank to @Robin S for the awesome idea! PS, It's now available from the modules directory: http://modules.processwire.com/modules/dynamic-description-notes/

This trash vs delete conversation makes me think that the Delete tab on the edit page interface should actually be called Trash. The page list action button is Trash, but the Delete tab does the same thing so they should be named for consistency.

I guess what you are saying here is if you set the "Estimated End of Maintenance" to a very short time from now, then the Retry-After timestamp will be changing constantly as soon as that initial timestamp point is reached. Is that what you mean but "without a fixed timestamp"? I see that the Retry-After actually allows specifying a timestamp or a delay in seconds, but a constantly changing timestamp would essentially be the same as the "seconds delayed" approach?

Ok, I have committed the new version. A huge thanks to @horst for contributing this functionality. Here are the key new sections to the module config: @Christophe - just pinging you to make sure you see this new functionality.

Yeah, that's essentially what I have done. Any thoughts/experience with this: http://www.nurkiewicz.com/2015/02/retry-after-http-header-in-practice.html What clients do you think they are referring to? I would have thought that search bots might be triggered by this, but doubt they would all hit it immediately at the Retry-After time. As for manual users - that is unlikely also. I guess I could randomize the Retry-After time somewhat - maybe at 1 minute intervals for up to 10 minutes after the entered time, but it sounds like overkill for almost all sites. I'll ignore unless you have any strong thoughts on it.

I'd like to hear more on your thoughts about this, because I was just finalizing incorporating your changes and I was about to add a protected vs maintenance option, because I know that many people use this module to protect a site that is always protected (it is only ever for logged in users), so I am not sure in this case that Retry-After is appropriate, because it will always be inaccessible. I don't really think 503 sounds appropriate either. If you have a site that is protected from public view then you don't care about SEO anyways Is there something obvious I am missing?

Hey @horst - I am happy to add that functionality to this module, but I guess I thought it belong more in Pete's module, but if you guys would rather see it here, that's fine with me. Do you feel like sending me a PR? Otherwise if you post the zip, I can grab the relevant bits and incorporate.

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.