Nico Knoll

Edit: Of course I would offer help in each of the points I've mentioned.

Hey, I think if you're a new user to Processwire it's really complicated to understand how to install a new language. I've got a couple of ideas how to optimize this: Better Description: It would be important to show at least a link to a documentary (for example: https://processwire.com/api/multi-language-support/) and add some screenshots to it. So that you get a step by step tutorial. Additonally I would add a description to the "Language Translation field" on how to get the language files (link to: http://modules.processwire.com/categories/language-pack/) Instant install: Another way to add languages could be the Textpattern way. But I'm not sure where to place this. In the module->new section? After clicking "add new" in the setup->languages page (that's the way I would prefer. And at the bottom a link "You're language doesn't exists? Create it now!")? Or somewhere else? What do you think about this? And what are your experiences with adding a new language for the first time? / Nico

Just wanted to mention that language packs should be treated different by module installer, too.

Hmm, what I think: Custom fields: You normally create a custom template file for each of the custom admin pages so I don't think you'd need custom fields here. And if you think about using the same custom admin page template multiple times you can use $page->name to difference them. Templates: I understand your point but first I don't see them as real templates but as subtemplates. Of course it probably is a bit cleaner to create a template for each. But as you already mentioned: it's really annoying. Especially if you can't use the fields added to the template anyway. I'm not sure which solution is the best one here, so I would go with the easier. If you would prefer to have a template for each file I would rewrite the select field to select templates instead of files from the template folder. (P.S.: I'm not sure if this is an equivalent comparison but admin pages like "setup" don't have a special template, too, only a file rendering the template and stuff like this).

I made it translatable and added Kongondos stuff

Good question - I'll have a look.

Hey, I forked this project and created a version which is a lot simpler but only runs on PW 2.4 or higher. https://github.com/NicoKnoll/pw-admin-custom-pages What do you think? @diogo Maybe you can merge them somehow and move your version in an "PW lower than 2.4" folder or so.

Looks really nice! Remembers me of an old ticket a little

Hey, it would be lovely if processwire could cache background images as well. Like used in: <div style="background-image:url(abc.jpg);"></div> Is there already a way to do this? / Nico

Do you added the hookable stuff we talked about already? So I could publish my module too

Hey, is there a way to "blow up" the image description field? Because I'm building a site or a photographer who needs longer descriptions for his images. But I don't want to create an entire page for every image... / Nico

@horst: corrected it: http://nico.is/impressum/

Hey, I finally finished a lot of changes on my personal website like responsive, an about site, a better reference page, ... and of course an update to PW 2.4 Check it out: http://nico.is / Nico

Looks nice. And Berlin ftw!

Nice, but next time I would like to sit in the audience rather than just watching the video

Sehr cool, gefällt mir gut Edit: "Really nice, I like it "

What about merchandise? Like T-Shirts and this kind of stuff?

Combined with the lovely theme made by renobird:

Ahhhh I got it. Now I've got "clients.dev" etc. running

@Soma: Sorry for the misunderstanding - I really meant the local domain thing Martijn described @Martijn: I use XAMPP for developing so I guess I just have to change the hostname table, haven't I? And btw. it's "private/etc/hosts" on mac

But how do you do this? I mean for example if I'm building a site locally I've got a url like "localhost/example/" and after uploading the path changes to "/" respectively "http://example.com/" ?

A good approch would be to store the installation path somewhere and when you load the admin path to compare it (maybe automatically) to the actual path. If the path is changed you could show a note "The path has changed - check for broken links?" directing to a page where you see all broken links with possible - working - fixes and a way to manually update them Maybe only check after login like this "the password-system is updated bla bla" note in 2.3

Hey, it's always the same: I'm builing a local version of a webseite using TinyMCE fields in the backend with images etc. But after uploading to the live server the relative path to images and pages change (of course). It would be lovely to have a module or a function to refresh this relative paths in TinyMCE / textareas What do you guys think? / Nico

Well I can give you the parser for free: Just put the "wp-import" folder in the same directory as "site" and "wire" and add the name of your xml file in the folders "index.php". --- And if you still prefer a real module you can support development via (for example) PayPal mail@nico.is --- Edit: Forgot to add the attachment wp-import.zip

I'm currently working on an importer. How fast do you need it?