Jump to content

adrian

PW-Moderators
  • Posts

    11,097
  • Joined

  • Last visited

  • Days Won

    365

Everything posted by adrian

  1. Not your fault at all - took me a while, but turns out it was my definition of a field in SettingsFactory that was causing the problem ? All sorted now and the new version works great for Settings Factory as well - really cool - I especially love the ability to upload directly via that field and it automatically reloads the available images after closing the modal.
  2. It wasn't created that way - just a regular image field. Even after deleting it I am still seeing the error - will have to dive deeper to see where it's originating.
  3. Yeah, I did. I just uninstalled it and that error is now gone, but I am now seeing: and having real problems getting rid of it.
  4. Really short on time, but wanted to take a quick look. So far looks really great - thank you! I noticed this error - only occurs if the child page doesn't have images available. Also, I am wondering about the radio buttons as a way to choose the fields that images can come from. I would have thought checkboxes were better to allow for multiple fields. This may be for multiple fields on the one page/template, but I can see it also being useful for different pages with different templates that have different image fields. Does that make sense?
  5. @gebeer - that all sounds brilliant - thanks again so much for this - it's going to be an awesome solution!
  6. Sorry, but uninstalling Tracy doesn't help replicate it for me either. I am curious - is this a new install of BCE, or did you upgrade from an older version? I get the feeling you may have upgraded from a version before the pagesToInclude option existed and there is a problem with the defaults not making it through when using separately configurable pages. Would you mind uninstalling and reinstalling BCE to see if that fixes it?
  7. Could you do me a favor please? Do you have Tracy installed? If you could enter: bd($currentData); after line 100 and post a screenshot of the output. It should look something like this: The key thing is that you will need to enable the Dumps Recorder panel in Tracy and after you click the export button, you'll need to reload the page to see the results in the Dumps Recorder panel. Thanks!
  8. Hi @pullasuti - welcome to the forums! I can't seem to reproduce this. Are you exporting a parent with separately configurable settings, or relying on BCE's default module settings? What version of PW and PHP are you using?
  9. I think "2" for sure. I think the thumbnails should be as you currently have them when there is more than one page with available images - in collapsed inputfields - one for a defined filepath, one for the current page, and one for each of the other available pages - which of these are shown of course will depend on the field's settings.
  10. I guess that's why I was thinking if the module was simply named "ImagePicker" - then it could allow picking from disk path, pre-defined pages, or the current page - would that model / approach make sense?
  11. Another thought for you - what about the option to select an image from an images field on the current page? I know sometimes I ask users to sort images so that the featured image they want is the first one in the list, or get them to tag an image with "featured", or some other approach. Being able to select an image from the current page with this field would be an awesome way of handling this.
  12. I guess I was thinking that you could combine both modules - just because the interface elements are so similar and thought it might be less maintenance for you. If a directory path is supplied in the field settings, then the images from that path could be added to a image selection section above or below the collapsed page sections. If none is specified, then only the pages would be shown. Similarly, it could be path only if no page / image field is specified in the field settings.
  13. @gebeer - I recently recommended this module to @eydun as he was looking for a media manager tool. He asked me about using it in @Macrura's awesome Settings Factory module. I had a quick play around with it but got some errors. Then I tried your FieldtypeImagePicker module and it actually works quite well. I am wondering whether: a) you are planning on maintaining this other module, and b) if you think it might be possible to make FieldtypeImageFromPage work with Settings Factory as well - I fear the need for storing multiple values might be the problem. I guess the data could be converted to json, but that complicates things for you and probably isn't worth it, but just wanted to start the discussion because I know that having an image field in Settings Factory is something many users have requested.
  14. Just a random thought - in addition to using child pages for categorizing images, I wonder if some users may prefer image tags? Perhaps you could group images for selection by the tags they have been assigned on their page. Really just thinking out loud, so please don't consider this a feature request unless you think it's a good idea - I haven't thought it through ?
  15. Yeah, being out of context like this will be confusing I think. Could you try the getForPage() method to find the page that the repeater item is on and link to that instead?
  16. Works great - thank you! This is going to be such a useful module ?
  17. Looks brilliant @gebeer A couple of minor things: 1) The "Include child pages of above page as source for images?" checkbox doesn't show as checked when it is actually checked. Typically the way to handle this is with a ternary conditional to set the checked attribute to "checked" if the value is "1", eg: $f->attr('checked', $data['enabled'] == '1' ? 'checked' : ''); 2) I didn't get an error message when deleting one of the source images. I actually wonder if you can hook into this and prevent deletion completely (unless the image is removed from being selected by this field.
  18. Or maybe you are looking to hook into the image deletion process to prevent an image from being deleted if it is used by an ImagePicker field? If so, that sounds like a smart thing to have ?
  19. I don't think it's possible. Two comments in the core code: "Fieldtype modules are not automatically loaded, they are only loaded when requested" "Inputfields are not loaded until requested" I think you might need to add a helper module for those hooks. I guess otherwise you would need to check for the presence of the pageimage from init(), rather than hooking which I think could also work fine.
  20. @gebeer - I am sure you have already thought of this, but if you're changing to only support selecting a page (and its children), you could make use of PW's API to load up the images in the picker field, rather than scanning the server folder directly. I don't think there is a reason not to change.
  21. You should be able to do that with any module, but you will likely also need to delete its entry from the modules DB table so that PW isn't looking for it. That said, I'd like to know more about the login issue - never heard anyone have that problem before - those details on PHP version etc will be useful.
  22. What about adding the image description, width, height, and filesize to the tooltip and under the selected image?
  23. I was thinking this would be optional - I don't think anyone has to set this up - the module would scan these only if they exist.
  24. I might be getting carried away, but I think it might also be nice to be able to select images from child pages of this page as well - I can see a use case for categorizing images and I think this would be a decent way of doing it. Perhaps the picker could even have a dropdown that lets you filter by child page (category). What do you think?
×
×
  • Create New...