Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/23/2015 in all areas

  1. I plan to give this all some serious attention next week. I'll get some updates out soon.
    2 points
  2. Just as a follow-up to the shortlinks tutorial posted yesterday: Jumplinks can also come in handy if you want to redirect ID-based URIs. This is a result of the Destination Selectors feature I added a while back, thanks to the suggestion by Macrura. The Process: Let's say you have a Journal located in the root of your page tree, named journal. Each journal entry is assigned to the journal-entry template If you want to redirect ID-based URIs to their named equivalents, create a new jumplink like so: Source: journal/{id} Destination: [[template=journal-entry,id={id}]] So, when requesting /journal/1078, for example, you'll be redirected accordingly to /journal/hello-world/. Of course, you could take this further, but this is just a basic idea. Might be handy for someone using Jumplinks.
    2 points
  3. As briefly discussed earlier with Ryan (http://processwire.com/talk/topic/1560-searching-multiple-fieldtypes/page-2#entry23307), I tried to build some sort of test suite for ProcessWire. The tests aim for selector consistency (in-memory and db) and of course making them free of bugs - once and for all. The beginning of the test suite with instructions can be found from https://github.com/niklaka/ProcessWireTests . I wouldn't be surprised if I had to go and restructure the whole thing sooner than later (more than once even), but that'll do for now. Next I'll focus on writing a basic set of tests to cover at least the most common selectors (as there's currently only a few of the most simple ones there). This testing stuff if somewhat new to me and I've been reading lately a little something on the subject. Hope I got at least something right . Having said that, any help (or constructive criticism) from you my dear friends is highly appreciated. Especially if you'd happen to have any/some experience on testing - but I'll take kind words from anyone . I decided to try where I'm able to get with PHPUnit and so far it looks like it would be very much possible to build something useful with it (no, I'm not exactly surprised as it sure is a proven tool for such a thing). I did take Ryan's idea of using Skyscrapers profile as a base for testing (you're not making changes to it are you Ryan ), but there may be need for some other approach as well, even another Skyscrapers based one. Well, I'll go and write a a couple of more tests now. (PS: If some admin feels this post fits some other area better, please do move it - I wasn't sure where to put it myself.)
    1 point
  4. Want to use Mandrill for sending emails using their HTTP API rather than SMTP? Read on! I've been working on a WireMailMandrill module for a site I'm currently adding some features to. So far, the module has been tested for simple mail sending, with basic options, and attachments. I haven't tested the full range of things that are possible with the official Mandrill PHP library, but I think I've implemented the ability to set most, if not all, of them. This should be considered beta and not entirely relied upon for sites in production. Testing and feedback welcome. I'm sorry about the lack of code comments at the moment as well, I was just throwing this together as I went along so I could move onto the next part of what I was building... This was originally mentioned in a discussion about SendGrid and Mandrill options in a thread in the Form Builder support area. Not everyone has access to that, which is why I'm putting this here WireMailMandrill on GitHub Quick example (taken directly from a site I'm working on): $mail = wireMail(); $mail->from('info@example.com', 'ExampleCOM Enterprises'); $mail->to($toMail, $toName); $mail->subject('Entry confirmation'); $mail->bodyHTML($bodyHTML); $mail->attachment($myPage->files->first()->filename); $count = $mail->send();
    1 point
  5. Hi Guys, I've only ever met one other person who uses Processwire (mainly as I told them too and i was wondering if there was many PW users in london and whether we should get togther for a drink sometime? ben
    1 point
  6. Yes, it is JavaScript. If an element is in the viewport, another element is set to fixed position until the element goes offscreen. In UIkit it is called the "sticky" component (the linked site does not use this one): http://getuikit.com/docs/sticky.html
    1 point
  7. The code on the post above is not full proof, if the process is interrupted for any reason, you would have to start over. The ideal would be to, on each iteration, read the last line of the file, identify the user, find the next user, and write the next line.
    1 point
  8. Sorry Antti. It's all good. I'm going completely mad.
    1 point
  9. If I use this I don't see the Delete tab either: <? echo $fredi->hideTabs("children|settings")->setText("Edit your page")->render("title|body"); This works fine though: <? echo $fredi->hideTabs("children|delete|settings")->setText("Edit your page")->render("title|body");
    1 point
  10. I know I am enjoying the recent changes to this module. Thanks for the new edit links.
    1 point
  11. While I was it, I decided to tackle the PageTable problem also. So now the version 1.1.1 works with PageTables also (it's modal inside modal, so not exactly the dream come true, but it works if you need it).
    1 point
  12. Just pushed version 1.1.0 to github. Please let me know how it works. I went pretty closely with Bernhard's original css stuff, I also added options to hide additional tabs. Although I have feature detect for touch, when hovering is not required to see edit links.
    1 point
  13. Updated my fork to 1.2.6: https://github.com/rolandtoth/ProcessWire-MarkupSitemapXML/tree/master The readme file is updated with info on the new features: auto generate sitemap on module submit ajax button to generate sitemap comments feature in exclude list
    1 point
  14. http://web.archive.org/web/20120819010829/http://lukasepple.de/blog/2012/08/grundlagen-processwire
    1 point
  15. Seeing the same issue here in 2.6.0, MySQL version 5.5.42-37.1-log. Error is being generated by /wire/modules/Fieldtype/FieldtypeComments/FieldtypeComments.module: if($createdVotesTable) try { $database->query("ALTER TABLE `$table` ADD `upvotes` $upvoteSchema"); $database->query("ALTER TABLE `$table` ADD `downvotes` $downvoteSchema"); $schemaVersion = 5; } catch(Exception $e) { $this->error($e->getMessage(), Notice::log); } Without any deep understanding of what's happening here, I assumed it just needs to check if the columns exist before adding them, so I added some logic based on some other column-checking code I found elsewhere in PW: $isUpvotes = $this->wire('database')->prepare("SHOW columns FROM `$table` LIKE 'upvotes'"); $isUpvotes->execute(); $isDownvotes = $this->wire('database')->prepare("SHOW columns FROM `$table` LIKE 'downvotes'"); $isDownvotes->execute(); if($createdVotesTable) try { if ($isUpvotes->rowCount() === 0) $database->query("ALTER TABLE `$table` ADD `upvotes` $upvoteSchema"); if ($isDownvotes->rowCount() === 0) $database->query("ALTER TABLE `$table` ADD `downvotes` $downvoteSchema"); $schemaVersion = 5; } catch(Exception $e) { $this->error($e->getMessage(), Notice::log); } This seemed to work, and it reported that the FieldtypeComments schema was updated from 0 to 5 -- not sure if this the desired outcome. The errors have stopped, although I have no clue if that's a good thing...! Also, just tried installing FieldtypeComments on my local machine running PW 2.6.0 and MySQL 5.5.39, and it seemed to work fine without this modification. My "fix" is probably not the right way about it, I'm guessing.
    1 point
  16. today I installed the latest dev (2.6 dev) and tried to install language files into the default language. The language files aren't visible, but the backend is translated. Clicking different pages or buttons in the admin result in a fatal error: seems, there is something broken in LanguageTranslator.php EDIT: found 2 corrupted language files, which caused the problem. Replaced them --> all fine!
    1 point
  17. This is exactly what I'm doing, and I've had the same experience: no more false SPAM. Such a great service. This new module is going to open up new possibilities I'm sure!
    1 point
  18. This is great Craig, thanks. These guys certainly note the benefits of using their system via API rather than SMTP: Not tried their system but it looks good, like another Mandrill. The benefits of using Mandrill as an intermediary for sending email are many. For me, switching to Mandrill (using Horst's excellent Wire Mail SMTP module) meant that all emails got through—I no longer had occasional false spam fails.
    1 point
  19. There is a comments fieldtype that makes adding comments to pages a breeze. Since reviews are some kind of 'comments', maybe you can use that module and then extend it to add a rating star system. EDIT here's a thread about adding additional fields to the comments system https://processwire.com/talk/topic/2898-adding-additional-fields-to-comments/
    1 point
  20. Alwaystrynewthingsandgetbetteroralwayadothesameandstaygood.
    1 point
  21. I have made a module for you (all). I have had allready a routine that iterates through all pages and clears all imagevariations. But this only can be safely used if you have not used images in RTE's from the same page. If you have done so, those cannot be identified and gets deleted too. So please double check that you do not use Pageimages in your RTE fields before running this module. To run it you have to install it, go to its configscreen and check the box to run it. Also there is a second box, always checked by default, that let the script run in testmode. In testmode it doesn't delete the variations but list all found pages and the images count. So, if you really want to delte all ImageVariations sitewide, tipp the box to run the script, untipp the box to run it in testmode and press the submit button. PageimageRemoveVariations.zip EDIT: better use this enhanced module version from @tpr, with configuration for excluding imagefields: enhanced version!
    1 point
×
×
  • Create New...