Jennifer S

Thank you! My admin log-in didn't work after the migration so I reset it using this nifty trick: http://processwire.com/talk/topic/490-how-to-reset-your-password-how-to-enable-the-forgot-password-function/?hl=%2Blost+%2Badmin+%2Bpassword Now I'm re-saving my all my users' passwords. I'm wondering for the future if I did something wrong with the import or if this is a known issue concerning the "salts" not matching up.

Oh, I think I need to choose one or the other. I will go with the masked URL. Yay! Now to do a find and replace on my database to fix the paths.

I turned on debug messages and the site told me: Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 7680 bytes) in /nfs/aesop02/hw21/d09/fyp/wire/core/Template.php on line 425 I deleted a dusty old php.ini file that had probably been sitting in the root for quite a while and now the home page renders! Then I uncommented the rewriteBase line in .htaccess and made it "/fyp" and now my pages render! Now to get this working with a DNS "pretty URL" redirect. How can I tell processwire that a page can be both: http://depts.washington.edu/fyp/community/ and http://fyp.washington.edu/community ?

whoops. posted to wrong thread.

Thanks for the suggestions. I installed the Profile Export module on the working site and followed its directions. I get this message during the compatibility check on the new install: "Unable to determine if Apache mod_rewrite (required by ProcessWire) is installed. On some servers, we may not be able to detect it until your .htaccess file is place. Please click the 'check again' button at the bottom of this screen, if you haven't already." I continued with the install and the new database was populated with my site content, but I still get 500 trying to access the site. I changed the permissions on the root index.php file to 0755, and the permissions on the .htaccess file to 644.

This morning I have been trying to copy my existing PW site to a new web root, as well as up one level in hierarchy (i.e. the old site was "fypnew/processwire" but the new site should be just "fyp"). I've copied the server files to the new location, edited the root level .htaccess file to point to /fyp/ as the new RewriteBase, and confirmed that the PW database user can still access the PW database (I am not planning on migrating the database location). I am getting the 500 error when loading the new location in my web browser. I am pretty sure the web server is reading the .htaccess file, and that it has the right permissions. I suspect I am missing some other piece of the puzzle? I am not sure how to debug from here, or what to do next, although I am looking at the PW Profile Exporter module.

Ah, I see. It is easier to learn new things than to unlearn old things. This system is so elegant!

Hi. I'm using this as a selector to grab every page in my site that has a multi-page select field set to a particular value: $theseones = $pages->get( "/" )->find( "has_parent=/, tag_seasons=/tags/seasons/spring" ); Is this un-wise in terms of performance, etc? Cheers, Jenn

I think I am talking about a way to access the content of repeating fields (or any field, for that matter) through the admin/editing panel, as if they were assets like images or files.

Thank you!

Does this mean that I can't sort repeating elements by one of their fields? So, say, alphabetically by title field *within* the repeater?

Yes. The hard part, I think, is making it clear to editors what to add to their text content to trigger the corresponding modal box. Which is why I was investigating using a "smart" field description that appended the correct ID to an example link tag that editors could then copy and paste as needed, once they added each piece of modal content as a repeating field. I'm also looking into other means of progressive disclosure because I think relying too heavily on pop-up windows is probably not optimal.

It took me a while tonight but I think I understand option "pages" now. The affordance for flowing checkboxes into multiple columns is the cherry on top. I want to buy someone a drink. I am *thrilled* with this software.

Here's what I'm doing: I added a repeater field to my basic page type to hold blocks of content to be called as modal pop-up windows as needed by editors. Ideally I could add a box to the Insert Link dialog in the TinyMCE editor and they could choose to insert a link to any and all instances of their repeating content just like a Page or File. In lieu of this, I'd like to output the correct link tag to make the modal appear as part of the field description. I'm currently using an instance of the Title field to use as the unique identifier in the HTML for the pop-up. I sense I may be going about this in an entirely backward fashion. Advice is welcome. J

I think I mean is it possible to index the site after content includes have been rendered by the individual pages. So that my include shows up as a result on its own, and as part of the page it is included in.

Once the content from the hidden sub-pages has been included on a regular page, does it get indexed by the search engine?

Hello world! The generator tag in the default templates/head.inc file reads: <meta name="generator" content="ProcssWire <?php echo $config->version; ?>" /> I think this should be <meta name="generator" content="ProcessWire <?php echo $config->version; ?>" /> Cheers, Jenn