Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/30/2012 in all areas

  1. Attached is an update to /wire/modules/Fieldtype/FieldtypePage.module that lets you do this, once you replace your existing file with the one below. You should be able to specify just about any native or custom page field after the dot, like above (where we're using 'title'). If anyone can test it out to confirm I'd appreciate it. I'll commit to the source after testing a little more locally too. FieldtypePage.module This type of syntax is already used by repeaters. But if you mean something like: "repeater_field.referenced_pages.title%=$query", I don't think the attached update would let you do that, though havent' tried. If it doesn't, it's probably not much of a stretch to support it though.
    4 points
  2. Hi folks I thought I'd post up a quick, basic tutorial of how to get started with Github and not have to learn any of the command line code. It's still recommended that you learn the basic commands, but this is aimed to help Git newbies like me get their modules on Github with the minimum effort possible. Check out the PDF below and have fun GitHub for Windows.pdf
    3 points
  3. One of my clients specializes in putting on conferences/summits around the world, primarily focused on architecture and sustainable design. I mentioned to them how some users here (starting with Netcarver) had expressed interest in a ProcessWire meetup or conference in the UK. This client does conferences in the UK every year and they are extremely enthusiastic about ProcessWire and interested in helping us to put on a conference by letting us collaborate with their conference and share the same venues and accommodations. This would help us benefit from their expertise in putting on conferences (which they've done for more than a decade), as well as help [significantly] on costs in reserving the venues, food, hotels. I have worked with this client since 1994 (18 years), so have a very high level of trust with them. The conference would be in August 2013 and be 1.5 days in London at a major ad agency, then we'd step on a train for an hour or so and do the rest of the conference in Cambridge at Kings College for another 1.5 days (total 3 days). This would be a small but relatively formal conference with presentations and workshops covering everything ProcessWire, design and web development. We'd cover topics at a higher level than you'd find anywhere else in the world. I don't yet have an idea on costs except to say that we'd find a way to make it accessible to as large of an audience as possible, and it would be completely non profit, food and accommodations (for those that wanted it) included. Yet, it'd still be higher class and more personal than any other webdev conference. This is about a year out, so I'm interested in finding out who'd be interested in this. Please 'like' or reply to this post if you would be interested in attending (or presenting) at this conference.
    3 points
  4. Since it's a tech-related event it would be great to be able to get some sort of video feed for some of the speaking parts of the event (death-by-Powerpoint ), even if it was just uploading them to Vimeo afterwards. Just a thought - I'm sure there are more hi-tech solutions, but since something goes wrong at presentations at the best of times it's sometimes better to aim low with technical elements
    3 points
  5. MacOSX Github App first steps Since ProcessWire modules directory supports and encourages you to use github for publishing modules and third-party content here's a little help getting started with github for mac. Go and install the app for mac here http://mac.github.com/ You'll have to first create a github account to where you can connect. Creating public repos is free, on top you'll see a "Free for open source" and a small button. https://github.com/plans Login in from your newly installed github app. Create new local repository by simply dragging the folder (your module) right into the app. The folder can be anywhere on your computer, maybe you choose to use the github folder automaticly created under ~user folder, or you decide. After you added it to github you'll see added a ".git" folder in your local repositiory. Now you'll see your files added in the app. Maybe you'll see the annoying ".DS_Store" file in there too. To ignore files simply right click on them and select "ignore". It will get added to the .gitignore file which now also appears in the files. Do the same and ignore it too. Now push the newly created repo to github using the button top right "Push to github". You'll be asked to enter a title and description then you can push it. It now will appear on github, but still empty. Now make your first initial commit, add a description i.e. "inital commit" and press "Commit" button. You'll see it add's a "Unsynced Commits" panel underneath. Press the button on top right "Publish branch" button and it will push it to the remote repository. You should now be able to see the files commited on your github page. On the repository page you'll see a "ZIP" download button. You can use that url to enter in the download field for the module when you add it to http://modules.processwire.com. Once you update the module, you have to enter a new version both in the module getModuleInfo() and on the module page. This makes sure people, also some apps using the webservice, know it is new and can update it. Screencats The following is a short screencats (no audio) showing me adding a new repositiory to github and update it using the mac github app. Screencast using MacGithubApp
    2 points
  6. Hello, I am going to resurrect this old post to share my "related pages" approach. It uses the described pages-as-tags and then looks for pages with the same tags. The more tags are shared, the more "related" the other page is, thus getting it further up on the list. foreach($page->tags as $tags) { $tag = $sanitizer->selectorValue($tags->title); $related_pages = $pages->find("tags.title=$tag"); foreach($related_pages as $related) { if($related->id != $page->id) $related_id[$related->id]++; } } arsort($related_id); foreach($related_id as $key => $val){ $rp = $pages->get($key); ?> <a href="<?=$rp->url;?>"><?=$rp->title;?><br><? } I just translated this to PW from a Perl module I had, so please feel free to correct my PW syntax since I'm new to this. Thanks, thomas
    2 points
  7. Soma: using php cache would be pretty much identical in speed, no difference. Implementation is much cleaner though with JSONP. Ryan: you can be pretty strict - If I remember correctly jquery uses only numbers, but I think it would be good to use same sanitizing than pw pagenames have. Actually you could even hardcode it, but that would make it harder to use using jQuery's callback (since it always adds random stuff there). http://www.michaelhamrah.com/blog/2010/02/using-flickr-and-jquery-to-learn-jsonp/
    1 point
  8. What you are describing is called JSONP (JSON with Padding). So the original data is valid, but not usable from cross domain. You can add own "cache" for it also (get the data through local php script) - but of course would be much more straightforward if JSONP would be available also. PS: I love the modules directory and modules manager! You rock fellas!
    1 point
  9. I just want to add a few statements: 1) PW-forum is the first forum, which makes me want to participate. 2) I got nice and quick support. 3) I love PW and therefore want it to be successful, but I'm personally missing nothing.
    1 point
  10. FWIW, I recently did something similar, but on various fields from $page->siblings with php's similar_text() function (and stopwords).
    1 point
  11. ok fixed this. It was permission problem... (smacks head.) had to make sure /site/config.php was readable. Clear case of the mondays.
    1 point
  12. Try this, at least you will be able to login immediately <?php $users->get("admin")->setOutputFormatting(false)->set('pass', 'yo123')->save(); taken from here http://processwire.com/talk/topic/490-how-to-reset-your-password-how-to-enable-the-forgot-password-function/
    1 point
  13. formmailer, yes I got it to work. ryan, I already found a hint from apeisa in another threat concerning include=all. I ended up with $published = wire("pages")->find("include=all, status=published"); foreach($published as $p) { The conditions regarding publish_from and publish_until are not part of the find. They are handled in the foreach loop. That solved my issue. Thanks both of you.
    1 point
  14. Can't comment on some of your questions, but let start.. ProcessWire "traversion" capabilities are more logical & better then seen elsewhere in CMS land. With a few switches or if statements you can find anything you want or exclude what you want. For forms & stuff, you're not bound to modules. You have the total freedom with PHP & you get the rely useful & understandable ProcessWire API for free. ( look at Soma's cheatsheet to get a point ). I stepped in in MODX This september, so started with Revolution. I always thought, MODX is a nice CMS, but lacked the overall vision. They added nice feathers, but they glue it to the core. Many things in my eye's are inconsistant or put where the don't belong. Working the MODX way give me a lot of trouble. Errors in PHP occurring in the cache, finding where some kind of variable is coming from, Unnecessary difficult ACL's. Don't allow me to disable cache ( even if I set: disable cache ). All "template" chunks & PHP snippets pilling up as high as the Mount Everest & then finding the way through that mountain. Not been able the really work with code on disk, cause all PHP etc is stored in the DB ( why the hell you want logic data in the DB ?) The must use of MOD FAST_CGI... I can continue but better to stop All things I mentioned above, is solved on a real clever way in ProcessWire. They don't just add things, adding things may have a big cost. I love the road PW is traveling. So no I don't want to step back
    1 point
  15. Chris - your English is far better than my German and reads well so don't worry about that - I always feel bad when people whose first language isn't English come to forums and apologise for their English when I can't speak much of their language "Wilkommen bei ProcessWire" is about my limit this morning I agree with diogo's points above. I'm sure someone made a module that allows for good blog-like tagging of pages (a specific tag fieldtype that was a bit like Wordpress) but can't seem to find the link - does anyone else know where this is? I have a feeling it might have been one of Nico's modules. As a long-time MODx user ProcessWire is now my main choice (and only choice) of CMS. It's the most flexible CMS I've ever worked with and every other system you use will feel too restrictive in comparison. There's nothing I could do in MODx that I couldn't do in ProcessWire - often it was a LOT easier in ProcessWire too! As an example, see this site: http://www.strategycore.co.uk/ - that all used to be MODx and now it's ProcssWire using a lot less lines of code than I had before. It does require that you learn a little bit of programming, but with a few examples you should get along just fine. I'd recomment the walktrhough tutorial here: followed by other tutorials in this forum: http://processwire.com/talk/forum/13-tutorials/ but often it's simple enough just to start building something and ask questions - we're happy to help. The Skyscrapers demo site is based on an older version so I don't think ryan has that available to download because a few things have changed, but the tutorials above will probably give you a better (gentler) place to start from anyway. Hope that helps
    1 point
  16. oop easier than no.oop. how abowt real objet likes coffey maker. $m=new coffeymaker(): $m->fillcoffey('frenchyroast'); $m->fillwater('750ml'); $coffey=$m->brew(); $me=new WillyC(); $me->drink($coffey); $t=new toilet(); $me->pee($t); and that.all there,^b^b^b oops $t->flush(); and thatall there is now.youknow oop(ee)
    1 point
×
×
  • Create New...