Jump to content

Pete Jones

  • Posts

  • Joined

  • Last visited

Everything posted by Pete Jones

  1. Another thread where this was discussed: https://processwire.com/talk/topic/11989-multiple-site-monitoring/ Great community and a really interesting development.
  2. Robin S, that worked (almost) perfectly, thanks. I just had to change it to: $config->paths->files = $config->paths->files . 'example/'; $config->urls->files = $config->urls->files . 'example/'; Thanks everyone.
  3. Is it possible to change where uploaded files are saved? They are currently saved to: /site/assets/files/ I'd like to save them to: /site/assets/files/example/ Thanks
  4. Before I download, I have a few questions: 1) Discount codes - is this supported? 2) Affiliates - are you able to give users a specific link and then assign orders to an affiliate 3) Product matrices - products can have pricing options (Small, Medium, Large and Black, Green, Yellow)
  5. Is Padloper still active? We're currently looking at developing a flexible ecommerce solution (we build a lot of PW sites) but need to check it out. Is there any form of dev download?
  6. Wow. Can I ask how you built the data structure? Was this all through processwire and pages? Did you customise the PW admin area or is this entirely frontend? Having tried to build a basic proof of concept the data structure it's tough to amek the admin area work sensibly. Pete
  7. Hi Tom, Thanks for posting. For me, it's about making the admin area nicely maintainable. To that extent we'd need to be able to customise the admin area fairly heavily. Is your ticketing system something I could take a look at from an admin perspective? Pete
  8. Right, so let's just say we have a members area which holds all of the User/Horse/Payment details and a CMS. Is there a way in which we can have a single point of access for all this? We've been discussing perhaps a Laravel user/horse system and expose some JSON for the website area. What I don't want to to provide 2 'admin' system to the client. One for users/horses and one for the CMS.
  9. OK. So if we were creating this sort of structure in the admin area of PW, could we build it using linked pages/repeaters? Also, is there any benefit in building the sort of admin functionality as a frontend or as part of the standard admin area?
  10. We are currently looking at building a custom administration area with the basic outlined functionality. Users will be able to login and see their horses, their events and their payments. Admins will be able to login and see all users, horses, events, payments. Data structure below. Questions 1) Would this make sense to build as a single frontend with different 'admin' levels' rather than customising the backend of PW? Ultimately the PW install will be running a full frontend website (showing Horses for Sale, Events and other misc content) so users will need to login to update content. 2) How does PW handle database relationships? Could this structure be built? Users ------ ID Email Horses - one user can own many horses ------- ID UserID Membership Level (payment) Events - one horse can enter many events ------- ID HorseID Required Membership Level Payments ----- ID TransactionID Payment Items - one payment can have many payment items ---- ID PaymentID Order Type - Horse Registration/Donation/Event ItemID - HorseID, DonationID, EventID Cost VAT Many thanks Pete
  11. Doesn't that defeat the object of having PC in the first place? Like I said, it's awesome, but stripping <body> tag, feels wrong to me. I wonder if any other front end devs would agree?
  12. In my mind, the word can should be in bold here. Just because you can, doesn't mean you should. Omitting the <body> tag, whilst saving a couple of bytes opens a can of legacy worms. Older browsers will revert to quirksmode and Google Analytics 'prefers' analytics code immediately after the <body> tag. The module is awesome, and has shrunk down the first site we built to be so quick, the web inspector barely keeps up, but this one seems like it should be optional in ProCache to help with legacy development. What do you think Andreas?
  13. Debugging the js for this shows an error at InputfieldCroppableImage.js?v=83-1460630526:36 Uncaught TypeError: Cannot read property 'crops' of undefined json = config.CroppableImage.crops[suffix];
  14. I've installed this over a fresh codebase so it's not a codebase issue that I can tell.
  15. Hi, We recently installed the 2.7/2 version with CroppableImage (which worked fine). We then upgraded to 3.X which broke CroppableImage. When you try to upload an image and then click on the crop button we get the following error message: Unrecognized path The process returned no content. We have since tried to downgrade the site back to V2.7.2 (fresh install and then copy over the existing database), but I still get the error. I assume this means a DB problem somewhere. Is there anything version specific stored in the DB that might need to be 'rolled back'?
  16. Yes, I have noticed that renderPager() is giving more pages than needed. Before I look at that, there is a strange reordering happening. Take this pair of selectors: $notes = $paginator(array( "template=horse-note, parent.h_type=2, h_notes_comments.count>0, h_notes_comments.$session->unread_by>0, sort=-h_notes_last_comment", "template=horse-note, parent.h_type=2, $session->unread_by>0, sort=-h_notes_last_comment" ), $pageNum, $limit); One of the pages from the second selector is appearing first in the list. It's definitely coming from that selector, because if I remove that from the array, that page is no longer returned. All other pages seem to be in the correct order. I've also noticed that on page 1, where I am echoing out count($notes), this is returning 96 even though $limit is 100. It's fine on all subsequent pages though.
  17. In reference to http://processwire.com/api/fieldtypes/repeaters/ is it possible to say 'where all repeater items' rather than 'where at least one repeater item' inside your selector? What I have is a repeater with a checkbox. I want to find pages where all repeater items on the page are checked or unchecked. If I do this: $pages->find("my_repeater.my_checkbox>1"); I get pages where at least one repeater item has the checkbox ticked, but what I want is pages where the checkbox is ticked in all of the repeaters.
  18. Just stripping this back to basics so that I can prevent duplicates in my selectors and have noticed that the order is being controlled by the sort that I have in the selectors, rather than the order that the selectors are put into the $paginator function. That probably makes no sense, so I'll try to illustrate. My paginator function looks like this: $notes = $paginator(array( "template=horse-note, h_notes_comments.$session->unread_by>0, sort=-h_notes_last_comment", "template=horse-note, $session->unread_by>0, sort=-h_notes_last_comment" ), $pageNum, $limit); h_notes_comments is a repeater with a few text fields and some checkboxes. So what I should get is: pages with 1 or more of the h_notes_comments repeaters containing a checked checkbox, sorted by the h_notes_last_comment datetime field other pages without a checked checkbox inside the h_notes_comments repeater (or no repeater items at all), sorted by the h_notes_last_comment datetime field But what's happening is the h_notes_last_comment field is taking precedence, so pages found with the second selector are appearing before pages found with the first, if the h_notes_last_comment happens to be more recent. Is that the expected behaviour or are we doing something wrong in our selectors? As an aside, am i right in thinking that when we're doing h_notes_comments.$session->unread_by>0 that will match any page that has at least one of the h_notes_last_comments repeaters with that checkbox checked? So even if there are 8 repeater items on a page, and 7 of them don't have the checkbox checked, it will still be returned?
  19. Actually, might be able to do it by being more specific in our current selectors. Will give that a go first.
  20. Is the best way to do this using a id!=$alreadyselectedelements? How would that work with a selector array?
  21. Would it be best if we try to make sure there are no duplicates in the selectors inside our $paginator function, and then we can use the regular PagesPaginator?
  22. Hi LK, we appear to have an issue with where the results are starting from on a particular page. For example, we're getting items on page 2 that have already been shown on page 1. Could this be something to do with the 'no duplicates' functionality that is somehow affecting start and end points?
  • Create New...