adrian

Not suggesting that we need to replace CkEditor - I think the integration with PW is working quite nicely, but I just stumbled across this and thought I'd throw it out there as another future possibility: http://quilljs.com/

Ok, I have added an optional "Format Export" option. It is on by default when you upgrade to the latest version of BCE, but you can easily uncheck this in the module config settings and then your imports should work as expected. As for the line break stuff - to make it easier for me to debug, could you please send me an example CSV export from BCE that shows the problem.

Hi @elabx - glad you're finding the module so useful. I think this line is the culprit: https://github.com/adrianbj/BatchChildEditor/blob/master/ProcessChildrenCsvExport.module#L106 I think there are use cases for wanting the CSV export formatted and cases when you wouldn't want it formatted. I will make this configurable so that the dev (and optionally the user) can decide. But before I do that, could you please comment out that line to make sure everything works as expected for you. Actually I see another line that will interfere for multiplier and file fields: https://github.com/adrianbj/BatchChildEditor/blob/master/ProcessChildrenCsvExport.module#L183 - this may or may not affect you. Thanks!

Sorry about that - you must be running PHP 5.3.x. I had some code in there that was 5.4+ only. I have made a fix so that it will work on 5.3. Please try again with the latest version on Github.

Hi @Beluga, Firstly, is it only the test send that isn't working, or do they also fail when adding a new user? Well I don't think there should be a reason why the syntax you changed it to should work while the: wireMail('user@domain.com', 'ryan@runs.pw', 'Mail Subject', 'Mail Body'); syntax won't. I think the most likely problem is that I had an incorrect static call to a non-static method in there when doing the test send. Maybe your new server is failing on strict errors? I have fixed this in the latest version. Please let me know if that fixes it for you. If it doesn't then you could play with Tracy like this and make sure they all return what is expected. // send test email if requested if (wire('input')->post->test) { bd(wire('user')->email, 'Admin User Email'); bd($data['fromEmail'], 'From Email'); bd($data['subject'], 'Subject'); // not really relevant, but may as well confirm its value bd(EmailNewUser::parseBody($data['body'], $data['fromEmail'], wire('user'), 'password'), 'Body'); // again, not really relevant wireMail(wire('user')->email, $data['fromEmail'], $data['subject'], self::parseBody($data['body'], $data['fromEmail'], wire('user'), 'password')); } You will of course have to enable the Tracy debug bar for the backend.

Looks cool and a big plus one because it uses MeteorJS !

