horst

Hi Philipp, hi Ryan, the idea of Philipp was very inspiring to me. So I have thought a bit about that and came to conclusion that the most common denominator is Email. Every smartphone supports Imagesharing via Email, and also one can put up an Image from DesktopPC. I've put together some php-classes to access POP3-Accounts, retrieve and parse Messages to (first find ) and extract Images. I have uploaded it as a first 'proof of concept'. In this state it retrieves the _first_ image from Message, regardless if it is attached, inline-attached, if it is a Textmail or HTML-Mail or from other MultiPart-Mails. The Subject from Email could be the Title of a Post. Adding Bodytext could be an option, but is not very foolproof with that lot of different Email-Mime-Types, but would be posible with some more amount of coding-time. Interesting Option could be to send Title in MailSubject and a Image-URL in MailBody - fetch the Image from URL and process it. Also sending multiple Images could be possible. - So, as I can do the above stuff by myself, I'm not able to put the ProcessWire-Part together at this time. (Maybe next year, - but not for now ;-) ) My question is: "Philipp, can you provide the code / example for the Import into ProcessWire?" If you like, we can put it together to become it a Plugin Module, maybe? At current state my class provides a array with str-Title and str-Imagedata per Mail. (processing till there is on the fly without using diskfiles) The current Setup can be viewed here: http://biriba.de/pw_pop3/pw_pop3_test.php But, please, no stress-tests! Emailadress is in the top-left corner, you may send a picture by mobilephone to it (around 500 px or smaller would be fine, because all images get scaled down to 320px for the test) and reload the page after a minute or two. Horst

Hi, I have had some (more) trouble to get started with PW :-( In my php.ini the default_charset was set to 'ISO-88591' or something similar. So, as the DB uses utf8 and the pages are delivered in utf8, php is required to use it too. If not you can run into errors when try to save strings with e.g. german umlaute: äöü ÄÖÜ Incorrect string value: '\xFCchte ...' for column 'data' at row 1 I'm not sure if this was checked with the install routine, but I have seen only green lines Maybe this could be done to avoid some hassle to users with a setup other than utf8. Or it maybe an option to add "ini_set('default_charset','utf8');" somewhere at the top of index.php, and to be very very sure (also for paranoics like me ) one can set and check it: ini_set('default_charset','utf8'); $php_use_utf8 = strtolower(trim(ini_get('default_charset')))=='utf8' ? true : false; Ok, now I can start try out that wonderful CMS

Hi Radek, yes you are right, that was needed I has to comment out the line: # RewriteBase / and also my Apache httpd.conf wasn't set right In the FAQ I have found a Thread about how to test for that: http://processwire.com/talk/topic/1-what-is-the-admin-login-url/#entry24096 And yes, I've better should used the search-function before posting this thing Horst

Hi, I'm very impressed of ProcessWire and want to test it local, so that I can see if I can handle it to use it for my website. So, I'm very new to ProcessWire and have installed the latest stable Version from ZIP to an Apache on Windows. Installprocess is perfect: everything green When it comes to "7. Use The Site!" - I can access the root url but not the admin-section: "http://localhost/processwire/" From the RootSite I also cannot go to another page: /about/ - /site-map/ - /templates/ The directories/files in htdocs are: /site/ |--assets/ |--install/ |--modules/ |--templates/ |--config.php /wire/ |--core/ |--modules/ |--templates-admin/ |--config.php |--index.config.php /index.php /.htaccess Maybe there is something wrong with the automatic created .htaccess-file? (I cannot find any of the url-parts within it: processwire about templates site-map) Horst