Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by wbmnfktr

  1. I know... closing issues and tickets comes straight after writing documentation. ? Some things just have to evolve and need to be established. Doing a clean-up once a week doesn't hurt. Ok first due to so many open issues but later on it gets easier.
  2. Sure... but it wouldn't help resolving those issues. Someone doesn't close an issue just because x amount of time has passed. Issues were opened for a reason. Therefore they should be closed for a reason, too.
  3. There are two things coming up my mind to get this done: FormBuilder + some hooks for checking and saving responses something similar like the Social Impact Award tool @bernhard built in the past
  4. I have had a similar problem while using Googlemail / G-Suite as outgoing and incoming addresses. Try as outgoing something like @yahoo.com and as recipient something like @gmx.net. You don't have to use those freemailers but you get the idea. Two totally separated servers and domains. Another thing could be a thing in cPanel powered hostings. Those sometimes have kind of a hiccup with who is actually the mail server for that domain.
  5. As I understand it, this is simply a matter of a user 2FA off for some account, then turning it back on, so they can establish a new secret/QR code. This is exact what the client is asking for. So it seems to be a perfect fit for them. This is definitely part of the plan. Though with the 2FA methods I've been working with, we can't enable it for anyone that hasn't set it up themselves. Maybe with Netcarver's PPP module when using email, it could work. Or maybe it would work with SMS when you've already got the user's mobile phone number stored. I guess they want kind of a soft force to motivate the editors to use 2FA. In this case they might actually prefer the e-mail way as the users/editors use their corporate e-mail addresses. It needs to know the user name in order to be able to look up the user-specific secret for the codes. Technically it doesn't need the password. But 2FA without a password is no longer two-factor, and would have its own security problems, which might be even worse than not having 2FA in the first place. If someone gets a hold of your device, and needs no password for your account, then they essentially have access to your account. Whereas, the intention with 2FA is that both your password AND your device are necessary. It's that combination of factors that makes it secure.  I can totally agree with that. I personally think that the 2FA could be a perfect thing to remove the password but keepign username of course (in this case) - the password is so often a problem. I know that removing the password makes 2FA kind of weak but replacing the password with a one-time-token could although be a nice option for those who don't play nice with passwords. ? We will see and I will try 2FA with some of my clients.
  6. Instead of assuming clients won't need or want this kind of feature I asked some of my clients today already and some of those who have more than 1 or 2 editors are welcoming such a feature. There are concerns but those shouldn't be the problem as I think that Ryan and therefore ProcessWire will take care of those things. The concerns were: the possibility of a reset for already saved tokens (I don't know how and if this will work with the Google app) the possibility to reset passwords and disabling 2FA for a user the possibility to have exact one user to maintain those settings the possibility to enable/disable it site-wide with a config-entry One client (a one-man business) asked if it's possible to remove username/password and just use this kind of token to login. I personally would use this on my personal sites but won't use it on client sites, as this part could end in an extra amount of work for me.
  7. I just ran into an issue using the Fixed Overlay at Top of Page placement option. The overlay was showing even after giving/denying consent. A look into your CSS showed that there is no real definition of hiding that banner. I added a few lines at the end of the CSS file and everything works as expected now - with the fixed at the top option. .pwcmb { display: none; visibility: hidden; } .pwcmb.js-show { display: block; visibility: visible; }
  8. Ok... so this is my workflow: At first I add all my necessary JS files into the <head> of my template. <script defer src="/site/templates/scripts/vendor/jquery-3.3.1.js"></script> <script defer src="/site/templates/scripts/plugins/plugin-a.js"></script> <script defer src="/site/templates/scripts/plugins/plugin-b.js"></script> <script defer src="/site/templates/scripts/plugins/typekit.js"></script> <script defer src="/site/templates/scripts/plugins/tracking.js"></script> This includes jQuery, all plugins I need for that project and sometimes tracking and Typekit. To make things go faster I add the defer attribute to my calls and let do ProCache all the minify stuff which ends in a single-file request like this: <script defer src=/site/assets/pwpc/pwpc-[RANDOMSTRING].js></script> With your module enabled things break right now. Your script tag is without defer and will be placed at the bottom of the template - therefore it ends in a separate file and won't work as expected. I changed the module code right now and added the defer attribute and placed everything at the end of my template. With the option to disable auto-injection I could easily keep my workflow, update most of my projects with ease and everything works and loads fast.
  9. First of all: this module plays really nice with my current ProcessWire instances - and will replace my previous CookieConsent setup. But there is one thing that came up while playing with the module. The option to disable auto-injection of the module's CSS and JS files. Is this kind of feature planned or already somewhere hidden in the code?
  10. There could be one but... I don't know where. Didn't you ( @Guy Verville ) did something similar with your skiing(?) project?
  11. Interesting to see this: https://www.1and1.com/digitalguide/fileadmin/DigitalGuide/Screenshots_2018/processwire-seitenbaum-beispiel.jpg A german file name. ? And it's not the only file with a hint of german. Here we go... https://hosting.1und1.de/digitalguide/hosting/cms/processwire/ (same as above but in german) https://hosting.1und1.de/cloud-app-center/process-wire-download#apps (some other news)
  12. As far as I know you have to go this way. You could take just that $data ['TypeDeMembre '] column on first run and create all non-existing pages and afterwards you import as usual.
  13. Is it me or does the site and those screenshots look a little off? Besides that the article is really nice for a post on a hosting company blog. Quite in-depth with some really nice examples and things readers might be interested in. One thing caught my attention:
  14. I think your module fork should be on its own - just to minimize the risk to break a site. I don't know if it's possible to check if Nicos version is installed and therefore your version can't get installed. Or similar. If an upgrade() method is easy to do I'll be fine with it, too. ? Regarding community help... count me in as tester (at least as this). As we talk about testing, where is the best place to report issues? Github? Here?
  15. I can confirm that children.count returns all children - including unpublished and hidden ones. At least in my current project. Maybe it's similar to this: A work-around... not yet. You could try to find out if those child pages are viewable or something like this.
  16. # ----------------------------------------------------------------------------------------------- # 9. If you only want to allow HTTPS, uncomment the RewriteCond and RewriteRule lines below. # ----------------------------------------------------------------------------------------------- # RewriteCond %{HTTPS} off # RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] This part of the .htaccess works absolutely perfect - at least for all my ProcessWire powered sites which are a few now. Too many redirects is most likely a caching problem in your browser. Try it in a private/incognito window again. If this doesn't change the wrong behaviour try a Google search for similar problems with your hosting company. Some hosting companies do weird things sometimes. If you are using any kind of CDN (for example: Cloudflare) disable caching, routing or forcing https and enable debug/developer mode.
  17. The second foreach($speaker as $thumb) looks like there is something missing. I'd expect something like this there: <?php foreach($speaker->photo as $thumb) { // } And I would remove the very first part of code. <?php foreach($page->speaker as $speaker): $thumb = $speaker->photo->width(310); endforeach;
  18. For those who want to know more or want dig deeper into this JSON-LD/Rich data/schema.org topic - there is a really good write-up about all this with examples and recommendations as well: https://www.link-assistant.com/news/structured-data-for-seo.html
  19. Thank you, @tooth-paste. The PagefieldPairs module keeps the mapping between tutor:instrument, tutor:ensemble and vice versa in sync. So editors can either add tutors to an instrument/ensemble or add instruments/ensembles to a tutor. This detail seems small at first but it's crucial. Keeping this in sync makes changes much easier and reduces the risk to miss a tutor/instrument/ensemble somewhere and it doesn't matter where this detail gets changed.
  20. I could give it a try next week. Never used this or the version from Nico so we will see. Anything special I should look for?
  21. Thank you very much @cstevensjr. I'll forward your compliment to the designer.
  22. I'm proud to share this newly released custom-made website with you. Musikschule Neumünster https://www.musikschule-neumuenster.de/ Design details The design was built from ground up to give every aspect and every detail of the website its very own unique look. We faced the demand to create a visual experience that is up to date but kind of classic at the same time. A fact you can't describe but you will feel and see it when visiting the website. ? Technical details From top to bottom every detail can be managed in the backend - all instruments, tutors, events, and content pages. In order to make life easier some things are automated (for example: archiving older events or managing the relationship between tutor and instrument). Modules and time-savers ProCache Croppable Image 3 PagefieldPairs MarkupSitemap Hanna Code Jumplinks I hope you enjoy the result as much as we* do. * A little side note to reduce confusion: I'm partner and the developer of Muskaat (design and development bureau based in Neumünster, Germany).
  23. Disclaimer: I'm not against beautiful crafted and designed themes for ProcessWire. Nor am I against an easy entry into the ProcessWire world. Users... who are these users? Is it the company owner that is in need of a one-pager/website to present his new start-up or product? Is it the company that wants to save money and wants to create something on their own? Is it the entrepreneur that needs a langing page builder to collect e-mail addresses in order to sell info products? Is it the photographer / film maker / author / designer that wants to share his/her work? Is it the young and new web developer that wants to know what he could achieve with ProcessWire? Is it the guy that is curious about all kinds of CMSs out there? Is it the long time full stack developer that needs a solid foundation for his ideas and projects? Is it the agency that wants to be flexible in order to create stunning web sites with ease? Is it the WP user you want to encourage to switch the CMS? Is it the user that wants everything just by clicking around? I think ProcessWire is right from the start way more for developers than end-users. Which is a good thing in my opinion. And for those developers we can find some really nice starting points already. Maybe there will be a company someday that wants to close that end-user-gap and pays a developer and designer full-time to create stunning themes/profiles.
  • Create New...