kongondo

I now see what you mean...I'll edit this post in a minute EDIT 1. There are two CORE user modules a. "Users" b. "User Profile" "Users" module has a module settings page that "allows" adding fields. It says "What fields should be displayed in the page listing?". By default, there are three fields - name; email, roles. You can add extra fields here. "User Profile" has no such settings OK, so we are dealing with the core module "Users" You add your field "images" to the module "Users" and press submit. You then go to /setup/access/ "your user name" but you don't see the field you just added, right? Well, I don't know why that is so. I haven't checked the logic behind it, or whether it's a bug...Plus, the user (e.g. "your name" is a page, and it is connected to its template (i.e. "user"). So, fields added to the template show up when editing a page using that template....However.... You can still add an image to a user by adding an image field to the "user" template, i.e. Allow display of system templates, then add your image field to the "user" template. This will then appear for each user when you go to /setup/access/ "your user name". Adding images this way works fine....Which brings me to the question; why not use this route?

Ah...I see you are using this module? http://processwire.com/talk/topic/2567-user-profiles-for-pw/, no? OK, that's a third party module but hopefully you can get answers here, although it would have been better to post in the modules support forum (it looks quiet over there though...) EDIT Ignore above - I got confused Troubleshooting: Are you getting any errors? When testing on your local install change config->debug to true. Also check for errors in /site/assets/logs/errors.txt..

OK, I think I get what you are saying...somewhat... 1. You've edited the admin template (admin/setup/template/admin 2. You've added an image field to the admin template 3. You've gone to admin/page/profile page and added an image there? Is that it? or is #1 = admin/setup/template/user ? What I am not getting is "user profile". Do you mean the user page? Also What list is this? What does this mean? The text is not visible or it is not working? What does modify mean? Delete it? What do you mean by server? Remote or Local install? Sorry, just trying to understand exactly what's happening. I have tried adding an image field in my "user" template, then uploaded an image in that field when editing the "superuser" page and it works fine. PW 2.4...

Hi Mike, Welcome to PW and the forums! In a hurry, so, maybe missing something - maybe the image field is set to accept only 1 image? Change that to "0" to accept multiple. I'm curious, why do you want to add more than one image to a user field? ..... You'll get a better answer soon...

Something to get you started: http://processwire.com/talk/topic/1932-security-sql-injections/?p=18127 http://processwire.com/talk/topic/4426-pushing-pw-in-web-design-agencies/ And more.... http://bit.ly/1fxHHux Good luck with your talk! I know you'll do PW proud!

Success it seems! Good! I'm glad you didn't give up...here's the same issue reported elsewhere: http://processwire.com/talk/topic/1962-cant-reach-admin-page/?p=49524 http://processwire.com/talk/topic/4807-fixes-for-pw-installation-on-a-shared-server/ http://processwire.com/talk/topic/2439-htaccess-issue/?p=49862

@Macrura - that was the post horst linked to ;-)

The exercise about commenting out the lines is to find out which rule is causing problems. By now you should be able to tell. Are you saying that you need to comment out every rule in the PW .htaccess in order for the site to work? That would be crazy. Could you find out exactly which rules in the .htaccess are causing problems and post those here? It's a pain but you will have to test commenting out each line until you find the offending line(s)...Or, talk to your host and tell them about your 500 errors...They'll normally tell you which lines to look at. Some hosts allow you to edit .htaccess files within their file managers in control panel. That should save you the uploading!

That shouldn't be the case. You should only have one under /yoursitefolder/. There shouldn't be another under /site/. Sometimes hosts include their own .htaccess files too. You need to confirm that you are using PW .htaccess.

It seems the problem is a directive in your .htaccess file. Have you tried to comment out these rules/directives one line at a time, saving and reloading the site as suggested above? That will help you figure out which line is the problem. Do that and let us know how it goes...I'd suggest to first try the ones I mentioned above... Edit: The bit about renaming .htaccess to htaccess.txt was to find out if that was the problem. You need to rename it back to .htaccess - then, proceed as I suggest above..

