Jump to content

teppo

PW-Moderators
  • Content Count

    2,217
  • Joined

  • Last visited

  • Days Won

    43

teppo last won the day on April 9

teppo had the most liked content!

Community Reputation

4,024 Excellent

About teppo

  • Rank
    Captain Earth
  • Birthday 08/21/1984

Contact Methods

  • Website URL
    https://weekly.pw

Profile Information

  • Gender
    Male
  • Location
    Finland

Recent Profile Visitors

44,038 profile views
  1. I'm wondering if the "override core module / multiple copies of the same module" feature would break after this, i.e. will ProcessWire understand that a .module file in /site/modules/ is a replacement for a .module.php file in /wire/modules/? This might not be an issue (can't check right now), but in case it is, then this should only be considered as a part of a bigger update, as it's a breaking change.
  2. teppo

    PW Review

    Related to links, I would also consider adding an underline – or some other obvious visual feature – to links. It's a little thing, but can make a notable difference in terms of accessibility: colour should never be the only thing separating text elements. Same thing goes for things like menus, i.e. active state shouldn't be communicated using colour alone Keep up the great work! Looking forward to featuring PW Review in the Weekly. How I wish that clients would sometimes say this too...
  3. I've been using a very similar solution at weekly.pw, i.e. indexing data into a field called "search_index". The content is mostly built using PageTable, and I'm indexing content from those for the parent page's search_index field as well. No Repeaters or RepeaterMatrix fields here, but they'd require similar processing. The whole solution is built into some methods placed in /site/init.php. Might be useful for someone, so here's the code: https://gist.github.com/teppokoivula/83036c6e73d7460be7706def620d80d4. Note that in this case I'm not using the same index as an excerpt, but rather the summary field of the page. Excerpt would be better – will probably add them at some point. Once you have the index at hand, it's relatively simple Another thing to note here is that I'm currently using the same index field to store links in link:url format. Since tags are stripped from the index text, URLs wouldn't otherwise be a part of the index – and this also allows me to perform specific link queries, such as https://weekly.pw/search/?q=link:https://modules.processwire.com/modules/sanitizer-transliterate/
  4. Hi there, That's somewhat odd question to post to a support forum dedicated ProcessWire, a PHP based CMS/CMF – but no worries, here in the Off Topic area all questions are fine Personally I've not used Redux that much, but have you already checked their own tutorials? The basic tutorial (https://redux.js.org/basics/basic-tutorial) and the advanced tutorial (https://redux.js.org/advanced/advanced-tutorial) should give you a solid understanding of Redux.
  5. Moderator note: this is not a support board for a new module, so I'm moving it to the General Support area of the forum. The "Modules/Plugins" section of the forum is for dedicated module support threads. If you have a general question regarding ProcessWire, ProcessWire core modules, or "how to do [x] with ProcessWire", you should post it to the General Support area – or if it's a question regarding an existing module, check the "Support Board" link from the modules directory entry for that module and post your question to the linked thread instead. Thanks!
  6. Moderator note: this is not a support board for a new module, so I'm moving it to the General Support area of the forum. The "Modules/Plugins" section of the forum is for dedicated module support threads. If you have a general question regarding ProcessWire, ProcessWire core modules, or "how to do [x] with ProcessWire", you should post it to the General Support area – or if it's a question regarding an existing module, check the "Support Board" link from the modules directory entry for that module and post your question to the linked thread instead. Thanks!
  7. Moderator note: this is not a support board for a new module, so I'm moving it to the General Support area of the forum. The "Modules/Plugins" section of the forum is for dedicated module support threads. If you have a general question regarding ProcessWire or "how to do [x] with ProcessWire", you should post it to the General Support area – or if it's a question regarding an existing module, check the "Support Board" link from the modules directory entry for that module and post your question to the linked thread instead. Thanks!
  8. Can you access any other pages? If not, there's very likely some sort of an issue with your .htaccess file, or rather an incompatibility with your server and the .htacecss file. The 404 error message you're seeing also sounds like the plain text version from server, not a 404 page from within ProcessWire – so most likely rewrite rules configured in the .htaccess file are not working as expected. Might also mean that something is missing from the server, though if you just ran the install process, that should've flagged any such issues. In a bit of a hurry, but at least the .htaccess file is where I'd start digging into this.
  9. Saturday morning I wrote in the the latest weekly issue this: And here's the view from my front door just now, Tuesday morning: I'm not particularly superstitious, but kinda feels like I dropped the ball on this one. To my defence, on Saturday there was literally zero snow here, and the whole day was sunny and warm and all. Proper shorts and T-shirt weather. I guess the lesson here is that it's always too early to say that the winter is over. Have a great day, folks!
  10. Moderator note: this thread is being moved to the "General Support" area. The Modules section of the forum is intended for module-specific support boards.
  11. Actually it seems that ProDrafts already supports Repeaters – this was announced in a blog post along with ProcessWire 3.0.75, and that detail just never made it into the description at the store. In case you have any questions regarding ProDrafts, I'd recommend sending a direct PM to @ryan VersionControl isn't really suitable for this purpose. Repeater support is one thing (though I seem to recall that the module might kinda-sorta work with Repeaters), but a bigger issue is that there's no draft feature. I could definitely hack it to do something like export a version and import it on another site (definitely something I'll keep in mind, sounds interesting!) but currently that's not doable. I haven't really used ProcessPagesExportImport, but I know that in case of Ryan the "beta" or "development" label doesn't necessarily mean that it isn't usable. I seem to recall that much of the data for the new processwire.com site was migrated using this feature (someone correct me if I'm wrong), and although I've heard some reports of missing features and such, as far as I know it should be pretty solid already. My first choice would definitely be one environment with the ProDrafts module. I'd only consider other options if that one doesn't pan out.
  12. If you don't create any variations on the front-end using size, width, etc. calls, ProcessWire won't create anything except for the variations created by default for admin (preview) purposes. Third party modules may still create their own variations, but if you're strictly against that behaviour, you can always avoid using any modules that do this What you're probably missing here is the amount of data: sure, browsers can handle resizing images, but if you're considering load times and amount of data users have to download to use your site, you absolutely want to resize images before they hit the visitors' browsers. When you're asking if this behaviour should be disabled to "reduce additional http requests (if the user resizes viewport)", it kind of sounds like you've implemented srcset on your site – otherwise there shouldn't be a additional requests when the viewport is resized due to images. Even then if you start with a larger viewport and then resize it to smaller size, browser shouldn't load the smaller sizes. Only case generating additional requests is when you go the other way, from small to large – otherwise tiny images would likely look pretty awful scaled to a larger size. Short answer is: no, it shouldn't be disabled. That being said, you don't have to create any additional variations if you don't want to – but be considerate of the user and don't make them download more data than they actually need
  13. Moderator note: I'm moving this thread to the "General Support" area of the forum. Modules/Plugins area is intended for dedicated module support threads only.
  14. Moderator note: I'm moving this thread to the "Module/Plugin Development" section. Modules/Plugins section is intended for support threads for existing modules only
  15. teppo

    Link field

    Hi, Unless I'm misunderstanding something here, what you want is actually a Page field. In your template files you can output the URL of the selected page: <?php if ($page->page_field_name): ?> <a href="<?php echo $page->page_field_name->url; ?>"><?php echo $page->page_field_name->title ?></a> <?php endif; ?> Does that sound about right?
×
×
  • Create New...