Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Macrura last won the day on December 26 2019

Macrura had the most liked content!

Community Reputation

3,067 Excellent


About Macrura

  • Rank
    Distinguished Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Westchester County, NY

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Maybe S3 doesn't support fopen (?), i use this for getting files from S3 (though the files are protected); https://css-tricks.com/snippets/php/generate-expiring-amazon-s3-link/
  2. This one is designed to work in the admin, so all of the settings, and how the javascript works is only going to work in the admin. But it's such a simple plugin, you could easily roll it into a formbuilder form.
  3. cool - thanks - did it and it worked. Sorry for the 'false alarm'...
  4. I started getting this error with the latest version: PHP Warning: in_array() expects parameter 2 to be array, string given in .../TracyDebugger/TracyDebugger.module.php:1078
  5. I think it is an important and valid question, discussion topic. One option is to let the admin set, within the module config, which template(s) to be used for X purpose, which page root, and so on. (This is how it is done in various modules). Another option is to include JSON files for field, template and page creation with the module and let the admin install them. Or have the option to install the fields, templates and pages, or not (using a checkbox in mod config), like in the AdminHelp module. This means that anyone who downloads the module will be able to make their own decision about if they want to install all of those things.
  6. Hi @Sevarf2 - i haven't tested the mod, so was hesitant to commit the change, but i should be able to do it this week. Are you having the same issue as Martijn?
  7. Cool - i was building this, but i got stuck on the Unsplah api which was telling me they didn't like downloads and wanted to only allow usage that would use the source image from them, and this wouldn't work with an images inputfield, or imagesizer engine, or any other image manipulation like srcsets etc; So i gave up... Looks like somehow you solved all of this, so thanks! Does this use a fixed api key, or will that api key need to be configurable at some point?
  8. @Martijn Geerts - many thanks for taking the time to make the fix here! I will implement is and do some tests and update the module soon.
  9. The Processwire admin does not support webp. Webp is an output format, but not a valid source format for images. The Imagesizer engine of Processwire is not capable of resizing webp images, therefore when you save, it cannot generate the thumbnail, and that's why you get the error. You'll need to delete that webp image and upload a jpg instead.
  10. @MarkE cool, i should be able to work on this soon, definitely in June, and will make some improvements according to your suggestions. If you want to post the mods here i can look at them.
  11. hey thanks - yeah, as you can see from the way the module is setup, it doesn't force you to use the installable fields, so in theory you could just setup any template you want to use for help docs, and any family relations required; and then you just select those in the module config. The default, out-of-the-box behavior is to be only 1 level. As far as i can see in the process module, if any help doc has children, they do get rendered; are you saying you need to go down a 3rd level?
  12. for (1) I'll need to call getFormatted which is what we do in ProcessDocumentation: $docBody = $docPage->getFormatted($this->body_field); Not sure what #2 is, in terms of a pop-out button; I also see now that this module has a hardcoded fieldname for the help doc body, so that needs to become configurable, as it is in ProcessDocumentation.. My original version did recurse down one level to child pages of the help pages...
  13. @MarkE - should be ok to use this, and i wouldn't say that this module is no longer supported, if there were to be a bug report, pull request, or feature request, this module is still live and functioning, and may receive future updates, especially with regards to permissions and flexibility of use. But in the meantime as mentioned above, ProcessDocumentation is a bit of a larger scale module and was designed so that it would be possible to have unlimited documentation pages, all accessible from the top admin menu, as well as the ability to download the PDF; In conjunction with the ContextHelpTemplate, you can achieve the same functionality ad Admin Help, so that you have a tab for help right on the page editor, which can open in the panel (instead of wiretab) if preferred. So in that sense, ProcessDocumentation is an evolution of this module, but doesn't necessarily replace it for simpler use cases. It is also possible that this module, AdminHelp could use updates to support pw panel, or other features of ProcessDocumentation.
  • Create New...