Soma

I want to be able to say on a per template basis, what role can use the template for new pages. Further considerations regarding templates setups I got pretty big setup with many different types of templates. I have each of them set up to allow only certain children and/or parents etc. This is great to reduce the selection one has when creating new pages, and allows for some great control. Sometimes it is may even needed to only allow a certain template in a certain section. But this may goes too far, but depending on how you use PW to build sites, it can be a neccessary feature. THis can get endless I thought and I can't wrap my head around this particular problem what is best way to go. This is very nice but can get a little cumbersome to manage and maintain, as there's no overview (especially for new admin that are new to a project). Mainly it's hard to keep track of what is where how it inherits. It is easy if there's only a handful of templates, but I got around 40 templates and it's still growing. But I guess that's the nature of having so much templates. And I fear that the level of complexity can get worse as a project grows. What would be the best practices, or would there be a way to solve it all different and more convinent? I would like to discuss this a little more and like to hear what others think. Also what are your plans on this subject Ryan?

Congrats on the Site. Looking good. One thing that came to mind: The top main nav has no highlighting.

Not sure about this. I thought about it too, but didn't feel it's needed. I mainly use search function or the left index, I never find myself scrolling really.

That would be great to have. Thanks for bringing it up Nico. Can someone please shift time 2 years forward! Can't wait for all these features to come. --- Oh, would it need to be automaticly or lazy cron, just a manual check would be enough?

tsd, if you need more help just ask here. I'm sure we can find a solution that suits your needs. But first try out and think what would be best for you. Let us know what you come up with using.

That would be the 1000th thread asking for repeatable/multifields already. I think they're are planned and on Roadmap

Why not? Actually pretty fine solution to add it in page to be able to say where it should go. There's actually some different ways you could archive something like this. - add a field for selecting what navigation the page should go. - add a structure to define navigation. Special type of pages where you can select what page should have link in footer navigation. - same but only one page with page reference field - add the 2-3 links manually to the footer nav code. And make them hidden in admin. - by a special template for footer pages.

Sure you can with no problem, just have to remember it.

I'd vote for as much as possible, bring them all. ;D But it's a valid question and should be well considered. Mainly the end user is the most important. But I think about site builders that don't speak well english, so I would go for complete, although this would add much more work and every future modules would need some translation... so definately worth considering having "system" section english. – Damn I couldn't decide.

I'll add mine too. Just waiting for godo.

Thanks for the kind words. Glad you like it. I also like it and thought long time about it. Happy it get's recognized ;D Good idea, I also worry about not being recognized by some. I'll give it a try. That would make sense I think. Well I thought judging by "used rarely" not always fits. I always worry about useful functions "rearely used" not being recognized when using simple mode. But I still also think having as few as basic as possible, will not overhelm the user on first sight. – I'll move them to advanced mode. There's a few such things that came to mind. Like this you mention here. For sure I will gladly add it. I think such things, mainly taken for granted by us experienced users, are dangerous to assume the users/new users will digg it. I remember not recognizing some things at first and getting confused a little. On the other hand it can get confusing for not so experienced php coders to have too many different ways to the same. I know of co-workers that don't like such things. What you guys think?

Thanks Ryan, I think this was it. Not sure how this happend, cause I never played with autoload. I think I even reinstalled it. And before attaching it I reinstalled again, but I think I wasn't looking at the code after. Somehow I successfully messed up and after doing it right I didn't look correctly... Now it works, and gets loaded after jquery core. If you uncomment the scripts add in ___execute, and remove the module js one it should work. I commented them out to test. HF

There's nothing special, pretty much what you describe. Theme doesn't matter... No other modules... I attached the module. But it's just rough code, nothing serious yet. DataTable.zip

Thanks formmailer, you're too kind! Glad you like it.

In the module's hook function you can do something like this: <?php public function someCustomFunction( HookEvent $event ) { // get page object $page = $event->object; // get first argument $some_id = (int) $event->arguments[0]; // current language $lang = $event->arguments[1];

I'm asking myself why youre trying to make a loop to get 3 random images. Can't you just use $result = $page->images->getRandom(3) ? Then loop the returned three images? Haven't you used the Cheatsheet???

I've done major update, just commited. - some restructuring, adds and removes - minor tweaks overall, typos, ordering - added "advanced" mode ADVANCED mode: Mainly it started with only "System Configurations" being advanced, but I added many of the more advanced functions overall to the advanced mode. I don't know if it really is the thing to go, but I thought why not try to have very simple and basic version so it would fit on a matchbox . So they're my guess on to what would be the more advanced stuff, and I had kinda hard time to decide what to do and how. After long back and forth I decided to just give it a go and see what people think. It will be cached on http://processwire.com/api/cheatsheet. Or avaiable also on http://somatonic.github.com/ProcessWireCheatsheet/

I was also thinking about this... That looks like a great datepicker addon, didn't know it exists. thanks!

Thanks, Ryan. Yes I'm doing it this way already to get it working. I add it through API. Yes the example getModuleInfo is untouched and there's nothing else, when I try again to have it loaded automaticly it get's added as first script before jquery core with the code posted. class ProcessDataTable extends Process { static $columns = array('id','title','path','modified','modified_users_id','actions'); public static function getModuleInfo() { return array( 'title' => 'DataTable', 'summary' => 'Provides ajax driven data table for pages.', 'version' => 100, 'href' => 'http://processwire.com/talk/index.php/topic,637.0.html', 'permanent' => false, 'singular' => true, 'autoload' => false, 'permission' => 'page-edit' ); } public function init() { parent::init(); } public function ___execute() { ...

Ryan, if something could be there to make this possible, that would be awseome. The thing is I use the edit/add hook to make WHOLE branches from the root editable, like for whole language tree of a multilang site. So there's de-ch,en-ch,fr-fr,en-fr,de-de branches, and I give edit access on user level via page reference field to one or two of those, so the other languages are also visible and a little confusing, as there are so many in one PW install (I know now I could use symlinks to setup a PW for each and share templates, but I think it isn't really an option as there is central branches that all language sites need access to). I know there's different needs and situations but if used like for whole main branches it works straight forward. I don't need to give user access to a subpage only. It only root pages and all subpages of it.

Ryan, the modules is autoload=false I just copied one to start with... class ProcessDataTable extends Process { static $columns = array('id','title','path','modified','modified_users_id','actions'); public static function getModuleInfo() { return array( 'title' => 'DataTable', 'summary' => 'Provides ajax driven data table for pages.', 'version' => 100, 'href' => 'http://processwire.com/talk/index.php/topic,637.0.html', 'permanent' => false, 'singular' => true, 'autoload' => false, 'permission' => 'page-edit' ); } public function init() { parent::init(); }

Hehe funny. I'm using "_images_tab" for tabs. The other day I was trying to get them more visible by renaming them to something like "____________images_tab" - but it wouldn't let me and rename it to _images_TAB, seems like only one "_" is allowed. I was a little bit sad, but found it's ok for now, and was sure it will come up somewhere. Good Idea with the indent Ryan!

Do you know there's tabs fields you can use to create custom tabs and put fields there. I'm using this quite a lot.

... or maybe "Tree" I agree, and good idea. As this is what I'm needing too, to define it per template. We were already discussing such things. Also a good feature would be to have an icon per template that show in the tree.

Great, I'm glad it was helpful for you. Thanks for sharing your experience! BTW I'm just working on a update with some things removed and some things added. Ryan helped some to double check everything is right and he made suggestion to move some parts or make them as an advanced mode that can be turned on or off. I think I'll have it ready this weekend.