adrian

Hi Jonathanp and welcome to PW! I have only played with that module once so far, although I will be using it in an upcoming project fairly shortly. You should be able to build the URL yourself using the page id and image name, both from the json data? Something like this - of course you'll need to define the $page_id and $image_name variables from the json data. echo $config->urls->files . $page_id . $image_name; Hope that helps. If you haven't already seen it, take a look at the cheatsheet: http://cheatsheet.processwire.com/ That will explain the $config->urls->files. All uploads in PW are stored in this directory, with subdirectories named with the page ID.

You certainly don't want to go modifying the module code. I don't actually understand why the pubdate is not being included in the feed in the first place since every PW page has a created timestamp and the module includes this as the default. Are you doing something custom with the output?

This should be fairly easy to do with a simple module. These two posts should get you going: There are several different possible methods detailed in here: http://processwire.com/talk/topic/1908-automatically-generating-new-page-names/ This post is less relevant since it is for pages created with the API, but might be worth a read still: http://processwire.com/talk/topic/4571-id-based-slug-instead-of-title/

Joss' Foundation 5 template: http://processwire.com/talk/topic/5293-zurb-foundation-5-profiles/

If I understand what what you're looking for exactly, you will probably want to make use of GROUP_CONCAT. I think something like this should work: SELECT CONCAT_WS(' ', g.lastname, g.firstname) AS Customer, g.id_customer AS customerID, GROUP_CONCAT(CONCAT_WS(' ', ad.address1, ad.address2, 'City:', ad.postcode, ad.city, ad.other, 'Phone:', ad.phone, 'Mobile:', ad.phone_mobile)) AS Addresses, gl.name AS group_name, g.email FROM ps_customer g LEFT JOIN ps_address ad ON (g.id_customer = ad.id_customer) LEFT JOIN ps_group_lang gl ON (g.id_default_group = gl.id_group) AND gl.name LIKE 'piiri%' GROUP BY g.id_customer

It sounds like the PubDate might be the issue: http://kb.mailchimp.com/article/ive-posted-new-information-to-my-rss-feed-but-no-campaigns-have-been-sent This might also be useful: http://blog.mailchimp.com/rss-to-email-tutorial/ It suggests that it can validate the feed without you needing to wait for it to send, which should help speed up your debug cycle considerably!

Whenever I edit a module in the modules directory and submit the changes it instantly grabs the new version number and code from Github. Of course you could even change the version number when editing, but it shouldn't be necessary

Related thread: http://processwire.com/talk/topic/4553-how-do-i-get-a-list-of-online-users/

Also wondering if it would be worth cleaning up the html a bit before it gets into the feed. All those tables and spans look kinda messy

The link you provided: http://www.birthfactdeathcalendar.net/bfd_processwire/rss/ doesn't seem to work, but this does: http://www.birthfactdeathcalendar.net/rss/ Probably a stupid suggestion, but are you submitting the correct one to MailChimp? I just ran a validator on your feed and it seems to be fine, so no major problems there: http://validator.w3.org/feed/check.cgi?url=www.birthfactdeathcalendar.net%2Frss%2F although maybe you could clean up the max-width issue and see if it helps. Regardless you should fix the relative urls to absolute, eg: <a href='/events/12-january-1893/'> to <a href='http://www.birthfact...2-january-1893/'> I know that FeedBurner is probably going to be another Google casualty soon, but try running your feed through it and giving MailChimp the FeedBurner link to make sure there is no issue with MailChimp accessing the feed or the format of the feed on your server. I know this has helped me in the past. Not a permanent solution, but a good debugging step.

BFD Calendar - I usually just make use of the page path history and the page link abstractor modules, but if you want ID based page links, you might find this module useful: http://modules.processwire.com/modules/process-redirect-ids/ Ryan has also mentioned that he was working on something called Link Monitor - although he may not be persuing anymore. Something to read anyway if you haven't seen it: http://processwire.com/talk/topic/236-module-page-link-abstractor/?p=34398

Maybe I am not fully following, but it sounds like you are assigning people to specialties. I would instead assign specialties and levels (two separate page fields) to each person. It would be trivial to generate the specialty pages with the appropriate levels this way. If this sounds like it would work for you, let me know if you need anymore details. Hope that helps.

Sorry, I am talking about the config.php in your PW folder. There is a debug setting there that you can set to true.

Not really sure, but does turning on debug in your config settings give you any php errors that might help?

Have a read of the "Do I have to keep track of the page number?" section on this page: http://processwire.com/api/modules/markup-pager-nav/ If you decide to keep track of the page number yourself, you can change the starting position, but if you always set: start=0 then it will start at the first page each time it is called.

Or you could try this module: http://modules.processwire.com/modules/process-page-field-select-creator/ You can easily paste in a CSV list using "Option 2. MULTIPLE FIELDS". Not sure if it does exactly what you need, but worth a look. Otherwise, Martijn's approach can be customized to whatever your needs are,

Have you seen this post: http://processwire.com/talk/topic/417-extending-image-field/ It describes how you can extend it yourself to handle the extra fields.

Just pushed a minor fix to prevent 403 forbidden errors when hitting the github page lists repository when starting the import process. Apparently they were forcing a user-agent header for several months now, but didn't seem to affect this module till recently. Anyway, should be fixed now. Sometime early in the new year I will sort out all the php notices/warnings in this module and add some more features for finer detailed selection of what you want to export/import.

Hey Martijn, Thanks for taking the time to help sort this out. I applied your fix and it works for page editing, but there were still notices if editing anything under the Admin page. I have to admit I haven't spent the time to fully understand the module and your fix, but I have added the following to line 97 and it seems to take care of the other notices: if(in_array($data_key, array('required', 'textformatters', 'size', 'maxlength', 'description', 'collapsed', 'required', 'moduleTypes'))) { $array = $data_value; $data_value = ''; if(is_array($array)) foreach ($array as $id) $data_value .= $this->pages->get((int)$id)->name . ', '; $data_value = rtrim($data_value, ', '); } $settings_str .= "<span>$data_key:</span> $data_value<br/>"; Not sure if there are any side effects.

http://php.net/rmdir should take care of that. And while you are on that page, read through all the "Filesystem Functions" in the left sidebar. Also, if you haven't seen it before, PYDIO is the best php/ajax driven file manager out there and it's free and open source: http://pyd.io/

There is this module: http://modules.processwire.com/modules/frontend-user-profile/ There are also these posts: http://processwire.com/talk/topic/1716-integrating-a-member-visitor-login-form/ http://processwire.com/talk/topic/107-custom-login/ http://processwire.com/talk/topic/2937-creating-a-front-end-admin/

Doesn't solve all your problems, but this helps a little: http://modules.processwire.com/modules/process-page-delete/ Somewhat related: http://modules.processwire.com/modules/process-page-publish/

Just a quick one - I know this could be done with a module, but I think a core setting that either ignores the field visibility setting completely for superusers, or allows selection of an alternate visibility option would be great. Thanks.

Manaus - my mistake, it should be last(). Please let us know what happens when you try: $users->get($page->createdUser->name)->image->last()->getThumb('micro');

Soma, Yep, just getting the array to string notices. I am on php 5.5.4 although I expect 5.4.x would also give these errors. Sorry in a rush at the airport, so can't debug right now.