Jump to content

adrian

PW-Moderators
 View Profile  See their activity

  • Posts

    11,185

  • Joined

  • Last visited

  • Days Won

    372

 Content Type 

Everything posted by adrian

  1. adrian
    Good point - sorry I had seen that - I was confusing list view with thumbnails displayed vs grid/thumbnails view. I think it works as you have it, but I think things look a little ugly in list view when you don't have the field set to use thumbnails, but rather the full sized version - maybe that is why I am getting the image centered and overlapping the info bar above? I am just using the standard default theme - PW 2.5.13 Probably doesn't matter in the popup for the grid view, but in the list view I think it would be more obvious for users, but not a big deal.
  2. adrian
    Hey guys - I have just started using this and have a couple of issue: Notice the way the image is transparent over the grey info bar? In thumbnail view, the crop button is not showing. Also I have two croppable image fields and toggling the thumb/list view buttons on one change the view on the other - not sure if this is related to croppable image or not though. One more thing - might just be me, but I'd prefer to see the crop buttons just below the image - ie, above the description and tags fields. Thanks!
  3. adrian
    Looks like you aren't doing the correct thing here. I am not very experienced with cPanel, but you don't want to be forwarding the email to the PW link. You need to set up a cronjob (from cPanel) using that format that @cstevensjr showed you. That cronjob will then periodically check the email address. Does that make sense?
  4. adrian
    Nice job on the configurable fields I have just committed an update that I think fixes all the issues you were having and also changes the selections for the config settings to use FieldtypeSelect and limits the options to templates and image fields as appropriate. Let me know if it works as expected for you.
  5. adrian
    Try this: wireMail('my@email.com', 'some@email.com', 'Message Subject', 'Message Body'); or $mail = wireMail(); Also, make sure your php mail function is available and working - likely it isn't on a local dev machine. So install and set up one of the SMTP options: http://modules.processwire.com/modules/wire-mail-swift-mailer/ http://modules.processwire.com/modules/wire-mail-smtp/
  6. adrian
    Sorry, I might be missing something obvious, but can you explain the issue with directory paths and why you can't use this module?
  7. adrian
    I just updated the gist with a version that deletes the images from the original parent album page. Let me know if that works for you. It's kinda funny that there has been quite a bit of interest in this, but not from the OP
  8. adrian
    Just wanted to let everyone know that thanks to @Sephiroth we now have support for comment migration - you'll need to grab the latest commits for both Migrator and MigratorWordpress! Next on my list is custom fields ...
  9. adrian
    I think you can still use this module to set up the page field and the Parent / Child A / Child B components of the tree, but to get the grandchildren: child A1 etc, you will need to add those by some other means - either manually or via one of the modules I mentioned. Remember that this module is just a shortcut method for creating Page Fields and their linked pages. You should still understand how they work and also realize that once created, all settings and content pages can be manually adjusted. Does that make sense?
  10. adrian
    I am having the same problem and it is affecting other modules too: https://processwire.com/talk/topic/4865-custom-upload-names/?p=84264 Not sure if it is relevant, but my 2.5.14 is not a fresh install though.
  11. adrian
    This is affecting certain other modules too - https://processwire.com/talk/topic/7588-admin-custom-files/?p=84276 I'll see if I can find some time later to figure out what changed and see about fixing things, either at the module side, or a core fix from Ryan.
  12. adrian
    Hi Maverick - these are two different issues. You must of course add svg to the list of valid extensions, but the problem reported above is related to SVGs that don't have their width and height set. Illustrator CC has added an option to make SVGs responsive which leaves off these attributes. I have submitted a PR for a fix for this issue, but it hasn't been incorporated yet.
  13. adrian
    Page Field Select Creator is not designed for adding multiple trees of parents/children/grandchildren. Are you actually setting up a page field, or do you just want a quick batch way of creating these for general content? If the latter, then take a look at these modules instead: http://modules.processwire.com/modules/batch-child-editor/ http://modules.processwire.com/modules/process-batcher/ If the former, can you please let us know your use case in a little more detail.
  14. adrian
    Just wanted to confirm that the: // make sure the value is of type Pageimages $obj_field->attr("value", new Pageimages($this->page)); fix also works for me. Thanks soma!
  15. adrian
    I can confirm you're not going crazy, and apparently neither am I (I wasn't sure at the time ) I saw this about a month ago, but now don't remember what I was doing at the time and I have no idea how to reproduce it!
  16. adrian
    I don't think (not positive) this is actually meant to be possible - I think this is by design - I actually get a message saying "You don't have access to list page X" when I try to click on a page to get the view/edit etc links. A couple of options for you - neither of which is really what you want, but might be useful Draft Creator: http://modules.processwire.com/modules/process-page-draft/ Page Protector: http://modules.processwire.com/modules/page-protector/ The first module should be self-explanatory. Regarding the second module - the workflow with this would be to publish the page, but protect it (also from the settings tab once the module is installed) - that way the view link will be displayed, but it won't be viewable by any guest user. You would probably also want to set it hidden so that it wouldn't show in the menu / searches etc. Sorry, neither are ideal for your needs If you want something closer to your original request, then you might need to some fancy hooking, unless I am totally wrong and missing something obvious
  17. adrian
    That sounds like the key issue in all this to me - very good point! And Pete - thanks for those links. Lauren will have some thinking to do when she finally gets back to this thread
  18. adrian
    Thanks to the three of you for you work on this! Can't wait to test - will definitely be using it on a new site that is starting dev in the next couple of weeks. I'll let you know how it goes!
  19. adrian
    Thanks Pete - I am not sure about the effect of removing StopWords on SEO either, but seemed like a nice quick module to whip up so thought I'd help out Actually I have just revised the module. The first iteration completely overrode the InputfieldPageName.sanitize method. This new version just adds and applies a new method for removing the stopwords. This should be much safer in that we don't need to worry about overriding any updates that are made to that method in the PW core. New version attached in my post above.
  20. adrian
    Hi Lauren, I have thrown something together for you. It isn't well tested yet, but seems to be working fine. You can edit the StopWords.js file if you want to adjust the words that are removed. If there is general interest in this module, I might consider making it configurable. Let me know how it goes for you. PageNameRemoveStopwords.zip
  21. adrian
    Ok, v3 takes care of populating the description fields for the new image pages. The one thing I don't like about all this is the duplication of the image files themselves. Maybe the module should delete the original images after the child pages have been created?
  22. adrian
    I think I know what you mean - I have just committed an update that will use the entered description for the title of the page is it is entered - otherwise it will fallback to the filename. Is that what you meant? The code was quickly put together, so I expect the OP may want to tweak other things along those lines - should hopefully be a good starting point though.
  23. adrian
    Hi Lauren, You'll need to hook into ProcessPageAdd::buildForm and potentially ProcessPageEdit::buildForm if you also want to change the name when the title is changed during a later edit. You can get an idea of how to do this from my Page Rename Options module (https://github.com/adrianbj/PageRenameOptions/blob/master/PageRenameOptions.module#L65) You can see that I have added some JS to override the native functionality when it comes to naming the pages. You will be looking to add to/override the functionality in these files: https://github.com/ryancramerdesign/ProcessWire/blob/6cba9c7c34069325ee8bfc87e34e7f1b5005a18e/wire/modules/Inputfield/InputfieldPageName/InputfieldPageName.js https://github.com/ryancramerdesign/ProcessWire/blob/6cba9c7c34069325ee8bfc87e34e7f1b5005a18e/wire/modules/Inputfield/InputfieldPageTitle/InputfieldPageTitle.js Hope that helps to get you started. There is nothing wrong with messing with the page name - in fact it is possible to manually edit it by hand. The one thing that some don't agree on is whether it should ever be changed after it is originally created. I would personally rather the name matched the title, but others think it should never change due to SEO and broken links. I make use of the Page Path History module to deal with these - maybe not perfect, but typically the only time the titles will change is during development, so I am ok with it.
  24. adrian
    Hi @paulbrause, Lots of great suggestions above regarding PageTable fields etc, but I just put together a quick module that I think does exactly what you are looking for. https://gist.github.com/adrianbj/2b3b6b40f64a816d397f To make it work as is, you will need these: Templates: album (for the album parent pages) image (used for the automatically created child pages) Fields: images (for the album template) image (for the image template)
  25. adrian
    Thanks Pete - it's been fun to work on I'll update the Readme to detail the new features and merge all the changes shortly.
×
×
  • Create New...