Jump to content

alan

Members
  • Posts

    854
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by alan

  1. Note: The below involves a clearly labelled optional setting so this post is not addressing a bug or a problem rather it's just me posting what I found in case it helps someone else In a PW 2.4.x setup I found that inserting an image in a CKEditor BODY field with the regular tools in the Admin (an image that had already been uploaded to the page and whose full width size was 230px wide) was getting really very 'grubby' when I resized it down to around 140px. So I took a look at the settings in config.php: $config->imageSizerOptions = array( 'upscaling' => true, // upscale if necessary to reach target size? 'cropping' => true, // crop if necessary to reach target size? 'autoRotation' => true, // automatically correct orientation? 'sharpening' => 'soft', // sharpening: none | soft | medium | strong 'quality' => 95, // quality: 1-100 where higher is better but bigger ); ...and changed soft to none. For my particular setup (MAMP / Mac) the difference was dramatic: Original 'soft' Then reinserted after changed to 'none' If this is typical then it looks like the 'out of the box' setting should be 'none' (Ryan?) but I don't know if it is typical.
  2. Tks adrian, that may be a much simpler way, will try that next time I need to do this
  3. Hi Jens, welcome and yes I am certain it is I just don't know if this is the most elegant: I created a second template, for example you could have category and category-children. Then you can assign access to those templates so that a role has edit access to one but not to the other using the usual controls in the Admin (I won't list them here as exploring is a great way to learn + no time right now, but if you get stuck you can post here and I or someone else is sure to help). One thing I do sometimes, not a necessity, is that if I have a pair of templates that are essentially for the same thing (and so I want them to have *identical* fields) and I don't want the bother of maintaining the set of fields in both templates, is make one template use the set of fields from the other. To do this, temporarily set in config.php $config->advanced = true; then create the new template, such as category-children and choose to have no .php template file associated or to copy in any fields, then, when it is created, you can choose that it will mirror the fields of another template, in this case, category. Usually I also set it, once created, to use the same template file as the 'parent' Template. Usually it's good to set $config->advanced = false; back to false after this. I hope that helps, sorry I've not linked to other examples but if stuck some searching here in the forums will reveal more help since there's tons of excellent example code and explanations in here
  4. Thanks for clarifying Ryan (and for the clearly well thought out module, a definite purchase this set of modules ).
  5. Joss: you are a star! Edit: Sorry Ryan, the Module's great too!
  6. SEO-wow! In a page of copy, will this cleverly link the first instance only or the first N instances or does it link, for example, every time API is in the copy (if I were manually HRO'ing (human reading optimization) and SEO'ing a page of copy I would not link every instance)? Excited by these products Ryan, thanks so much!
  7. If is JS, so maybe of ho help, but I have used this before: if (Modernizr.touch) { alert('Touch Screen'); } else { // alert('No Touch Screen'); } Written in jQuery (in case that matters) and therefore assumes jQ is loaded. Also requires http://modernizr.com/ Of course this detects for tablets too (and for the MS tablet that has trackpad and keyboard I think).
  8. I like the licence model where once I have purchased I may use on any site. Each model has it's benefits. For me the ease of managing a simple model where if I have bought it I can use it is a big one. Another thing I like is that if I have bought a module and learnt how to use it then there is nothing reducing my enthusiasm to use it on the next site I work on. I recognize that there is no 'one size fits all' and that therefore any solution has to be a compromise to some extent with some of the audience, all I can say personally is that the model used feels best to me.
  9. Thanks for noting Soma, I love finding nuggets of gold in the Modules but so often miss them, so v. pleased to be helped in any way to keep abreast of what's available
  10. I love how this Module is clearly excellent for larger sites, useful for any site but not essential to building brilliant PW sites. Building an income stream for PW is a healthy thing to do and like the rest of PW it's clearly being done with care; thanks for this and the upcoming great new tools Ryan And nice to hear, from the vocal commentary, that not just the Admin i/f has a theme
  11. FYI diogo, not important, I just spotted a typo in the info on the Modules page, where you link to Nico you've got https and Chrome gets all sulky and jaundiced as the site is http. See, I have my uses—I may be too thick to produce a Module but show me a spelling mistake and I'm ALL over it.
  12. FYI Installing by Modules Manager or visiting directly, github is 404ing https://github.com/netcarver/PW-TextformatterThinspace/archive/.zip
  13. Steve, if this is something that tidies up extra fluff added to textareas by the otherwise lovely CKEditor then fab! (And thanks if that's what it is or not ) PS: Also the coolest Module name yet.
  14. Thank you very much indeed for this Module Wanze. After fixing a silly from Google 401. That’s an error.Error: invalid_client no application name that you'd kindly posted the fix to, I was in! And wow... It's clean view of GA data is in ways a significant step up from the native view in GA console. Let alone the convenience of seeing this data when I am working on a site. Fabulous Wanze!
  15. Thanks teppo, Ryan, Horst, et al It looks seductively like a Lego solution might exist..? Seeing your module uses Swift Mailer and these guys note Swift Mailer at the top... I wonder if there is an easy way to use their service now, thanks to this Module?
  16. Thank you for the tips horst, most appreciated
  17. Thanks Wanze for this Module Has anyone used Wanze's Module to create a downloadable PDF of a form entry from the From Builder system by any chance? Doing booking confirmations for people, I'm considering upon form submit offering the submitter a link to a PDF of their booking so they can download it. I'll need to address security so others can't access PDFs (such as matching a session variable and if I read this Module right, it can create PDFs for download 'on the fly' rather than storing them?). Thanks for any pointers
  18. Wow, Adrian, I am such a clutz for having not spotted this Module before, thanks SO much for creating it! Cheers, -Alan
  19. Hi everfreecreative, thank you for that catch! I had been switching it back and forth knowing that in some circumstances search is limited in some way when it's only 1 image (although limiting to onl1 one image was just what I wanted) and sure enough the last way I had left it set while trying to debug my own attempts was to 0. Switching it to 1 did indeed make the eq() redundant. Thanks SO much for the simple and quick explanation!
  20. FWIW After reading The Truth About HTML5 and also because Google, Microsoft and Yahoo all piled in on schema.org (and agreed something!), even tho' I loved and used http://microformats.org/ before I now standardize on using schema.org micro format markup. The ability to auto-add micro format data to content sounds very good, I just expect there to be enough permutations that I would likely need to hand mark up content often as well and so I wonder if auto added micro format data could ever take over. If it could it would be a boon
  21. Also had to change code <a href="<?= $image->images->url to <a href="<?= $image->images->eq(0)->url like noted in the above post. Edit: Don't know if I am having to add the eq(0) due to me making the gallery components functions or not, but just in case that is why, thought I'd mention that I have, made the gallery into a couple of functions.
  22. Only thing I've had to change to get this revised version to 'fire up' and produce thumbs was $thumb = $image->images->size($thumbWidth, $thumbHeight); changed to $thumb = $image->images->eq(0)->size($thumbWidth, $thumbHeight); and I found that out from this post (thanks all, especially everfreecreative )!
  23. You are a STAR everfreecreative! Thanks for the fast reply, I am very grateful and off to go and apply! Cheers!
  24. Following on from the chat about storing each image on a page of it's own, or not. I made the Album code into a function (not that that matters but it explains why the code below is a fn) and this how it starts, you can see it is basically identical to everfreecreative's code function galleryAlbum() { $page = wire('page'); if($page->treat_as_gallery) { $out = ''; $input = wire('input'); // Configure thumbnail width/height & number of photos to display per page $thumbWidth = 77; $thumbHeight = $thumbWidth; $imagesPerPage = 8; // Make ProcessWire pagination work on the images field (see for full explanation of this) $start = ($input->pageNum - 1) * $imagesPerPage; $total = count($page->images); $images = $page->images->slice($start, $imagesPerPage); // Paged galleries // Create a new pageArray to give MarkupPagerNav what it needs $a = new PageArray(); // Add in some generic placeholder pages // org foreach($images as $unused) $a->add(new Page()); foreach($images as $myKey=>$unused) { $a->add(new Page()); } // Tell the PageArray some details it needs for pagination $a->setTotal($total); $a->setLimit($imagesPerPage); $a->setStart($start); $a->renderPager(); $out .= "<div id='gallery-t-group' class='royalSlider rsDefaultInv rsMainSlideImage'>"; foreach($images as $image) { ... etc The trouble is I really need to store, per image, more than the image and a plain-text description and so the page-per-image approach is ideal. I spent a few hours trying to work out how to do this and my code fumblings are not above, above is the clean approach that works (tks to everfreecreative ) Essentially I need: ideally to get the paging code to work with images that are child pages of the current $page to get $images built properly before I arrive at the line foreach($images as $image) so it works just as it does when images are all stored on one page. Cheeky question, does anyone have any ideas how to achieve these probably simple-if-you-know goals? If not I will return here at some point and list my code fumblings (which get some way there) and explain what works and what fails. I've not done that straight away because they are pretty feeble plus that version of the site is archived and the 'simple' one is restored (as I need to launch something with very little time right now). Thanks lots in advance if you can comment!
×
×
  • Create New...