Jump to content

teppo

PW-Moderators
  • Posts

    3,208
  • Joined

  • Last visited

  • Days Won

    107

Everything posted by teppo

  1. +1 for "modern" for the reasons Adrian mentioned.. and because the "warm" color scheme gives me this nostalgic feeling I can't quite explain. It feels comfortable (kind of like 80's product design and advertising), but doesn't really match my image of ProcessWire as a present-day top-of-the-line software product
  2. minimize.pw (@minimizepw) is an image compression service for #ProcessWire. Commercial, but free for small-scale use.

  3. Some time ago, while debugging a misbehaving site, I found out that one user had a habit of hitting shift + enter at the end of each line in the editor. That made sense as an attempt to gain more control over the typography, but it also explained the situation.. especially since the site in question was responsive. Making each <br /> visible could've prevented that whole mess -- or at least made it easier to understand why it was happening
  4. PuPHPet seems very interesting; setting up web development environments via simple GUI: https://t.co/Rmkyk5JNRo

  5. RT @spinlock: Teaching my kid the ins and outs of iOS development. Lesson one: forming strong opinions and arguing on the internet.

  6. Agreed -- and I'd like to add that in some cases even the page names and/or titles themselves could be considered confidential data. I'm thinking about things like closed intranet for managers, working group discussions etc.
  7. @ryan: I'm not 100% sure that we're talking about same issue here, though I thought they would be related as symptoms are practically identical. Previous case where this happened was when page A had field that referenced page B.. which had a field that referenced page A. With page fields (strictly speaking fields where the value is instance of Wire) change tracking does something I can't quite grasp -- instead of answering the question "has field value changed", it seems to check if object that field references has changes. Different kind of circular reference issue, perhaps? Just to be very clear: apart from what this module was doing earlier, I've never had/seen any reason why page should be able to reference itself.
  8. Just for the record, similar issues have caused me a lot of headache over last month or so; the more I work with page references, more obvious it becomes that something is broken. Even though there's a way around it here (and usually in other cases too), I really hope that module authors wouldn't have to jump through hoops to achieve something that should be a no-brainer. Sorry if I sound a bit agitated, but having spent literally hours in my last module to hunt an issue down -- only to find out that it requires what I'd consider an ugly hack to get over -- has that kind of effect on me
  9. Soma: edited my previous post. Didn't see couple of latest posts until after writing that (and also misread some points), so you can simply forget most of that now.. By the way, Modules Manager Notification looks awesome!
  10. Edit: this message was written before reading posts above and makes no sense anymore.. weird things going on with cache, I think. Anyway, thanks Soma, problem solved!
  11. "The most unknown parts of PHPUnit". Just learned couple of neat new tricks. http://t.co/bVbphlIbjG

  12. RT @smashingmag: Looks promising: a small library for manipulating lists via swipe and drag gestures, Slip.js. https://t.co/UC5lIQ0okb

  13. picture.0x100.jpg and picture.232x176.jpg are size variations dynamically created by ProcessWire. Original image is saved as picture.jpg, that's all. Directly uploading image with FTP won't do any good, since PW won't know about it, i.e. there's not going to be required metadata to support it. If this image field of yours is called "images", see contents of database table "field_images" for an example. Each uploaded image gets a row of data in table associated with the field it's uploaded to. I'd still suggest that you don't attempt FTP upload + directly manipulating database content, unless you absolutely have to, as that could result in issues elsewhere.
  14. And here I was questioning their motives, thinking that the money each vote brings in would be too tempting.. good to hear that it's actually fair too @apeisa: I know.. "all publicity is good publicity" and so on. Just saying that there's a flip side to that coin too
  15. RT @stop: Benefit # 14,792 to use Twitter: Receive advice on what to do if your dog gets sprayed by a skunk.

  16. I'm *not* a fan of anyone deciding for me whether or not a link opens in new window / tab, but this is the one case where it might make sense. I'm not too fond of the "even content authors should be able to get used to it" explanation either, partly because I myself keep forgetting it.. Form Save Reminder helps a lot with this issue, though. As a matter of fact it's one of those 3rd party modules I think should definitely be baked into core and even enabled by default. By the way, Ryan, this is probably wrong place and time for this, but were you aware that modules directory is currently doing exactly the opposite of this? Module links are catching mouse middle button clicks and redirecting, effectively overriding commonly used setup where middle click opens link in a new tab. (It's driving me nuts, another quirk I just can't seem to memorize..)
  17. @SiNNuT: agreed. I believe that PW deserves to win this one, but votes like these are still mostly bullshit. Bitnami should at least require authentication via another platform or something similar in order to keep their "contest" (even remotely) fair. Sure, malicious users will find their way past that limitation too, but at least it'd look like the people responsible for the contest actually give a shit..
  18. Probably should've mentioned in my last post that it's, of course, possible to support both $db and $database simultaneously. Ryan posted an example of this in the first post of the thread linked above. That would make sure that your module works now and in the future releases, though I must admit that I still haven't added this to any of my own modules either.. Oh, and by the way: this module seems very useful. Had a quick look and so far I'm liking it very much
  19. @Larry: just had a very quick look around and.. well, so far things look amazing (probably 'cause parts of this remind me very much of how Zend Framework works.) Will definitely dig in further
  20. Minor clarification: Since current master doesn't yet support PDO and according to Ryan 2.4 will be backwards compatible with earlier versions (thus supporting $db and MySQLi) "in near future" might be a bit of an overstatement here. If this module needs to work with current master (stable) branch of ProcessWire, $db is a requirement.
  21. "Responsive Design Isn’t Good Enough" http://t.co/8d5bjWWwrw

  22. At the moment ProcessWire is in second place in Bitnami contest. If you'd like to see PW packaged by Bitnami, vote: http://t.co/K3EJf8NaEm

  23. @landitus: you're right in that using the code I posted earlier message would get sent every time user is saved, which probably isn't correct behavior. One way to achieve what you're describing here would be by simply adding a check for changed status (published). You might want to take a look at Process Changelog for some sample code. "@" character was missing by purpose; in PHP adding @ before function such as mail() suppresses errors. If you're relying on these emails getting sent, this makes very little sense, as it just tells PHP that "if this fails, no worries, just keep going as if nothing happened!"
  24. Two missing letters, serious headache. Thanks a bunch, Font Awesome. http://t.co/bIIiH6lbQA

  25. RT @brad_frost: Thanks to Hertz, I will no longer be sleeping tonight. http://t.co/ZrNlhUJyKW

×
×
  • Create New...