Jump to content

Guy Incognito

Members
  • Content Count

    125
  • Joined

  • Last visited

Community Reputation

52 Excellent

About Guy Incognito

  • Rank
    Sr. Member

Profile Information

  • Location
    Kent, UK

Recent Profile Visitors

958 profile views
  1. 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?
  2. 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?
  3. 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 πŸ˜ƒ
  4. 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?
  5. 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. πŸ˜ƒ
  6. 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.
  7. 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');?>
  8. I think I can also implement pseudo enforcement by not dishing out roles to users until they opt into the suggest 2FA. πŸ˜ƒ
  9. 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 🀣
  10. Ok I was only on latest master. Have updated and now have the options screen in that blog post. But unless I'm thick I still can't figure out how to force TOTP? I see you can 'strongly suggest'. I see Ryan wrote Has it just not happened yet?
  11. What's the best process for adding another user with TfaTotp 2FA? Just using it for the first time. Should I supply them with them with the secret when I first create their account? Seems like a security risk? Otherwise how do I create a 2FA user and let them login for the first time?
  12. I think you can still store HTML in Editor.js. So I wonder if it might be feasible to add a new editor field alongside CKeditor ones then use a hook to copy the content over on page save... or something like that anyway!... I'll be looking to address the same issue if this module works out.
  13. Ok this is awesome then - best of both worlds! One other feature request that will make this a killer module IMO... that it should work with Front End editing.
  14. This looks cool. One bit of feedback (and this may just be my opinion rather than a general consensus) but I really dislike how the WP Gutenberg treats every paragraph as a block. To me it makes no sense to be able to rearrange text at the paragraph level. To me a single block of text with multiple paragraphs within it seems more sensible. Although looking at the example JSON doc on the Editor JS homepage it looks like it treats every para as an element and for ease of maintenance I guess you won't won't want to stray too far the default behaviour.
  15. Amazing thank you! Works like a charm. πŸ˜ƒ
Γ—
Γ—
  • Create New...