Jump to content

onjegolders

Members
  • Posts

    1,147
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by onjegolders

  1. Could you make a link on jsfiddle or codepen? Then I'll gladly take a look.
  2. Hi Bacelo, Welcome to the community and don't be worried about your current lack of skills. We all have to start somewhere. You're in a good place. That said, it seems what you are asking is more of a CSS/JS question than anything to do with PW. To start with I think you need to determine your structure in HTML. Eg: Link -Sublink --Subsublink --Subsublink Link Link Link -Sublink Then figure out how to output that in PW. This part is relatively easy. It will be a combination of loops, referencing a links children. Eg: $link_pages = $pages->get("/")->children(); // These are your top level pages foreach ($link_pages as $lp) { echo "<li>" . $lp->title; if (count($lp->children()) { // does this page have children? echo "<ul>"; foreach ($lp->children() as $lpc) { echo "<li>" . $lpc->title . "</li>"; } echo "</ul>"; } echo "</li>"; } This is only intended as pseudo-code. Let us know if you get the basic idea.
  3. I'm guessing "tags" here is something you'd need to be testing for. $randomimg = $randogal->images->find("tags=fave")->first(); Haven't actually used them recently so not 100% sure.
  4. Sounds like you want to create a login.inc template where you include a login form (modal or the like) and on pages where you want to password protect, include this form and do a check to see if the user is logged in. If they are, then form doesn't show and content does, otherwise vice versa. If you really don't want them to have a username you could just do a check between your predefined password and what they enter in the password field. If it passes, then let them see the content (and set a $session variable so they remain able to see that page)
  5. I think based on the number of likes Willy's comments get that he's well liked
  6. Hi Jonathan, I might be wrong but I'm thinking that the main reason this is so useful is that with Wordpress there are so many obstacles to overcome and this helps reset them in some way. With ProcessWire basically being a blank canvas I suppose the need is less great? That said, there are sure to be things here that can help speed up any site's development.
  7. Hi Tyssen, regarding the likes module. I've recently implemented a liking system that isn't as yet moduralised but that works well. I'd be happy to point you in the right direction.
  8. A very happy Sublime user. Atom's close though....
  9. You could also set a $session variable at the top of every page (or header.inc) and then call that. $session->prevPage = $page; Courtesy of Diogo, 2 years ago https://processwire.com/talk/topic/1257-non-admin-users-login/?p=11250
  10. Guenter have you set $menu_items?
  11. Hi ankh, Looks interesting and shouldn't be too hard to incorporate into any PW project. Let us know how you get on and if you get stick am sure we can help you figure it out.
  12. Hi ankh, You have a capital $P on your variable. $P->body = $body; //Set the body This could be why the body is not getting updates. For the redirect you can use: $session->redirect("/");
  13. Joe, you still can list them directly on the event page and you don't ever have to go to a separate page to add new ones. You can create new performers directly from the event page. It would work as follows: 1) Create two templates - "performers" and "performer" (can have their own file or not) 2) Create a page on the pagetree called performers and give it the "performers" template. Now any children of this can be individual performers. 3) Create a field of type "Page" call it "performer". On the input tab, set the selectable pages parent to be "Performers" and the template to be "performer" and at the bottom click the checkbox "allow new pages to be created from field". Now add this performer field to the event template. You don't ever have to worry about performers again. Just add them as needed to the event page. Note: You can set this field to allow 1 performer or multiple performers. This is generally the advisable way to perform this sort of relationship in PW (it is far easier to search, sort and work with the API when the performers have their own page)
  14. Landscape piece of paper and map out all necessary templates and fields that belong to them. I normally start with a base folder with my commonly used modules also. Pretty simple stuff.
  15. Hi Joe, maybe this post from Diogo will help https://processwire.com/talk/topic/2518-repeater-fields-via-api-it-has-no-parent-assigned/?p=24062 Can I ask why you're not considering using pages for the performers here? It would seem a perfect use case for them.
  16. Great to have you here Guru and I think you summed up perfectly why we all love ProcessWire - it's just an incredible tool that allows us to do what we want and in many different ways. Your appreciation for what Ryan (and contributors) have created here will grow as you realise its true potential
  17. Thanks guys, yes Kongondo has it spot on. Just wanted to be able to sort a user's reference/subscription to a page field.
  18. Can't believe I don't know this but is there any way of accessing a date/time of when a field was added/modified as opposed to the page itself? Or would I need to create an additional field to map times to another field's events? Thanks.
  19. EDIT: OK, having gone over and over it, I think I have a solution. By default with DropZone, you don't include your own input type of file and you can access the uploaded file(s) as though you did have an input with the name value of "file" (that's Dropzone's default it would seem). So when initiating a new WireUpload: $u = new WireUpload('file'); Anyone has any issues, let me know...
  20. Sorry, long time ago Just the docs seem to leave out at what point Dropzone leaves the file...
  21. Kongondo, did you ever get Dropzone working with PW? Having issues finding how to hand over the Dropzone "result" to the usual WireUpload call.
  22. The voice of reason as ever Kongondo
  23. Thanks Pete, I guess what I mean is there was a way of doing this trivially in EE, which I think is in keeping with Nico's original post. To confirm, it's not to do with the "theme" but to do with what is being shown to different users/roles. Here it is: http://devot-ee.com/add-ons/zoo-flexible-admin I would also add in the way Meteor JS has very simple modules for adding in login functionality for users : password, Facebook, GitHub etc but I'm guessing this is just something we need more modules for (I think there are already some)
  24. Tell me more
  25. The ExpressionEngine module that made it trivially easy to show different looking Admin areas for different admin roles. Can't remember the name.
×
×
  • Create New...