Adam Kiss

To answer my own question: It seems, that Textformatter modules are added to the dropdown menu in field edit page if they are categorized as 'textformatter' modules. And it's categorized via first camel cased word in the name of the module (its class). So there.

I was trying to do a custom TextFormatter, which takes custom-formatted textarea, does double expolde and returns array with my values, so instead of parsing my special fields in template, I can use straight values (it also seems to be very nice idea to do with PW workflow) FIELD: test:value1 test:value2 upon loading the page, following array should be returned: [0]=> (k: test, v: value1) [1]=> (k: test, v: value2) So I took one of the Textformatter plugins, created /site/modules/Textformatter/ directory and added the copied (and modified) plugin in there. After refreshing the modules, my plugin isn't added in the 'Textformatter' group, and also I can't select it in the text formatter dropdown. I don't have access to it right now, but it was the NLBR formatter, and what I did: changed module information modified format function I basically took ther string input, did double explode (\n and and one trim and returned the resulting array as the modified &$str What to do/how to create new textformatter plugin? Thank you!

Unfortunately, it isn't possible to solve this way. It isn't in the same tree, because then it would be too complicated for content manager. It works this way: there is a number of parcell pages, which relate to place on map. Number of these places, as well as their location doesn't change. Then there is a list of shops, which I want to tie to these 'places' on map, so I can generate maps via HTML then easily. Explanation: 'HOUSE' template is for shops (thus SHOP template in following text) and PARCELL template is for PLACES on the map (in the shopping centre). I just tried to describe my problem without enclosing real purpose Proposed structure: - shops - category 1 - shop 1 - shop 2 - shop 3 - category 2 - shop 4 - shop 5 .. - internal_data - places - place 1 - place 2 Seeing this structure, due to CRUD of shops, you'll agree it's better to relate places to shops in the shop pages, so the content manager can edit everything in one place. Other option, that came to my mind: is it possible to do something like this: ? <?php //..upon saving 'shop' template, $this is the shop page I'm saving $place = $this->related_place; $place->shop_that_is_here = $this->id; $place->save('shop_that_is_here'); //..upon deleting 'shop' page $place = $this->related_place; $place->shop_that_is_here = null; $place->save('shop_that_is_here'); $this->delete; Thanks Ryan for your help

Hi all, I have following setup: [only relevant part showed] HOUSE .. parcel_reference: single_page PARCELL .. reserved: checkbox/boolean Note: there is X PARCELLs and Y HOUSEs. each HOUSE has exactly one PARCELL, meaning there might be page with template PARCELL, which isn't referenced by any HOUSE page, but there can't be HOUSE page, which has no reference to PARCELL. Now, I would like to select all pages of type PARCELL (e.g. via 'parent=/parcells/'), that isn't referenced via any HOUSE page AND doesn't have 'reserved' checked. Is there any possible API way, or do I have to select all PARCELLs with no reserved checked (query: 'parent=/parcells/, reserved=0') and test this array against 'template=HOUSE' query?

that wasn't idea... nevermind, do what you feel will be good, you were right so far

Ouch. I just wasn't sure if simple copy&paste will work – in case that some of html/css is overloadable from /site/admin-templates/ but if not overloaded, it's generated from module or something. Thanks Ryan

I was asked by my client to modify header of admin, so end-client will feel special That got me thinking: is it possible to modify only a part of admin themes via 'admin-template', or is it better to replicate whole directory from 'wire' and change the parts I wish to change?

Ain't you a sweetheart

Alastair, Antti (really? Top posters' names (except Ryan) start with A? We should call ourselves PW AAA): I know it works, but was more looking for recommendation for Ryan I mean, I believe both of you, but, after all, there are people who call WP a perfect any site CMS, it only needs 30 plugins (and you have plugins for everything!) [/irony] And since it was Ryan who did not recommended 2.1 for production, I was curios whether he thinks it's ready now edit: Also, no disrespect to you two

Hi all (and Ryan mostly:) ), what's the current status of PW 2.1, and it's readiness for production? I remember announcement of 2.1, that went with 'not recommended for production'. However, that was around a month ago, so I'm curious what's current status? Note: I have to go live in about a week, will have to build a site on PW in next three days, so I'm curious which version to build on.

