kongondo

Hi Pierre, Welcome to the forums. Actually, lots of us have been using 2.4 for a while now..But that is now history, 2.4 is now in RC status! A newsletter went out late last week to this effect. An official announcement is soon to follow. You are good to go! Edit I forgot to respond to the issue about upgrade. Nothing breaks upgrading 2.3 to 2.4, at least not in the core. And I haven't heard of any of the custom modules breaking either...

More links for you... http://processwire.com/talk/topic/3619-updating-repeaters-via-api-without-removeall/ http://processwire.com/talk/topic/3969-problem-repeaters-why-u-no-save/?p=38938 Seems you may have to save repeaters individually as well...and not just the page? Maybe that's just for editing? But if adding a second item to a repeater, maybe that is editing? Try and see Edit: Just to reiterate what's on the other thread and in above posts. Repeaters are themselves "hidden" pages. So, You have to iterate through the repeaters and treat them one by one as if they were normal pages.

I should have added, "ugly" is relative . You are right, I wouldn't lose sleep over the dotted lines

Felix, this is a very beautiful site! One of the best I've seen showcased here! Two issues: - Jumping to sections is a bit too fast for me. - There's an issue with the way menus hovering over each other (can't describe it well) but will edit this post and try again - OK, let me try again: The menus at the top allow the visitor to quickly jump through sections. Once one has jumped to a section, that section's menu is displayed at the bottom of the screen. One would expect that clicking on them the page would scroll down to view the content. That doesn't happen..one has to scroll manually. E.g., If I click on "in balance", I am taken to the right section. However, (and this comes naturally), when I click on Sport und Freizit, I would expect the page to scroll ... Hope I make sense. But very nice site, cheers! Edit: Third issue: - In Firefox, one sees the ugly dotted outlines around the section menu links.Maybe needs a -moz-focus-inner border:0, unless this is intentional, of course

I'm glad you like it landitus. In a sense, PW already has those tables by default - they are just not set up yet . As you know, PW gives you the tools to build what you want (in this case MarkupAdminDataTable). If you look at the code in my example module, it is all PW API. Yes, it has some in built classes to interact with javascript, but it is all PW. Part of PW philosophy is to be clean, lean and mean and not make presumptions. I am liking your idea about generating such tables via the admin UI. Actually, similar things have been done. See the proof-of-concept module by Soma DataTable. Batcher also comes close. Ryan has also spoken of developing a site where pages appeared in a table (IIRC) when they reached a certain number in the tree or toggable or something. I can't really remember the details. But yes, it can be done. Back to the admin tables, if it is something you'd like to discuss, let's open a new thread. In a sense though, Batcher already fulfils some of the functions you are talking about, albeit it is not configurable in terms of what to display.

@dragan...a clarification - if you have a chance, have a look at Wanze's code in his module Batcher. He creates a permission "batcher" which you can give a certain role. Although the batcher page appears under setup, it doesn't have to be moved manually from under setup in order for the non-supersuser (manager in your case) to see it. They will only see "batcher" or in your case "changelog" under the setup menu; nothing else. Try it and see! Speaking of batcher, I prefer the route batcher takes of creating a permission to give access to the module rather than applying it site-wide with a page-edit permission (Wanze was just giving an example above). Of course, there will be times you don't mind giving permissions site-wide....OK, enough rambling...Hope this makes sense! Edited for clarity

@PeterDK, What didn't work? Don't you get an image output? Do you get errors? The code works for me..Make sure your replace $page->images with the actual name of your image field, e.g. $page->bilder...

Whether we win or not today, guys, you've done an awesome job! Respect all round. Much appreciated... Either way, I see no way that PW will not be packaged by BN...they will do it....(just my take..)...signing off now...

Co-founder of Bitnami votes for PW. Huh?

Disappointing.. I'm not watching this anymore...

If interested in further developing your php skills, some handy tips I have received/learned from the pros in these forums include.. var_dump gettype - this will tell you the data type - object, array, etc. exit - this will allow you to go get some coffee ;-) - instead of smashing your head against the wall! (kidding!) Happy coding!

