Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


eelkenet last won the day on October 16 2019

eelkenet had the most liked content!

Profile Information

  • Gender
    Not Telling
  • Location

Recent Profile Visitors

2,737 profile views

eelkenet's Achievements

Sr. Member

Sr. Member (5/6)




Community Answers

  1. Hi @Pete, could the minimum character count for the search on the forum please be reduced to 3 instead of (what I suspect) 4? It's really impractical to not be able to search for words like 'api', or 'get', while you know for sure that there must be many results for those words.
  2. Note: if you want to force a download but don't want to change the downloaded filename, you should omit the value of the download attribute like so: <a href="yourfile.pdf" download>link</a>
  3. Hi @joshua, that works - sort of. When setting the user language inside a template we still only get the default language, as your hook gets called earlier. However, what does work is hooking into the same Page::render method with a lower priority number, so our code gets an earlier execution. Great! In ready.php we now have: <?php namespace ProcessWire; // Hook into Page::render, just before PrivacyWire's hook // Which uses the default priority of 100 wire()->addHookBefore('Page::render', function (HookEvent $evt) { // Only apply to front-end pages $page = $evt->object; if ( $page->template == 'admin' || // exclude admin pages $page->template == 'form-builder' // exclude from form-builder iframe ) { return; } $user = wire()->user; $languages = wire()->languages; // Get and sanitize the ?lang= get param $lang = strtolower(wire()->input->get("lang", "text")); // Set appropriate language if ($lang === "en") { $user->language = $languages->get("default"); } else { $user->language = $languages->get("de"); } }, ['priority' => 99]);
  4. Hi, I've got a site that uses multi-language URLs based on a query-param, ie. https://example.com/some/page?lang=de. The site exists of a Vue.js app on top of a very basic HTML skeleton generated by PW, and we don't use the LanguageSupportPageNames module at all (so no example.com/de & example.com/en ). In order to set the initial skeleton HTML (such as page title etc), which gets rendered before the Vue app has booted, I set my $user->language based on the $input->get('lang') value. After the Vue app has booted, it takes over control and loads the remaining data in the appropriate language through a multilingual API endpoint. Next to the Vue app, we also use PrivacyWire. However, due to the way PrivacyWire has been built, it looks at the $users language BEFORE any of this takes place (in its ready() function). As a result, I can't get the correct language content inside the PrivacyWire popups, it always shows the default language content instead. So probably I need to hook into the getPrivacyWireConfigObject method, and overrule the PrivacyWire::lang variable with the language that I get from my $input->get('lang')? Or would there be another, easier approach? Any pointers would be most welcome! Thanks.
  5. Today I again bumped into an issue I had last year with creating WebP images: Enabling WebP on another project by setting imageSizerOptions' webpAdd to true immediately resulted in the same behaviour as I had last year: the server simply keeps on creating new variations of images, while they already exist. WebP images are created correctly by the way. Seems to be a bug, can anybody else confirm? I am using PW Master (3.0.165) on MAMP Pro (MacOS 11.2, PHP 7.4.2)
  6. Great addition @ryan! Quick question: will ProCache be able to cache (the result from) these URL hooks?
  7. Hi @Sebi, I ran into a bug: Currently the Router::handleError() function incorrectly reports HTTP 500 errors that result from methods that should have remained silent, because they are called with the error control operator '@'. As the PHP documentation on error control operators puts it: I bumped into this while working on a project with some semi-broken images, where the APP API module kept throwing 500's from PW's ImageInspector class. Exif issues can be rather difficult to handle sometimes.. The solution is simple: just add a check error_reporting() before the handleError method, for instance public static function handleError($errNo, $errStr, $errFile, $errLine) { if (error_reporting()) { $return = new \StdClass(); $return->error = 'Internal Server Error'; $return->devmessage = [ 'message' => $errStr, 'location' => $errFile, 'line' => $errLine ]; self::displayOrLogError($return, 500); } }
  8. Something I'm missing in the new Modules page are the requirements for installing, such as PW version and other required modules.
  9. For what it is worth, I use this intermediate solution to use ProCache in combination with the RestAPI module: https://processwire.com/talk/topic/20006-module-restapi/?do=findComment&comment=186881. Which gives me: 1. site.url/rest-api => live data 2. site.url/api => served by ProCache Of course this would only be useful for (static) pages that don't require any authentication or whatsoever.
  10. Removing $config->imageSizerOptions from config.php solved the issue, which lead me to test its settings. Turns out specifically setting webpAdd to false fixed it!
  11. Thank you for you insightful reply @Robin S! I've decided to step away from the FieldstePage method, and just creating simple fields with longer names. Takes some time to copy over all existing data, but it makes it all a lot simpler to deal with.
  12. Hi, I'm working on a process module which hooks after ProcessPageEdit::buildForm. // Inside the module's init() method: wire()->addHookAfter('ProcessPageEdit::buildForm', $this, 'renderFieldsAccordingToStop'); Using a lot of variables, the script decides then which fields to render and which ones to hide. It also dynamically sets the 'required' flag to only the visible fields, making sure the proper warnings get shown but only when these fields are visible. It's all quite straight-forward, when it comes to the regular InputFields: /** * Render the form, and hide all the fields that are not part of the currently active step * Note: These fields are hidden with the css class "hideme", as hiding them with collapse logic gave issues in combination with the dynamic requirements * * @param mixed $event * @return void */ public function renderFieldsAccordingToStop(HookEvent $event) { $return = $event->return; // Get the page that is currently being loaded $page = $event->object->getPage(); $input = wire("input"); $form = $event->arguments(0); $step = $this->getProgress($page); // Add some class to hide field when needed $html = "<style>.hideme{display: none;}</style>"; $form->prependMarkup($html); // Get all the fields inside the form $inputfields = $form->getAll()->not("id=submit_save"); // Set all inputfields according to step foreach ($inputfields as $key => $inputfield) { // Run some logic to decide if the field should be invisible (using CSS to hide, as the inputfield->collapse gave issues) if ( ... ) { $inputfield->wrapClass("hideme"); } // Else make sure to require it. else { $inputfield->required(true); } } } This works fine for most field. However, this does not work for fields that are embedded inside a FieldsetPage. The FieldsetPage itself does get set to required correctly, but the fields inside are not, and as a result a user can now skip these fields while I wish them to be required (but only when visible). I've tried a bunch of different techniques, but I can't get the fields inside of the FieldsetPage to become required. In fact, I can't figure out how to address these from inside the hook at all. The furthest I've gotten is access the names of the fields inside this FieldsetPage: $field = $inputfield->hasField; if ($field->type == "FieldtypeFieldsetPage") { // Get the inner fields foreach ($field->repeaterFields as $f) { $repeaterFieldName = wire()->fields->get($f); $subfieldName = "{$field}->{$repeaterFieldName}"; self::log("The current field inside the FieldsetPage is: $subfieldName"); //--> logs "myfieldset->myfield" } } But how on earth do I use that information to update the settings of the Inputfield for myfieldset->myfield? Especially how do I set the required property, but also in a more of a general question. (In addition, I also tried hooking into the Inputfield::render but to no avail. ) Thanks in advance!
  13. Thanks for your replies guys! Here is the output when outputting all the debugInfo inside the JSON. What seems interesting to me is that every variation seems to refer to itself as the original? That could be something maybe? The weird thing is, I use this exact same technique on a lot of sites and never had this issue. So I would guess it's some configuration setting somewhere that might be off.
  14. Hey everyone, I have a weird one. Somehow my image variations keep being regenerated, instead of served directly. The variations that are requested are in fact already present, but still get overwritten by (identical!) files upon page load, making everything rather tedious and slow. Permissions from config.php are set to default: <?php $config->chmodDir = '0755'; // permission for directories created by ProcessWire $config->chmodFile = '0644'; // permission for files created by ProcessWire ?> Files before loading the page, notice the time of the requested variations is 14:14: Same folder after loading the page just now (14:24): Some background: I'm currently implementing my standard technique (using the RestApi module to output json) on an older but updated site (3.0.148), running on PHP 7.2.22 (MAMP Pro), while still in (local) development. My image parser function is pretty basic: <?php public static function parseImage(PageImage $image) { $settings = [ 'sharpening' => 'medium', 'cropping' => false, "quality" => 95 ]; $sizes = [ "L" => [ "width" => 1500, "height" => 1500, "settings" => $settings, ], "M" => [ "width" => 750, "height" => 750, "settings" => $settings, ], "S" => [ "width" => 320, "height" => 320, "settings" => $settings, ], ]; // get orientation if ($image->width > $image->height) { $orientation = 'landscape'; } else { $orientation = 'portrait'; } $resulting_image = [ 'name' => $image->name, 'description' => self::parseLanguageField($image->description), "focus" => "{$image->focus()["left"]}% {$image->focus()["top"]}%", 'original' => [ 'src' => $image->url, 'width' => $image->width, 'height' => $image->height, 'orientation' => $orientation, ], ]; foreach ($sizes as $sizeName => $size) { $img = $image->size($size["width"], $size["height"], $size["settings"]); $resulting_image[$sizeName] = $img->url; } return $resulting_image; } ?> With (for the image above) the following output once rendered as JSON: "image": { "name": "cirkels_oo.jpg", "description": [], "focus": "50% 50%", "original": { "src": "/site/assets/files/2823/cirkels_oo.jpg", "width": 300, "height": 240, "orientation": "landscape" }, "L": "/site/assets/files/2823/cirkels_oo.1500x1500.jpg", "M": "/site/assets/files/2823/cirkels_oo.750x750.jpg", "S": "/site/assets/files/2823/cirkels_oo.320x320.jpg" }, Any ideas on what might be going on? Probably missing something very obvious here.. EDIT: I tried explicitly including 'forceNew' => false in the settings, but that gave the same result
  • Create New...