apeisa

Thanks for the feedback! I will change field & template string to id:s. This is actually implemented, but it is very bare bones implementation. I use a elements for value keys - and I have actual value there in title attribute. So depending on the browser you should see the value if you keep cursor on top of the key.

I started coding and I have a pretty good start. Still very much work in progress, but works as a proof of concept. It would be super helpful for me, if you find time to check this out at some point and give me some comments or tips what I am doing wrong https://github.com/apeisa/ProcessDataImport It is actually pretty cool stuff (ugly, but still cool ), I can't wait to get this ready and start using it. UPDATE: Oh, forgot to say that works only with JSON feeds at this point. Here is couple of feeds you can test (should "work" with any valid json though): http://search.twitter.com/search.json?q=processwire http://keikalle.com/api/city/helsinki http://gdata.youtube.com/feeds/api/standardfeeds/most_popular?v=2&alt=json (this is monster)

P21 has excellent support for user profiles: meaning site builder can add fields to profiles like any other pages, and users can update those fields by themselves. Basic forum: I have been planning on building forum module a long time now and I think I will build it sooner or later. But my plan was just to use pw-pages as topics and replies. So I would have two templates, forum-topic & forum-post. This can be done already using just templates and adding custom form to those templates (which creates new pages). But as I said, I hope I found time for simple forum module soon. There aren't lot's of social features out of the box or as 3rd party modules yet, but this is probably one area where we all want to take pw (and the module route, not "out of the box" -bloat route). So lot's of improvements coming, I hope! EDIT: Typos

Nice approach. Ryan's example could be extended so that after first run template could be changed for something else, like image-category. Then it wouldn't try to create image pages again, but show them instead. Also maybe get var or something that is required before template tries to create pages could be nice.

This was pretty quick Looking very good, I will probably implement this on twitter puller. And nice list of other commits to P21 also!

I did found it and added cross link from my reply: http://processwire.com/talk/index.php/topic,171.msg1124.html#msg1124

Back to topic: I added caching and also ability to pull tweets based on username. I think this is pretty save now for use. There isn't any settings and it generates awful markup by default - so you probably need to edit lines 238 or 247 for your usage. I am not sure if I will support or develop this much further (well, if people really find this useful, I can add needed settings etc.. but this is fine for my own needs now), so please feel free to fork this if you want (I'll put it on github if someone requests). If you have installed this, please remove all the pages (from trash also) using templates twitter-puller or twitter-tweets and after that uninstall. I haven't done any error checking on those install / uninstall methods, so it is pretty easy to get errors there...

Yes, that is pretty much it! Very well planned too. Just add cron and we have it ready, so this tool could be used to import events from event calender feed, news from rss and tweets from twitter feed. What this adds is few things: We have to tell which field (or many fields combined, like title and date) is "id" - so that we don't end up with duplicates. We need list view of all data feeds, where we can choose how often it is fetched (or if it's manual) I actually really want to build this, since I know we will have ton's of imports coming in our projects. About page relations: I think if these are needed then many times best way could be running another script after import, which adds needed relations. About images & files: I don't remember any import where we would have need for importing files, so I'm glad to drop this out to keep things simple. Well.. simple enough at least

http://processwire.com/api/variables/pages/ <?php // Creates pages, saves, adds image and saves again $skyscraper = new Page(); $skyscraper->template = $templates->get("skyscraper"); $skyscraper->parent = $pages->get("/cities/atlanta/"); $skyscraper->title = "W-Hotel Tower"; $skyscraper->body = "This is a nice hotel and it has a helicopter landing pad on top of it." $skyscraper->save(); $skyscraper->images->add("http://starwoodhotels.com/w-atlanta.jpg"); $skyscraper->save(); Yes, it is possible - though there is little bit of coding work ahead. You could take a look of my redirects module on how to create admin pages using Process class: https://github.com/apeisa/ProcessRedirects Other option would be to create this on template level, outside of admin (of course using authentication still). But probably creating this inside admin is better option. This is pretty simple. I would create two image fields: image_highres and image_preview. When creating image_preview I would use current filename and resize it to maybe 1024 width. After that I would rename the original image to something unique (maybe md5 hash from pageID, or maybe just pageid?) and save that image to image_highres. That way you would have both images available as pw fields, but when using image_preview in your templates no-one could guess the filename of image_highres. Hope this helps you even a little bit - I'm happy to help you with this if you need more support.

Thanks for the compliments. It's running on very modest virtual server at the moment (don't remember the specs now). There is few other php apps running on the same server and all in all it's taking very little resources. But good performance is sum of many things: bandwidth, server specs, backend coding, http server conf and most important: front-end coding. There is many little details that I will work on to make it even snappier (like expires headers, combining js etc). In my opinion pw is very lightweight cms. Of course it depends how you use it, but in basic usage I haven't found any slow queries or things like that. But I think that Ryan would probably know much better how pw compares in performance wise?

Thanks Ryan - looking your older module is very helpful (although these work pretty differently). I think that using pages will be a bit too much in most cases (it creates templates, fields etc), but I think it will allow simple UI for hiding tweets (this is requirement for one of our clients). I actually started to think about some kind of data importer: you could put any feed (well.. at least xml, json and cvs) and after that map those values to your pages. That would be so great, but probably little bit too much for my skills.. although I do like challenges Well.. I finish this first and after that I'll create RSS to pages -module. If these aren't enough, then I'll start to think about some kind of data importer... Probably they are, since PW makes it really simple to create import scripts. What do you guys think?

Did all the "nothing new here" items turned to "already started" state? Brilliant! Also: good information about details on these items.

Yep! Few other PW-stars also featured