Someone more knowledgeable than I will give you a better answer but am wondering..why not just create pages outside admin for each user if that's what you are after? Behind the scenes, users (i.e. those under admin/users) are also pages! So, you can create a parent page "riders" with child pages "ridername". You will just have to access them with the $page or $pages variables rather than $user. You can then associate users (created in Admin) with their pages (those under "riders"). A search of the forums will reveal this has been done before (and it gives you more options quickly, although users under Admin can also be extended [via the user template]). You might also want to check out the various PW modules that help manager user access on a page or field level. Edited for clarity

Nice! Thanks. Aaah, a Windows issue.... Let me test.. Edit: Bazinga! Fixed! Am the proud owner of a brand new Core tab!

Attached, the whole list (local install, no worries...) fields.txt

No errors - it works as intended; outputs a list of all modules and the files they come from....

Yes, they are listed under Site tab (PW 2.3.15, W7, Chrome, FF, IE). This drove me nuts yesterday debugging! tried in xampp 1.77, 1.8x, Uwamp - no dice! But it works in two different remote servers! The mystery InputfieldWrapper4 just doesn't show up! A search for "autocomplete" reveals the same 4 hits in both cases, i.e. where the "Core" Tab does not show up in some installs and where it does. See code below <span role="status" aria-live="polite" class="ui-helper-hidden-accessible"></span><input type="text" id="ProcessPageSearchQuery" name="q" value="" class="ui-autocomplete-input" autocomplete="off"> <td><a href="edit?name=InputfieldPageAutocomplete">Page Auto Complete</a></td> <ul class="ui-autocomplete ui-front ui-menu ui-widget ui-widget-content ui-corner-all" id="ui-id-1" tabindex="0" style="display: none;"></ul></body></html> Edit: @Ryan....RE your quote above, this is a typo "InputfieldAutocomplete", no? Should be InputfieldPageAutocomplete

Thanks Adrian for the reminder. Yes, there's that as well. I forgot to mention that this could also be accomplished using a custom admin page....We're spoilt for choice with PW!

Nik, thanks for the update! I'll test and see if I disagree (e.g. make the choices configurable? or maybe that's overcomplicating things...)

Hmmm, You could easily do this with a very simple module, no? E.g. make use of Soma's latest jQuery Data Tables helper class (with Ajax goodness, etc) or PW inbuilt MarkupAdminDataTable. I'll post a link to a short demo video here and some code in Github to show you how simple this can be accomplished..... Edit: added video demo code: Will upload soon....it is very rough code, a proof-of-concept... ;-) As you can see from the video, a couple of things could be improved! Uploaded here The code here is so trivial it shouldn't even be upped to Github. However, I hope this helps to show newbies that PW is dead-easy!..even for PHP newbies like me! Pete, sorry to hijack your thread

Hmmm..well this is happening in different local installs - skyscrapers, blog profile + 3 other....

Update: No JS errors here as well. Tested in FF, Chrome and even IE. Cleared cache all round...But... Remote server: It works fine in remote install! - I see all 3 tabs Local (XAMPP) server: I see only 2 tabs (site and new). I tested both upgrade and new installs. Conclusion: Something is wrong in XAMPP? I am upgrading to the latest version to see.. Thanks.

Nik, Thanks for the update. Works nicely but there is one issue..A cookie is not being set/or is being ignored for "remember this setting" when it comes to "Edit next sibling page". Is this the intended behaviour? (maybe to deal with cases where there is no next sibling?). At the moment, it is rather tedious to keep on selecting after save -> edit next sibling on each page edit

Yep...several times...unless there's another cache I don't know of?

I am not sure whether I am posting on the right thread... On one PW install (2.3.14 - dev), when viewing the modules page, I see the nice tabbed separation of modules, i.e. "Site", "Core", "New" (see screen). On all other sites I don't see "Core". This happens on all four new Admin themes. Am I missing something? Thanks.

has_parent.... http://processwire.com/api/selectors/ http://cheatsheet.processwire.com/