Jump to content

LostKobrakai

PW-Moderators
  • Posts

    4,956
  • Joined

  • Last visited

  • Days Won

    100

Everything posted by LostKobrakai

  1. Any 3rd party or custom modules installed?
  2. Feel free to support my request for it here: https://github.com/ryancramerdesign/ProcessWire/issues/932. I could try to implement this in the module, but I'd rather not do it. If Ryan implements it, then other inputfields can be compatible, too.
  3. It's actually not the really the hidden field in this case but this rule: .Inputfields .Inputfield:not(.InputfieldSubmit)+.InputfieldSubmit{ clear:left; } This will hit no matter of the visual setting of the hidden field.
  4. $german = $languages->get("german"); $germanDesc = $page->myimage->first()->description($german); // returns a json string of all languages $json = $page->myimage->first()->description(true);
  5. Just use insertAfter / insertBefore if you need buttons to not be appended after the hidden input: https://processwire.com/talk/topic/9832-how-to-create-an-action-in-an-admin-page/?p=94500
  6. With lot's of page tables and page fields (which even get hiccups from time to time with the nativ import) I like to port templates and fields manually. My current project is already in a state where lots of things are manually copied over (lot's of id inconsistencies) so maybe I should give the module another try on a smaller, more controlled environment first.
  7. You're using subfields the wrong way. "features" holds a few pages, which on their own hold fields. E.g. "features.title=Garden" would find all properties, which has (at least one) page selected in features, that has a title of "Garden". Subfields are in this case all the fields of the linked pages. You should be aware that theoretically titles could not be unique, therefore if you can't be sure about that you could fallback to using the id instead if the title. If you query multi-pagefields directly, then it automatically queries for id's so "features.id=1015" is the same as "features=1015".
  8. Go to the template of the pagetable page. Click on "title" and chose "Hidden. Not visible in the Editor" or similar in the "Visibility" dropdown.
  9. @adrian Migrator works for you? I've tried it once, wanted to move a branch of the pagetree to staging, but it did import all the pages, that where linked by pagefields, as siblings of my branch, while all of them where already part of the staging environment. Also I'd like a option to just export pages (trees), without fields / templates, as I like to use the native ex-/import of both.
  10. I cannot tell from experience, but I don't think you can make it perfect the first time. I'd do two things: Make a list of "technical words" (hooks, urlSegments, templates, …) and try to translate them. And on the other hand just start translating with the help of this list, maybe append things to it on the go.
  11. Users aren't actually the only part where this workflow is flawed, while maybe it's the most obvious. You've the same problem with every bit of dynamic page content in contrast to more "static" pages, that are manually created for things like structure. There's no real way to update only the first or only the latter – it's one pagetree full of pages. I don't know any easier way to update a page other than using maintenance downtime to do so.
  12. Without a solid drafting feature I'd suggest writing content externally as soon as multiple users are working on text.
  13. The listed script snippet is part of the jquery core library, which should be rather stable. Please refresh the modules in the backend and hardreload the browser to clear your cache. If the error persists, please report back.
  14. There are ways to change the url (and therefore path) of a page, see here: https://github.com/apeisa/Multisite/blob/master/Multisite.module. It just could be less efficient, as this hook can easily hog resources as url is quite often called property.
  15. With FieldtypeOptions there would even be a more lightweight alternative to using pages for storing the tags.
  16. @fenton PageTables are something different to the Profield: Table. But to answer your questions: While both things are possible, they can only be achieved with extensions of the core by modules. For the first one, keep in mind that the page, created by the pagetable, does not differ from other pages. It does not know it's part of a pagetable. Only the data stored for the field does include a reference to the page(s).
  17. PageArray's are not compatible to PageFiles, but you should be able to import both in a single basic WireArray.
  18. The problem aren't people who actively turn off their javascript, but rather all the cases where it's execution breaks. Just be on a train with bad network, then you're happy if a page is "accessable" without js. No need to fully support all fancyness, but make the html base usable without js.
  19. The same error occurs when pages with pagetables are cloned.
  20. if($page->Background_Image->count > 1 ){ $bgimage = $page->Background_Image; echo '<script>$.backstretch(["'; echo $bgimage->implode('", "', "url"); // results in url", "url", "url echo '"], {…});</script>'; } }
  21. The contents of the "ProcessWire-master" should be uploaded. Of those five site-* folders there will only be one left after the installtion.
  22. This is certainly possible, but should most likely not be done as part of the admin backend, but via modules. There are various point where you can hook into the core functions to inject your validation rules. The most obvious would be Inputfield(Name)::processInput or Pages::save.
  23. This is already on the Wishlist, but named a little different. https://processwire.com/talk/topic/9730-get-pages-used-by-a-pagefield/
  24. I don't think there's a module for this, but it's kinda easy to circumvent timeouts. You'd build a php file that calls a reasonable number of users (1000 or so) using the pagination feature of processwire. The results are then written / appended to a file somewhere in the system. And the php then returns the next pagenumber, at best as simple json string. Now you'd just build some js, which calls the same page via ajax and iterates on as soon as the response is returned. After 40 calls you've your full csv. Another way would be using some SQL, to get all user id's and select the emails directly from the email fields table.
  25. Any reason why you'd use this version? There where a lot of different fixes leading up to 2.6.0 so you should really be using it if you want a stable installation.
×
×
  • Create New...