Jump to content

Guy Incognito

  • Posts

  • Joined

  • Last visited

Profile Information

  • Location
    Kent, UK

Recent Profile Visitors

1,004 profile views

Guy Incognito's Achievements

Sr. Member

Sr. Member (5/6)



  1. @Robin S Thanks for this - really useful and puts my fears to rest. @gornycreative Thanks also for sharing info. I can't see I'll need anything like 50 of templates (famous last words 🤣) and TBH what I'm building is should have pretty low demands in terms of resources anyway - for the end user its more of a set-and-forget scenario. So demands should only increase with a significant number of users... but hey that's a good problem to have eh!
  2. Thanks for the detailed response. This basically summarises exactly the choice in front of me... I'm pretty sure I can dramatically reduce the amount of code by using a new template for every view or configurable feature of my app and feeding it into my _main.php. But I'm not sure if creating loads of templates (I would estimate this will end up being around 10 to create the product MVP) is bad idea or particularly inefficient approach in terms of performance and database?
  3. Hi all, Just embarking on a new web app project that I'm planning to use Markup Regions for. I've experimented with Markup regions before and am happy with the syntax and coding but wondering on the overall approach. The project will have a simple user dashboard with various typical web app views for account management, settings etc etc... I'm wondering am I better having one 'dashboard.php' template with PHP routing/conditions/includes to determine the content each page feeds into the _main.php file. Or is it better to have a seperate template for every page in my dashboard? I could end up with quite a lot of templates to realise my final functionality this way and pretty sure I've seen posts that PW is intended to have a vast number of templates. However routing all the views with new code could also get quite complex quite quickly too. Wondering what thoughts/experiences others have had - I hope this questions makes some sense!
  4. Hi @Macrura thanks for this - module looks fantastic and not sure how I managed to pass it by until now! One quick question - can you export settings to other sites? One big advantage of coding modules is obviously the portability.
  5. After reading up further I see I should have built my own UI on a Process page rather than using a module config screen to achieve this. 🙈 I never realised there was such a disconnect between using module config screens and the UI of Process modules. It would be awesome if there was a way to optionally pull module config screen into the Process page view as most of the simple modules I need to make for sites don't need more than what the config screen provides other than granting permissions to non super users. Don't know if anyone has come up against this or created a work-around?
  6. Hi all, Title says it all really. Have created a little site-specific module and want to give a non-superuser access to edit the module settings. What's the best way to go about this. I've added a nav item to the the setup menu using the getModuleInfo() array in the module file but this just returns a 'The process returned no content.' message. Should I be redirecting this the config screen or rendering the config screen into this page somehow? Thanks, J Incidentally the icon I choose for the module isn't rendering - do I just choose the name from FontAwesome for this?
  7. Sorry to necro an old post, but I was searching for a pointer on a PW .htaccess config ( @horst's post above super useful btw thanks). @teppo your reply got me thinking - wouldn't it therefore be useful/better if PW were to auto redirect any invalid host requests back to the first domain in the httpHosts array rather than successfully loading the page for the reasons you've outlined - or maybe it should throw an error? I get that it picks it up in debug mode or when you're logged into dashboard, but maybe not ever showing someone a page using an unlisted host on the frontend would be safer?
  8. Hijacking my own thread here lol... but now I think about it more it would be cool to allow images in the comments but looks likes this might be more complex. Might need to switch to an API/repeater based solution and use a CKeditor text field... unless anyone else has a solution/ideas around the comments field?
  9. Sweet, thanks, works perfectly! I knew there had to be a non-destructive preset in there. You just saved me having to pour through the module classes 😃
  10. I've just realised the default form already renders with the current logged in user name and email... so I guess my revised question is can we disable these fields rather than just hide them?
  11. I'm thinking of using the comments fieldtype for a very basic support ticket system for a project. I guess I can just hide the fields and populate them using JS or something - I'm just wondering if it's possible out the box to disable the name/email fields and use the current logged in users as the comment poster instead without hacking at it. 😃
  12. You know what - I can't even remember now if/how I resolved this! 🙈. But the answers from @d'Hinnisdaël and @adrian are cool for future reference as I had never even noticed you could use regex in the allowed URL segments so that's great to know.
  13. Hi all, is it possible to setup an inline frontend edit on a FieldsetPage field? It works with <edit> tags, but can't make it work inline. Have tried the following to no avail. (Header is the FieldsetPage). TIA. <?=$page->edit('header.simple_text3');?> <?=$page->header->edit('simple_text3');?>
  14. I think I can also implement pseudo enforcement by not dishing out roles to users until they opt into the suggest 2FA. 😃
  15. No probs thanks for your help. This is the first time using PW 2FA on a client project and just making sure I get my facts straight before looking like a fool 🤣
  • Create New...