ren

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

12 Good

1 Follower

About ren

  • Rank
    Jr. Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Patch #5463406 solves both issues Thanks Ryan
  2. Thanks matjazp, I've added to the issue report.
  3. Opened an issue on github. Thanks
  4. Ah great, thanks Soma! Will do.
  5. Will do. With no other confirmed replications yet, I'm wondering if it's a server config issue, although I've no idea what that may be. Thanks Edit: just seen Soma has replicated.
  6. It's replicated on two servers, one running PHP 5 and the other PHP 7. It's also replicated in Chrome on a Windows machine, so it doesn't seem to be a Linux browser issue. The only other thing to try is a different internet connection. Thanks
  7. Hi folks, wondering if anyone's encountered this problem before?... 1) Trash a page from the page tree (screenshot1.png) 2) The page is removed from the page list (screenshot2.png) 3) Close the page tree (screenshot3.png) 4) Open the page tree, the page reappears (screenshot4.png) If I do a browser refresh the page permanently disappears, so it seems the problem is with the AJAX admin. Replicated with: Clean installations of ProcessWire v 3.0.98, 3.0.96 and 3.0.34 With and without AdminKitUI No additional modules Basic profile Linux Chrome 67.0.3396.99 Linux Firefox 61.0.1 PHP 5 PHP 7 Restrictive and fully permissive file permissions Sometimes it takes adding and deleting a few pages for the problem to appear. There are no console errors. Thanks
  8. ren

    Clarification: by 'setup costs' I mean any initial costs associated with getting to grips with things, i.e. the codebase, server and deployment strategy etc.
  9. ren

    Hi Victor, Just PM'd you. Thanks
  10. ren

    Hi folks, My department is planning to move up to five of our employer's websites in-house and onto ProcessWire from a CMS which has not seen much development in the last few years. They're B2B magazine websites and we feel that ProcessWire would be a great fit. But there are concerns over support. I'm the only server side programmer, so what would happen were I to leave or be hit by the proverbial bus? So we're looking for some kind of insurance. Thinking along the lines of a support contract, covering maybe 2 hours of support time per month. With a commitment to become more involved should the need arise, so providing more support if needed to someone who takes over my role, or in the 'bus' type emergency, be willing to take over full support duties for a limited period of time. The 2 or so hours would be used for providing advice if I were to really get stuck. But I'm happy using the forums for help, and I've built a prototype of one of the sites without huge difficulty (go ProcessWire!), so under normal circumstances they probably won't be used. The five sites are all quite large (the prototype site has 40 templates and 95 fields), consisting of news sections, a jobs section, a business directory, reader polls and social media integration. Some of the sites allow membership for the business directory, so companies can login and manage their listing and upload press releases, via a custom dashboard (implemented as a Process module). All code will be commented and held in a git repo. We're located in the UK. Email support would be sufficient I think. If you're interested, please PM me with a rough estimate of costs for: The ~ 2 hours per month standard support. Full 'emergency' support of all 5 websites. Any one-off setup costs. And/or suggest an alternative pricing structure / proposal. Again at this stage we're just looking for a rough idea of costs and who would be available, so ballpark figures would be fine If you could also provide a link to your website please. Please let me know if you would like any further information. Thanks
  11. Doh. Yes, that works Prefer this to matching urlSegment I think. Thanks!
  12. Hi @Robin S, Thanks, Tracy Debugger is looovely. I did as you said, and put db calls to log both cases (redirect and no redirect): // do not redirect if page matches: if($this->page->template != "admin" // any non-admin page || $this->page->is($this->redirectPage) // the dashboard page (prevent infinite loop) || $this->page->parent->is('/admin/login/') // various attempts to allow logging out || $this->wire("process") == 'ProcessLogin' || strpos($this->page->url, $this->wire('config')->urls->admin . 'login/logout') !== false ) { bd($this->page, 'no redirect page'); return; } bd($this->page, 'redirect page'); When I tried to logout it logged both cases, with 'redirect page' first: data protected => array (3) title => "Login" (5) process => "ProcessLogin" (12) urlSegment => "logout" (6) ... for some reason 'ProcessLogin' is sailing through the conditional. Followed by 'no redirect page': data protected => array (2) title => "Dashboard" (9) process => "ProcessDashboard" (16) The first log gave me the idea to match the urlSegment, which works a charm! So if it's of any use to anyone, the working code is: if($this->page->template != "admin" || $this->page->is($this->redirectPage) || $this->input->urlSegment1 == 'logout') { return; } // find roles set in module configuration and create array $roles = explode(',', $this->userRoles); // for each user in module config check to see if current user foreach ($roles as $key => $val) { // get a role from the roles array $roles[$key] = trim($roles[$key]); // if current user found with role then redirect if($this->user->hasRole($roles[$key])){ // redirect session to page stored in config $this->session->redirect($this->redirectPage); // code should never get here but this is a simple fallback break; } } Thanks Robin, you've been a great help, and I'm sure to be using Tracy Debugger again
  13. Hi all, I'm creating a website for a magazine publisher. This will include a supplier section with press releases attached to company profiles. The idea is that companies can register and manage their profile and press releases (CRUD) via a dashboard. The dashboard is a Process module. Ben Byford's RedirectAdminPages module is being used to lock out the rest of the backend, with a few modifications. The following code should redirect every admin page to the dashboard page but still allowing logging out. However logging out just redirects to the dashboard page: // do not redirect if page matches: if($this->page->template != "admin" // any non-admin page || $this->page->is($this->redirectPage) // the dashboard page (prevent infinite loop) || $this->page->parent->is('/admin/login/') // various attempts to allow logging out || $this->wire("process") == 'ProcessLogin' || strpos($this->page->url, $this->wire('config')->urls->admin . 'login/logout') !== false ) { return; } // find roles set in module configuration and create array $roles = explode(',', $this->userRoles); // for each user in module config check to see if current user foreach ($roles as $key => $val) { // get a role from the roles array $roles[$key] = trim($roles[$key]); // if current user found with role then redirect if($this->user->hasRole($roles[$key])){ // redirect session to page stored in config $this->session->redirect($this->redirectPage); // code should never get here but this is a simple fallback break; } } } } I'm surprised that this URL matching doesn't work: || strpos($this->page->url, $this->wire('config')->urls->admin . 'login/logout') !== false Because this does work for allowing page edit: || strpos($this->page->url, $this->wire('config')->urls->admin . 'page/edit') !== false Any ideas? That issue aside, as a learning process I'm going to re-implement the dashboard as front-end pages. I guess that the advantage of using the ProcessWire back-end is most of the functionality is already there, you don't need to create forms and handle the processing, create / import css etc. So it'll be interesting to see how much of a difference this makes, and how much control each approach provides. I'd love to have some thoughts and feedback from those of you who've tried both methods? PS this will be my third website created with ProcessWire and it's already been a lot of fun, and as a CMS it 'just feels right', so a big thanks to Ryan and everyone who has contributed. Thanks