FuturShoc

Eureka. That was it. Thanks, Soma!

Yep! Page numbers are enabled, per the documentation/tutorial. Here's a link: http://pvcc.inthooz.me/members/

We're trying to build a "Members" page, with pagination of the 2,000+ user profiles. The pagination links are showing up as expected and some results are being displayed. And the URL does change correctly as page links are clicked. However, the pagination links themselves aren't changing the content of the page. It always just shows the first page of results. $results = $users->find("id>1, start=0, limit=24, sort=name"); $pagination = $results->renderPager();

Ah, yes. Definitely a cleaner soluton. Thanks, apeisa.

Ok, it appears my problem was trying to delete a user that was already deleted. See, I'm reading all this user data from a CSV file and I'm mapping various bits of text from each row to the different fields I've added to the user template. If I get the mapping wrong or I need to revise it, I needed some way to delete all of those users so I can retry the import again. In the process of going back and forth, I got my unique usernames mixed up a bit (generated by concatenation of row data). This fixed me up: try { $u = wire("users")->get($username); wire("users")->delete($u); } catch (Exception $e) { // fires when no user exists by that username }

Ah, I see. I've revised my code to this: $u = wire('users')->get($username); wire('users')->delete($u); ... and I get this: Error Uncaught exception 'WireException' with message 'Unable to delete pages of type ''' Thoughts?

$u = $users->get($username); $users->delete($u); I'm trying to delete users in a batch process as I perfect my import script. However, I'm getting this error on the above code. Error Call to a member function get() on a non-object Cany anyone see a reason this might fail?

Thanks for your input, Pete. Yes, I was afraid of that. I'm really pushing ProcessWire adoption in my shop, but we just landed a big new contract with a municipal client who specifically asked for version control of pages and approvals. I may have to use SilverStripe (our previous shop standard CMS) for this one as I won't likely have time to work out the details of our own PW module in the timeline I have.

We've got another upcoming website project with a client who wants to manage site updates in an approval style workflow. User roles would be generally normal, but they'd like to have the sit generate emails to super users who then "approve" site changes before publishing them. I don't expect anyone to write the code for me, of course, but I'm interested in general feedback on what parts of PW to exploit to achieve this goal. I'm guessing from other posts I've read about user roles that a PW hook might be the best answer here... But I also want to make sure I'm considering any and all native features that PW might provide to help.

Outstanding. Thanks again, guys!

Aha! That seems to give us what we need. Thanks, Ryan. Off the cuff, I wouldn't have expected that to work since I see "parents" as however many siblings exist above the current level. But, clearly, the parent/child model doesn't work *quite* like genetics. ;-)

Can someone suggest a way to get the *level* of a page in the hierarchy? I need to do something different on a page template, IF the page exists at the third level of the page hierarchy. I was hoping for some kind of $page->level() method I could call, but that doesn't seem to exist.

Wow. I just stumbled on this: http://processwire.com/api/variables/user/ It looks like I don't even *need* to know the structure behind user accounts. By using the PW API, I can generate user accounts all day long... Am I right? So. Awesome. Thanks, Ryan! And everyone else here, of course. lol

Hi, folks! We're working on our first big website project using ProcessWire. We're no longer in "fiddle and play with PW" mode. We're committed. My question: The site will have a directory of organization members, each needing a login/pw and a profile page. We're planning to use the existing Users/Roles model of ProcessWire, but we need to generate several thousand users from a pre-existing text file. Now, I won't have a problem writing a plain PHP script to parse the text file and interacting with the database. BUT i could use some help understanding how the user details and fields are laid out in PW's default install. I'm discovering, as many of you already know well, that even users are just pages. This, however, makes it a bit less than obvious how one might generate users programmatically on the fly. I would welcome any input or guidance you might have in helping me know *where* to insert *what* into the DB schema. I'd also welcome any anecdotal experiences you may have had doing something like this yourself. Caveats?

Got it! Thanks, guys! I'd have sworn I tried dumping my cache. As it turns out, the "/styles" folder wasn't getting uploaded when I installed the theme. nikola - The theme is gorgeous! Thanks for your work on it!

This is my favorite of all the listed admin themes. For some reason, none of the CSS files are loaded properly when I install this theme. Could it be because I'm using a non-standard URL? http://74.52.58.162/~imageeff/

I seem to be having some trouble here. I'm developing a site that must live at a staging web host during development, then move to its permanent home at launch time. During development, the site address is: http://74.52.58.162/~imageeff/ I've successfully installed PW, however, i'm not able to get to the PW control panel using: http://74.52.58.162/~imageeff/index.php/wire or this: http://74.52.58.162/~imageeff/wire ============================ ...later. Ok, although I had a suspicion that htaccess was the source of my problem, I hadn't dug deeply into it enough. 1. I had failed to notice the helpful comments in the PW htaccess file which noted a need to add a RewriteBase rule for sites including the tilde character. 2. I had foolishly not trusted the documentation which clearly noted that "http://74.52.58.162/~imageeff/processwire" would be my control panel url. NOT "/wire" as I had oddly assumed by looking at the directory structure. D'oh. Apologies for the false alarm.

For the record, I have a friend who works at Ellis. They've just fixed the trailing slash issue on the CI documentation.

I guess what threw me about how PW handles image uploads is adding an "image field" to the template. This, in my mind, implies that any page derived from that template is inheriting its own images "container". But from reading your clarification, I gather that this images field is more like adding a "portal", of sorts, to ProcessWire's image directory... Correct?

Thanks so much for your help, guys. So, as I understand it, I essentially have to *attach* a photo to the page using an additional field before I can place it using TinyMCE? ** Updated: I see now. So, the new "images" field I create and add to the template serves as a repository for images that I will want to insert INTO a given page derived from that template. This will take some getting used to. Other CMSes I've developed with tend to store images in a single common "container" of sorts. This container would be accessible by any page and any template. I guess its just something we'll have to un-learn.

I'm brand new to PW and would like to find out how you guys are handling a need for image placement in a WYSIWYG field. We almost always need to place an image in a page's content with text wrapping, floated left or right. However, I don't see a way to do that in the default TinyMCE...?