Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/17/2012 in all areas

  1. We released our new site yesterday: www.avoine.fi Development started over a year ago with 2.0 and we nearly finished it then. After that we let it be for 12 months and now got back to it with good content and development sprint. We are quite a happy how it turned out. Now running latest 2.2. Initial design was made by Niko Kauranen (www.propello.fi) and development by me. There are few changes in design also in this almost 1½ year cycle, but not that much. Niko has done great job, since it still looks fresh in my eyes, I really like the design.
    5 points
  2. Ajax Search 1.1.0 There was a request for a ajax live search. So I went and created a simple module. Added in 1.1.0 * added key support for browsing results with arrow down and up. * added escape key to close results. * added close results on click outside http://modules.proce...es/ajax-search/ From the readme: This module progressively enhances the search form to an ajax live search. It will perform a search like you would use the form normally, and returns the output of the search page. So the search will still work without js enabled. There's some basic styling attached to this module in the "styling-example". You can use it to get started. See readme in there. Setup the search.php So it works almost out of the box with the basic install profile of ProcessWire, you only need make a minor change to the search.php template file to only return the content part (results) on a ajax request. To get the ajax search only return the content, open search.php and change the output on the bottom to this: ... if(!$config->ajax) include("./head.inc"); echo $out; if(!$config->ajax) include("./foot.inc"); Module Settings It comes with some module options to define various settings regarding the search form. Following a list with the defaults. Minium length = 3 min length for starting ajax request Close button text = 'close' close button text ID of searchform = #search_form if you have a different search form id,class ID of input = #search_query if you have a different search input id,class Query name = 'q' this is the default param name as_query_url = '' if left blank the script will take the action of the form Any help testing this module is appreciated. If you have any questions or problems setting this up feel free to ask here. Also feel free to use this as a starting point for your own, or take out the script to implement it differently. It's quite simple and can be adapted really quickly.
    4 points
  3. Just wanted to say that it was nice to meet a few new people in #processwire today. Hope to see you again and that you find the channel useful.
    2 points
  4. I created a simple blank install profile for ProcessWire. I think it has been asked for a couple times, although the basic site is something really good to start with and fast to get rid of things you don't need. However in case someone wants one here it is. https://github.com/s...ireBlankInstall PROCESSWIRE 2.+ BLANK INSTALL ============================== This is a blank site profile for ProcessWire2+. It's done using the ProcessExportProfile module. There's only the following left in this profile: Fields: - title - body ProcessWire Templates - home - basic-page Template Files - admin.php (required) - home.php (required root page) - basic-page.php (404 page) INSTALLATION ============================= Get the latest ProcessWire install package. Before you install, replace the folders /basic-site/install /basic-site/templates with the ones from this blank install. Proceed with the installation as usual.
    1 point
  5. @12345j and @Ryan and the superDuper @Soma! Thanks SO much. I just searched "obfuscation" in the forum and < 5 mins later here I am with auto-obfuscation happening. Brilliant!
    1 point
  6. Great module Soma! I've been meaning to add something like this in the admin search too, and look forward to taking a closer look at what you've put together here.
    1 point
  7. store the page in a variable, and get the image only later: $randomPage = $pages->get("template=artworks-child, sort=random"); $image = $randomPage->artworks_thumb->getRandom(); $thumb = $image->size(550, 0); echo "<a href='{$randomPage->url}'><img src='{$thumb->url}'></a>";
    1 point
  8. Forget about me. I took a quick look at the screenshot and thought it was for admin use
    1 point
  9. Hi all, I know it's been awhile, but I'm just now checking back on this thread. Thanks for all the kind words - I'll be sure to pass them along to the folks on our team who actually did the design for it (I'm only responsible for the guts of it, not the prettiness). @ryan, I am using template level caching - I have each template set to clear for all pages including the home page on each save, and to save the cache for 24 hours. Without this aggressive caching, I think the site would be too slow in the real world. @AnotherAndrew, in this case the videos are just text fields, representing the main video file name. We are using the JW Player, and do have HTML5 compatibility setup, so the mp4, ogv and webm files are all named the same, save for the extension. For another site I did with PW - on which a client is making updates, including adding videos - I've set it up so that they upload the videos through ProcessWire. Knowing I can't count on the client to upload the HTML5 safe formats, I restrict the file field to mp4 only, then do a check for the existence of the other versions, changing the JW Player config as needed for each instance. I was thinking that, as we continue to use ProcessWire for sites going forward, that I might build a module that uses the Zencoder encoding API, along with JW Player, to allow full HTML5 compatibility for any video file the client uploads. I'll keep the community in the loop on that effort. Thanks again all.
    1 point
  10. Hey 12345j, are you still here? I just tried this out and fixed a bug with "$config" should be $this->config in modules. Mind if I put this on my github account? Edit: I just added a configuration setting, for defining the html tag the js script will get prepended to. Right now it will be prepended to the </head>, which might not where one wants to have it. So I added a text field where you can for example use "</body>" instead. Edit: Ok I just went and created a git repo with the updated version of this module. I also renamed the module to EmailObfuscator: https://github.com/s...EmailObfuscator
    1 point
×
×
  • Create New...