kongondo

PW-Moderators
  • Content Count

    5,626
  • Joined

  • Last visited

  • Days Won

    90

kongondo last won the day on November 20

kongondo had the most liked content!

Community Reputation

6,200 Excellent

5 Followers

About kongondo

  • Rank
    Hero Member

Profile Information

  • Gender
    Not Telling
  • Location
    UK

Recent Profile Visitors

25,922 profile views
  1. kongondo

    Ah, yes. As documented here as well: http://processwire.com/api/ref/wire-array/import/
  2. kongondo

    I've only had a quick look at your post. It could be 'default' is a reserved word/keyword?
  3. kongondo

    Hi @xportde, It would be and it doesn't need to wait for the future. It is already here . With the new version (announcement imminent), you can add as many fields as you want to your respective Media Manager templates. Let's say you want a URL for your images. All you would need is to: Add a URL field (in this example, called link) to the Media Manager image template (media-manager-image). If not accessing your Media Manager Library directly, create a Media Manager Field (let's call it albums) and add it to your page's template, say basic-page. In the Media Manager Field (albums) settings, enable 'Allow users to edit selected media'. Edit a page using basic-page template. Add images to the field Hover over an image and click the Edit link. Edit your link field to add your URL. In your template file, you can access your URL like this: $albums = $page->albums; $out = '<div>'; $out .= $albums->each(function($m) { if($m->typeLabel !='image') return; $thumb = $m->media->height(260); $img = "<img src='{$thumb->url}' alt='{$m->media->description}' height='130'>"; $o = "<div><a href='$m->links'>$img</a></div>"; return $o; }); $out .= '</div>'; // OR: Using foreach /* $out = '<div>'; foreach ($albums as $a) { if($m->typeLabel !='image') return; $thumb = $m->media->height(260); $img = "<img src='{$thumb->url}' alt='{$m->media->description}' height='130'>"; $out .= "<div><a href='$m->links'>$img</a></div>"; $out .= $m->body; } $out .= '</div>'; */ echo $out; And that's it. Any field you add to your Media Manager template is available as $m->name_of_field, where $m is an instance of MediaManager field as per the example above. More examples in my next (eventual) post(s). I tried to make a video, or an animated GIF, even a simple screen capture to show you what I mean but everything failed! Lots of artefacts, etc. I've recently moved to Linux, so still finding my way round.
  4. kongondo

    Thanks buddy. I appreciate it.
  5. kongondo

    Welcome to the forums @MateThemes Yes. It is here. I quote: You can set up shipping by postcodes, states/provinces, countries or continents. All these are just sub-divisions of the same thing :-). A group of postcodes make a city, a group of cities a state, a group of states countries and a group of countries continents :-). Padloper will not have something like 'what type of shipping zone do you want to create?' Instead, you create the zone and throw in the countries or provinces (optionally delimited by postcodes) you want. If you want a European Union zone, throw in the countries that make up the Union in that zone and the applicable shipping rates. If you want a zone for South America, throw in the countries that make up that continent. If you want zones for Middle, Far and Near East, specify the respective countries for those regions. Please note that it is not an all or nothing system. If you don't want Brazil in your South America zone, then don't include it in the zone but instead create a different zone for it, unless of course you don't ship to Brazil, in which case, just exclude it entirely. Hope this answers your question.
  6. kongondo

    Welcome to the forums @spackmat, Just in case you couldn't find it, here's the docs on hooks. Have a look at these two files as well, under /site/: ready.php and init.php. Normally, you place your hooks in either of these, depending on when you want to intercept an event.
  7. kongondo

    What @LostKobrakai said. :-). I don't think this is something Padloper should handle. If prices need to be adjusted, we have Hooks for such things. Alternatively, you could add custom price fields to the product template and use those instead, following some logic. So, this is up to the dev. On a side note, I'm not sure I get the rationale of adjusting a product's price based on a customer's location. Shipping, yes, but not the actual product price. Is it because of exchange rates? Aren't those handled by the merchants? I'll consider these when we get to that stage, thanks. My initial estimates was 6 months from when I got started (please see first post). I can't promise that though; it could even be shorter! Thanks for the interest.
  8. kongondo

    No. It means I'm using different versions of Tracy on different sites (multisite) on the same machine . Edit: Maybe this old version is why Tracy is not appearing in modal windows or that has always been the case?
  9. kongondo

    In fact I misspoke in my previous post. I've been using the new version but on a different local site. On the site I'm currently on, I have the older Tracy :-). Yeah; now I seem to remember this. It was of course on the other site where I had the new Tracy. I even played around with Adminer, I recall. Good to know, thanks.
  10. kongondo

    I'm using the icon; it's not hidden for me. On this machine I'm running 4.8.24 The new window came handy today. I needed to see different windows at the same time and docked, the console was in the way, plus I just couldn't make it bigger. I've done it before, but can't remember how :-).
  11. kongondo

    Awesome work @bernhard and @adrian. Hopefully one day I'll get to test all these wonderful stuff being added. That might be a while, given that it's only today that I discovered the Tracy console can be opened in a new window!
  12. kongondo

    @teppo <aside>Dude, you threw me off with that new avatar . I was like who's this replying to Teppo's post; I haven't 'seen' them before...</aside>
  13. kongondo

    Wow! s'all am sayin
  14. kongondo

    Hi @Orkun, You say this is happening with all media types you try to upload? That's strange. I think I've experienced this once when Media Manager was not installed properly and every created child (media page) was heading to the first available media parent, and that happens to be 'Audio'. Is this a fresh install? Or has Media Manager on that site been working OK previously? Is it possible to have a copy of the images and any non-sensitive documents you are trying to upload so that I can debug? Clearing cache several times and deleting the offending Is reinstalling Media Manager and option? Does that help? Any errors? We've previously had a similar problem with Imagick but I'm not sure whether that's the case. By the way, JqueryFileUpload Version: 0.0.2 is a bit outdated :-). Grab the latest version if you can. Thanks.
  15. kongondo

    Security Report: FYI TL;DR: Our module does not use the vulnerable PHP files. We are OK; nothing to see here . You might have come across reports that Blueimp jQuery File Upload on which the module JqueryFileUpload is based had some vulnerabilities that had gone undetected for 8 years! The vulnerabilities, that have since been fixed, had to do with the server-side application examples that ship with Blueimp jQuery File Upload, specifically the two PHP files Upload.php and UploadHandler.php. Our ProcessWire JqueryFileUpload module is not in any way affected by the vulnerability. Here's why: We don't use Upload.php and UploadHandler.php nor any server-side samples that might ship with Blueimp jQuery File Upload. We use ProcessWire's WireUpload Class instead. We don't ship our module with these files. We use Blueimp jQuery File Upload purely for its client-side upload capabilities (only the JavaScript). Blueimp jQuery File Upload aside, we operate a very tight ship with our module. These include: Not everyone can upload files. That decision is left to the developer. All files are validated for both MIME types and file extensions. Only extensions specified by admin are allowed to go through to validation. All uploads are stored in a temporary folder pending validation. The location of the temporary folder is configurable. One can set either a web-accessible folder (e.g. in cases where one wants to show thumbnails of uploaded images) or a hidden one. All actions sent from client-side are validated against settings stored server-side. For instance, uploading, listing and deleting files. So, changing a JSON setting sent to the module client-side has no effect server-side. We use CSRF. Etc... Here are the relevant links to the above mentioned (but now fixed) exploits. https://blogs.akamai.com/sitr/2018/10/having-the-security-rug-pulled-out-from-under-you.html https://www.exploit-db.com/exploits/45584 https://github.com/blueimp/jQuery-File-Upload/blob/master/VULNERABILITIES.md https://github.com/blueimp/jQuery-File-Upload/blob/master/SECURITY.md In conclusion, this is just for your information, in case you were wondering or came across it. We are not affected and we didn't have to patch anything. Having said that, as per our OP, we urge all developers who use this module to exercise best practices to secure their applications.