Holy Macaroni! I can save only one field in template? I didn't know that – that's why I was curious about impact between 500–1k visits, because I thought whole pages are saved. As for bots, I don't care for real pageviews by people – there's always GA set up on the page for the real count, but I assume bots crawl sites fairly equally, so statistics (and therefore selecting top 3) should be rather fair.

Hi Ryan, I'm thinking of having internal viewpage count for one of my templates (they are shop profiles), because client would like to have 'most favorite shop' feature on the webpage. So my idea is to modify one value (integer) every time somebody loads the webpage, and check once a month whether there isn't something irregular (so I could bump the hackers down). What might be the impact of this, if we talk about +/- 500 visits a day? Would it be okay, or could we feel it? Also, I thought about something more sofisticated (something like IP count, for instance), but I couldn't come up with anything better with session saved array of what was already visited, so the shops can't open up their pages and hit Cmd+R forever (or, worse yet, just so they get a bit higher in the top count, because that wouldn't be flagged as irregularity) What's your take on this? Note: we already scratched the like button for shops

Question for Ryan: Ryan, when I save page with this field [named body_more], PW always informs me, that there has been change in this field. Content appears the same, I am unable to spot the difference, yet every page save, this field is 'changed'. Could you have a quick look at it, maybe there's something wrong with my code, maybe it's some combination of characters, i don't know?

I believe mobile support for administration is currently very very low on priority scale. I mean, I believe there isn't a system which administration supports mobile browsers, since mobile platform is meant more to consume, than to create. But in future, I don't see why this couldn't work. *) note: support for me means that administration is adjusted for mobile browsers, so that administration and content management is not only possible, but also natural. I think that iOS WebKit (safari) is awesome, but there needs (in my opinion) to be a lot of front-end work done, so that administration is truly mobile.

Come on slkwrm. It's obvious it'should remind a post-it on the white background on the gray page. D'oh!

TL;DR so far, but it sounds awesome. I'll read this & comment more when I care again. Good job!

Great work Antti! By the way, if you haven't noticed, one of things using original css is the pagination

Thanks guys, I'm very glad you two [and Karen!] liked it, I just hope now Almonk won't do something much better [although PW would profit from it, I would be very sad ] Regarding your comments, many of those were mentioned also on the Original forrst snap, so I'll reply there, except: It might need it Let me reply with my original post My original reasoning was that it needs to be on the knowledge base template only, but the site might actually profit from having it on every site. I will think this through. And here I thought you'll know temporary texts when you see them. I had play button over the screenshots in mind, which would bring some overlayed video – either via some lightbox or it could animate from the screenshot. Of course, I'm an idiot and although I thought about it like six times, I forgot to add it. Well, I know all of you I'm actually not sure about the flow. I know the rhythm is a little fucked up [more about why on the forrst], but I still need to think through what on the homepage would PW benefit most from. "Oh god, I need to go away to do sports in ten minutes. I want to have it online by then. Quick, some footer." –me, when doing footer. I had quite a feeling in mind, but the technical details like spacing and rhythm (again) need some some. It's for of them, and I don't see how could I use less of them. But I will work on the typography, that's for sure Avenir – the main headline font Maha...lao or something – to have the same feeling as logo does Lucida Grande – main body font Georgia Italic – used in body, so the Maha...lao effect can be carried through the rest of the page. Also, if use the tagline and the download button as images, we don't have to include the Maha...lao font *– Maha...lao is the additional PW font, but I can't remember it's fucking name. Oh, Antti, you're gladly ignored. No, your suggestions I had mostly on mind already, I just can't work on one design for more then 3-5 hours, otherwise I go nuts.

Here is little something I've been playing lately with. http://adamkiss.deviantart.com/#/d3h6i1q or http://forrst.com/posts/WiP_ProcessWire_homepage_full_view-DQD As there is mentioned in the comment, I already some stuff I would realing and/or change. Adjust spacing a little to keep it a bit lighter News and footer need some more love Maybe 14px font for body copy wasn't the best idea Also, news center should put short news, blog & releases/release info in one place, just the way the knowledge base should keep introduction, tutorials, documentation and other stuff at one place. I have layout for both of them in mind already, I just need some time off before reiterating

If I recall correctly, I did that expand on click just because I wanted to show more with less – in original UI, you had just one pencil, which you had to click to get to editing buttons and more information. I put the buttons out and put a bit deeper the more information parts. I think that this more information could be useful, but under certain circumstances out of scope of this post.

Ha! It was supposed to go into the admin before you changed it! The smaller @Almonks' UI looks very nice

There is also 'start' selector, you might want to use that. http://processwire.com/api/selectors/ $page->children("sort=-created, start=4, limit=3") This should return pages 4,5,6. I'm not sure about whether this is zero-based or what, so you might play with it a little to get a good grasp of it.

It's not buzzwords if you have something in mind with them; If the goal is to create website described by them rather than say them a lot Almost. I thought, that in sake in having some system in chaos, we must go through forums and compile on-site tutorials and how-tos from the answers in this forums, without regard to what forum/topic they were in before – you might find 'tutorializable' how-tos in faq section, in general support, etc. No. What I had in mind are two separate sections of the website – tutorials, where you talk about 1., principles [first chapters] and small/big tutorials examples [latter chapters], which do not describe the 'how it works', but rather 'how can you achieve this' – 'object-oriented' was typo on my side, I had 'goal-oriented' [again those buzzwords] in mind. Imagine current 'documentation' as first chapters in the 'resources' section, and that compiled tutorials from forums as the latter sections. Also, the current documentation should be shortened, with links to what I called 'programmer-oriented' documentation, which should be more aimed at programmers & describing modules and 'how-it-works' stuff without describing why we did it this way [imagine flash documentation, or php documentation] Adam

So many things to react to... Oh well. First of all, I'm not sure if forums is the ideal medium to talk about this, but after all, PW is really open source, if we talk possible strategies in opened forums I think this is really tied with the page design; You said that this website was design in oh-so-quick manner, and I think it's quite nice (I especially adore the color combination). I think the right thing to do [regarding website] is to prepare website focused on the modern designers/agencies: Create modern, goal-oriented website Prepare all information sections with future in mind Compile all existing information, how-to's and tutorials in one big pile of information Sort that pile out into meaningful resources part Instead of current 'API' documentation, create object-oriented resources and programmers-oriented documentation Prepare for future: all sections you are 'dreaming' of, so you can easily add information You see, there is (i think) quite a lot of information available, even in comparison with few of the seasoned open source projects . So it actually comes to creation of welcoming visual & informational design; Then you/we cab push this project forward, into opensourcecms.com and such – I think it's more important to let the people know this project grows and goes ahead, rather than have all the section already filled with information. That's all I have to say to this matter right now; also, I apologize for any mistakes, I'm going away during weekend and I'm thinking about four things every moment.

OT: Ryan, I think, that the reason you're working for one client is: 1., you've done bazillion [yes, exactly one bazillion] sites for them and 2., each of these pages have like 3.4 gazillion [that's like, more] pages. On Topic: I like the content structure & ordering of the content here, also typography is quite nice, but I really dislike the color combination. And what really kills me is the gray border colors. If I had to change something, I would: Orange – tone it down [a little] Blue – it's too dull in combination with that orange. More saturation and lightness Borders – instead of gray, select appropriate color–light orange for when background is orange, blue for blue. you can use the same hsl, except 'l' is +10 or +15