Jump to content

Pierre-Luc

Members
  • Posts

    291
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Pierre-Luc

  1. Haven't tried myself, but does it work when using field.title ? It is possible to do field->value and field->title, so maybe it could work.
  2. Looking nice! But I don't know about you guys, it seems like Bootstrap feels a bit old and somehow weird to use, especially with all the cool stuff out there now (the structure is so restrictive IMO). Personally, I've completely switched to Sass recently and been using these as starting points incredibly efficiently: - A customized reset - Susy — Grid/Layout framework (you HAVE to try this!) — http://susy.oddbird.net - Bourbon — Awesome mixin library — http://bourbon.io - Bitters — Unobtrusive, minimalistic and easily editable boilerplate starter styles — http://bitters.bourbon.io Hopefully the new Bootstrap components aren't too tied together.
  3. The 'name' field isn't translatable. Do you mean the title field?
  4. Use either $this->users->… or wire('users')->…
  5. As a sidenote though, simply defining the classes will not give the full picture, but a good part of it. Some methods that are added through hooks via modules like PagePermissions or LanguageSupport for the Page object won't be seen. I found this out lately while toying with Reflection classes trying to automate the Cheatsheet. If anyone has any idea how to make this work, I'd be a taker. So far it doesn't seem possible unless the class explicitly adds the methods in its header docblock, and that itself has its own shortcomings.
  6. I updated the install script. It is now interactive and prompts for which branch and which site profile you want to use. See it in action here: https://vid.me/gDwZ You can download the unified install script on GitHub. https://github.com/plauclair/pwscripts
  7. … and v.0.0.5 Changes : https://github.com/plauclair/PasswordReset/commit/cd1b8041906eaf31848e55a0973af6b2362a93ac
  8. Just pushed v.0.0.4 Fixes : https://github.com/plauclair/PasswordReset/commit/fa9cdcbea7425c8efc8eb316573df89870f2c802
  9. Thanks guys. @mr-fan it needs to be production ready this week so for sure it's going to be there pretty soon. @jacmaes yes currently there is a length check in the module properties. There will be a strength check at some point, but probably not at v.1.
  10. Alright! I haven't tested the URL so far in a lot of mail clients so was kinda wondering. ——— Just posted a new release. v.0.0.3 changes https://github.com/plauclair/PasswordReset/commit/95a61b91ccca276b6c9eef1b3884af0f98250c58
  11. @Macrura -- Did the url break in PW's reset module or mine? Also what messaging client (if any)?
  12. I really want to push the usability side of this one. If you've found other shortcomings of ForgotPassword that would like to be improved, let me know. We used to use ProcessForgotPassword too but it's not working that great for us.
  13. Nope, unfortunately I don't typically use ProCache on my projects. My understanding is that ProCache completely bypasses the typical rendering procedure, and this module hooks to Page::render so they might not be compatible. I would suggest contacting support and see if there's a way to hook into it, I'd be glad to implement this.
  14. I just published a pre-release of my new password reset module. It will enable identification from any field of your choice, and is fully translatable. Integration is just 2 lines of code, the first is calling the controller, the second is loading a script (no dependencies). You can download the code on GitHub at https://github.com/plauclair/PasswordReset. Also, have a look at the reset process in this video https://vid.me/eEVY. This exemple is not styled, but there should be all you need in there to style it. Comments and feature requests very welcome!
  15. It would depend if you want a page-based or site-wide solution.
  16. Another approach I've used in the past is to implement a simple language status handler. Basically I added fields to languages and had a bit of code that would display a page or not based on the status of a page translation. Mine was used to display a notice to users, but it could just as well be used to do redirects or throw 404s.
  17. I've been thinking about having a read-only field that could be used to display documentation that wouldn't normally be a good fit for the field description or notes.. Let's say at the top of a page or tab field group. Conceptually I think it might fit in a field, but since you'd probably need to have multiple ones on each template and based on context, maybe it'd need a different approach.. Has anyone implemented something like that or would have an idea how to implement something like this in a way that doesn't feel like a hack? Think it'd be useful too?
  18. This is **amazing**! Implementing Mandrill using the API was actually on my to-do. Can check that off.
  19. I am pleased to announce the full release of version 2.6.1 of the language pack. (Versioning now moving to match that of PW itself) I setup a new module info section in the modules repo. http://modules.processwire.com/modules/french-language-pack/ (might not be live as you read this) Also, the GitHub repo is moving to https://github.com/plauclair/pw-lang-fr/. Head over to the releases page for download https://github.com/plauclair/pw-lang-fr/releases. Enjoy!
  20. Let's hope all major browsers will add them to their secure lists! Has good potential
  21. It is certainly possible, I don't think it would be that big a deal. Note though that your usage would not be linear, would probably be something like a Gaussian curve so better measure peaks that way, and compound with days of the week. Storage is cheap so that's clearly not an issue, places like Digital Ocean provide you with good performance and you can upgrade/downgrade easily. I would start with a prototype of the site, and test using Apache JMeter, top and whatnot. Launch an instance, install your prototype and start stress tests watching if your site is more CPU, storage or memory bound, then adjust accordingly by tweaking your server and application settings, and throwing more hardware if need be. I am not an expert on infrastcture, but if I need it it's how I typically go at it. Hope it helps.
  22. ACF can sometimes feel like it gives WP superpower abilities, but under the hood it is a big, big hack. All fields stored in the database use the same table, most often serialized. This caused me big issues lately when doing a migration. Also, their API isn't that robust (case in point, I've been exchanging with ACF support lately, I'm finding lots of "should work, sorry"). To me robustness means things won't explode when approaching edge cases.. it's clearly not it.. especially if I pay for it. As has been said, every time you call a field with the_field(), a DB call is made. This obviously taxes your server's ressource, and the problem grows exponentially when the project you're on won't allow for caching. Managing content relationships in ACF is far from ideal either, if you ask me. All in all, it might kind of feel similar UI-wise, but the architecture is lacking, all due to the DB schema limitations in WP itself.
  23. Could one of you add me as a maintainer on the package page? Thanks!
×
×
  • Create New...