adrian

Please try the latest version just committed - this should now be taken care of. I am still not sure about the country/extension checkboxes - they are working fine here. Could you please try the latest version anyway and see if it helps, but also any other info about the field would be helpful.

On that important point, if you decide to use the BCE module, note this config setting:

Almost one click - check out the Batch Child Editor module: http://modules.processwire.com/modules/batch-child-editor/ - either Edit or Replace mode. You could also code an API snippet and store it in the Tracy Console panel snippets list - just run it from the parent page (either on the frontend, or while editing the parent page in the backend - the console will get $page as the page being edited): Or you could use that code in an AdminActions (http://modules.processwire.com/modules/process-admin-actions/) action.

Hi @godmok - thanks for the report - regarding the checkboxes not sticking, I am not seeing that issue here. Is your phone field just a regular field, or is it inside a repeater, or is there anything else unusual? As for the labels not appearing unless explicitly set, I will check that shortly. I'll play around with more options for setting the subfields widths.

I have just been playing around with the "Selector Queries" section of the Tracy Debug Mode panel. Now it adds the SQL Query column to show you the query that was used for each of the selectors called in generating the current page. I am not yet convinced it's perfect for all selectors, so I haven't committed it yet, but if anyone would like to try it out, I can either post here or push to a dev branch. Also, any thoughts on this? How useful it is, and if you have ideas for making it more useful.

Hi @lpa - sorry you're having trouble with this approach. I have definitely used it before with the "intermediate" approach, but it turns out I was doing things a little different in terms of how files were being prepended. I just tried with the regular intermediate templating approach and I could reproduce the errors you were seeing. I have a fix in place for you though. My login.php template file looks like this. <?php $content = $page->loginForm; include '_main.php'; Obviously you can use whatever *.php file you want - selected from the module settings. The key difference now is that you must use: $page->loginForm and not $loginForm Please test the attached version (I don't want to commit just yet) and let me know how you go. PageProtector.zip

I quick follow up on the Form Builder issue - I have a posted a solution to that FB thread - hopefully Ryan will implement, but if anyone wants to use it in the meantime, you can make the change I indicated here:

@szabesz and @godmok Ok, new version supports custom labels and input widths on a per field basis. The subfield labels are now also translatable: So in this example, the Spanish rendering looks like this: Please let me know if you have any issues/suggestions. Note for @mel47 - there is currently an issue with the multi-language subfield labels in FormBuilder. Waiting on Ryan here: https://processwire.com/talk/topic/18347-subfield-uselanguages-not-getting-re-populated/

Just an FYI that PW actually disabled the strict setting to avoid this error. This is something that I think should be changed in the future. I dealt with upgrading a lot of complex queries on a non-PW project a while ago and it can be a pretty painful migration - in some cases the results can actually be quite different so some caution is definitely needed.

Take a look at the screenshot in this post:

Yep, coming soon - I have to get off the computer for now, but here is what it looks like. I'll try to commit later today. Do you think we want pixel or percentage widths? Do we want to make sure there is a enough room for all the digits, or do we want to make sure it fits on one line (which could be an issue with pixels if the phone field itself is maybe 33% (or less) of the row). Any thoughts? Settings: Input:

See if this helps: https://processwire.com/talk/topic/17089-images-disapear-after-uploading-and-saving/?do=findComment&comment=150139

Thanks for the report - i was missing a formatValue method which is needed by Lister. Please try the latest version and let me know how that goes for you.

You need to take a look at the Network panel and view the reponse for the ajax upload script - it looks like a PHP error that is causing that unexpected character - probablt something about memory.

@godmok, @szabesz and @mel47 - could you please try the latest version on the dev branch. I had to rejig a few things to get this new version to also work with Form Builder. @mel47 - please read my previous post above regarding the breaking changes in this new version. I'll be making this the master version once I have confirmation from you guys that you aren't seeing any problems. I don't like introducing breaking changes, but in this case it was necessary to allow more flexibility for calling custom outputs via the API. Thanks!

Look here, there is complete upgrade procedure with help: Thanks for chiming in @horst - I have already linked to that: This is the problem with multiple threads for the same issue, but I think @Oca2 has the message on that now

http://modules.processwire.com/modules/markup-social-share-buttons/

@bernhard - not sure if this is useful or not, but it shows you the SQL that the PageFinder uses for a given selector.

Each page can be restricted to a user role, so you could setup each page to be limited to a different role and assign these roles to separate users - I think this would give you what you want. But without knowing exactly your scenario, it's hard to know if this would be the best option or not. You might be better off with a custom module or a ready.php hook on Page::render and handle the logic that way.

Sorry to sound like a broken record, but CroppableImage returns a pageimage object, not a url, so you need to add ->url to the end of that: <img src='{$child->overviewimg->eq(0)->getCrop('thumbnail')->url}' alt='$child->title'> If you take a look at the HTML source of the page you would have seen that it was return an ID and not a URL to the image. Also another tip is to use the Console Panel in Tracy to investigate things. In particular note what happens when you echo (which outputs a string) that it returns the filename, but not the URL.

Have you looked at the path to the image in the HTML? Did you add the ->url at the end? If it's a multiple images field, you will also need ->first() in there or a foreach loop to get each image individually.

@Oca2 - please try to avoid double posting and if you do, please follow up on both so people don't try to help you when you've already been helped. Thanks! Cheers, Adrian

It sounds like your site/assets/files folder is not writable. You can check out the Diagnostics panel in Tracy for info on the settings for each of the key directories.

You need to have a read of this: https://processwire.com/talk/topic/14251-upgrading-from-thumbnails-module-to-croppable-image-3/ Also note that once you have taken care of that, you need to add ->url to the end of your src - croppable image returns a pageimage object, not a url like the old module did.

I don't think Croppable image has this method - I think you'll have to updated your API calls for this module.