adrian

I think this was fixed here: https://github.com/pine3ree/ProcessWire/commit/8cc1bcccaaf717871a7173b7cbc3fe2e8552afc7 and discussion here: https://github.com/ryancramerdesign/ProcessWire/issues/547 So please try the latest dev and see if it works for you now

Yep - you need to use: $article->featured_image->first->url; Have a thorough read through this: http://processwire.com/api/fieldtypes/images/

Hey teppo - nice! I know this is just a rough start, but here are some quick observations. The fullscreen mode sits below PW tabs The insert link functionality doesn't have a target option, but I guess this dialog would be replaced a PW specific one anyway, like with Tiny and CK I'd like to see a formatter for code view - I don't know if Trumbowyg has an available plugin or not What about paste as text or from Word buttons - are they available? Otherwise, it looks pretty nice and clean.

You can filter by all sorts of things: Can you see those options?

I'll post the same answer I posted in response to your Lister thread issue, just in case someone else is confused. "Ah - I guess you must have upgraded a 2.4 stable installation to dev - that is why Lister wasn't installed by default !"

Ah - I guess you must have upgraded a 2.4 stable installation to dev - that is why Lister wasn't installed by default !

I can't understand how $article->featured_image->url could possibly give /post/July/postname. Image paths in processwire look like: /site/assets/files/1001/ Maybe I am just being slow this morning and someone else will see what is going on

I am guessing you are logged in as a non-superuser? If so, then you need to give your role "page-lister" permissions.

Did you see the edit to my last post? If you don't want to run PW dev, or wait for 2.5 to be released, there is another option than Lister - you can use this excellent module from Soma: http://modules.processwire.com/modules/page-list-image-label/

What you see in the lister video is a very early version of lister before Ryan split it into Lister and Lister Pro. Unfortunately you will need to wait for Lister Pro to be released if you want to be able to create those custom lister items in the admin interface, but the use of lister in Pages > Find is very powerful already and you can instruct your users how to easily add a new filter that limits the view to a particular parent.

Oh I think I understand - do you want the user's image to show up when viewing the User list through the admin panel - Access > Users ? EDIT: If you're running the dev version of PW, that is really easy to do now that the Users page uses Lister - just choose the image field from the columns tab. Like this: Is this what you are looking to do?

I think horst's post has your answer - please show us the code you are trying and the result you are getting.

Yup - it's installed by default - it is used to display users (Access > Users) and also Pages > Find. With the standard version of Lister you can't add custom views - that requires Lister Pro, which hasn't been released yet, but should be available when PW 2.5 is released which should be too far away.

Nice one Wanze

Sorry I am confused here - you say that first solved the problem, but that my code didn't work? By "name", do you mean the filename? You can access that using: echo $article->featured_image->first->name; That will give you just the filename. If you change it to: echo $article->featured_image->first->filename; you'll get the full disk path to the image, although this is probably not what you are looking for - useful for image manipulation, but not display. Basically you can access anything you want about the image. Take a look here: http://cheatsheet.processwire.com/#files

That code is a little weird - I don't really understand why the image is working at all. What is the Details > Max Files Allowed setting for the featured_image field? If it is set to anything but 1, then this should work for you: <img src='<?php echo $article->featured_image->first->url; ?>' alt='<?php echo $article->featured_image->first->description; ?>' /> If it's set to 1, then you won't need the "first". Are you using the latest dev or 2.4 release? I am wondering if the new Formatted Value setting is at work here?

@tobaco - please try the latest version - I have made a lot of fixes and I now get a fully(?) working import of your json file! Firstly, please run the export on your original site again first as I made a couple of fixes there. Then test on a clean PW install and use the REPLACE option so that your import will completely replace the existing pages from the default PW profile. Please let me know if all the content appears to be populated as you expect - there are lots of fields with empty values in the json export, but I am not sure if that is correct or not, so I'll need your input on that. There are still a couple of issues: Using the replace method a second time results in out of memory errors - I think it's the recursive deletion of the content from that repeater field I have temporarily disabled importing content for image fields inside repeaters as that is causing errors with your import. I am pretty sure images in repeaters worked fine in my previous testing, so I am not sure where that problem is yet. Thanks again! PS The latest version handles installation of all required language modules and gracefully warns of missing language packs and lets you install them as needed. PPS - if you are doing lots of testing and need to be able to revert to a fresh install regularly, it pays to fire up PHPMyAdmin and create a clean copy of the DB after you have installed PW (or perhaps after you have also installed all your required modules) so that you can simply drop the actual DB and create a new copy from the backed up copy. You might be already aware of this approach, but it's a huge timesaver when testing things like this.

For sending one message to one user at a time with a download link should be fine via PHP mail(), however, to reduce the potential spam score of the message, it is often preferable to send via a properly configured smtp server, which is where these modules come in: http://modules.processwire.com/modules/wire-mail-smtp/ http://modules.processwire.com/modules/wire-mail-swift-mailer/ I can't see any real reason to use an external service in this case.

Just wanted to add that I have the same problem on PW 2.4 release and 2.4.5 - it happens every time I change a field type to it's Language version. The only fix seems to be to manually create the dataxxxx field in the DB.

Unfortunately, the built-in search on this IP.Board forum is not very good. We all use Google site search: site:processwire.com/talk "redactor"

Hi Soulsliver - just a quick heads up - this has been discussed before: https://processwire.com/talk/topic/1964-redactor-wysiwyg-editor/ I don't remember the outcome, but you might be interested in reading through that thread.

Might be a stupid suggestion, but has he tried clearing session data from FF - I would think that should do it.

@Ronnie, I should also mention that you do not need to import the blog.zip file. You can use Kongondo's Blog module (http://modules.processwire.com/modules/process-blog/) as the base, or just import your WP xml and manually create the templates to suit your needs. If you decide to use the Blog module, here is a screenshot of the MigratorWordpress config settings that are required:

@Ronnie, Sorry about that - it was a simple fix - please try the latest version on Github and let me know how it goes for you. You might be still be affected by an outstanding multi-language issue but hopefully I can have the fixed soon. @tobaco Still have some issues with the language error and also trying to improve the Replace option - need to sort out recursive deletion of existing pages to work better, but I have fixed a bunch of issues around reporting/automatic installation and proper configuring of Inputfield types that are needed by the imported fields - for example, the icon select field now properly detects the need for installing InputfieldSelectMultipleTransfer and then uses it once installed. This should work for all input field types now.

Hi Ronnie - I am taking a look at this now - it is possible I broke something with the MigratorWordpress in my recent changes to Migrator. I see that you also posted over in the Migrator thread, so I'll respond there when I have an answer/fix. EDIT: Fixed in latest version on Github