Jump to content

teppo

PW-Moderators
  • Posts

    3,262
  • Joined

  • Last visited

  • Days Won

    112

Everything posted by teppo

  1. @horst: sorry, no idea. I don't see any reason to use this module over VersionControl on a 2.4+ site, to be honest
  2. RT @codinghorror: I never get tired of watching this video. I've watched a dozen times. It is the reason I get up in the morning. https://t…

  3. Note to self: set up autosave and/or proper confirmations. Just lost a whole chapter of text by accidentally swiping left with two fingers.

  4. This is the course I wish I could've taken *before* I started building stuff for the web: http://t.co/m93NV8pkev. Still enjoying it *a lot*.

  5. Thanks! To be honest this seems to be out of the scope of this module. I've been going over your suggestions a few times in my head, and while I think I could probably implement something like that to this module if I really wanted, I don't really think it's a good idea. Drafts would most likely be easier to implement using a completely different approach. Ryan took some steps towards drafts support a while ago, so you might want to see where that goes. If Ryan implements that as a core module, I've no interest in trying to duplicate similar behaviour here. Though I haven't used any of those that much, there's also Process Preview by Nico, Page Draft Creator by Rob, and Process Page Drafts by Jan Romero; you could always give one of these a try.
  6. Not familiar with your particular issue, so I'd start from the basics: have you checked error logs yet? A 500 error should leave something in the Apache error.log, and that something should at least point us to the right direction. I'd also check PW log files, especially /site/assets/logs/errors.txt, for any inconsistencies. Edit: additionally, please make sure that /site/assets/cache/ and /site/assets/sessions/ are writable by the Apache user.
  7. RT @chrismessina: The state of the art in terms of service UIs on TV from @netflix. Ready to read 106 pages of legalese? http://t.co/FkbZAY…

  8. RT @processwire: New blog post: Target templates w/field editor, better field clone & tons of session updates… https://t.co/LEjo8EHiyc (Pro…

  9. I think the issue Soma is referring to was that in fact only the person originally reporting the issue (or Ryan) can reopen a closed issue at GitHub. Last time this resulted in a bit of a mess when existing issues (and feature requests) where the reporting person had disappeared were closed and reopening them seemed rather difficult. That's why I really don't believe in this strategy either. If there's a bug report, discussion, or feature request, it's probably there for a reason, and closing those en masse feels plain wrong On the other hand, I do believe that issues that are solved can be swiftly closed without waiting for an answer. I also generally speaking agree with what's being said here, i.e. that these figures matter. Helping Ryan by tracking down any bugs and commenting on feature requests etc. sounds like a potential first step towards this goal to me.
  10. Got a coffee ticket as a compensation for the train being over an hour late. Tried to cash it in, but they're out of coffee. #doingitwrong

  11. It's been a while, but just for the record: this issue (or at least one with identical symptoms) has been fixed some time ago.
  12. @majkiris: it's quite simple, really. Groups are just pages and view/edit permissions are defined by page fields view_groups and edit_groups. There's also a separate manage_access checkbox field, which defines whether a specific page manages permissions itself, or if it uses permissions from one of it's parent pages. If you want to add a new group, just add a page with template user-group under the groups page at Admin. If you want to grant this new group view permission to a page, find the page and add this new group into its view_groups field. Then save the page, and UserGroupsHooks.module should handle the rest -- though you might also have to enable manage_access (setting it to '1'), can't remember how exactly this worked. Hope this helps a bit. Please let us know if you need more specific instructions.
  13. This is solvable by using Jumplinks, but especially if there's a potential of a lot of traffic, redirect at .htaccess level would be more efficient. Jumplinks is flexible and easy to use, but the downside is that the whole system has to be started just to realise that "oh, this request doesn't belong to this site at all". Waste of time and resources, really Never seen this particular issue, but it sounds like you're, perhaps, doing this at the end of your .htaccess file, or something like that? The .htaccess file adds ?it=... and in a case like this that part of it shouldn't run at all. As a first step I'd try moving this as close to the beginning of the .htaccess file as possible. This is a simple redirect, so it's quite likely that the issue is something simple too
  14. Especially if the site is working otherwise, i.e. you can navigate pages and so on, this sounds more like a compatibility issue with URLs in use (or perhaps something else in Plesk) and ProcessWire's method of finding out required paths. Much of related magic happens in index.php, so that's where I'd start looking. Never used Plesk myself, and sadly it seems that I can't get my hands on one of those without paying for it, so I probably won't be able to debug this further
  15. RT @processwire: New blog post: a new Fieldtype for supporting selectable option fields (w/o pages) in ProcessWire (2.5.17) – https://t.co/…

  16. Regarding HHVM, this could be of interest: https://processwire.com/talk/topic/5226-does-processwire-work-with-the-hiphop-virtual-machine-hhvm/
  17. Exactly. It would be nice to know a) how big the need really is, and b) how much work is needed to add and maintain this. I don't have anything against IIS, but it's also very unlikely that I'll ever need it either. We've already got native support for Apache, and personally I'd like to see native support for nginx too. On my list that's much higher than IIS. .. although I did specifically make the Changelog module IIS compatible, so who am I to speak
  18. Technology is no longer a barrier for remote work. Outdated and/or misinformed attitudes are.

  19. "Adventure games from the 1990s are notorious for puzzles that are obtuse and often nonsensical". But isn't that exactly why we love them?

×
×
  • Create New...