monchu

Members
  • Content count

    55
  • Joined

  • Last visited

Community Reputation

25 Excellent

About monchu

  • Rank
    Distinguished Member

Profile Information

  • Gender
    Not Telling
  • Location
    Melbourne

Recent Profile Visitors

1,583 profile views
  1. If you're looking for error don't change or remove any installed module. Activate $config->debug = true; in config.php to see the errors if any, and study the logs from Log tab, from the date that the users found that error, and check what is the latest date for new module/s if any at least from there hopefully you have the starting point to trace the problem
  2. You can sort them from your home template, under Family tab
  3. Because you're using option A. Try other option (B,C) which is not using iframe
  4. pw give us the flexibility to customise the admin part. for backend part to avoid the admin's user confused about the 'Pages' concept, I just simply rename the Pages label into Dashboard.
  5. I used to work on localhost, but now since the Internet connection is much more reliable and fast, I do all development in web server directly. Localhost only for a backup purpose. There are a lot of advantages doing that way; I can work from anywhere and at least make sure that the server configuration meets the client's server configuration.
  6. wow you should take a break ... glad to hear you're ok, watch on tv Irma was really bad
  7. try to add "template=blog-entry, include=all" to see all pages
  8. I suggest not to touch the admin template. You can create a new role with permissions that you would like to provide for some users. Edit the template that you want to assign the new role, click the Access tab. Click Yes, under 'do you want to manage view and edit access for pages using this template?'. You also can do the same in field level, by editing each field that you want to apply for that new role. However, doing this way remember to put it in your documentation otherwise it will become a little bit complicated for maintenance in the future.
  9. Read this as starting point:
  10. I'm not too sure it is doable or not, just an idea, you can read about multi sites here: https://processwire.com/api/modules/multi-site-support/
  11. yes it is doable however, you don't have to create a file anytime you create a new template in admin. you create a template file if you want to 'view' the page using that template
  12. You don't have to edit .htaccess file, just edit your config.php at $config->https = true;
  13. Try to clean compiled files and refresh first if still got the error try to uninstall any 3rd party modules
  14. I still prefer the Page Reference because the flexibility to get more values from the page itself
  15. On each process page I usually added an option field for i.e named it as 'toggles' to restrict user's view access. So in wire('pages')->find('template=your_template, toggles=your_user_roles'), you can restrict the user's access. At the moment I'm developing the process for thousands of property addresses and contractors, the queries are quite fast. It always relies on how you design the process itself. In term of security, at least until today pw doesn't have any security issue. As long as you're sure to manage your front-end script carefully I think pw core is really good in the security part.