owzim

PW-Moderators
  • Content count

    479
  • Joined

  • Last visited

  • Days Won

    4

owzim last won the day on March 12 2015

owzim had the most liked content!

Community Reputation

595 Excellent

About owzim

  • Rank
    Sr. Member
  • Birthday 09/09/1983

Contact Methods

  • Website URL
    http://owz.im
  • Skype
    chrauni

Profile Information

  • Gender
    Not Telling
  • Location
    Berlin, Germany
  • Interests
    Design, Frontend, Music, Cycling, Nutrition, Politics, Evolution

Recent Profile Visitors

8,867 profile views
  1. Works now, thanks a lot @Mike Rockett for reacting so fast.
  2. Thanks for the update @Mike Rockett. After the update: without trailing delimiters (foo;bar) I get: ProcessJumplinks: SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '-0001-11-30 00:00:00' for column 'date_start' at row 1 With trailing delimiters (foo;bar;;) I get: Notice: Undefined index: date_end ProcessJumplinks: SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '-0001-11-30 00:00:00' for column 'date_start' at row 1 This only happens if I input more than one line. If it's only one line, it works. If it's only one line, both values separated by the delimiter land in the source field, destination stays empty. Is there a reason, why you rolled your own CSV parser instead of using str_getcsv?
  3. Hi @Mike Rockett, I can't get the CSV import on 1.5.46 to work: Tried: foo,bar baz,qux foo;bar baz;qux foo,bar,, baz,qux,, foo;bar;; baz;qux;; In the cases without trailing delimiters I get: Notice: Undefined index: source Notice: Undefined index: destination ProcessJumplinks: SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '-0001-11-30 00:00:00' for column 'date_start' at row 1 With trailing delimiters, the jumplinks are created but source is empty and destination is a string: page:1. I made sure, no empty lines are present.
  4. A classic case of RTFM %#~* Thanks @Mike Rockett, this is brilliant.
  5. Thanks @Mike Rockett, the implicit option with {all} will suffice. I haven't dug too deep into all the options, but it would be great if mapping could be done without collections: source: project?id={someCustomField} dest: projects/{someCustomField} So that someCustomField would be a field of projects/ child pages, like $pages->get('/projects/')->children('someCustomField={value}'); This way one could simply migrate the ids of the old site over. source: project?id={oldID} dest: projects/{oldID} $pages->get('/projects/')->children('oldID={id}');
  6. Hi @Mike Rockett, this module is awesome, thanks! I have this collection thing going on: example source: project?id=1&foo=bar So I set it up like this: source: project?id={id}&foo=bar dest: projects/{id|projects} Works! But, when &foo=bar is omitted this does not work: project?id=1 How to make anything after id optional, I tried brackets, but it does not work. source: project?id={id}[anything here, but optional] Thanks!
  7. Often times, the RewriteBase rule is the source of a server error. Try tweaking that.
  8. Got it working. The source of the misbehavior was, that I set the string somewhere else afterwards, like so: $field->options = $optionsString; Doh! The side effects are still very strange though, and interesting that the field class even uses it somehow.
  9. I have this string of options: option1|Option 1 option2|Option 2 option3|Option 3 I add the options string like mentioned before: $manager = new \ProcessWire\SelectableOptionManager(); $manager->setOptionsString($field, $options, true); The result is this: If I add it with IDs 1=option1|Option 1 2=option2|Option 2 3=option3|Option 3 The result is this: In both cases within the field settings detail tab, everything looks OK, and the preview shows the expected output: Also: Changing the override argument to false, does not affect this behavior. In the database, everything looks fine: Debugging $inputfield->options in FieldtypeOptions:getInputfield, the options array looks fine as it should: Three items with an id, value and title. This is VERY weird: If I replace the return value in FieldtypeOptions:getInputfield // original return $inputfield; // replace $fs = $this->modules->get('InputfieldFieldset'); $fs->add($inputfield); return $fs; I get the correct output, in the given Fieldset: This suggests that the misbehavior is happening somewhere else? If I create it via admin, everything works as expected, only the titles show. Any help? Thanks!
  10. The additional settings will be very useful, thanks. The core inclusion of Parsedown and your module renders my module from 2014 redundant. I'll take it off.
  11. On Vimeo: What Comes Next Is the Future (2016)
  12. @Mike Rockett interesting content already. Would be cool if you implemented some sort of notification system, email, twitter or whatev, so one doesn't miss new posts, without visiting the site manually.
  13. This is 'classic Soma'.
  14. This is what the editor sees: This is what I see: There just one thing different about Standort (Location) and Veranstaltung (Event) compared to Bezirk (District): Both can be in multiple places within the site structure, so that one has to select a parent before creating (this is where only I get to): i.e. all locations have Calendars, which hold the Events. Access management is set to No to all of these. ProcessWire 2.7.2 Thanks!
  15. Yeah, well ... Thanks @Klenkes! That did it, wasn't aware of that. Sometimes I chose the complicated route over trying more obvious options. Those RTEs are dinosaurs anyway, my next PW installation will have Repeater Matrix and Ace-Fields only.