I created simple module for fetching data from Twitter and saving those results as pw pages (or can be used without saving also). This is very much work in progress and I don't recommend anyone to use this on live site just yet, since there is few rough edges I want to solve first. But if you are interested, please try this out and comment. Screencast: http://screencast.com/t/zBJOWzma Usage: Install the TwitterPuller-module Create new page and give it template: twitter-puller Give the fields values that you want Edit one of your template files and add $page->renderTweets("/url/to/page/you/just/created/") It should work What it needs: Caching: it supports cache now Settings: there should be some editable defaults jsondecode messes up tweet id value (too long integers or something like that, not sure if I even try to fix this...) Maybe way to use cron and never fetch data for live user? I didn't implement caching yet since that would require Markup Cache module and it's not installed by default. Do we have some way to tell about module dependency? Also Ryan - I am not sure if adding custom method to all pages is best way here? Is there lot's of overheat doing it this way? UPDATE: New version. Now it supports caching and also possibility to pull tweets based to username. TwitterPuller.module

Thank you guys for all the nice words here and on twitter! Hope to get next topic here on this section soon enough.

Well... It's 90% just Ryan who does all the work here, so there is definitely room for everyone's input

Yes, this sounds excellent. I think broken on-site links is one of the major pain points in many cms-software, at least when doing structural changes to sites. Of course this is not so big issue when site is well build and cms support clean relations (like PW does), but still excellent addition. I couldn't find the topic where this was discussed months ago - it would be nice to link it here if anyone remembers that topic?

Just wanted to reply here just to wrap up how much processwire has progressed in little bit under 4 months: Not to mention all the other modules and improvements that are not part of this list (redirects, page link abstractor, new fieldtypes etc...). And most important: more and more activity here on the forums, twitter etc! Just amazing!

I actually didn't read any of these So actually, just ignore my nitpicking and keep going on this way!

We launched today our first pw site: http://lukio.fi It is website for high school / college students association in Finland. Site is only in Finnish. This was pretty hectic project: build on few coding days in time period of little over two weeks. In feature wise there are 25 templates and about 30 fields and this is build on latest version of P21. Site is pretty much blog based, but also features sections for image galleries with tag clouds (http://lukio.fi/kuvat/), Simple FAQ (http://lukio.fi/opiskelijakortti/palvelut-ja-neuvonta/), simple poll (front page), tiny "personality test" (http://lukio.fi/jutut/unelma-automaatti/). Also site pulls data from other web service and displays it: http://lukio.fi/opiskelijakortti/edut/5/ (they keep that "member discounts" data in their member registry) etc. We have some nice and simple features for content editors: those blocks on right side are defined only once and can be picked (through page reference) where-ever you want (some of those have dynamic content, others are just text & links). Featured image visibility on blog post page can be toggled etc... We also use markupCache module on few places (footer links & tagcould) - I really like that module. Super simple to use. Client is loving the site and pw. There were two other companies involved (Vapa Media is behind the concept & content, KWD digital has done visuals). From our company my colleague did most of the html&css (actually, there is some of the demo site css still - we started in hurry ), I did all the coding (php, js) and some of the html & css. Still in need of some finishing touches, but overall pw was great platform for this project and I really enjoyed developing it. Best part is that I could say "yes, let's do it" to every request that client had and we still managed to release it on time.

I agree: very good work! I also liked your copywriting a lot - especially the third news item is diamond (also - I wan't to test Almonk's "mummy module" ) I really like the color scheme (and bold usage of pink!). I agree with Ryan that typo on the pink area is too small, but I think that there is also too much text - so less text there and bigger font: problem solved. My only concern is that site feels little bit packed: it would benefit with more white space. What came to my mind is to drop "latest news" block beneath the "What makes pw special" area. So there would be clear vertical stop after the four main features, and below that all the "active stuff", like "item of the day", "twitter" and "news". This would be more towards marketing for first time visitors, but would also give clear picture about the active community behind the project. Nitpicking: I do not like the usage of mahalia font - I first looked the screen on my mobile and I was thinking that it rendered the picture wrong. I do like the font, but I would like to see spacing between the words. Overall, very good looking and well formatted site! Good job!

Actually you recall wrong: http://processwire.com/talk/index.php/topic,56.msg235.html#msg235 (huh - that version does look ugly.. ). Original had two buttons: open panel + quick edit. Most common use case is by far "quick edit". After that I think what is needed is quick link to admin view - and linking to pagelist would be best option there (now that we can link to certain page on list), since that would kill the need for sitemap. I have to test different variations here... I don't think that current "toggle view" is bad solution - but even I haven't used it at all and always had trouble to find my way back to admin site (I started to use sitemap -> go to administration link).

Heh, I know That was before we could link to an single page on pagelist though. After using adminbar myself I realised that another sitemap is just confusing. Also I'm not sure how important it is to see additional info about current page through adminbar? Things like who edited last time, who can access this page etc? I start to lean towards less is more philosophy here...

Almonk: Nice work, I like it! I have been using Adminbar pretty much last few weeks and I have few improvements in mind. One of them is "smaller UI" - no sliding "more info" tab etc. Probably less buttons (like you have). Also current modal wastes space (which is not problem on wide screen, but is very annoying on smaller resolution). I think I will replace "sitemap" button with link to admin site (that opens sitemap there on the right page). So there would be three buttons: edit, add child, go to admin (to sitemap view). Any thoughts people? I am having very little time besides client projects, so it will probably take few weeks before I can continue develepment.

Hmm.. maybe it key icon should appear only if viewing rights are changed? This is very minor thing, but nice little touch like lock-icon (although we do not want to end up with tons of mysterious tiny icons).