slkwrm

Tested it a little. Seems like I'll be often keeping it open on a separate tab. Thanks!

Hi, Beto. This topic has been discussed here. Also check out Ryan's Blog Profile.

Have you tried to increase max_execution_time in php.ini? Not sure it helps, but maybe worth trying.

Great work, Nikola! I love its weightless look, "colorless" fields and palette in general. Looks like my dream theme

One of the ways is to extend user template (don't forget to set filter to display system fields in the list) with a new field "viewable_pages" of a Page type and let site admins select pages that user need view. In order it to work you have to add additional check if the current page is accessible to a user into all of your templates (you can do it in the header you include in each template). Then if the page is in the list you output it's content to a user otherwise you redirect them or show them an error message. Should be something like this: if ($user->viewable_pages->has($page)) showUserContent(); else showError(); This is one of the basic methods, there are many of them, as always in PW

Nice jQuery cheat sheet. Check it out.

Voted for PW everywhere it fits! (counted 4 categories). Speaking of captures. Did anybody have a chance to have fun discriminating cats from dogs hiding behind letters several years ago on Rapidshare? That was fun! I remember reloading that captures 10 times in a row and then I still made a mistake

Gazley, I think appending your special page like you intend is a good way to handle it (PW should take care of duplicated pages in array). And runtime sort sounds good to me too. So this is basically a cheer up post

Gazley, this is some kick-ass avatar! Grab it asap WillyC, I bet if you make mine it would be pretty cool, it's a pity I already use one. But nothing compares to superfly knitted beard!

Hi, Daniel. 1) Very easy: go to 'fields -> your field -> input tab -> visibility' and change it to whatever you find convenient (note that you can use contexts to display fields differently depending on the template they are in). 2) Even easier: drag and drop your fields in your template to change their order and then click 'Save'.

This is just amazing! I'll will check it as soon as I fly back to Russia. Can't wait to try it!

Thanks for clarification, Soma. I use Notepad++ and it detects templates encoding (or expanding? ) as being ANCI. And if I put any cyrillic text to a template it looks broken in browser, so I convert it to UTF-8.without BOM. Maybe I should mention I use XAMPP running on Windows. Reminds me some kind of 8-bit graffiti

Ryan pointed to a good solution here. Edit: Soma, as always you're first

Yellowled, so many ideas! Nice) 1. I agree that having a tool to detect new translatable files would be great. I tried to write a module that would do this, but then I had some more important things to do and postponed this affair. 2. These are nice features, especially, to have a placeholder for fields that don't need translation and fallback to default. (English, I guess). But are not must have as you said. 3. I can't agree here. It's nice to have a free schedule of translation updates. It's more convenient for community as everybody make their contribution when they have some vacant time. Would be nice to have an ability to download and install translations along with modules via modules repo. Especially if it is possible on the first step of installation, so that even the remaining steps of installation are localized. 4. I don't think it is a viable scenario. PW releases are very stable, so it's not a problem to update to a newer version. For now I would maintain translatoin only for the latest version, maybe it will change in future when Ryan will deside to drop backward compatibility for a new version of PW. 5. All translations are in the translation page /assets/files/ folder (the same as page id), your translations are safe during core updates, but if you update translation files then yes, you can easily erase your changes. What about having an opportunity to specify fallback translation for a hmmm... translation? So if you have your personal, say, German translation files you can fallback to general German which you download from GitHub, so your translation remains even if you update general German files. Sorry for mistakes. I'm really sleepy now

Why are they here? Wanted to mention that all templates in PW use ANSI encoding by default, so cyrillic symbols don't display correctly if you put them right into template. It's not a problem for me to convert them to UTF-8 but it can cause a bit of trouble for newbies. Would be really nice to have them multilanguage-ready. I've never used VIM, but heard many legends how configurable it is

I think that if($page->id) checks here that the page isn't a new/just created one.

Just kidding Seriously, closestParent is a nice name as it's self-explanatory, no need to guess.

Soma, I find it too long. What about closestP($sel)? It's like a gangsta rapper's nickname Nobody will guess what it means.

bitmax, not sure what you mean Could you explain in more detail?

You can't use this code inside heredoc string as it's basically a big string from <<< _OUT to _OUT; Heredoc syntax is easy to understand so try to look up the link SiNNuT posted. You can have as many heredoc identifiers as you need. echo <<<MYSTRING my string's content and $myVar MYSTRING; So it basically serves to let you write a big string right in your code. If you don't want to fiddle with heredoc, you can still use ordinary echo to output your form line by line.

Wow! Very nice website, everything's in harmony. Congratulations!

Also you can get a page by its id even when it's unpublished

Overall I enjoy using a new forum. Indentation bug is a little bit annoying, but all in all I have very positive experience so far. Thank you, Pete!

This is because $user->outputFormatting is on in templates by default. It should be this way. Try to set $user->of(false) before this code and you'll get an error using this syntax.

If you mean wrapping your inputs in fieldsets then you could do it this way: $fNum = 3; //number of fields in a fieldset $n =1; //counter foreach ($products as $product) { $checked = in_array($product, $form['products']) ? "checked" : ''; $out = "<label><input type='checkbox' name='products[]' value='$product' $checked> $product</label>"; if (($n%$fNum == 1) || $product === $products->first() ) { $out = '<fieldset class="prod_col">'.$out; } if (!($n%$fNum ) || $product === $products->last() ) { $out = $out.'</fieldset>'; } echo $out; $n++; } Edit: corrected wrong variable names