Jump to content

dragan

Members
  • Content Count

    1,524
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by dragan

  1. @iipa You probably have to update PW. It was introduced with 3.0.127: https://processwire.com/blog/posts/pw-3.0.127/
  2. You can easily change the order with CSS flexbox, i.e. place a custom link first, before pages. Together with the body role- classes, it would be a breeze to re-arrange the order (or perhaps use a different styling). A quick-and-dirty example: body.role-nonsuperuser li.page-10065- { flex: 1; order: -1; } body.role-nonsuperuser #pw-masthead .uk-navbar-nav> li.page-10065- a { font-size: 1.5em; color: yellow; font-weight: 800; } page 10065 is a custom dashboard page here, and with the first two CSS statements it puts the dashboard link first, and pages etc. after that - only for non-superusers.
  3. @Nicolas This looks like @Noel Boss's admin theme: https://modules.processwire.com/modules/admin-theme-uikit/ If you want to customize the admin theme yourself, you can clone the wire/modules/adminthemefolder/ to site/modules/. PW will detect that you have two such folders and ask which one to use. You've got the full monty in the package: LESS files, webpack etc.etc.
  4. Never had to use any such thing myself, but take a look here: https://modules.processwire.com/categories/social/ What exactly should this "comment system" do? Do you want to embed FB comments in your site? Something like this?
  5. That's weird. Re-ordering images shouldn't do anything besides.... re-ordering and nothing else. I don't get it. Is that text (This is intentionally invalid image data) displayed in the browser? Look in the page's asset folder. Are all your images still there? Also, check server- and PW error logs, and your browser JS console for suspicious stuff.
  6. Not related to search, but: Are these really three templates? i.e. do you really use them as PW-templates, or just as partials that you include() in the template? Perhaps this is useful: https://processwire.com/blog/posts/processwire-3.0.91-core-updates/ $pages->find("FieldtypeTextarea|FieldtypeText|FieldtypePageTitle%=coffee"); or this: Here's an example with PHP: https://stackoverflow.com/questions/9373023/how-can-i-get-a-summary-string-around-a-search-query-within-a-longer-string Here's a little JS lib: https://markjs.io/
  7. no it isn't. What makes you say that? Perhaps you should spend some time "learning the ropes" instead, before declaring an entire decades-long tried and tested scripting language as "awful".
  8. Well, I have never used this inputfield type, but did you also try sort=stars.count ?
  9. @rick Are you talking about FieldtypeStarRating? Perhaps you should better post it in the support forum thread instead. Anyway: did you already try to sort by that field and it failed? Give us some code examples of what you've already tried, so we can get a better picture of your setup etc.
  10. I'm quite happy with https://keep.google.com/u/0/ - use it across devices etc.
  11. uhm, this is purely frontend code and hasn't got anything to do with PW per se. Did you just copy-and-paste your existing code from somewhere? Just add class .open to the panel and adjust the right CSS value to -3px (inline style, same as when opened) slide-out-enquiry open
  12. I mean this: note the "active" checkboxes. OK, now I know a bit better what you mean. These pages are not created "manually" in the admin, but from a page-reference field that has the option "allow to create new pages?" in the field settings. If that is indeed the case, I wouldn't know what the expected / default behavior would be. Only create the page in the default language? (which seems to be the case). I don't know if that is configurable. I don't have time right now to investigate - maybe you'd have to use a hook to automatically activate all languages when creating a new page like that.
  13. Well, there are two things to watch out for: Is the page activated in the alt. language? How is the title-field configured in the alt. lang. page version? At field-level, you can define the behaviour of what's shown, in the details-tab: If you use the option shown above, you still have to make sure the alt. lang. page version is activated.
  14. Do you have an ___executeRefresh() method? There's plenty of infos in this old thread:
  15. Which "main menu"? In your frontend-template, or in the backend?
  16. Yep, that's certainly worth a try. See this announcement from @ryan https://processwire.com/blog/posts/using-innodb-with-processwire/ tl;dr: Row locking versus table locking (Inno vs. ISAM)
  17. I won't 🙊🙉🙈 I just realized the "view" link in the RF Tester (zooming glass icon) seems to be hard-coded: it's assuming my PW backend is "admin". This should probably be defined dynamically instead (or at least configurable). Also, I noticed the div.paginationPageSize is always showing "undefined" o_O
  18. What do you mean with "better standard"? You can move your custom process module within 2 seconds. That's not really too cumbersome, isn't it? In this example, dashboard + forms are top-level links in the admin, not under "setup". The "default standard" prevents breaking the top-level admin links to have too many items and therefore maybe breaking the navigation (visually, i.e. two or three rows instead of just one).
  19. @Lutz True. But maybe I'll have another setup where I need to query pages that live under different parents, and (theoretically) also could have identical page-names. @bernhard Now that sounds both easy and awesome (plus "safe", in the sense that a page ID is always unique, while page-names aren't - unless they are children under the same parent page). I've been playing a bit more with RF... pure awesomeness and fun. Together with Lazy Cron, Tabulator.js and RF, a small test-setup runs incredibly fast. (Lazy Cron to store the RF-output - JSON - once a day). Makes me almost sad I currently don't have a real use-case / client-project to use all this...
  20. Where? In the frontend or backend? If you're doing forms in the frontend, you have to write your own validation logic. Or do you refer to field dependencies in the backend ("required only if...") ?
  21. Sabre seems to be the market leader. Other hotel sites built with PW also use it. There's also https://hotelnetsolutions.de/cbooking-onepagebooking/, https://www.simplebooking.travel/de/ or https://www.dirs21.de/direktbuchung/
  22. That was an issue until v. 3.0.85, but apparently was fixed in 3.0.86. What PW version are you running?
  23. Two small questions (and I guess I know the answers already): a) I can't get any RF output (arrays, objects) to play nice with PW's pagination / renderPager(). I guess pagination expects a PageArray, not just any kind of array. I know RF was never meant to be used in the frontend, but I tried anyway (and of course, I know building my own pagination with something like Tabulator is quite easy). I just wanted to compare an existing page (how much speed I would gain using RF instead of native PF find). b) I tried queries like $finder = new \ProcessWire\RockFinder('parent=1041, include=all, template=project, sort=-year', ['title', 'year', 'modified', 'url']); url is not recognized. I guess because a PW page URL is not stored inside the DB as-is, but is created when calling the $page->url() method. Am I correct? (PW has to assemble parents(s), page-names etc.)
  24. This happens when I run setup/rockfindertester/, but Tracy is enabled. When I use RF code inside Tracy console in Chrome, everything's fine.
  25. I am getting ERR_RESPONSE_HEADERS_TOO_BIG in Chrome with the RockFinder Tester. After googling, I tried to add this line at the top: header_remove('Set-Cookie'); which doesn't change anything. Did you ever encounter this as well? Problem is, this even happens for really small datasets like limit=10 :-| In Firefox there are no such problems, even with huge datasets.
×
×
  • Create New...