Sorry about that @mr-fan - looks like a forgot to change the name of a few variables when I did some refactoring a while back. This only affected CSV creation of pages. Please check the latest version and let me know if you still have any problems. I know I am OT and bordering on self promotion (actually it's promoting the Tracy guys), but the new AJAX functionality that just got added to TracyDebugger made debugging this so easy

Hi @gunter, I don't have much time, but have a read of this blog post: https://processwire.com/blog/posts/new-module-configuration-options/

Hi everyone, New version just committed. It comes packaged with both stable (2.3.10 - what it was using before) and master (2.4 dev) versions of Tracy. If you have PHP 5.4.4+ it will use the master/dev version which among other improvements, adds support for monitoring of, and allowing dumping from, AJAX calls. One quick way to see the AJAX monitoring in effect is to check "Backend" under the "Show Debug Bar" config option. Then hover over the PW menu in the admin to one of the AJAX-driven submenus - notice the new row in the debug bar showing the time etc for the AJAX request. You'll also see this popup when clicking on the Children tab when editing a page, and several other places throughout the PW admin. Of course this will also work for any AJAX requests on the front-end of you site. Here's a screenshot showing both rows (normal and ajax) with the Dumps panels for both. I have two bd() calls - one "classic" and one via "ajax". Please let me know if you notice any issues with this new version.

Thank you Ivan - very kind words indeed There is definitely something about this community - Ryan has managed to foster an environment where people really want to share and help others - almost addictively. I think it's a very rare thing we have here. I completely agree - I was actually wondering myself how I was going to manage to make something useful out of all the info in the support thread. I guess it should probably end up in the ReadMe at some point, but then I don't really like having unnecessary screenshot images in the Github repo, so the blog request by Ryan came at a very good time in the evolution of this module. Thanks again.

Just wanted to let you all know that I added a new section to the blog post. Hard to believe I had missed anything given how long it already was, but this new section deals with Access Permissions / Restrictions and how they are controlled/related to the Detect, Development, & Production Modes. Here's the shortcut link to this new section: https://processwire.com/blog/posts/introducing-tracy-debugger/#access-permissions-restrictions Hopefully you'll find it useful in understanding who has access to what with which settings. Please let me know if there is still something that isn't clear or even if you have suggestions on how the settings/logic might be tweaked.

The only things that won't work in 2.7 are the NonPW Template Variables panel, and the Runtime Debug Statements functionality. I feel like there should be a way to make the former work in 2.7 but I haven't figured it out yet and with 3.x stable not that far away I don't have too much motivation to. The latter won't though, although as mentioned it's a bit of an obscure feature anyway

@Christophe and @jploch - I have committed a very quick fix that allows this module to work even if you don't have ffmpeg installed. Obviously the ability to grab poster images for the video won't work. Also it won't be able to determine the length of the video. Both of these require ffmpeg. I will revisit this again when I am back from vacation and add the ability to manually upload a poster image, but for now at least this module will work and you can now have the benefits of automatically playing videos with a simple: echo $page->video_field->play; Hope that helps as an interim improvement.

Hi @ottogal, I have just committed a new version which handles both your requests: hiding the instructions about the shortcut to protecting the entire site ability to set a default Prohibited Message in the module's config settings. Let me know if you have any problems with this.

Hi @slave - sorry you haven't had a reply until now. I haven't tried that combination myself, so not sure if it will work or not, but the new Repeater Matrix field sounds like it might suit your needs: https://processwire.com/api/modules/profields/repeater-matrix/

I just added another option to this module that can limit the automatic naming to match the title to only unpublished pages. If the page is published, the name will be left untouched. This might help out those users who are steadfast in their opinion that the URL to a page should never change - not judging this opinion by the way - it is a very strong argument. With this new setting you can change the title multiple times while it's still in unpublished (in draft if you will) and the name will change automatically. Once it is published, changes to the title won't affect the name. Hope that wins a few more users over

Thanks for the kudos - and yes, I will look into adding that Xdebug helper module (https://componette.com/jsmitka/nette-xdebug-helper/). There is actually another one that I didn't mention in the post: https://componette.com/milo/xdebugtracepanel/ which is for showing Xdebug traces in a Tracy panel - it is currently abandoned, but the author says he is working on a new version, but not sure on the status of that. I shouldn't be, and I am not really - I was just silly enough to check my email the other day and saw a request from Ryan for a blog post. I am actually away on an extended trip, so I don' really mind

The latest PW blog post is all about TracyDebugger: https://processwire.com/blog/posts/introducing-tracy-debugger/ Hope you guys find some new info and tips in there - sorry, it's a pretty long read

Might be an option. I'll have a play with the new ajax stuff in the latest version of Tracy and see if it's worth it.

Cool, I hadn't seen this yet - could be very handy!

Can I just say that even though it looks cool, it is almost as bad as a 90's splashscreen to me - please don't help to perpetuate the return of that evil! PS - I wouldn't mind it so much if it went straight to the slideshow - but the delay on his name when I can't do anything is my biggest beef with it.

Hi @Tom Walcher and welcome to the forums. It is for getting variations of an image - cropped, resized, etc. So based on a quick look, you probably won't see these variations listed in your images field. Not ideal, but maybe not critical for you needs - hard to say. The getExtension method for DirectoryIterator was added in PHP 5.3.6 so that is your key issue. There are other places it is used in the PW core though too: https://github.com/ryancramerdesign/ProcessWire/search?utf8=%E2%9C%93&q=%22-%3EgetExtension%22 So you might have other issues when viewing log files through Setup > Logs or dealing with multi-language stuff. It actually wouldn't be hard at all to replace this method with another approach to getting the file extension, but given that PHP 5.3.3 is 6 years old I think you might be better off hassling your hosting provider to update their system

Thanks for the report @tpr and for the solution @LostKobrakai. Sorry, I am on the road at the moment (mostly vacation) and so my response time could be several days. It sounds like you have everything working as needed at the moment, but let me know if you think that perhaps Tracy needs to handle this better. Not the same thing I know, but the latest version of Tracy (the core project) now provides details on ajax requests - might be coming soon to this module, but there is a PHP 5.4.4 requirement, so might have to wait until PW drops 5.3 support.

@jploch, It sounds like you have the same needs as @Christophe. I have been meaning to take care of this but haven't managed to get to it just yet. I am currently traveling (mostly vacation), so can't guarantee when I will get to this, but it would be good to get this done shortly and tune this up for official release in the modules directory.

Hi @MikeB, Sorry that you are seeing those errors. I can't figure out why here at the moment. I could add a check to make sure that $value is an object before the code on lines 140 and 145 is processed, but I would like to be able to replicate what you are seeing first. Presumably you are getting this error when saving a page with this template in the admin? Is the phone field in a normal template, or is it part of repeater, or some other combined field situation? Let me know more and I am sure this will be an easy fix. PS - I am on the road at the moment, so forgive me if my responses are delayed.