kongondo

PW-Moderators
  • Content count

    5,228
  • Joined

  • Last visited

  • Days Won

    77

kongondo last won the day on March 27

kongondo had the most liked content!

Community Reputation

5,696 Excellent

2 Followers

About kongondo

  • Rank
    Hero Member

Profile Information

  • Gender
    Not Telling
  • Location
    UK

Recent Profile Visitors

25,104 profile views
  1. Since at least 2.4.x. However, some properties like defaultGamma since maybe 2.5.x.
  2. Hi @harmvandeven, OK. Makes sense. It doesn't sound too difficult given the Vimeo/YT API. I'm thinking we'll add a setting in MM for users to indicate whether they'll want to view/manage online content such as YouTube. We'll create a list for this but currently, support only YT and Vimeo. Later, we could expand this to include other media sources. We can add the input to the upload screen as a third tab (only visible if users indicate they'll want to view/manager online content such as Vimeo). So, Add / Scan / Online (or Other or something appropriate) - I'll be removing the 'Help' tab. With good documentation, we don't need it. I'll be working on the docs once version 012 is in beta testing. We'll also have an input for the media Title. We'll either reuse the file field that video media use to store the image or copy and reuse the image field that image media use in the video media templates. We'll use an InputfieldTextarea field to store the embed code and other data. We can just reuse the Textarea field we use for MM settings - copy that to the video template. Again, this field will only be added to the video template if online content feature will be used. For the frontend, we'll have video media return a property with the data required for video output. I think that should cover it. OK. I'll have a look.
  3. Maybe 'easiest' to just duplicate the uikit admin, edit it as you wish and install that as your admin theme. Of course, you'd still need to dig into the code to find out what you need to change...It might not be as straightforward as it sounds though .
  4. xdebug has always been slow (all over Google). Some things you can do Disable xdebug Profiler Disable xdebug Profiler enable trigger Disable xdebug auto trace Disable xdebug auto start (if you can) Helpful hints http://www.devinzuczek.com/anything-at-all/i-have-xdebug-and-php-is-slow/
  5. @SamC, Moderator Note FYI, you posted 3 other copies of this thread. I am guessing you were on mobile, or your computer was a bit wonky. I've deleted the other three.
  6. @dweeda, Moderator Note Multithreading is not allowed. Please, do not open different topics regarding the same issue. Keep it in one place. I have merged your other thread with this one.
  7. From the repo. Browse the repository commits and click on the commit shown in the screenshot below: That will take you to the page where you can clone/download that version.
  8. loadPageField() is required to stop the field from visiting the database. There is a comment right there in the method . If we remove the method, it will just call its parent loadPageField() (Fieldtype.php). Hence, we override it. We can have it return true. That results in renderMarkup() being called once only (rather than twice currently - once each for wakeupValue() and loadPageField()).
  9. @adrian, I have tested and cannot replicate this. I tested with both single and multi page reference fields using different inputs (Asm, Checkboxes, etc). I also tested using render via code and via wire('files')->render('some-file'). This is what I get if I put bd($page->id) at the top of renderMarkup(). 1367 is the ID of the page being edited. The pages saved in the page reference fields are not called. Edit I think there is something else going on in your install. There is nothing peculiar about the field. Apart from renderMarkup(), all the other methods are ProcessWire Field methods. Theoretically, it means if a bug exists, then all Fields should be exhibiting the same behaviour.
  10. Hi @Bacelo, Achievable from version 0.1.5 using the getMenuItems() method (see examples here) or from version 0.1.8 using the 'disable menu items' feature. Please note that support for ProcessWire 2.x ceased with version 0.2.2. In your case, you can upgrade Menu Builder up to version 0.2.1. and you'll be fine. If you can though, I'd advise to upgrade to ProcessWire 3.x.
  11. Hi Alex. Not yet. Illness, Easter and Hay Fever all colluded against me. Please note that I'm also upgrading Jquery File Upload alongside Media Manager. I'm working as fast as I can .
  12. Hi @harmvandeven, Welcome to the forums. Thanks for the purchase. Currently no, but it's something I've thought about, briefly. I've not been able to decide how to best implement it. For instance, they would need to live under /video/. However, that would require a video file to be uploaded. Also, should the videos be embedded or not, etc? Thinking out loud, maybe we should have a different media type for online content - mainly for YT and Vimeo. What's the workflow? Your custom module gets the thumbnails and then you upload these as images to Media Manager? Do you want them to be able to play the related videos by clicking on the thumbs? Frontend, Backend? Sounds cool. Hard to tell without knowing more about how your modules work. We can discuss here or in PM or email if you wish.
  13. Hi @adrian, ___wakeupValue is needed for frontend access. I am assuming some people use the field in the frontend. ___sleepValue should be able to work with return true only. I'll have to investigate deeper though. The whole module is based on Ryan's concat field. These methods were copied as is (or almost) from that module. So, his module must be having the same issues then. I'll have a look sometime. Still no ETA though, sorry.
  14. How did you update ProcessWire. Using some module? Manually? For now, are you able to downgrade ProcessWire to the last stable version you had? What version of ProcessWire was that, 3.0.62? Does it work then? You can then upgrade incrementally, e.g. 3.0.62 to 3.0.7x to try replicate the issue. If you are able to do the test on a local server first, the better. I'm probably clutching at straws here...