Jump to content

johnstephens

Members
  • Posts

    103
  • Joined

  • Last visited

Everything posted by johnstephens

  1. Thank you! It was obvious what I overlooked. Having picked a "Template for selectable pages", it works perfectly.
  2. Hi! I'm new with ProcessWire, and I'm trying to model different kinds of pages in order to teach myself the system. Right now, I'm trying create a field similar to the tags field in the blog profile mentioned above. So far I seem to be hitting a wall, and I need some outside insight to find out what I'm doing wrong. I tried following the guidance in this thread: I created a parent page for my "tags". I created a new field, and set the Type to "Page". Under the field's Details tab, I selected "Multiple pages (PageArray)". Under the field's Input tab, I set the page I created in step 1 as "Parent of selectable pages". I set the Input field type to "AsmSelect", and checked "Allow new pages to be created from field?". I added the field to a template, and used the template for a page. But when I create a new page in the editor, my "tags" field is an empty select element, with no options, and no text input to create new pages. So I downloaded and the blog profile mentioned above and created a fresh install to compare. The "tags" field in the blog profile's editor looks and works perfectly, of course. But I can't figure out how to duplicate the settings in my own installation. I checked the field settings, and they are almost identical to mine. I see that the Input field type is set to "Select" in the blog profile, instead of "AsmSelect*", but using that setting doesn't change the outcome in my other installation. I also see that the blog profile's "tags" field includes "Autocomplete Advanced Settings" under the Input tab, which is missing from mine. I installed the "Page Auto Complete" extension, and that setting is still missing. Is it obvious what I have overlooked? Thanks in advance!
  3. I file everything under "F", for "files".

  4. RT @quakerbiz: Psst! Registration for the Quakers and Business conference opens today! https://t.co/3fdpbLxoNz

  5. RT @quakerbiz: Registration for the first Q&B summit opens tomorrow, 2 April! http://t.co/zeHDVPCRMc #quakers #quakerbiz

  6. (Apologies to the Man in Black.)

  7. Thank you both! Adrian, you identified the exact problem. Since I installed it to play rather than for a specific project, I hadn't set up a virtual host yet, and the PW directory was located at ~/Sites, with "http://localhost/~{username}/ prepended to the URL. Uncommenting line 84 of the .htaccess file and filling in my username and PW directory appears to have solved the problem entirely. Thanks again!
  8. Dear ProcessWire patrons, I'm installing ProcessWire on my local development machine to try it out. I'm running Mac OS 10.9.2, running the default Apache and PHP (v5.4.24), and MySQL 5.6.13. I also have phpMyAdmin and several other LAMP applications running without any problems. The ProcessWire install script ran without any apparent errors, prompting me for my database details, letting me create the admin user, writing the config file, and populating its database with new tables. Finally, it prompted me to log in or look at the site, and that's where my success streak ends. When I try to access the admin url "/processwire/", I'm greeted with the error: "Database unavailable." Likewise when I try to access any page on the "Basic Example Site"—all except for the homepage, which loads fine. No errors are logged by Apache. I removed the ProcessWire directory and database, and database user, and installed it again from a fresh zip package and fresh database, and I hit the same wall after the install script runs. Again, the config file was created and the database was populated, so I can see that it actually connected to MySQL using the credentials I entered. I don't know what steps to take to troubleshoot this. My other local LAMP applications, including phpMyAdmin, Textpattern, and others, continue to run fine. I'd appreciate any insight or suggestions. Thanks in advance! John
  9. Great summary of the ambiguity of inequality: Income Equality: A Search for Consequences http://t.co/HbmrHCV26D [ht @flowidealism]

×
×
  • Create New...