You will have to edit your post using the full editor in order to edit the subject line...

Well-done Neeks! That's a really beautiful site! I am glad you are enjoying PW! Is the site complete? Currently all (?) links seem to be taking me to the contact page? - sorry, my bad Btw, may I suggest that you rename the title of this thread? E.g. Principled EDU?

Yes...I agree...

Yes...repeaters, behind the scenes have their own templates You have to enable "show system templates" under : admin/setup/templates filters. Select radio button "Yes" to show system templates (you can disable this later). Then, under admin/setup/templates system, you will see your specific repeater template named "repeater_nameofyourrepeater" - you know what to do from here...

@Adrian, I was looking for that module to point to but I couldn't remember the name nor find it in the modules directory ...Yes, that's a good place to start

If uploading to a sub-directory, you may want to sort out the RewriteBase directive as Adrian pointed out in the links..E.g. see this. http://processwire.com/talk/topic/4917-the-admin-cannot-be-reached-in-new-installation/?p=47780

Hi Hari, Creating fields using the API is very easy in PW. Have a look at various modules. See also this thread:http://processwire.com/talk/topic/1051-adding-and-assigning-fields-without-using-gui/. Of course, you will have to adapt the code for a module (essentially a PHP class).... The ___install() method is only called when the module is installed. Use this if you want to create something only one time, e.g. custom tables in your database that your module will be using. For "creating" other fields that will be used when the module runs in the admin (e.g. for process modules) you can throw those other methods in your module class, e.g. ___execute(). - [this one is executed when module is called]. Again, have a look at the various modules out there... If you will be creating a module, what is the need for a template and a template file? This bit I don't get Hmm...I like this idea about a blog module... Edited multiple times for clarity and sanity!

What I meant is, if it is a Field created in the PW admin, (e.g. a text, date, email, textarea, etc.) - not via API. Is this still the case? Could I create a Field in the admin, say, called summary but have that store its data in Amazon S3, flat flle, etc?

Nice one..! Only issue for me is that it could be somewhat "tiring" [can't get a better, more subtle word] to navigate after some time since one needs to scroll down to view the content....which just peeks at the bottom of the screen... Uh, missing image [carcallen-values.jpg] here: http://www.carscallen.com/firm/core-values/

Hi John, Welcome to PW and the forums. 500 internal errors like that normally point to an Apache error, i.e. something on your server. In addition to Adrian's suggestions, note that some web hosts don't allow some rules in .htaccess file, e.g. these: Options -Indexes Options +FollowSymLinks Options +SymLinksifOwnerMatch Comment those out one by one and see if your site loads. If not, also, check /site/assets/logs/errors.txt although I doubt you'll see anything there at this stage.... Other: if you have access, check your Apache error log Are the folders in your /site/assets/ writable? You actually have a .htaccess file? If you do, rename it temporarily to htacess.txt. Does the problem vanish? If yes, then Apache is definitely unhappy with some rule in your .htaccess file. Are you installing in a sub-directory? Version of PW?

To expound on what Apeisa has said... There's a very good write-up by Teppo about Fields and Inputfields over at his blog http://www.flamingruby.com/blog/anatomy-of-fields-in-processwire/ A bit more here: http://processwire.com/api/fieldtypes/ http://processwire.com/api/fieldtypes/validation-fieldtypes-vs-inputfields/ All Fields have a corresponding table in the PW database named like so.. field_title, field_body, field_myfield, etc. Have a look in phpMyAdmin or something

David, Welcome to PW and the forums. This module is now part of the core so you don't need to install it this way. If you are using PW 2.4 (i.e. the latest version) you should see it under the "Core" tab under /modules/. I believe its called "Languages Support - Tabs" (see category Language)

I'd say this has been a resounding success! Very good idea this one!

OK. Sorry, I can't help much further; I don't know how to accomplish conditional styling in the admin...

OK...now waiting for the "all will become clear soon" bit....