Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by dragan

  1. Yep, I'd guess that's the culprit too. I remember MODX Evo had similar problems (though I don't remember with which mySQL version exactly).
  2. Sorry for replying back so late, but it's been a hectic (and hot) week... I guess the reason it didn't work, was simply because some pages didn't have the correct / updated template .php assigned, and thus missing a newer include file. Mea culpa! Thou shalt not multitask, unless you are a machine. <slighlty off-topic> Seriously now - I really believe multitasking should be left to computers, not humans. I guess I was trying to build / fix / update too many things at once. And as is always the case in such situtations, small (but important) details get easily overlooked. </slighlty off-topic>
  3. Actually, I'm beginning to believe it's a server issue. On another site / server it's working perfectly. Could a multilingual site setup be a potential error source? (I wouldn't know why that would be the case, everything looks perfectly OK - just clutching at straws here...)
  4. Quite possible. The devil is always in the details. Thanks for your clarifications though. Will try again today with more caffeine
  5. OK, I'll try to rephrase it. I have this in leftnav.inc: $leftNav = $modules->get("MarkupSimpleNavigation"); $leftNavOptions = array( 'max_levels' => 3, 'collapsed' => true, // I guess this is the param that's not being executed correctly atm... 'show_root' => false ); echo $leftNav->render($leftNavOptions); For simplicity's sake, let's say I have this basic 08-15 site structure: - Company - Products - Downloads / Manuals - News Each of these main sections has sub-sections: max. 2 levels down. Now, no matter if I'm at the root page of "products", or in a detail-page within products, the menu always outputs the entire tree. Like a sitemap, everything from A to Z. But that's not what I want. Shouldn't "collapsed = false" take care of that? The idea is to have a basic HTML list that only displays the top-level hierarchy as links. But when I'm further down in level 1-2-3, it should recognize this... "ah, that's my home category, let's open up this navigation tree as well to show where we live". Right now, all levels / sections are open all the time, at all levels, everywhere. "Collapsed" parameter true or false: doesn't change anything. So e.g. if I'm visiting a product page (= 1 level down inside "products"), it should only render: - Company - Products -- product A -- product B (= active) -- product C - Downloads / Manuals - News But what the module actually does, is showing every single page, no matter how far up or down you currently are. Surely that was not the intention of the module? So either I'm completely misunderstanding how this module is supposed to work, or it's some kind of bug. I'm sure I could visually hide the superflous elements via CSS, but I'd rather have the module not render them in the first place... in a nutshell: a) show only top-level links + b) but also show (nested) sub-levels if I am in inside this parent category, right down to the child (or grand-child document).
  6. Well, every single page is being rendered as list / link, not just the top most hierarchy.
  7. If I only want to show the top-level items, what would be the correct options? I tried 'max_levels' => 1, 'levels' => false, 'collapsed' => true, but I still get all items. Is this module "overkill" if I only want to list topmost pages? Should I be better just using a simple selector and foreach, to output such a simple nav-list?
  8. Was looking for that feature as well, and found this thread. Works like a charm with purl.js + highlight.js!
  9. It was with trailing slash (apart from CSS copied from sample install). Perhaps a little note in the docs wouldn't hurt, that's why I added my last comment. Just in case someone else stumbles upon similar gotchas tl;dr: Rename your id 1 page, and GET params won't get passed along anymore.
  10. I can now replicate this behaviour: When you rename the "name" field of the home page (the URL alias), the GET parameter never arrives. That's probably what you meant with Is this a bug or feature? Anyway, I'll better leave the homepage (id 1) as is in the future, i.e. blank (/).
  11. Nice. Just used this button for the first time
  12. Nice! I now added the JS and CSS bits in BOTH wire + site folders. Just placing them in one or the other didn't. This is cool. Works like a charm. Thanks again!
  13. Thanks! I really appreciate the time you took for this. After all, it would only be a "nice to have" feature, nothing else. I tried to add the CSS and JS now, but it doesn't work. Google Chrome console shows a JS error: Uncaught TypeError: Cannot read property 'length' of null in wire/modules/Jquery/JqueryCore/JqueryCore.js?v=183 Where did you add your last JS code? in main.js, install.js or inputfields.js? I tried it in the latter two, but it didn't make any difference. (latest stable 2.3.0 install here, if that matters...)
  14. Thanks. I never really knew about fieldset_open / fieldset_end. Stumbled over this forum thread also: http://processwire.com/talk/topic/665-editing-fieldsets/ It will surely come in handy at some point. Although I do save some space now, I still didn't find a way to actually be able to display image thumbnails next to each other (3 or 4 in a row). Is that somehow possible? e.g. I have two fieldsets: content 33% (everything else than images) + images 67%. But the thumbnails are still displayed one on each row. Is it not possible to change the CSS properties of the image input field? I tried editing .InputfieldImage in wire\modules\Inputfield\InputfieldImage\InputfieldImage.css with no luck
  15. I only now discovered that it's possible to declare individual input-field widths. Excellent feature! However, image-fields are not supported. Well, the fields are resized, but it seems to be still "display: block" i.e. each image-input field is displayed one below the other. With image-heavy pages, it would be cool to say e.g. "image input field: width: 33%" and being able to show more images per row. This would make sorting much easier. Right now I have to resize the browser content (CTRL -) so I can see more images per screen real estate. Even then, I have to often move an image up or down several times to reorder them. I guess all it would take is changing / adding a CSS property somewhere? e.g. from "display: block" to "display: inline" or similar.
  16. Turns out the hoster actually IS using mod_sec and blocks certain URLs; got whitelisted now after talking to support. The internet isn't what it used to be...
  17. Thanks. I changed it back to GET. However, when doing so, I get an absolutely puzzling 403 error for one certain tag only: No umlauts there, and it appears in two images. Using one of the other tags for the same images, it works fine. I could maybe understand an error 404, but 403? e.g. tags/?tag=poker = error 403 these work fine: tags/?tag=cardgame tags/?tag=gambling tags/?tag=jassen tags/?tag=Jass Guess my hoster is paranoid and blocking certain keywords... o_O
  18. Funny how small this planet is... I grew up in Regensdorf Gretag doesn't exist anymore, it was liquidated in 2004 (now the buildings are rented to various new companies).
  19. I stumbled upon a problem with URL segments. URL segment 1 is supposed to be the image tag. Works fine (= 2nd half of your example code "find all pages with the supplied tag") However, when I call a page like /tags/Genève I get an error 404. In other words: image tags with umlauts (àèöéç etc.) are not being recognized when called with $tagvalue = $sanitizer->selectorValue($input->urlSegment1); Do I have to change something in the code or config to make image tags work with umlauts? btw: simply using page/?tag=Frühling works fine, i.e. $tagvalue = trim($_GET["tag"]);
  20. That works like a charm! Thanks again. iirc, image tags are supposed to be separated by space, so the two lines if(strpos($tags, ',') !== false) $tags = str_replace(',', ' ', $tags); if(strpos($tags, '|') !== false) $tags = str_replace('|', ' ', $tags); can be omitted. The URL segments tip is golden, I definitely have to explore that further. So far, I've only used it in a multi-language setup. Didn't even occur to me to use that here...
  21. Awesome, thank you! I'm on the road today but I'll tinker around this evening and tomorrow. (btw, the much bigger work is actually tagging thousands of pics in the first place...)
  22. Excellent! Thanks so much.
  23. Thanks, but that's not what I'm looking for. I need individual tags for each image. I can set them alright, finding all of them is where I'm a bit stuck. AFAIK, this was only introduced in PW 2.3 - the blog profile is 2.2. The tags there are per page, not per image. I'm already familar with page-selectors, the page input field etc. It's the specific image tags I'm having problems with.
  24. I decided to rebuild an old image gallery site with PW. I know there's countless image-gallery scripts out there, but for my liking, most of them are too bloated. Also, I thought this was another good opportunity to dive further into PW-world. I'm keeping the old basic gallery structure: 95% of the galleries are in date-folders (monthly), like a blog archive. But I'd like to add some filter / search functionality, because there's just so many pics - when you come to the site and look for a specific subject, there was no way to do that on the old site. Q 1: How can I create a simple "search by image tag"? I want the results to list all images (thumbs) with tag x, and a link to the parent page. Q2: How would I most efficiently grab all tags from all pages, all images, and present it alphabetically (not necessary a fancy tag-cloud, but making sure I list each unique tag only once)? So when the user clicks on one tag link, he sees all image thumbs that have that tag on the results page. $p = $pages->find("images.tags~=$tag") works fine. I can explode("|", $p) to get a page-id array, but where would I go from here? A tag can be any anywhere, in various galleries (pages), and most pics have multiple tags. I'd like to group the results by page, so I guess I need to add 1-2 foreach loops, no? Can somebody help with some example code? I'm a bit stuck right now.
  25. Sure: http://dnik.ch/050506/
  • Create New...