adrian

Hi @PWaddict - thanks for the report and for finding the solution - much appreciated. I have removed the changes from that update (I agree that the Page Name core module should be used to define those replacements). I noticed in the original version of your last post you mentioned a second more critical bug, but you've now deleted that - can you please confirm that everything is in fact OK with that and that nothing needs fixing?

Hi @itsberni - sorry for such a delayed response - I am just back from an extended time away from my computer. I have added a new Bcc email field to the module config settings. All emails will be Bcc'd to the entered address automatically. Please let me know how it goes for you.

Hi @Arcturus - sorry for such a delayed response - I am just back from an extended time away from my computer. I can't imagine why it's not working for you, unless you are entering the entire "416 7773333" in the main number sub field. The 416 area code needs to be entered in the area code subfield. Could you please confirm how you are entering things and also the settings for the "cell_phone" field with some screenshots so I can help you diagnose?

Hi @elabx - sorry for the long delay. Currently there isn't an option to provide a selector to filter the child pages being exported. It wouldn't be a terribly complex addition, but remember that if you have ListerPro, you can do this using the CSV export action. Do you have access to this?

Thanks for the report @Marcel Stäheli - it should be fixed in the latest version of BCE. Please let me know if you have any more troubles.

Hi @Pretobrazza and @CodeCoffeeCode - I am sorry for the very long delay in responding - I have just returned from an extended time away from my computer. It looks like the issues you were having with textareas fields and the map marker were actually due to PHP 7. The latest version should fix things - I tested with textareas which now work perfectly again - hopefully map marker fields will also work again now. I have also fixed some other issues with adding multiple new child in Edit mode and also taken care of this issue. Please let me know how things work for you now.

Just a repeat of part of a message above so hopefully more of you will see it: I am going to be mostly offline for the next 2 months, starting right now It's going to be strange being away from PW and the forums for so long. Hopefully if anyone has any issues with this (or any of my other modules), some of you who are more experienced might be able to help, or at least let those users know that I am away and will take care of things when I return. Cheers all!

Ryan just got back to my PM and this should now be fixed.

Thanks @Robin S - should be fixed in the latest version. Although, I am wondering if perhaps I should be disabling much of Tracy in CLI mode anyway. Maybe just disable the debug bar, but allow for error logging still? Any thoughts?

Sorry @mel47 - I am still not sure exactly what is happening here. I can't see what the title(s) are for that page. BCE should create the names from the entered titles, but of course the support for multi-language is limited to display rather than entry. It would really help to get a list of exactly what you are doing, in what order, and some examples of the pages you are creating via BCE. Remember that PageRenameOptions is for when you change the title of an existing page - it doesn't really impact newly created pages, which is what I think you are doing with BCE.

@Robin S - can you please test with the latest version of Tracy and let me know the current line numbers that are reporting that notice (if any) - those line numbers you are reporting don't seem to match the current version. I fixed something like this a while back (https://github.com/adrianbj/TracyDebugger/commit/8e8309e13c9edf6ad36f0e29b91cc52b77ffc7e1), but maybe there are still some outstanding issues.

The PagePath module is not affecting what you are seeing - that just records any changes and creates automatic redirects. As for the "name not being the good one", can you please provide some examples of exactly what you are entering into BCE, the page names you are getting and what you expect/want them to be.

Done!

Not sure if it suits your needs or not, but you can link to the admin page tree like this: http://mysite.com/processwire/page/?open=1045&open=1046 Sorry, ignore that (only works for one ID) and I have to run, so can't investigate further right now.

Hey @horst - now that Chrome (https://9to5google.com/2017/04/27/chrome-59-animated-png/) (and others) are supporting aPNGs have you looked into what is needed to support this in PW?

@incognito.ms - I just took a look into that notice and I have fixed it in the latest version - thanks for reporting!

Your module submitted fine and I have approved it, but please check your author details.

Thanks @rick for those screenshots. Unfortunately I am having trouble reproducing at the moment - the console panel is automatically adjusting its height to match the available viewport and the code and results windows are both scrollable and the window title bar is always visible. I assume you are running the latest version of Tracy? If you notice something specific that causes the title/header bar to be above the viewport, please let me know. In the meantime, I will keep an eye out myself, but as a heads up to you and everyone else here, I am going to be mostly offline for the next 2 months - it's going to be strange being away from PW and the forums for so long. Cheers, Adrian

Hi @incognito.ms - I am not sure why you are seeing that - I define the "showDebugBar" index here: https://github.com/adrianbj/TracyDebugger/blob/bf9ab88cc9d15e4f0ec06193c30873b7f15af54c/TracyDebugger.module#L150 Is this something that only happens with ProcessWire 3.0., or have you seen it with earlier versions as well? Fixed - see other reply further down. Hi @rick - it should already be scrollable, eg: Is the problem always present for you, or are there just some circumstances that cause it not to scroll?

My module (https://processwire.com/talk/topic/9496-restrict-tab-view/) mentioned above still works fine in PW 3 if that's helpful for you.

No problem - I'm used to it I am away next week, so it's now or not for a while. I have committed a quick update that should take care of Profields Textareas. Please let me know if you have any problems. I really need to revisit this action and add support for other field types as well - for example I haven't tested inside repeaters or page tables. I'll add this to my list, but might be a while.

It shouldn't be hard to support. When I set this action up I limited it to text and textarea fields, but it makes sense to expand to others - I just didn't have time to test it then. I'll see what I can do tomorrow to get this working for you.

Thank you both for getting to the bottom of this! @tpr - I did tweak your changes slightly to use "one" and "mouseover": $(document).one('mouseover', bce_adminDataTableSelector, function () { instead of "on" and "hover": $(document).on('hover', bce_adminDataTableSelector, function () { so that it's triggered only once. I know you had another check in there to see if the controls were already added, but I still think this an improvement. Do you see any issues with this change?

Ah yes - sorry I missed the importance of "View" - that definitely seems odd and a bug - do you agree @ryan ?

?s=1 has always been there, but yes, c=0 is new: https://github.com/processwire/processwire/commit/75a969bafbd95143013f015c3e726d82087cc68a#diff-18988bf581321686eb798ec4f657506fR1455