adrian

There is nothing really wrong, just a case of not very explanatory notices. Go to the edit page for the field and save it again. You might need to save it twice to get the message to go away. Some discussion about it: https://github.com/ryancramerdesign/ProcessWire/issues/582 https://github.com/ryancramerdesign/ProcessWire/commit/c1dd1b37e529eff4e5219d1b790275fe71771936

Thanks Martijn, I haven't had a chance to test yet, but I am sure you've done a great job!

Hi Thomas, Sorry to hear you are having a bad day Here are some thoughts on why you might be having issues with each of those approaches. My module - firstly this was never really finalized for general use (and hence not in the modules directory). I have made some changes to it that haven't been pushed to Github, so maybe there is something there, but I have also stopped allowing insertion of images into Texatarea fields on new sites anyways. I always hated the potential side effects and now with PageTable blocks there is a decent alternative that allows for flexibility without the problems - sorry getting OT now. It also uses the description field that is available when the image is uploaded, and not the one when inserting the image into the textarea, so is it possible that the main description field is empty? With teppo's module, did you remember to add it as a formatter for the textarea field? Edit the field - Details tab > Textformatters With Ryan's approach - that code was written for his Foundation profile and makes use of: $("#bodycopy p img[alt]").each(function() { Is your content inside an element with an ID of bodycopy? Hope that helps a bit.

Hey Peter, To avoid confusion, you should change the status of Admin > Pages > Image Crop to "hidden" so it doesn't show in the Pages submenu. I have reminded Antti about this (https://github.com/apeisa/Thumbnails/issues/23) so hopefully it will be fixed in Thumbnails shortly. Cheers!

Hi Dan, Sorry I don't have time to help at the moment, but just wanted to quickly drop you a line to let you know that there is some raw javascript appearing at the bottom of all pages on your website. Good luck finding some help.

Hey Peter - great job. Just one small thing I noticed - you are missing some css definitions for the page number buttons

Hey Martijn, Just wanted to say that I finally had a real-world need for this. I combined it in a PageTable template along with X and Y label and chart type fields, together with C3js to create a very easy method for editors to add in dynamic charts anywhere in the page layout with their own data. Very cool! Now we just need a CSV import button for ProFields Table and we'll have an alternate solution for letting editors build charts with much larger datasets, but this is still perfect for smaller datasets.

I have another idea for an enhancement for you - the ability to specify a user that does not raise the alert for other users trying to edit. That way you could have the edit page open while helping a user debug an issue on their end, without needing to close at your end and have them wait till it is available again.

It's not really an issue for me at the moment, but I just thought that in some cases people might want to apply different css/js chunks to different themes and if their users are allowed to select their own theme, then this might be a useful enhancement to your module.

Taken from AdminThemeReno, but I think credit actually goes to Nico: .content .PageList .PageListItem:hover .PageListActions{display:inline;-webkit-transition-delay:.25s;transition-delay:.25s} .content .PageList .PageListItemOpen .PageListActions{display:none !important;} .content .PageList .PageListItemOpen:hover .PageListActions{display:inline !important;-webkit-transition-delay:.25s;transition-delay:.25s} I added the other two lines to hide links on an open parent

Absolutely love it Martijn - now I can have hover links and debug toggle in the default theme Lots more potential obviously. One request - any chance you could make it possible to limit the actions to only certain themes?

Both work here - what version of PW are you running? One thing to note though is that you shouldn't be overwriting $users as this contains all users in the system. If you redefine it, you won't have access to all users via $users further down in your code.

Or if you have the skills, perhaps you'd be interested in creating an plug-in for Migrator, like Nico's WP migrator. We have a lot of ModX refugees here, so I am sure it would get lots of use. I don't know anything about ModX, but I'd be happy to help in any way I can.

Maybe the way is a modal dialog on the templates edit screen that accesses the complete field creation and configuration options and as soon as you save and the modal closes, the field is added to the ASM of fields in the template? Otherwise you could be potentially stuck with needing to go back and edit the field settings.

Hey horst - good points about shared servers for sure! I guess I am in the unusual situation of managing my own servers so I have disabled FTP, but I do have SFTP enabled. To compare, I know that Wordpress does not support SFTP by default which would make their automatic core upgrade process useless for me - lucky I don't want to use WP I'll probably still be using git pull for all my PW upgrades, because of the write permissions I have set on my servers, but I think it would be nice to have this module support all possible options.

I think @NorbertH's motivation might be that he doesn't want standard FTP enabled on his server at all. I think it is about keeping the server in general more secure, rather than protecting the actual transfer of PW files. Is that correct?

Ok, I'll stop hassling you about an orange warning option now that I know that a revamped notifications system is on the way The upgrade module really is fantastic - thank you!

Might be nice on a small site, but would be slow and cumbersome on a larger one. PS You should upgrade your version of ProcessPageDelete - actually uninstall and reinstall the new one so it gets rid of that extra "Delete Page"

Sorry - more things: The entry in the modules directory goes to this broken link: http://modules.processwire.com/modules/-process-wire-upgrade/ The upgrade notification on login is awesome, but being in green I don't think anyone will notice them. If someone is regularly accessing their site, they might never (or at least rarely) have to login. Especially if they are using Persistent Login module. Any chance of running the checks in the background at some interval?

Works great! Only one thing - I am worried that someone running dev will see the "Older than current" on the PW Stable row - click to /setup/upgrades/check?branch=master and run the Download Now "upgrade". Maybe this is fine and should just be a case of reading things properly, but just thought perhaps there could be a warning about it being a downgrade?

I am not really sure, but PW 2.5 is just moments away from being released: https://github.com/ryancramerdesign/ProcessWire/commits/dev So I would say grab a copy of that, do a fresh install and see if that works for you. If not, then we'll figure out what is going on with your particular setup. And sorry for the rough start - this is highly unusual

Great to have module upgrade notifications in the core - thank you! Oops - not in the core, but thanks anyway

error_log won't send anything to the PW error log. They will go to the php error log. If you are using commercial hosting with cpanel there should be an error log you can view. If you are running a setup on a Mac, this command in terminal will get you the last 50 lines of your error log: tail -50 /var/log/apache2/error_log although it is possible the path may be different. If you bootstrap that file to PW you could also do one of the following (https://processwire.com/talk/topic/3768-processwire-dev-branch/#entry36787): $log->message("This saves this line to messages.txt"); $log->error("This saves this line to to errors.txt"); and those will send messages to /site/assets/logs/ Hope that helps.

This may not be an indicator - try: error_log('reponsive-images.php called'); and see if that appears in your php error log.

Does /mnt/sites/klauser-design.ch/web/pw/wire/modules/ exist on your server? If not, it looks like you didn't manage to get all files onto your server. Can you check that and get back to us?