Jump to content

joey102030

Members
  • Content Count

    60
  • Joined

  • Last visited

Community Reputation

18 Good

About joey102030

  • Rank
    Full Member
  • Birthday 12/10/1978

Profile Information

  • Gender
    Male
  • Location
    Cheltenham, UK

Recent Profile Visitors

2,482 profile views
  1. I am really missing this module in version 3, are we any closer to an update? I am having to make do with Croppable Image 3, but the crop settings require both width and height values, not allowing either to be flexible.
  2. Thanks Horst Just tried it with a jpeg and it works a treat. Any plans to get this working for PNG / GIFs?
  3. I'm not sure if this is the intended functionality: When I click to edit a crop under 'predefined Crops', the overlaid 'marquee' always reverts to the far top left of the image, even when I move it around and click 'Crop and go'. I know the crop has saved correctly because I can hover the button and see a thumbnail appear.
  4. When using this module with PW 2.6.19 dev, if I uploaded an image then clicked to zoom before saving, I was getting a blank popup with the following error in the js console: Uncaught TypeError: Cannot read property 'find' of undefined I tracked it down to the following lines in InputfieldCroppableImage.js magnificOptions = { type: 'image', closeOnContentClick: true, closeBtnInside: true, image: { titleSrc: function (item) { return item.el.find('img').attr('alt'); } }, I fixed the error by editing it to match the following lines in wire/modules/Inputfield/InputfieldImage/InputfieldImage.js var magnificOptions = { type: 'image', closeOnContentClick: true, closeBtnInside: true, /* image: { titleSrc: function(item) { return item.el.find('img').attr('alt'); } }, */ Horst, can you check this is correct and I haven't been a n00b?
  5. Whatever happened with this? I'm getting the same issue, been testing with superuser up until now so all worked fine. Now testing with a different role and I'm unable to access a custom page field in the user template. Edit: It seems to depend on the type of page field. I just changed to checkboxes and it works fine, still weird why it doesn't work with the other page field types.
  6. This is exactly what I'm looking for. Kongondo, I would be interested in beta testing this.
  7. This is brilliant! I've just started using Docker with a view to testing my PW sites locally, so this couldn't have come at a better time.
  8. I currently use a bespoke (non PW) system where outgoing emails are queued in a DB table, and a cron job sends the queue through Mandrill every 5 minutes. This method was originally used to eliminate the lag associated with sending through an external SMTP server, but actually having all emails permanently stored in the database offers loads of other unexpected benefits. I'm not sure how sending in this way could be best done in a PW module. I wouldn't like to leave it up to lazycron, so maybe the choice of immediate sending, or alternatively a cron job would need to be setup manually to fire a PW url every x minutes, which would be responsible for clearing the queue. I'm not sure the best way to illustrate a pagetree here, but I would actually envisage the top level being the email templates themselves, then the children being the outgoing emails, and the children of those being the actions captured from the webhook. The benefits from a module like this would be huge. Apart from just being able to see instantly which emails have sent successfully or not, a simple selector could show information like which is the most popular link in an email, or which emails aren't being opened at all. It's good to know the WireMail __send function is hookable, this should mean the internal emails sent from PW (eg forgotten password) could be intercepted and forced into the new Mandrill system
  9. Hi Craig I've actually been thinking about the same thing for a while. In my mind, one of the main benefits of the API over SMTP is the ability to setup webhooks to track actions against each sent email. Therefore I had envisaged each email first being saved to the pagetree before being sent. Then each action against that email (eg, open, click, bounce) to be captured and saved back to the pagetree as children of the sent email. I hope that makes sense. I've not tried your module yet, but I've had a look through your code and it all looks great.
  10. That would be excellent, thanks very much!
  11. Thanks for the replies, and thanks renobird, that's exactly what I want, except I want to be able to pass a selector instead of a text field
  12. A search didn't bring up any useful results. Anyone know of any modules which can output a tree as a javascript accordion?
  13. I have one central 'wire' folder, with multiple sites symlinking and it works great. I do the same with the site/modules folder, so all sites have access to the same modules. Something I've found: I have to SSH as root to create my symlinks, but then I need to chown them from root to the correct user or they won't work.
  14. This module works great, but does it have to completely overwrite the classes of the containing element? Can it not just append emo_email to any existing classes?
  15. Just noticed a small issue. If you use: $some_other_page->render(), any emails in the rendered code don't get de-obfuscated
×
×
  • Create New...