Macrura

yes of course, but it could seem that way to the 'beginners' who won't then be able to adapt the module to their site's logic; so i'm suggesting to have a site profile (that may include modules) where the full logic of the relations of fields-templates-modules can be studied and then reworked to the developer's needs;

the reason why i think it would be better to have site profile instead of modules is because i think it's better to learn by example rather than rely on some magic module..

$getTest = $findit->ProfName->title; assuming that a field title is used for the template that is being used for the pages that are being selected.

is the name of your page Select actually 'pageSelect' ?? that would be really unusual. you have to replace the word pageSelect with your actual page select field title

can you post your actual code and the complete error message?

it is true that the more sites you build with PW the better you get at using it and thinking in terms of a collaboration between yourself and the api, and the more you read the forum, view the source code of the profiles, modules etc, you are constantly improving and becoming less of a 'beginner', but that term also implies that PW is comparable to the big 3 (and that eventually when you are no longer a beginner you'll be able to achieve those things in the same time as you would in W/J/D), and as Ryan recently pointed out, it's really not, and probably will never be something that can be compared 1-to-1 with those fully interfaced options. The more you know about and work with PW, the more you come to realize that there really couldn't be a generic frontend user management 'module' since the needs of any such system would be unique to the business/application logic of that project. The productivity and simplicity that the clients get through having their site be 100% custom in terms of both the front and backend is really priceless, and that extra time it might take to build something custom as opposed to using a pre-built component/module/plugin pays off over and over again for years to come. I have built a lot of sites with Joomla and a few sites with Wordpress. In 90% of those sites (that are stuck on those CMS) the clients still regularly contact me to perform content management work, because as simple as they might seem to techies, they are incredibly confusing and complex for the average user especially those people who update their site only once in a long while. When i compare that to the processwire sites built for clients, the result is that none of them ever contact me for content management, they can do it themselves, none of them break their sites, or destroy the formatting or look of the pages through gross violations of the wysiwyg... so my response to your post would be of course, it would be great if someone could write those modules, but I think they would need to be subsidized... maybe start a kickstarter campaign for whichever one you think is most helpful?

@zahari - I don't believe any offense was intended .. I read your posts and found them thoughtful and productive. WillyC is a staple of mirth on this forum....

@Enver - i think you are trying to return values of the page selects; that if they are single page selects then you can just output those like: $findit->pageSelect->name_of_field_you_want_to_return_from_the_page_that_is_selected_on_this_page_select_field

you can use the api, and selectors to 'query' your data. For the page fields i believe you can use a subfield selector, like SelectProf.title i'm not totally clear on what you are asking - did you do the following before posting: 1.) Read (study) api section on selectors http://processwire.com/api/selectors/ 2.) Look at the source code of the various profiles including the default, blog and skyscrapers 3.) Carefully looked at the cheatsheet and gained an understanding of the $page object http://cheatsheet.processwire.com/ you should possibly post the code that you are using now and we can try to troubleshoot what you are trying to do. It's hard to help when you only post a sort of theoretical explanation

@J1312 - titanium is right, the option would be that you always have absolute URLs there, but a lot of us use page paths for internal links, so it would be annoying to have to put the absolute url there, especially since the first part of the url might change from development to launch (like you might develop on a dev.example.com and then move to a www.example.com) so i always tell editors to copy the full URL from the page they want to link to if it is external...

right...i guess i would vote for that, unless there is some good reason not to, perhaps there needs to be a way to have a made up url there also (one that is using segments or get vars)

oh right - now i get it! so that panel lets you put in a custom url, and you're thinking that since it's being stored as a page path, that the concern is what if you change the page path; one idea might be the page paths history module, which would automatically handle that redirect; another idea might be to actually enter the page id in that field like /?id=1024/ and then use a module to check for urls that are page ID and rewrite them to the current url..

you can make up your own config vars, like $config->my_special_frontend_login_url = '/login-here/'; i think that is what martijn was implying?

all of my joomla subscriptions are about expired, i think i have 1 wordpress subscription, so once i cancel that i'll be free!

Coda http://panic.com/coda/ Copy Folder: Select Folder, Edit > Duplicate Copy File: Select File > Duplicate Edit: i use these functions so often i can't imaging working without being able to duplicate files and folders on the server. also you can option+drag files and folders to different directories and that copies them also.

have you taken a look at how the formbuilder and the profile exporter are doing this?

have you checked the cheatsheet? http://cheatsheet.processwire.com/

maybe i'm misunderstanding the op, but i copy files and folders all the time using Coda, never had a problem.... (it probably does it behind the scenes, creating the folder and uploading it etc..) and it's transparent to the user; so my recommendation would be to use a good ftp client that supports this?

i guess what you're implying is that the year needs to have leading zeroes; like 0043; maybe add leading zeroes to the year if it is less than 100...? not sure but you should be able to get something to work.. if($page->bfd_year < 100) $page->bfd_year = '00' . $page->bfd_year; // test // echo $page->bfd_year; $year = date(Y, strtotime($page->bfd_year));

this is what i love about the system, i have a client who accidentally deleted some important pages (before i removed page-delete from their permissions) and all i had to do was go in the trash and move them back... i can sleep at night because i know that processwire has been designed from the ground up to be 'safe' in so many ways... edit: @lundy - i should have recommended that you try the batcher module - i recall using that for batch page deleting and i believe that it does actually delete the pages in 1 step; You could then use batcher to find all pages using a template and then batch delete them, then you could delete the template with 1 click.. and also it would probably be possible to write a module that would add a trash button to the page list, maybe look at the modules that are doing similar things with the page tree, such as this http://modules.processwire.com/modules/process-page-publish/

i don't think there is a way to change things to accommodate your complaint; each element has is dependencies, you'll get used to it... have you looked at information architecture and database design? i always plan out on paper the structure of the site before making fields, templates etc.. oh and another pointer - make sure your data and admin structure is really stable before you write any front-end markup

tough one; have you considered using a different system that already has advanced front-end user management, like drupal, wordpress, joomla etc..

users are pages. pages already have auto-id increment

it should work, you should be able to put as many fields there as you want to return results; you can also do stuff like this, if you have different fields on different templates: also notice the % sign $matches = $pages->find("title|body%=$q, template=basic-page|faculty|class"); $kmatches = $pages->find("keywords=$q, template=class"); $matches->import($kmatches)->sort('template,title');

I think what soma is saying is why didn't you use the 'title' field for the band template and then use template context to define that field as the band_title, this reduces the # of fields you need to use, and also simplifies writing the search stuff with the api